%% You should probably cite draft-ietf-pce-circuit-style-pcep-extensions-12 instead of this revision.
@techreport{ietf-pce-circuit-style-pcep-extensions-11,
    number =    {draft-ietf-pce-circuit-style-pcep-extensions-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-circuit-style-pcep-extensions/11/},
    author =    {Samuel Sidor and Praveen Maheshwari and Andrew Stone and Luay Jalil and Shuping Peng},
    title =     {{Path Computation Element Communication Protocol (PCEP) extensions for Circuit Style Policies}},
    pagetotal = 17,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {Segment Routing (SR) enables a node to steer packet flows along a specified path without the need for intermediate per-path states, due to the utilization of source routing. An SR Policy can consist of one or a set of candidate paths, where each candidate path is represented by a segment list or a set of segment lists, which are essentially instructions that define a source-routed policy. This document specifies a set of extensions to the Path Computation Element Communication Protocol (PCEP) for Segment Routing Policies that are designed to satisfy requirements for connection-oriented transport services (Circuit-Style SR policies). They include the ability to control path recomputation and the option to request path with strict hops only, being also applicable for generic SR policy use cases where controlling path recomputation or deterministic and persistent path requirements are applicable.},
}