RFC 2929: 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 5395.
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 discusses the Internet Assigned Number Authority (IANA) parameter assignment considerations given for the allocation of Domain Name System (DNS) classes, Resource Record (RR) types, operation codes, error codes, etc. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC2929
- Published
- September 2000
- Authors
- D. Eastlake 3rd; E. Brunner-Williams; B. Manning
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- int
- Pages
- 12
- Also known as
- —
- Obsoleted by:
- RFC 5395
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 3110RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)Updated
May 2001
- RFC 3364Tradeoffs in Domain Name System (DNS) Support for Internet Protocol version 6 (IPv6)Current
August 2002
- RFC 4641DNSSEC Operational PracticesObsoleted
September 2006
- RFC 2672Non-Terminal DNS Name RedirectionObsoleted
August 1999
- RFC 2671Extension Mechanisms for DNS (EDNS0)Obsoleted
August 1999
- RFC 6891Extension Mechanisms for DNS (EDNS(0))Current
April 2013
- RFC 10029DNS Multiple QTYPEsCurrent
July 2026
- RFC 2541DNS Security Operational ConsiderationsObsoleted
March 1999
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?