| Internet-Draft | BGP-LS SR Policy | October 2025 |
| Liu, et al. | Expires 17 April 2026 | [Page] |
This document supplements additional information of the segment list in the BGP-LS advertisement for SR Policy state information. Two new flags and a new sub-TLV are introduced in the SR Segment List TLV of BGP-LS SR Policy Candidate Path NLRI.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 17 April 2026.¶
Copyright (c) 2025 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
SR Policy architecture details are specified in [RFC9256]. An SR Policy comprises one or more candidate paths (CP) of which at a given time one and only one may be active. Each CP in turn may have one or more SID-List of which one or more may be active; when multiple are active then traffic is load balanced over them.¶
[I-D.ietf-idr-bgp-ls-sr-policy] describes a mechanism to collect the SR policy information that is locally available in a node and advertise it into BGP Link State (BGP-LS) updates. Various TLVs are defined to enable the headend to report the state at the candidate path level and the segment list level.¶
Currently, a few segment-list-related information is not yet included in [I-D.ietf-idr-bgp-ls-sr-policy]:¶
Besides, [RFC8662] describes how Entropy labels (ELs) are to be applied to SR-MPLS to improve load-balancing. Multiple <ELI, EL> pairs may be inserted in the SR-MPLS label stack. A typical use case is that the ingress router (e.g., the headend node) computes a hash based on several fields from a given packet and places the result in the EL(s). The values and the positions of the ELs inserted in the SID-lists may be required by the controller when the headend reports the state of SR Policies via BGP-LS. However, carrying MPLS labels in BGP-LS that are not SR-MPLS SIDs are not yet supported.¶
This document supplements some additional information of the segment list state as mentioned above in the BGP-LS advertisement for SR Policy state information.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
SR Segment List TLV is defined in [I-D.ietf-idr-bgp-ls-sr-policy] to report the SID-List(s) of a candidate path. As show in Figure 1,this document introduces two new flags in the flag field of SR Segment List TLV, where,¶
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | | | | | | | |S|B| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The MPLS Label sub-TLV is defined in this section to carry the generic MPLS Label information. The MPLS Label Sub-TLV is an optional sub-TLV of SR Segment List TLV, and it may be used as the sub-TLV of other TLVs, for the latter case, the detailed usage is out of the scope of this document.¶
0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | MPLS Label | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: TBA¶
Length: The value is 4 octets.¶
MPLS Label: a 4-octet-field carrying the MPLS Label.¶
When receiving the BGP-LS advertisement for the SR Policy Candidate Path NLRI with SR Segment List TLV carrying the MPLS Label sub-TLV, it indicates that there's a MPLS Label inserted in the SID LIST. The MPLS Label sub-TLV can appear multiple times in the SR Segment List TLV. For example, if there're two adjacent MPLS Label sub-TLVs in the SR Segment List TLV, with the value of the MPLS Label in the first MPLS Label sub-TLV set as 7 (the reserved label value for ELI[RFC6790]), it indcates that a <ELI, EL> pair has been inserted in the SID list, and the second MPLS Label sub-TLV carries the corresponding EL value.¶
This document requests bit 9 and bit 10 in the flag field of "SR Segment List TLV" [I-D.ietf-idr-bgp-ls-sr-policy] under the "BGP-LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs" registry.¶
Bit Description Reference
------------------------------------------------------------------
9 Administrative Shut State Flag(S-Flag) This document
10 Backup Path State Flag(B-Flag) This document
¶
This document requests a new type sub-TLV of "SR Segment List TLV" [I-D.ietf-idr-bgp-ls-sr-policy] under the "BGP-LS Node Descriptor, Link Descriptor, Prefix Descriptor, and Attribute TLVs" registry.¶
Type Description Reference
------------------------------------------------------------------
TBA MPLS Label Sub-TLV This document
¶
Procedures and protocol extensions defined in this document do not affect the security considerations discussed in [I-D.ietf-idr-bgp-ls-sr-policy].¶