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 obsoletes RFC 6220 to replace all references to the IETF Administrative Support Activity (IASA) and related structures with those defined by the IASA 2.0 Model.
Document record
- Document ID
- RFC8722
- Published
- February 2020
- Authors
- D. McPherson; O. Kolkman; J. Klensin; G. Huston
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 11
- Also known as
- —
- Obsoletes:
- RFC 6220
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9120Nameservers for the Address and Routing Parameter Area ("arpa") DomainCurrent
October 2021
- RFC 2860Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers AuthorityCurrent
June 2000
- RFC 8726How Requests for IANA Action Will Be Handled on the Independent StreamCurrent
November 2020
- RFC 8688A Session Initiation Protocol (SIP) Response Code for Rejected CallsCurrent
December 2019
- RFC 9029Updates to the Allocation Policy for the Border Gateway Protocol - Link State (BGP-LS) Parameters RegistriesObsoleted
June 2021
- RFC 8356Experimental Codepoint Allocation for the Path Computation Element Communication Protocol (PCEP)Current
March 2018
- RFC 9184BGP Extended Community Registries UpdateCurrent
January 2022
- RFC 9281Entities Involved in the IETF Standards ProcessCurrent
June 2022
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?