%% You should probably cite draft-ietf-pce-segment-routing-ipv6-22 instead of this revision. @techreport{ietf-pce-segment-routing-ipv6-02, number = {draft-ietf-pce-segment-routing-ipv6-02}, 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/02/}, author = {Mahendra Singh Negi and Cheng Li and Siva Sivabalan and Prejeeth Kaladharan and Yongqing Zhu}, title = {{PCEP Extensions for Segment Routing leveraging the IPv6 data plane}}, pagetotal = 22, year = 2019, month = apr, day = 8, 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. 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 SR 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 document describes the extensions required for SR support for IPv6 data plane in Path Computation Element communication Protocol (PCEP). The PCEP extension and mechanism to support SR-MPLS is described in {[}I-D.ietf-pce-segment-routing{]}. This document extends it to support SRv6 (SR over IPv6).}, }