%% You should probably cite draft-ietf-pce-segment-routing-ipv6 instead of this I-D. @techreport{negi-pce-segment-routing-ipv6-04, number = {draft-negi-pce-segment-routing-ipv6-04}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-negi-pce-segment-routing-ipv6/04/}, author = {Mahendra Singh Negi and Cheng Li and Siva Sivabalan and Prejeeth Kaladharan}, title = {{PCEP Extensions for Segment Routing leveraging the IPv6 data plane}}, pagetotal = 20, year = 2019, month = feb, day = 6, abstract = {The Source Packet Routing in Networking (SPRING) architecture describes how Segment Routing (SR) can be used to steer packets through an IPv6 or MPLS network using the source routing paradigm. Segment Routing (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). It depends only on "segments" that are advertised by Link- State IGPs. A Segment Routed Path can be derived from a variety of mechanisms, including an IGP Shortest Path Tree (SPT), explicit configuration, or a Path Computation Element (PCE). Since, Segment Routing can be applied to both MPLS and IPv6 forwarding plane, a PCE should be able to compute SR-Path for both MPLS and IPv6 forwarding plane. This draft describes the extensions required for Segment Routing support for IPv6 data plane in Path Computation Element communication Protocol (PCEP).}, }