The Use Cases for Using PCE as the Central Controller(PCECC) of LSPs

Document Type Replaced Internet-Draft (individual)
Authors Quintin Zhao  , Zhenbin Li  , Zekung Ke , Luyuan Fang  , Chao Zhou  , Telus Communications 
Last updated 2016-01-07 (latest revision 2015-07-06)
Replaced by draft-zhao-teas-pcecc-use-cases
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-zhao-teas-pcecc-use-cases
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 network while removing the complexity of existing signaling protocols such as LDP and RSVP-TE. In this document, we propose to use the PCE as a central controller so that LSP can be calculated/ signaled/initiated/downloaded/managed 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 describes the use cases for using the PCE as the central controller where LSPs are calculated/setup/initiated/downloaded/ maintained through extending the current PCE architectures and extending the PCEP.


Quintin Zhao (
Zhenbin Li (
Zekung Ke (
Luyuan Fang (
Chao Zhou (
Telus Communications (

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