%% You should probably cite draft-ietf-pce-segment-routing-ipv6-25 instead of this revision.
@techreport{ietf-pce-segment-routing-ipv6-16,
    number =    {draft-ietf-pce-segment-routing-ipv6-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-pce-segment-routing-ipv6/16/},
    author =    {Cheng Li and Mahendra Singh Negi and Siva Sivabalan and Mike Koldychev and Prejeeth Kaladharan and Yongqing Zhu},
    title =     {{Path Computation Element Communication Protocol (PCEP) Extensions for Segment Routing leveraging the IPv6 dataplane}},
    pagetotal = 27,
    year =      2023,
    month =     mar,
    day =       6,
    abstract =  {Segment Routing (SR) can be used to steer packets through an IPv6 or MPLS network using the source routing paradigm. SR enables any head- end node to select any path without relying on a hop-by-hop signaling technique (e.g., LDP or RSVP-TE). A Segment Routed Path can be derived from a variety of mechanisms, including an IGP Shortest Path Tree (SPT), explicit configuration, or a PCE. Since SR can be applied to both MPLS and IPv6 forwarding planes, a PCE should be able to compute SR-Path for both MPLS and IPv6 forwarding planes. The PCEP extension and mechanisms to support SR- MPLS are described in {[}RFC8664{]}. This document describes the extensions required for SR support for IPv6 data plane in the Path Computation Element communication Protocol(PCEP).},
}