RFC 6220: Defining the Role and Function of IETF Protocol Parameter Registry Operators
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8722.
Current version: RFC 8722 — Defining the Role and Function of IETF Protocol Parameter Registry Operators
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC6220
- Published
- April 2011
- Authors
- D. McPherson; O. Kolkman; J. Klensin; G. Huston; Internet Architecture Board
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 11
- Also known as
- —
- Obsoleted by:
- RFC 8722
Referenced by
One later RFC formally updates or obsoletes part of this document.
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?