Search RFCs

RFC Editor

File formats:

Status:

BEST CURRENT PRACTICE

Obsoletes:

RFC 2434

Obsoleted by:

RFC 8126

Authors:

T. Narten
H. Alvestrand

Stream:

IETF

Source:

NON WORKING GROUP

Cite this RFC:TXT  | XML  |  BibTeX

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

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 5226

Abstract

Many protocols make use of identifiers consisting of constants andother well-known values. Even after a protocol has been defined anddeployment has begun, new values may need to be assigned (e.g., for anew option type in DHCP, or anew encryption or authentication transform for IPsec). To ensure thatsuch quantities have consistent values and interpretations across allimplementations, their assignment must be administered by a centralauthority. For IETF protocols, that role is provided by the InternetAssigned Numbers Authority (IANA).

In order for IANA to manage a given namespace prudently, it needsguidelines describing the conditions under which new values can beassigned or when modifications to existing values can be made. IfIANA is expected to play a role in the management of a namespace,IANA must be given clear and concise instructions describing thatrole. This document discusses issues that should be considered informulating a policy for assigning values to a namespace andprovides guidelines for authors on the specific text thatmust 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.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.