%% You should probably cite draft-ietf-idr-sr-policy-path-segment-09 instead of this revision.
@techreport{ietf-idr-sr-policy-path-segment-06,
    number =    {draft-ietf-idr-sr-policy-path-segment-06},
    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-idr-sr-policy-path-segment/06/},
    author =    {Cheng Li and Zhenbin Li and Yuanyang Yin and Weiqiang Cheng and Ketan Talaulikar},
    title =     {{SR Policy Extensions for Path Segment and Bidirectional Path}},
    pagetotal = 12,
    year =      2022,
    month =     aug,
    day =       8,
    abstract =  {A Segment Routing (SR) policy is a set of candidate SR paths consisting of one or more segment lists with necessary path attributes. For each SR path, it may also have its own path attributes, and Path Segment is one of them. A Path Segment is defined to identify an SR path, which can be used for performance measurement, path correlation, and end-2-end path protection. Path Segment can be also used to correlate two unidirectional SR paths into a bidirectional SR path which is required in some scenarios, for example, mobile backhaul transport network. This document defines extensions to BGP to distribute SR policies carrying Path Segment and bidirectional path information.},
}