RFC 6220

Defining the Role and Function of IETF Protocol Parameter Registry Operators, April 2011

File formats:
icon for text file icon for PDF icon for HTML
Status:
INFORMATIONAL
Obsoleted by:
RFC 8722
Authors:
D. McPherson, Ed.
O. Kolkman, Ed.
J. Klensin, Ed.
G. Huston, Ed.
Internet Architecture Board
Stream:
IAB

Cite this RFC: TXT  |  XML  |   BibTeX

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

Discuss this RFC: Send questions or comments to the mailing list iab@iab.org

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


Abstract

Many Internet Engineering Task Force (IETF) protocols make use of commonly defined values that are passed in messages or packets. To ensure consistent interpretation of these values between independent implementations, there is a need to ensure that the values and associated semantic intent are uniquely defined. The IETF uses registry functions to record assigned protocol parameter values and their associated semantic intentions. For each IETF protocol parameter, it is current practice for the IETF to delegate the role of Protocol Parameter Registry Operator to a nominated entity. This document provides a description of, and the requirements for, these delegated functions. This document is not an Internet Standards Track specification; it is published for informational purposes.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search