%% You should probably cite rfc9050 instead of this I-D. @techreport{ietf-pce-pcep-extension-for-pce-controller-09, number = {draft-ietf-pce-pcep-extension-for-pce-controller-09}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-extension-for-pce-controller/09/}, author = {Zhenbin Li and Shuping Peng and Mahendra Singh Negi and Quintin Zhao and Chao Zhou}, title = {{PCEP Procedures and Protocol Extensions for Using PCE as a Central Controller (PCECC) of LSPs}}, pagetotal = 38, year = 2020, month = nov, day = 25, abstract = {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 MPLS and GMPLS 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/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 PCEP extensions for using the PCE as the central controller.}, }