Dear lsr WG: draft-ietf-ospf-link-overload  defines a new BGP-LS Graceful-Link-Shutdown TLV. When an early allocation was requested, it was mistakenly requested from the "BGP-LS NLRI-Types" registry , not from the "BGP-LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs” registry . IANA allocated a value according to the request: 1101.
The mistake wasn't noticed until the document was in IESG Evaluation -- we are in the process of correcting it. However, the 1101 code point is already allocated [*] in the "BGP-LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs” registry, so a different value is needed - the current suggested value is 1121. Are there implementations of draft-ietf-ospf-link-overload with the 1101 code point? Are there deployments of those implementations? What will be the impact of changing the value to 1121? Thanks! Alvaro. [*] The 1101 code point in the "BGP-LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs” registry corresponds to the Peer-Node-SID, an early allocation made to draft-ietf-idr-bgpls-segment-routing-epe , which says that "several early implementations exist".  https://datatracker.ietf.org/doc/draft-ietf-ospf-link-overload/  https://www.iana.org/assignments/bgp-ls-parameters/bgp-ls-parameters.xhtml#nlri-types  https://www.iana.org/assignments/bgp-ls-parameters/bgp-ls-parameters.xhtml#node-descriptor-link-descriptor-prefix-descriptor-attribute-tlv  https://datatracker.ietf.org/doc/draft-ietf-idr-bgpls-segment-routing-epe/
_______________________________________________ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr