%% You should probably cite rfc8537 instead of this I-D. @techreport{ietf-teas-assoc-corouted-bidir-frr-05, number = {draft-ietf-teas-assoc-corouted-bidir-frr-05}, 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-teas-assoc-corouted-bidir-frr/05/}, author = {Rakesh Gandhi and Himanshu C. Shah and Jeremy Whittaker}, title = {{Updates to the Fast Reroute Procedures for Co-routed Associated Bidirectional Label Switched Paths (LSPs)}}, pagetotal = 16, year = 2018, month = aug, day = 8, abstract = {Resource Reservation Protocol (RSVP) association signaling can be used to bind two unidirectional LSPs into an associated bidirectional LSP. When an associated bidirectional LSP is co-routed, the reverse LSP follows the same path as its forward LSP. This document updates the Fast Reroute (FRR) procedures defined in RFC 4090 to support both single-sided and double-sided provisioned associated bidirectional LSPs. This document also updates the procedure for associating two reverse LSPs defined in RFC 7551 to support co-routed bidirectional LSPs. The FRR procedures can ensure that for the co-routed LSPs, traffic flows on co-routed paths in the forward and reverse directions after a failure event.}, }