Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

PROPOSED STANDARD

Updates:

RFC 8408

Updated by:

RFC 9756

Authors:

S. Sivabalan
C. Filsfils
J. Tantsura
W. Henderickx
J. Hardwick

Stream:

IETF

Source:

pce (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

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

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

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

Abstract

Segment Routing (SR) enables any head-end node to select any pathwithout relying on a hop-by-hop signaling technique (e.g., LDP orRSVP-TE). It depends only on "segments" that are advertised bylink-state Interior Gateway Protocols (IGPs). An SR path can bederived from a variety of mechanisms, including an IGP Shortest PathTree (SPT), an explicit configuration, or a Path Computation Element(PCE). This document specifies extensions to the Path ComputationElement Communication Protocol (PCEP) that allow a stateful PCE tocompute and initiate Traffic-Engineering (TE) paths, as well as aPath Computation Client (PCC) to request a path subject to certainconstraints and optimization criteria in SR networks.

This document updates RFC 8408.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.