BCP 26

RFC 8126

Guidelines for Writing an IANA Considerations Section in RFCs, June 2017

Canonical URL:
https://www.rfc-editor.org/bcp/bcp26.txt
File formats:
Plain TextPDF
Status:
BEST CURRENT PRACTICE
Obsoletes:
RFC 5226
Authors:
M. Cotton
B. Leiba
T. Narten
Stream:
IETF
Source:
NON WORKING GROUP

Cite this BCP: TXT

Discuss this RFC: Send questions or comments to iesg@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA). To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry. This is the third edition of this document; it obsoletes RFC 5226.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Download PDF Reader



Search RFCs
Advanced Search
×