Dear Colleagues,
The IAB will be responding to the NTIA Notice of Inquiry on IANA during the IETF week. (see http://www.ntia.doc.gov/frnotices/2011/fr_ianafunctionsnoi_02252011.pdf) One of the references that will be made from that response is to "Defining the Role and Function of IETF Protocol Parameter Registry Operators" (draft-iab-iana-07). That document has been under development for quite a long time but having a stable reference to an RFC will make our response more convincing. About a year ago draft-iab-iana-05 got some significant feedback from community members. It has also been the subject of debate and review by the iana-strategy group, an IAB steered program. The current version has been condensed to express the IETFs requirements for the IANA protocol and parameter function and is significantly different from the 05 version. Normally the IAB posts the intention to publish a document two weeks before submission to the RFC editor so that there is a reasonable opportunity for feedback but, in this case, we want to make an exception and approve the document and submit it to the RFC editor on Tuesday for expedient publication as an Informational document on the IAB stream. This leaves only a few days for your feedback (until 10 pm Monday Prague time). I apologize for rushing this and ask for a pragmatic approach on the matter. Abstract Many 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 intent. 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. Please send substantive comments to [email protected]. Any NITS can be send directly to Danny McPherson (Danny Mc Pherson <[email protected]>) --Olaf Kolkman IAB Chair http://tools.ietf.org/html/draft-iab-iana-07 ----------------------------------- The Internet Architecture Board www.iab.org [email protected] _______________________________________________ IETF-Announce mailing list [email protected] https://www.ietf.org/mailman/listinfo/ietf-announce
