Carrying Binding Label/SID in PCE-Based Networks
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 19
- Abstract
- 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.
- Publication Date
- 2024-08-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC9604- Link
- https://doi.org/10.17487/RFC9604
- Author(s)
- Siva SivabalanClarence FilsfilsJeff TantsuraStefano PrevidiCheng Li
Latest version of IETF RFC 9604
Document Versions — IETF RFC 9604
-
▶ IETF RFC 9604 (2024-08-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 3032 [Active*]
- IETF RFC 5440 [Active*]
- IETF RFC 5462 [Active*]
- IETF RFC 8126 [Active*]
- IETF RFC 8174 [Active*]
- IETF RFC 8231 [Active*]
- IETF RFC 8253 [Active*]
- IETF RFC 8281 [Active*]
- IETF RFC 8402 [Active*]
- IETF RFC 8664 [Active*]
- IETF RFC 8986 [Active*]
- IETF RFC 8996 [Active*]
- IETF RFC 9050 [Active*]
- IETF RFC 9603 [Active*]
Bibliographic Reference(s)
- IETF.draft-ietf-pce-controlled-id-space-00 — I-D.ietf-pce-controlled-id-space EXTERNAL
- IETF.draft-ietf-pce-pcep-yang-25 — I-D.ietf-pce-pcep-yang EXTERNAL
- IETF.draft-ietf-pce-sr-path-segment-09 — I-D.ietf-pce-sr-path-segment EXTERNAL
- IETF RFC 4655 [Active*]
- IETF RFC 8283 [Active*]
- IETF RFC 8754 [Active*]
- IETF RFC 9256 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC9604.json
Amended by:
IETF RFC 9756 [Active*]
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 9604, Carrying Binding Label/SID in PCE-Based Networks. Available at https://doi.org/10.17487/RFC9604
Snippet:
IETF RFC 9604, Carrying Binding Label/SID in PCE-Based Networks. Available at https://doi.org/10.17487/RFC9604
HTML (ISO 690 compliant)
Preview:
IETF RFC 9604, Carrying Binding Label/SID in PCE-Based Networks. Available at https://doi.org/10.17487/RFC9604
Snippet:
<span class="citation"><cite>IETF RFC 9604</cite>, Carrying Binding Label/SID in PCE-Based Networks. Available at <a href="https://doi.org/10.17487/RFC9604" target="_blank" rel="noopener">https://doi.org/10.17487/RFC9604</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 9604, Carrying Binding Label/SID in PCE-Based Networks
doi: 10.17487/RFC9604
url: https://doi.org/10.17487/RFC9604
doi: 10.17487/RFC9604
url: https://doi.org/10.17487/RFC9604
Snippet:
<li> <cite id="bib-rfc9604">IETF RFC 9604</cite>, Carrying Binding Label/SID in PCE-Based Networks <span class="doi">10.17487/RFC9604</span> </li>
Referenced By
- IETF RFC 9756 [Active*]