Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

RFC 8722

Defining the Role and Function of IETF Protocol Parameter Registry Operators,February 2020

File formats:

icon for HTMLicon for text fileicon for v3pdficon for XML
Also available:XML file for editing
 
Status:
INFORMATIONAL
Obsoletes:
RFC 6220
Authors:
D. McPherson, Ed.
O. Kolkman, Ed.
J. Klensin, Ed.
G. Huston, Ed.
Stream:
IAB

Cite this RFC:TXT  | XML  |  BibTeX

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

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

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


Abstract

Many Internet Engineering Task Force (IETF) protocols make use ofcommonly defined values that are passed in messages or packets. Toensure consistent interpretation of these values between independentimplementations, there is a need to ensure that the values andassociated semantic intent are uniquely defined. The IETF usesregistry functions to record assigned protocol parameter values andtheir associated semantic intentions. For each IETF protocolparameter, it is current practice for the IETF to delegate the roleof Protocol Parameter Registry Operator to a nominated entity. Thisdocument provides a description of, and the requirements for, thesedelegated functions. This document obsoletes RFC 6220 to replace allreferences to the IETF Administrative Support Activity (IASA) andrelated structures with those defined by the IASA 2.0 Model.


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2026 Movatter.jp