RFC 9050: Path Computation Element Communication Protocol (PCEP) Procedures and Extensions for Using the PCE as a Central Controller (PCECC) of LSPs
In plain English — editorial summary, not part of the RFC
The Path Computation Element (PCE) is a core component of Software-Defined Networking (SDN) systems. A PCE as a Central Controller (PCECC) can simplify the processing of a distributed control plane by blending it with elements of SDN and without necessarily completely replacing it. Thus, the Label Switched Path (LSP) can be calculated/set up/initiated and the label-forwarding entries can also be downloaded through a centralized PCE server to each network device along the path while leveraging the existing PCE technologies as much as possible. This document specifies the procedures and Path Computation Element Communication Protocol (PCEP) extensions for using the PCE as the central controller for provisioning labels along the path of the static LSP.
Document record
- Document ID
- RFC9050
- Published
- July 2021
- Authors
- Z. Li; S. Peng; M. Negi; Q. Zhao; C. Zhou
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 33
- Also known as
- —
- Updated by:
- RFC 9756
Topics
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 9437Publish/Subscribe Functionality for the Locator/ID Separation Protocol (LISP)Current
August 2023
- RFC 9451Operations, Administration, and Maintenance (OAM) Packet and Behavior in the Network Service Header (NSH)Current
August 2023
- RFC 8453Framework for Abstraction and Control of TE Networks (ACTN)Current
August 2018
- RFC 8413Framework for Scheduled Use of ResourcesCurrent
July 2018
- RFC 9689Use Cases for a PCE as a Central Controller (PCECC)Current
December 2024
- RFC 9703Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data PlaneCurrent
December 2024
- RFC 9716Mechanisms for MPLS Ping and Traceroute Procedures in Inter-Domain Segment Routing NetworksCurrent
February 2025
- RFC 9731A YANG Data Model for Virtual Network (VN) OperationsCurrent
March 2025
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?