IANA,

Please update as follows per the author's reply (and the edited document: 
https://www.rfc-editor.org/authors/rfc9926.txt).

1) On 
https://www.iana.org/assignments/icmpv6-parameters/icmpv6-parameters.xhtml#p-field-values
please add 'Unicast'.

Old:  3   Registration for a Prefix
New:  3   Registration for a Unicast Prefix


2) On 
https://www.iana.org/assignments/icmpv6-parameters/icmpv6-parameters.xhtml#sixlowpan-capability-bits
 please lowercase 's'.

Old: 16  Registration for prefixes Supported (F bit)
New: 16  Registration for prefixes supported (F bit)

Thank you.

Alice Russo
RFC Production Center


>> <!--[rfced] Why is "Supported" capitalized here? If this may be 
>> changed, then we will ask IANA to update the registry 
>> (https://www.iana.org/assignments/icmpv6-parameters/icmpv6-parameters.xhtml#sixlowpan-capability-bits)
>>  based on your reply.
>> 
>> Original:
>>    The new "Registration for prefixes Supported" (F) flag indicates ...
>> 
>> Perhaps:
>>    The new "Registration for prefixes supported (F bit)" indicates ...
>> 
>> Or (if you prefer title case, which is similar to X flag in that registry):
>>    The new "Registration for Prefixes Supported (F bit)" indicates ...
>> -->
> 
> We do not seem to be consistent either way in  IANA "6LoWPAN Capability Bits" 
> but lowercasing seems to be the norm. Please use the perhaps and update the 
> IANA section.
> 
[...]

>> <!--[rfced] In Table 1, this meaning has been updated to exactly match
>> the IANA registry. Please let us know if that is not your intention.
>> (See 
>> https://www.iana.org/assignments/icmpv6-parameters/icmpv6-parameters.xhtml#p-field-values)
>> 
>> Original: 3   | Registration for a Unicast prefix
>> Current:  3   | Registration for a Prefix
>> 
>> Due to this, please review whether any other updates updates 
>> are needed. For example, in Section 1, should "unicast" be removed here?
>> 
>> Original:
>>    This specification updates the above registration and subscription
>>    methods to enable a node to register a unicast prefix to the routing
>>    system and get it injected in the routing protocol. 
>> -->
> -> Unicast should be everywhere. We do not support registration for multicast 
> prefixes. Please update the IANA section too.


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

Reply via email to