%% You should probably cite draft-ietf-mpls-egress-protection-framework instead of this I-D. @techreport{shen-mpls-egress-protection-framework-04, number = {draft-shen-mpls-egress-protection-framework-04}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-shen-mpls-egress-protection-framework/04/}, author = {Yimin Shen and Jeyananth Minto Jeganathan and Bruno Decraene and Hannes Gredler and Carsten Michel}, title = {{MPLS Egress Protection Framework}}, pagetotal = 25, year = 2017, month = feb, day = 1, abstract = {This document specifies the framework of a fast reroute mechanism for protecting IP/MPLS services and MPLS transport tunnels against egress node and egress link failures. In this framework, the penultimate- hop router of an MPLS tunnel acts as the point of local repair (PLR) for egress node failure, and the egress router of the MPLS tunnel acts as the PLR for egress link failure. They each pre-establishes a bypass tunnel to a protector. Upon an egress node or link failure, the PLR performs local failure detection and local repair, by rerouting packets over the bypass tunnel. The protector in turn performs context label switching or context IP forwarding to send the packets to ultimate service destination(s). This mechanism can be used to reduce traffic loss before global repair reacts to the failure and control plane protocols converge on the topology changes due to the failure. The framework is applicable to all types of IP/ MPLS services and MPLS tunnels. Under the framework, service protocol extensions may be further specified to support service label distribution to protector.}, }