RFC 8664: Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC8664
- Published
- December 2019
- Authors
- S. Sivabalan; C. Filsfils; J. Tantsura; W. Henderickx; J. Hardwick
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 29
- Also known as
- —
- Updates:
- RFC 8408
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8660Segment Routing with the MPLS Data PlaneCurrent
December 2019
- RFC 8669Segment Routing Prefix Segment Identifier Extensions for BGPCurrent
December 2019
- RFC 8670BGP Prefix Segment in Large-Scale Data CentersCurrent
December 2019
- RFC 8637Applicability of the Path Computation Element (PCE) to the Abstraction and Control of TE Networks (ACTN)Current
July 2019
- RFC 8697Path Computation Element Communication Protocol (PCEP) Extensions for Establishing Relationships between Sets of Label Switched Paths (LSPs)Updated
January 2020
- RFC 8779Path Computation Element Communication Protocol (PCEP) Extensions for GMPLSUpdated
July 2020
- RFC 8814Signaling Maximum SID Depth (MSD) Using the Border Gateway Protocol - Link StateCurrent
August 2020
- RFC 8413Framework for Scheduled Use of ResourcesCurrent
July 2018
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?