]> China Mobile

Beijing China liuyisong@chinamobile.com

New H3C Technologies

Beijing China linchangwang.04414@h3c.com

New H3C Technologies

Beijing China qiuyuanxiang@h3c.com

IDR Working Group This document defines the extension of BGP to distribute the threshold constraint parameters of candidate paths for SR Policy to achieve flexible path selection.

Introduction Segment Routing (SR) is a source routing paradigm that explicitly indicates the forwarding path for packets at the ingress node. The ingress node steers packets into a specific path according to the Segment Routing Policy (SR Policy) as defined in . An SR Policy may have multiple candidate paths that are provisioned or signaled from one or more sources. proposes a flexible SR policy candidate path selection method. Based on the real-time resource usage and forwarding quality of candidate paths, the head node can perform dynamic path switching among multiple candidate paths in the SR policy. Multiple threshold parameters for SR Policy candidate path selection are listed in Section 4.1 of . This document defines extensions to BGP to distribute threshold constraint parameters of candidate path (CP) for an SR Policy.

Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here. The definitions of the basic terms are identical to those found in Segment Routing Policy Architecture .

Carrying Threshold Constraint Parameters of CP in BGP As defined in , the SR Policy SAFI with codepoint 73 is used to advertise an SR Policy Candidate Path in the NLRI. According to , the content of the SR Policy Candidate Path is encoded in the Tunnel Encapsulation Attribute defined in using the Tunnel-Type called the "SR Policy" type with codepoint 15. The use of the SR Policy Tunnel Type is applicable only for the AFI/SAFI pairs of (1/73, 2/73), and the use of any other Tunnel Type with the SR Policy SAFI MUST be considered malformed and handled by the "treat-as-withdraw" strategy . This document defines the following Sub-TLV to carry the threshold constraint parameters for candidate paths.

• SR Metric Constraint Sub-TLV

The new SR Policy encoding structure with the Sub-TLV of CP threshold constraint parameters is expressed as below: Attributes: Tunnel Encaps Attribute (23) Tunnel Type: SR Policy (15) Binding SID SRv6 Binding SID Preference Priority SR Policy Name SR Policy Candidate Path Name Explicit NULL Label Policy (ENLP) SR Metric Constraint Sub-TLV Segment List Weight Segment Segment ... ... ]]>

SR Metric Constraint Sub-TLV The SR Metric Constraint sub-TLV is used to carry the threshold constraint of a candidate path. The SR Metric Constraint sub-TLV is optional. Multiple instances of this sub-TLV may be used to carry different metric types. The format of the SR Metric Constraint Sub-TLV is defined as follows: where:

• Type: to be assigned by IANA.
• Length: Specifies the length of the value field. The value MUST be 10.
• Flags: 1-octet field that indicates the semantics of the Metric Margin and Metric Bound. The following bit positions are defined and the other bits MUST be cleared by the originator and MUST be ignored by a receiver: where:
  • M-Flag: Indicates that the metric margin allowed is specified when set.
  • A-Flag: Indicates that the metric margin is specified as an absolute value when set and is expressed as a percentage of the metric when clear.
  • B-Flag: Indicates that the metric bound allowed for the path is specified when set.
  • F-Flag: Indicates that the Metric Margin and Metric Bound are floating-point numbers when set to 1. When set to 0, it indicates they are integer numbers.
• Metric Type: 1-octet field which identifies the type of the metric being used. The metric type code points are as follows:
  • 0: Available bandwidth threshold in bytes per second.
  • 1: Actual bandwidth threshold in bytes per second.
  • 2: Round trip delay threshold in microseconds.
  • 3: Round trip loss threshold. The unit is 0.000003%.
  • 4: Jitter threshold in microseconds.
• Metric Margin: 4-octet value which indicates the minimum threshold when the M-flag is set. The metric margin is specified as either an absolute value or as a percentage of the path metric based on the A-Flag.
• Metric Bound: 4-octet value which indicates the maximum threshold that is allowed when the B-flag is set. If the path metric crosses the specified bound value then the path is considered invalid.

Operations The document does not bring new operation beyond the description of operations defined in Section 4 of . The existing operations defined in can apply to this document directly. Typically, but not limited to, the SR policies carrying the threshold constraint parameters of CP are configured by a controller. After configuration, the SR policies carrying the threshold constraint parameters of CP will be advertised by BGP update messages. The operation of advertisement is the same as defined in , as well as the reception.

IANA Considerations This document defines a new sub-TLV in the registry "BGP Tunnel Encapsulation Attribute sub-TLVs" to be assigned by IANA: This document also requests that IANA create a new registry named "SR Metric Constraint Metric Types" for the Metric Type field of the SR Metric Constraint sub-TLV. The registration procedure for this registry is Specification Required . The initial values of this registry are as follows:

Security Considerations has discussed the security considerations for distributing SR Policy through BGP. This document does not introduce any new security issues.

References Normative References Informative References

Cross-WG Information This section describes cross&nbhy;working group information for use during the IETF review process. This section, including the reference to which is cited only within this appendix, will be removed by the RFC Editor prior to publication.

Spring WG This document builds directly on the work of the SPRING Working Group. The threshold constraint parameters for SR Policy candidate path selection defined in Section 4.1 of are carried by the BGP extensions specified here. The SPRING WG should be aware that this BGP extension is intended to be consistent with the flexible candidate path selection framework and that no changes to the semantics of the parameters are introduced. The definitions of the metric types and their usage remain as described in the SPRING document.

PCE WG The PCE Working Group has a companion document that defines PCEP extensions for carrying the same set of threshold constraint parameters. Both the BGP mechanism (this document) and the PCEP mechanism serve the same architectural goal: allowing a controller to communicate candidate path threshold constraints to a headend. Implementations or deployments that use both BGP and PCEP for SR Policy distribution should ensure semantic alignment between the two protocols. The PCE WG may wish to note that the format and flag definitions in this document have been aligned with those in the PCEP extension to ease interworking.

Acknowledgments TBD