RFC 6195: Domain Name System (DNS) IANA Considerations
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6895.
Current document in this lineage: RFC 6895 — Domain Name System (DNS) IANA Considerations
In plain English — editorial summary, not part of the RFC
This document specifies Internet Assigned Number Authority (IANA) parameter assignment considerations for the allocation of Domain Name System (DNS) resource record types, CLASSes, operation codes, error codes, DNS protocol message header bits, and AFSDB resource record subtypes. This memo documents an Internet Best Current Practice.
Document record
- Document ID
- RFC6195
- Published
- March 2011
- Authors
- D. Eastlake 3rd
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- int
- Pages
- 17
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 2929 (2000)
- RFC 5395 (2008)
- RFC 6195 (2011)
- RFC 6895 (2013) ✓
Read the full history of Domain Name System (DNS) IANA Considerations →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6221Lightweight DHCPv6 Relay AgentCurrent
May 2011
- RFC 6224Base Deployment for Multicast Listener Support in Proxy Mobile IPv6 (PMIPv6) DomainsCurrent
April 2011
- RFC 6164Using 127-Bit IPv6 Prefixes on Inter-Router LinksUpdated
April 2011
- RFC 6148DHCPv4 Lease Query by Relay Agent Remote IDCurrent
February 2011
- RFC 6245Generic Routing Encapsulation (GRE) Key Extension for Mobile IPv4Current
May 2011
- RFC 6253Host Identity Protocol CertificatesObsoleted
May 2011
- RFC 6261Encrypted Signaling Transport Modes for the Host Identity ProtocolCurrent
May 2011
- RFC 6269Issues with IP Address SharingCurrent
June 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?