%% You should probably cite rfc9689 instead of this I-D.
@techreport{ietf-teas-pcecc-use-cases-16,
    number =    {draft-ietf-teas-pcecc-use-cases-16},
    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-teas-pcecc-use-cases/16/},
    author =    {Zhenbin Li and Dhruv Dhody and Quintin Zhao and Zekung Ke and Boris Khasanov},
    title =     {{Use Cases for a PCE as a Central Controller (PCECC)}},
    pagetotal = 45,
    year =      2024,
    month =     may,
    day =       27,
    abstract =  {The PCE is a core component of a Software-Defined Networking (SDN) system. It can be used to compute optimal paths for network traffic and update existing paths to reflect changes in the network or traffic demands. PCE was developed to derive traffic-engineered paths in MPLS networks, which are supplied to the head end of the paths using the Path Computation Element Communication Protocol (PCEP). SDN has much broader applicability than signaled MPLS traffic- engineered (TE) networks, and the PCE may be used to determine paths in a range of use cases including static LSPs, Segment Routing (SR), Service Function Chaining (SFC), and most forms of a routed or switched network. It is, therefore, reasonable to consider PCEP as a control protocol for use in these environments to allow the PCE to be fully enabled as a central controller. A PCE as a Central Controller (PCECC) can simplify the processing of a distributed control plane by blending it with elements of SDN without necessarily completely replacing it. This document describes general considerations for PCECC deployment and examines its applicability and benefits, as well as its challenges and limitations, through a number of use cases. PCEP extensions which are required for the PCECC use cases are covered in separate documents.},
}