PCEP Procedures and Protocol Extensions for Using PCE as a Central Controller (PCECC) of SR-LSPs

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2018-12-20 (latest revision 2018-06-18)
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


The Path Computation Element (PCE) is a core component of Software- Defined Networking (SDN) systems. It can compute optimal paths for traffic across a network and can also update the paths to reflect changes in the network or traffic demands. PCE was developed to derive paths for MPLS Label Switched Paths (LSPs), which are supplied to the head end of the LSP using the Path Computation Element Communication Protocol (PCEP). But SDN has a broader applicability than signaled (G)MPLS traffic-engineered (TE) networks, and the PCE may be used to determine paths in a range of use cases. PCEP has been proposed as a control protocol for use in these environments to allow the PCE to be fully enabled as a central controller. A PCE-based 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 LSP can be calculated/setup/initiated and the label forwarding entries can also be downloaded through a centralized PCE server to each network devices along the path while leveraging the existing PCE technologies as much as possible. This document specifies the procedures and PCEP protocol extensions when a PCE-based controller is also responsible for configuring the forwarding actions on the routers, in addition to computing the paths for packet flows in a segment routing network and telling the edge routers what instructions to attach to packets as they enter the network.


Quintin Zhao (quintin.zhao@huawei.com)
Zhenbin Li (lizhenbin@huawei.com)
Dhruv Dhody (dhruv.ietf@gmail.com)
Satish Karunanithi (satishk@huawei.com)
Adrian Farrel (adrian@olddog.co.uk)
Chao Zhou (choa.zhou@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)