%% You should probably cite rfc8664 instead of this I-D. @techreport{ietf-pce-segment-routing-14, number = {draft-ietf-pce-segment-routing-14}, 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/14/}, author = {Siva Sivabalan and Clarence Filsfils and Jeff Tantsura and Wim Henderickx and Jonathan Hardwick}, title = {{PCEP Extensions for Segment Routing}}, pagetotal = 31, year = 2018, month = oct, day = 13, abstract = {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 Interior Gateway Protocols (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). This document specifies extensions to the Path Computation Element Communication Protocol (PCEP) that allow a stateful PCE to compute and initiate Traffic Engineering (TE) paths, as well as a PCC to request a path subject to certain constraints and optimization criteria in SR networks.}, }