Search RFCs

RFC Editor

File formats:

Status:

BEST CURRENT PRACTICE

Obsoletes:

RFC 5226

Authors:

M. Cotton
B. Leiba
T. Narten

Stream:

IETF

Source:

NON WORKING GROUP

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8126

Discuss this RFC: Send questions or comments to the mailing listiesg@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8126

Abstract

Many protocols make use of points of extensibility that use constantsto identify various protocol parameters. To ensure that the valuesin these fields do not have conflicting uses and to promoteinteroperability, their allocations are often coordinated by acentral record keeper. For IETF protocols, that role is filled bythe Internet Assigned Numbers Authority (IANA).

To make assignments in a given registry prudently, guidancedescribing 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 documentationof these guidelines by specification authors, in order to assure thatthe provided guidance for the IANA Considerations is clear andaddresses the various issues that are likely in the operation of aregistry.

This is the third edition of this document; it obsoletes RFC 5226.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.