Defining the Role and Function of IETF Protocol Parameter Registry Operators
RFC 8722

Received changes through RFC Editor sync (changed abstract to '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.', changed pages to 11, changed standardization level to Informational, changed state to RFC, changed IAB state to Published RFC)

Received changes through RFC Editor sync (created alias RFC 8722, changed abstract to '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.', changed pages to 11, changed standardization level to Informational, changed state to RFC, added RFC published event at 2020-02-27, changed IAB state to Published RFC, created obsoletes relation between draft-ietf-iasa2-rfc6220bis and RFC 6220)