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

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Authors Quintin Zhao  , Zhenbin Li  , Dhruv Dhody  , Chao Zhou 
Last updated 2016-09-17 (latest revision 2016-03-16)
Replaced by draft-ietf-pce-pcep-extension-for-pce-controller
Stream (None)
Expired & archived
pdf htmlized (tools) htmlized 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


In certain networks deployment scenarios, service providers would like to keep all the existing MPLS functionalities in both MPLS and GMPLS while removing the complexity of existing signalling protocols such as LDP and RSVP-TE. In [I-D.zhao-pce-central-controller-user-cases], we propose to use the PCE [RFC5440] as a central controller (PCECC) so that LSP can be calculated/ signalled/initiated and label forwarding entries are downloaded through a centralized PCE server to each network devices along the LSP path while leveraging the existing PCE technologies as much as possible. This draft specify the procedures and PCEP protocol extensions for using the PCE as the central controller and user cases where LSPs are calculated/setup/initiated and label forwarding entries are downloaded through extending the existing PCE architectures and PCEP. This document also discuss the role of PCECC in Segment Routing (SR).


Quintin Zhao (quintin.zhao@huawei.com)
Zhenbin Li (lizhenbin@huawei.com)
Dhruv Dhody (dhruv.ietf@gmail.com)
Chao Zhou (choa.zhou@cisco.com)

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