RFC 8664

Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing, December 2019

File formats:

icon for HTML icon for text file icon for v3pdf icon for XML
Status:
PROPOSED STANDARD
Updates:
RFC 8408
Authors:
S. Sivabalan
C. Filsfils
J. Tantsura
W. Henderickx
J. Hardwick
Stream:
IETF
Source:
pce (rtg)

Cite this RFC: TXT  |  XML

DOI:  10.17487/RFC8664

Discuss this RFC: Send questions or comments to pce@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF


Abstract

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

This document updates RFC 8408.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Download PDF Reader