metasystema.org
ObsoletedBEST CURRENT PRACTICEIETF stream

RFC 5226: 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 8126.

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

Many protocols make use of identifiers consisting of constants and other well-known values. Even after a protocol has been defined and deployment has begun, new values may need to be assigned (e.g., for a new option type in DHCP, or a new encryption or authentication transform for IPsec). To ensure that such quantities have consistent values and interpretations across all implementations, their assignment must be administered by a central authority. For IETF protocols, that role is provided by the Internet Assigned Numbers Authority (IANA). In order for IANA to manage a given namespace prudently, it needs guidelines describing the conditions under which new values can be assigned or when modifications to existing values can be made. If IANA is expected to play a role in the management of a namespace, IANA must be given clear and concise instructions describing that role. This document discusses issues that should be considered in formulating a policy for assigning values to a namespace and provides guidelines for authors on the specific text that must be included in documents that place demands on IANA. This document obsoletes RFC 2434. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

Document record

Document ID
RFC5226
Published
May 2008
Authors
T. Narten; H. Alvestrand
Status
BEST CURRENT PRACTICE
Stream
IETF
Area
—
Pages
27
Also known as
—
Obsoletes:
RFC 2434
Obsoleted by:
RFC 8126

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 2434 (1998)
  2. RFC 5226 (2008)
  3. RFC 8126 (2017) ✓

Read the full history of Guidelines for Writing an IANA Considerations Section in RFCs →

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.

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?

canonical URL: /rfc/5226-guidelines-for-writing-an-iana-considerations-section-in-rfcs