%% You should probably cite draft-ietf-pce-pcep-extension-pce-controller-srv6 instead of this I-D. @techreport{dhody-pce-pcep-extension-pce-controller-srv6-03, number = {draft-dhody-pce-pcep-extension-pce-controller-srv6-03}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-dhody-pce-pcep-extension-pce-controller-srv6/03/}, author = {Mahendra Singh Negi and Zhenbin Li and Xuesong Geng and Shuping Peng}, title = {{PCEP Procedures and Protocol Extensions for Using PCE as a Central Controller (PCECC) for SRv6}}, pagetotal = 17, year = 2020, month = mar, day = 9, 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 (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. 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 for Segment Routing in IPv6 (SRv6), in addition to computing the SRv6 paths for packet flows and telling the edge routers what instructions to attach to packets as they enter the network.}, }