Hi Carles,

Thank you for the clarification; my apologies for the confusion.

Could the text be updated for clarity so that the full registry name is 
present? E.g., "...in the Dispatch Type Field registry in the IPv6 Low Power 
Personal Area Network Parameters registry group."

Thank you!

Best regards,

David Dong
IANA Services Sr. Specialist

On Fri Mar 13 15:20:47 2026, [email protected] wrote:
> Dear David,
> 
> Thanks for your message.
> 
> Please find below our inline responses:
> 
> On Fri, 13 Mar 2026 at 14:06, David Dong via RT <
> [email protected]> 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/draft-ietf-6lo-schc-15dot4/
> >
> > Is the “6LoWPAN Dispatch Type Field” registry a new registry to be
> > created
> > by this document? If so, could language be explicitly added stating
> > that
> > this document is creating this registry, identifying the registration
> > procedures and the initial registrations of the new registry?
> >
> >
> No, the “6LoWPAN Dispatch Type Field” registry is not a new registry.
> It
> already exists:
> https://www.iana.org/assignments/_6lowpan-parameters/_6lowpan-
> parameters.xhtml#_6lowpan-parameters-1
> 
> Would you have any suggestion to refer to it more clearly in the
> draft?
> 
> Thanks,
> 
> Carles (on behalf of the authors)
> 
> 
> > 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,
> >
> > David Dong
> > IANA Services Sr. Specialist
> >

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

Reply via email to