[Teas] [IANA #1238308] Last Call: <draft-ietf-lsr-isis-rfc5316bis-03.txt> (IS-IS Extensions in Support of Inter-Autonomous System (AS) MPLS and GMPLS Traffic Engineering) to Proposed Standard

[Sabrina Tanamal via RT <[e-mail]>]

(BEGIN IANA COMMENTS)

IESG/Authors/WG Chairs:

The IANA Functions Operator has completed its review of draft-ietf-lsr-isis-rfc5316bis-03. If any part of this review is inaccurate, please let us know. 

The IANA Functions Operator understands that, upon approval of this document, there are three actions which we must complete.

First, in the IS-IS Top-Level TLV Codepoints on the IS-IS TLV Codepoints registry page located at:

https://www.iana.org/assignments/isis-tlv-codepoints/

the reference for the existing registration for TLV codepoint 141 will be changed to:

Type Description IIH LSP SNP Purge Reference
---- ---------------------- --- --- --- ----- -------------
141 inter-AS reachability n y n n [ RFC-to-be ]
information

Second, in the IS-IS Sub-TLVs for TLVs Advertising Neighbor Information registry also on the IS-IS TLV Codepoints registry page located at:

https://www.iana.org/assignments/isis-tlv-codepoints/

Three existing registrations will have their references changed to [ RFC-to-be ] as follows:

Type Description 22 23 25 141 222 223 Reference
---- ----------------------------- --- --- --- --- --- --- -------------
24 remote AS number n n n y n n [ RFC-to-be ]
25 IPv4 remote ASBR identifier n n n y n n [ RFC-to-be ]
26 IPv6 remote ASBR identifier n n n y n n [ RFC-to-be ]

Also, in the same registry a new registration will be made as follows:

Type Description 22 23 25 141 222 223 Reference
----------------------- ----------------------------- --- --- --- --- --- --- -------------
[ TBD-at-Registration ] IPv6 local ASBR identifier n n n y n n [ RFC-to-be ]

As this document requests registrations in an Expert Review (see RFC 8126) registry, we will initiate the required Expert Review via a separate request. This review must be completed before the document's IANA state can be changed to "IANA OK."

Third, in the IS-IS Sub-TLVs for IS-IS Router CAPABILITY TLV registry also on the IS-IS TLV Codepoints registry page located at:

https://www.iana.org/assignments/isis-tlv-codepoints/

two existing registrations will have their references changed to [ RFC-to-be ] as follows:

Type Description Reference
---- ------------------------------ -------------
11 IPv4 TE Router ID [ RFC-to-be ]
12 IPv6 TE Router ID [ RFC-to-be ]

The IANA Functions Operator understands 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
Lead IANA Services Specialist

(END IANA COMMENTS)