Hello, Some comments on this document, currently in Last Call. I don't see why the intended status for this document is Standards Track. Wouldn't Informational be enough? Could you please justify why have you chosen it?Network Working Group M. Westerlund Internet-Draft Ericsson Updates: 5245 (if approved) C. Perkins Intended status: Standards Track University of Glasgow Expires: September 29, 2011 March 28, 2011 Your registry description does not mention what is the precise name of the registry. While everybody understands that is sands for ICE options, it would be useful to give IANA distinctive guidelines on its name (this is also required in RFC5226, Section 4.2, 1) in the list; http://tools.ietf.org/html/rfc5226#section-4.2). From RFC 5226, also Section 4.2: 5) Initial assignments and reservations. Clear instructions should be provided to identify any initial assignments or registrations. In addition, any ranges that are to be reservedfor "Private Use", "Reserved", "Unassigned", etc. should be clearly indicated. Are there any initial assignments? Your document mentions one option; shouldn't it be registered? Shall this be mentioned as a registration template?A registration request MUST include the following information: [ . . . ] I think you should add the name of the contact person to the name of this field as well.o Email and Address of the Contact person I see, except some aforementioned issues, this document conforms to RFC 5226, particularly Section 4.2. Thanks in advance for considering my comments. Mykyta Yevstifeyev 28.04.2011 19:01, The IESG wrote: The IESG has received a request from the Multiparty Multimedia Session Control WG (mmusic) to consider the following document: - 'IANA Registry for Interactive Connectivity Establishment (ICE) Options' <draft-ietf-mmusic-ice-options-registry-01.txt> as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@xxxxxxxx mailing lists by 2011-05-12. Exceptionally, comments may be sent to iesg@xxxxxxxx instead. In either case, please retain the beginning of the Subject line to allow automated sorting. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-options-registry/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-mmusic-ice-options-registry/ No IPR declarations have been submitted directly on this I-D. _______________________________________________ IETF-Announce mailing list IETF-Announce@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf-announce |
_______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf