This begins a 2-week Early Allocation WG LC for the following three BGP SR TE
drafts.
* draft-ietf-idr-sr-te-policy-attr-05.txt
* draft-ietf-idr-sr-policy-path-mtu-14.txt
* draft-ietf-idr-sr-policy-metric-04.txt
These drafts request allocation from SR Policy List Sub-TLVs for the specific
request listed below. If you have any concerns with the early allocation of
values from the registry, please respond to this message. If no concerns are
raised, the IDR chairs will request the early allocations below.
Please note that these are 3 of the 4 drafts mentioned at IETF-125 under the
topic of squatting. The 4th draft in this "squatting" discussion
(draft-ietf-idr-sr-policy-path-segment) is on hold due to technical issues.
These drafts do not have the Cross-WG section, but it crucial to allocate these
values in a formal fashion. If you have questions on the "squatting", please
query me. We'll rekindle the "squatting" thread from IETF-125. Let's leave
this mail thread clear for pros/cons of the allocations.
Cheerily, Sue
-------------------
draft-ietf-idr-sr-te-policy-attr-05 requests alphabetical identifier
allocations for new
"Segment Types" under the "Segment Routing" registry with reference to this
draft.
Value Description
L IPv4 Node Address and Local Interface ID with optional SR Algorithm for
SR-MPLS
M IPv4 Addresses for link endpoints as Local, Remote pair with optional SR
Algorithm for SR-MPLS
N IPv6 Node Addresses and Interface ID for link endpoints as Local, Remote
pair, with optional SR Algorithm for SR-MPLS
O IPv6 Addresses for link endpoints as Local, Remote pair, with optional SR
Algorithm for SR-MPLS
draft-ietf-idr-sr-te-policy-attr-05 from the "SR Policy Segment List Sub-TLVs"
registry [RFC9830] under the "Border Gateway Protocol (BGP) Tunnel
Encapsulation" registry group.
Value Description
TBD1 Segment Type L sub-TLV
TBD2 Segment Type M sub-TLV
TBD3 Segment Type N sub-TLV
TBD4 Segment Type O sub-TLV
-------------------------
draft-ietf-idr-sr-policy-path-mtu-14 requests one new Sub-TLV from the "SR
Policy Segment List Sub-TLVs" registry [RFC9830] under the "Border Gateway
Protocol (BGP) Tunnel Encapsulation" registry group.
Value Description
TBD1 Path MTU sub-TLV
===========
draft-ietf-idr-sr-policy-metric requests one new Sub-TLV from the "SR Policy
Segment List Sub-TLVs" registry [RFC9830] under the "Border Gateway Protocol
(BGP) Tunnel Encapsulation" registry group.
Value Description
TBD Metric
In addition, the draft-ietf-idr-sr-policy-metric requests a new registry.
However, this cannot be assigned at this time. If IANAbis WG work allows for
early allocation of registries, the IDR chairs will query these WGs on
allocation.
_______________________________________________
spring mailing list -- [email protected]
To unsubscribe send an email to [email protected]
