Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

PROPOSED STANDARD

Updated by:

RFC 9756

Authors:

S. Sivabalan
C. Filsfils
J. Tantsura
S. Previdi
C. Li, Ed.

Stream:

IETF

Source:

pce (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC9604

Discuss this RFC: Send questions or comments to the mailing listpce@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 9604

Abstract

In order to provide greater scalability, network confidentiality, andservice independence, Segment Routing (SR) utilizes a Binding SegmentIdentifier (BSID), as described in RFC 8402. It is possible toassociate a BSID to an RSVP-TE-signaled Traffic Engineering (TE)Label Switched Path (LSP) or an SR TE path. The BSID can be used byan upstream node for steering traffic into the appropriate TE path toenforce SR policies. This document specifies the concept of bindingvalue, which can be either an MPLS label or a Segment Identifier(SID). It further specifies an extension to Path Computation ElementCommunication Protocol (PCEP) for reporting the binding value by aPath Computation Client (PCC) to the Path Computation Element (PCE)to support PCE-based TE policies.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.