%% You should probably cite draft-ietf-pce-segment-routing-policy-cp-22 instead of this revision.
@techreport{ietf-pce-segment-routing-policy-cp-11,
    number =    {draft-ietf-pce-segment-routing-policy-cp-11},
    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-segment-routing-policy-cp/11/},
    author =    {Mike Koldychev and Siva Sivabalan and Colby Barth and Shuping Peng and Hooman Bidgoli},
    title =     {{PCEP extension to support Segment Routing Policy Candidate Paths}},
    pagetotal = 22,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {A Segment Routing (SR) Policy {[}RFC9256{]} is a non-empty set of SR Candidate Paths, that share the same \textless{}headend, color, endpoint\textgreater{} tuple. This document extends {[}RFC8664{]} to fully support the SR Policy construct. SR Policy is modeled in PCEP as an Association of one or more SR Candidate Paths. PCEP extensions are defined to signal additional attributes of an SR Policy, which are not covered by {[}RFC8664{]}. The mechanism is applicable to all data planes of SR (MPLS, SRv6, etc.).},
}