RFC 2434: Guidelines for Writing an IANA Considerations Section in RFCs
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5226.
Current document in this lineage: RFC 8126 — Guidelines for Writing an IANA Considerations Section in RFCs
In plain English — editorial summary, not part of the RFC
This document discusses issues that should be considered in formulating a policy for assigning values to a name space and provides guidelines to document authors on the specific text that must be included in documents that place demands on the IANA. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC2434
- Published
- October 1998
- Authors
- T. Narten; H. Alvestrand
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- —
- Pages
- 11
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2434 (1998)
- RFC 5226 (2008)
- RFC 8126 (2017) ✓
Read the full history of Guidelines for Writing an IANA Considerations Section in RFCs →
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2754RPS IANA IssuesObsoleted
January 2000
- RFC 2036Observations on the use of Components of the Class A Address Space within the InternetCurrent
October 1996
- RFC 2939Procedures and IANA Guidelines for Definition of New DHCP Options and Message TypesCurrent
September 2000
- RFC 1917An Appeal to the Internet Community to Return Unused IP Networks (Prefixes) to the IANACurrent
February 1996
- RFC 1881IPv6 Address Allocation ManagementCurrent
December 1995
- RFC 3171IANA Guidelines for IPv4 Multicast Address AssignmentsObsoleted
August 2001
- RFC 3679Unused Dynamic Host Configuration Protocol (DHCP) Option CodesUpdated
January 2004
- RFC 5237IANA Allocation Guidelines for the Protocol FieldCurrent
February 2008
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?