[spring] draft-ietf-spring-dhc-distribute-srv6-locator-dhcp-11

[[e-mail]]

Dear authors, WG.

Very late and minor comment,

|  149  | OPTION_IA_SRV6_LOCATOR
|  150  | OPTION_IALOCATOR

any reason for not being consistent with the naming? i.e., using OPTION_IA_LOCATOR

Thanks,
Regards,
--Bruno
-----Original Message-----
From: Sabrina Tanamal via RT <[e-mail]>
Sent: Monday, November 24, 2025 8:22 PM
Cc: [e-mail]; [e-mail]
Subject: [IANA #1436399] Last Call: <draft-ietf-spring-dhc-distribute-srv6-locator-dhcp-11.txt> (Distribute SRv6 Locator by DHCP) to Proposed Standard


IESG/Authors/WG Chairs:

IANA has completed its review of draft-ietf-spring-dhc-distribute-srv6-locator-dhcp-11. If any part of this review is inaccurate, please let us know.

IANA understands that, upon approval of this document, there are two actions which we must complete.

First, in the Option Codes registry in the Dynamic Host Configuration Protocol for IPv6 (DHCPv6) registry group located at:

https://www.iana.org/assignments/dhcpv6-parameters/

the temporary registrations for the following option codes will be made permanent and their references changed to [ RFC-to-be ]:

+=======+========================+========+===========+===============+
| Value | Description | Client | Singleton | Reference |
| | | ORO | Option | |
+=======+========================+========+===========+===============+
| 149 | OPTION_IA_SRV6_LOCATOR | NO | No | [ RFC-to-be ] |
+-------+------------------------+--------+-----------+---------------+
| 150 | OPTION_IALOCATOR | NO | No | [ RFC-to-be ] |
+-------+------------------------+--------+-----------+---------------+

Second, in the Status Codes registry in the Dynamic Host Configuration Protocol for IPv6 (DHCPv6) registry group located at:

https://www.iana.org/assignments/dhcpv6-parameters/

a new code will be registered as follows:

Code: [ TBD-at-Registration ]
Name: NoSRv6LocatorAvail
Status:
Reference: [ RFC-to-be ]

We understand that these are the only actions required to be completed upon approval of this document.

NOTE: The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is meant only to confirm the list of actions that will be performed.

For definitions of IANA review states, please see:

https://datatracker.ietf.org/help/state/draft/iana-review

Thank you,

Sabrina Tanamal
IANA
____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.