RFC 9604: Carrying Binding Label/SID in PCE-Based Networks
In plain English — editorial summary, not part of the RFC
In order to provide greater scalability, network confidentiality, and service independence, Segment Routing (SR) utilizes a Binding Segment Identifier (BSID), as described in RFC 8402. It is possible to associate a BSID to an RSVP-TE-signaled Traffic Engineering (TE) Label Switched Path (LSP) or an SR TE path. The BSID can be used by an upstream node for steering traffic into the appropriate TE path to enforce SR policies. This document specifies the concept of binding value, which can be either an MPLS label or a Segment Identifier (SID). It further specifies an extension to Path Computation Element Communication Protocol (PCEP) for reporting the binding value by a Path Computation Client (PCC) to the Path Computation Element (PCE) to support PCE-based TE policies.
Document record
- Document ID
- RFC9604
- Published
- August 2024
- Authors
- S. Sivabalan; C. Filsfils; J. Tantsura; S. Previdi; C. Li
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 19
- Also known as
- —
- Updated by:
- RFC 9756
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9603Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment RoutingUpdated
July 2024
- RFC 9600TRansparent Interconnection of Lots of Links (TRILL): Explicit Congestion Notification (ECN) SupportCurrent
August 2024
- RFC 9612Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs)Current
July 2024
- RFC 9613Requirements for Solutions that Support MPLS Network Actions (MNAs)Current
August 2024
- RFC 9616Delay-Based Metric Extension for the Babel Routing ProtocolCurrent
September 2024
- RFC 9587YANG Data Model for OSPFv3 Extended Link State Advertisements (LSAs)Current
June 2024
- RFC 9624EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Using Bit Index Explicit Replication (BIER)Current
August 2024
- RFC 9625EVPN Optimized Inter-Subnet Multicast (OISM) ForwardingCurrent
August 2024
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?