%% You should probably cite draft-ietf-pce-pcep-extension-pce-controller-sr instead of this I-D. @techreport{zhao-pce-pcep-extension-pce-controller-sr-01, number = {draft-zhao-pce-pcep-extension-pce-controller-sr-01}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-zhao-pce-pcep-extension-pce-controller-sr/01/}, author = {Quintin Zhao and Zhenbin Li and Dhruv Dhody and Satish Karunanithi and Adrian Farrel and Chao Zhou}, title = {{PCEP Procedures and Protocol Extensions for Using PCE as a Central Controller (PCECC) of SR-LSPs}}, pagetotal = 24, year = 2017, month = oct, day = 28, abstract = {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 signaling protocols such as LDP and RSVP-TE. PCE has been proposed to be used as a central controller (PCECC) so that LSP can be calculated/setup/ initiated and label forwarding entries are 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 the PCE functions as one of the central controller components in Segment Routing(SR).}, }