%% 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-10,
    number =    {draft-dhody-pce-pcep-extension-pce-controller-srv6-10},
    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/10/},
    author =    {Zhenbin Li and Shuping Peng and Xuesong Geng and Mahendra Singh Negi},
    title =     {{PCE Communication Protocol (PCEP) Extensions for Using the PCE as a Central Controller (PCECC) for Segment Routing over IPv6 (SRv6) Segment Identifier (SID) Allocation and Distribution.}},
    pagetotal = 19,
    year =      2023,
    month =     jan,
    day =       15,
    abstract =  {The PCE is a core component of Software-Defined Networking (SDN) systems. 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 Path Computation Element Communication Protocol (PCEP) extensions when a PCE-based controller is also responsible for configuring the forwarding actions on the routers, in addition to computing the paths for packet flows in the for Segment Routing (SR) in IPv6 (SRv6) network and telling the edge routers what instructions to attach to packets as they enter the network. PCECC is further enhanced for SRv6 SID (Segment Identifier) allocation and distribution.},
}