Thanks Amanda, i processed your feedback to be included in -06.
Paolo On 12/3/26 13:04, Amanda Baber via RT wrote:
Dear Authors, Before the IETF meeting, we check working group agendas for documents with IANA-related issues. We have notes about this document: https://datatracker.ietf.org/doc/html/draft-ietf-grow-bmp-rel-05 General notes: Is it intentional that only the first registry includes “BMP” in the name? We generally recommend including the protocol name, if appropriate. Also, my understanding is that the IESG will push back on the use of RFC 2119 terminology in the IANA Considerations section. There's no need to include it in instructions to IANA. The section can say "the procedure is X" rather than "the procedure MUST be X." In some cases, it's not clear whether you'd want a field to be named "Name" or "Description." Section 7.1: It’s not clear whether this section is providing the exact text that should appear in the registry or descriptions of text that should appear in the registry. For example, is the preferred description for value 5 "Indicates IANA-registered reason code for event," "IANA-registered reason code for event," or "event"? A table would be useful here. Section 7.2: There’s a mix of hex and decimal in this section. Is that intentional? Is the maximum assignable value 255? If so, there seems to be too much padding here. If this is a registry of reasons, is it necessary to include the word “reason” in the name/description field? (It may be; just checking on this.) What are the names of the fields? Section 7.6: There’s a mix of hex and decimal in this section. Is that intentional? If you have any questions, just let us know. If you'd like to talk in person, you can find us next to the RFC Editor's table from Monday through Thursday. You can also request another review at any time by contacting us at [email protected]. For more information about IANA Considerations section requirements, please see https://www.iana.org/help/protocol-registration Best regards, Amanda Baber IANA _______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
_______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
