Dear Authors (cc: anima),

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-anima-brski-discovery-09

Section 5.1.1: “sub-registry” (two instances) and “registry” should be replaced 
with “registry” and “registry group”.

Section 5.2: We need an assignee and contact as well. You could just add a 
sentence here that says, “For all of the service names listed above, the 
contact is the IETF Chair, and the assignee is the IESG.” (The assignee is 
usually the IETF, but RFC 6335 specifies the IESG instead.)

Section 5.3: Please make the following replacement:

OLD: IANA is asked to add the following entry to the "GeneRic Autonomic 
Signaling Protocol (GRASP) Parameters Registry" page, "GRASP Objective Names 
Registry".

NEW: IANA is asked to add the following entry to the "GRASP Objective Names" 
registry in the "GeneRic Autonomic Signaling Protocol (GRASP) Parameters” 
registry group.

Section 5.4: Can you confirm that this registration procedure table would be 
correct?

New | Specification Required
Modification | Specification Required (same level as initial specification or 
higher)

Does this apply to any of the subregistries, or just to the BRSKI Discovery 
Parameters registry?

Section 5.4: Just a suggestion about the subsections: it can be useful to start 
a registry name with the name of the protocol, or some other string that could 
set it apart from similarly-named registries in a search. 

If you have any questions, just let us know. If you'd like to talk in person, 
you can find us at the IANA 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

_______________________________________________
Anima mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to