%% You should probably cite draft-ietf-pce-segment-routing instead of this I-D. @techreport{sivabalan-pce-segment-routing-02, number = {draft-sivabalan-pce-segment-routing-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-sivabalan-pce-segment-routing/02/}, author = {Siva Sivabalan and Jan Medved and Clarence Filsfils and Edward Crabbe and Robert Raszuk}, title = {{PCEP Extensions for Segment Routing}}, pagetotal = 18, year = 2013, month = oct, day = 16, 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 Protocol (PCEP) that allow a stateful PCE to compute and instantiate Traffic Engineering paths, as well as a PCC to request a path subject to certain constraint(s) and optimization criteria in SR networks.}, }