%% You should probably cite draft-ietf-mpls-egress-protection-framework instead of this I-D.
@techreport{shen-mpls-egress-protection-framework-03,
    number =    {draft-shen-mpls-egress-protection-framework-03},
    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/03/},
    author =    {Yimin Shen and Jeyananth Minto Jeganathan and Bruno Decraene and Hannes Gredler},
    title =     {{MPLS Egress Protection Framework}},
    pagetotal = 20,
    year =      2016,
    month =     oct,
    day =       21,
    abstract =  {This document specifies a fast reroute framework for protecting IP/ MPLS services and MPLS transport tunnels against egress router failures. In this framework, the penultimate-hop router of an MPLS tunnel pre-establishes a bypass tunnel to a protector. Upon an egress router failure, the penultimate-hop router performs local failure detection and local repair, by rerouting traffic over the bypass tunnel. The protector in turn performs context label switching or context IP forwarding to send the traffic 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 facilitate service label distribution to protector.},
}