%% You should probably cite draft-ietf-pce-sr-bidir-path-13 instead of this revision. @techreport{ietf-pce-sr-bidir-path-10, number = {draft-ietf-pce-sr-bidir-path-10}, 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-sr-bidir-path/10/}, author = {Cheng Li and Mach Chen and Weiqiang Cheng and Rakesh Gandhi and Quan Xiong}, title = {{Path Computation Element Communication Protocol (PCEP) Extensions for Associated Bidirectional Segment Routing (SR) Paths}}, pagetotal = 20, year = 2022, month = aug, day = 31, abstract = {The Path Computation Element Communication Protocol (PCEP) provides mechanisms for Path Computation Elements (PCEs) to perform path computations in response to Path Computation Clients (PCCs) requests. Segment routing (SR) leverages the source routing and tunneling paradigms. The Stateful PCEP extensions allow stateful control of Segment Routing Traffic Engineering (TE) Paths. Furthermore, PCEP can be used for computing SR TE paths in the network. This document defines PCEP extensions for grouping two unidirectional SR Paths (one in each direction in the network) into a single associated bidirectional SR Path. The mechanisms defined in this document can also be applied using a stateful PCE for both PCE- initiated and PCC-initiated LSPs or when using a stateless PCE.}, }