Browse Prior Art Database

Defining the Role and Function of IETF Protocol Parameter Registry Operators (RFC6220)

IP.com Disclosure Number: IPCOM000206159D
Original Publication Date: 2011-Apr-01
Included in the Prior Art Database: 2019-Feb-11
Document File: 11 page(s) / 19K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. McPherson: AUTHOR [+4]

Related Documents

10.17487/RFC6220: DOI

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.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 15% of the total text.

Internet Architecture Board (IAB) D. McPherson, Ed. Request for Comments: 6220 O. Kolkman, Ed. Category: Informational J. Klensin, Ed. ISSN: 2070-1721 G. Huston, Ed. April 2011

Defining the Role and Function of IETF Protocol Parameter Registry Operators

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.

Status of This Memo

This document is not an Internet Standards Track specification; it is published for informational purposes.

This document is a product of the Internet Architecture Board (IAB) and represents information that the IAB has deemed valuable to provide for permanent record. Documents approved for publication by the IAB are not a candidate for any level of Internet Standard; see Section 2 of RFC 5741.

Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6220.

McPherson, et al. Informational [Page 1]

RFC 6220 Role of Registry Operators April 2011

Copyright Notice

Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved.

This document is subject to BCP 78 and the IETF Trust’s Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document.

Table of Contents

1. Overview ........................................................2 2. Roles and Responsibilities Concerning IETF Protocol Parameter Registries ...................................3 2.1. Protocol Parameter Registry Operator Role ..................4 2.2. IAB Role ...................................................7 2.3. IESG Role ..................................................7 2.4. Role of the IETF Trust .....................................8 2.5. Role of the IAOC ...........................................8 3. Miscellaneous Considerations ....................................8 4. Security Considerations .........................................9 5. IANA Considerations .............................................9 6. Informative References ..........................................9 7. Acknowledgements ...............................................10 8. IAB Members .......................................................

Processing...
Loading...