%% You should probably cite draft-ietf-pce-sr-path-segment instead of this I-D. @techreport{li-pce-sr-path-segment-08, number = {draft-li-pce-sr-path-segment-08}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-li-pce-sr-path-segment/08/}, author = {Cheng Li and Mach Chen and Weiqiang Cheng and Jie Dong and Zhenbin Li and Rakesh Gandhi and Quan Xiong}, title = {{Path Computation Element Communication Protocol (PCEP) Extension for Path Segment in Segment Routing (SR)}}, pagetotal = 26, year = 2019, month = aug, day = 19, abstract = {The Path Computation Element (PCE) provides path computation functions in support of traffic engineering in Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks. 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. 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). Path identification is needed for several use cases such as performance measurement in Segment Routing (SR) network. This document specifies extensions to the Path Computation Element Communication Protocol (PCEP) to support requesting, replying, reporting and updating the Path Segment ID (Path SID) between PCEP speakers.}, }