%% You should probably cite draft-hu-spring-segment-routing-proxy-forwarding-24 instead of this revision.
@techreport{hu-spring-segment-routing-proxy-forwarding-13,
    number =    {draft-hu-spring-segment-routing-proxy-forwarding-13},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-hu-spring-segment-routing-proxy-forwarding/13/},
    author =    {Zhibo Hu and Huaimo Chen and Junda Yao and Chris Bowers and Yongqing Zhu and Yisong Liu},
    title =     {{SR-TE Path Midpoint Protection}},
    pagetotal = 23,
    year =      ** No value found for 'doc.pub_date.year' **,
    month =     ** No value found for 'doc.pub_date' **,
    day =       ** No value found for 'doc.pub_date.day' **,
    abstract =  {Segment Routing Traffic Engineering (SR-TE) supports explicit paths using segment lists containing adjacency-SIDs, node-SIDs and binding- SIDs. The current SR FRR such as TI-LFA provides fast re-route protection for the failure of a node along a SR-TE path by the direct neighbor or say point of local repair (PLR) to the failure. However, once the IGP converges, the SR FRR is no longer sufficient to forward traffic of the path around the failure, since the non-neighbors of the failure will no longer have a route to the failed node. This document describes a mechanism for fast re-route protection against the failure of a SR-TE path after the IGP converges. It provides fast re-route protection for an adjacency segment, a node segment and a binding segment of the path.},
}