API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 5226
[SUPERSEDED]

Guidelines for Writing an IANA Considerations Section in RFCs

Metadata

Publisher
IETF
Doc Type
Best Practice
Pages
27
Abstract
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.
Publication Date
2008-05-01
Status Note
Best Current Practice
DOI
10.17487/RFC5226
Link
https://doi.org/10.17487/RFC5226
Author(s)
Dr. Thomas Narten
Harald T. Alvestrand
Keyword(s)
IANA, Code Point
Latest version of IETF RFC 5226

Document Versions — IETF RFC 5226

  • ▶ IETF RFC 5226 (2008-05-01)
    THIS DOC [SUPERSEDED] [LATEST VERSION]

Superseded by:

Normative Reference(s)

Bibliographic Reference(s)

Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC5226.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 5226, Guidelines for Writing an IANA Considerations Section in RFCs. Available at https://doi.org/10.17487/RFC5226
Snippet:
IETF RFC 5226, Guidelines for Writing an IANA Considerations Section in RFCs. Available at https://doi.org/10.17487/RFC5226

HTML (ISO 690 compliant)

Preview:
IETF RFC 5226, Guidelines for Writing an IANA Considerations Section in RFCs. Available at https://doi.org/10.17487/RFC5226
Snippet:
<span class="citation"><cite>IETF RFC 5226</cite>, Guidelines for Writing an IANA Considerations Section in RFCs. Available at <a href="https://doi.org/10.17487/RFC5226" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5226</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 5226, Guidelines for Writing an IANA Considerations Section in RFCs
doi: 10.17487/RFC5226
url: https://doi.org/10.17487/RFC5226
Snippet:
<li>
<cite id="bib-rfc5226">IETF RFC 5226</cite>, Guidelines for Writing an IANA Considerations Section in RFCs
<span class="doi">10.17487/RFC5226</span>
</li>

Referenced By