RFC 5395: 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 6195.
Current document in this lineage: RFC 6895 — Domain Name System (DNS) IANA Considerations
In plain English — editorial summary, not part of the RFC
Internet Assigned Number Authority (IANA) parameter assignment considerations are specified 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 document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC5395
- Published
- November 2008
- 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 6895Domain Name System (DNS) IANA ConsiderationsCurrent
April 2013
- RFC 5380Hierarchical Mobile IPv6 (HMIPv6) Mobility ManagementCurrent
October 2008
- RFC 5419Why the Authentication Data Suboption is Needed for Mobile IPv6 (MIPv6)Current
January 2009
- RFC 5452Measures for Making DNS More Resilient against Forged AnswersCurrent
January 2009
- RFC 5338Using the Host Identity Protocol with Legacy ApplicationsCurrent
September 2008
- RFC 5453Reserved IPv6 Interface IdentifiersCurrent
February 2009
- RFC 5454Dual-Stack Mobile IPv4Current
March 2009
- RFC 5460DHCPv6 Bulk LeasequeryUpdated
February 2009
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?