%% You should probably cite draft-hu-spring-segment-routing-proxy-forwarding-24 instead of this revision.
@techreport{hu-spring-segment-routing-proxy-forwarding-21,
    number =    {draft-hu-spring-segment-routing-proxy-forwarding-21},
    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/21/},
    author =    {Zhibo Hu and Huaimo Chen and Junda Yao and Chris Bowers and Yongqing Zhu and Yisong Liu},
    title =     {{SR-TE Path Midpoint Restoration}},
    pagetotal = 14,
    year =      2022,
    month =     oct,
    day =       24,
    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 the restoration of the routes to the failure of a SR-MPLS TE path after the IGP converges. It provides the restoration of the routes to an adjacency segment, a node segment and a binding segment of the path. With the restoration of the routes to the failure, the traffic is continuously sent to the neighbor of the failure after the IGP converges. The neighbor as a PLR fast re-routes the traffic around the failure.},
}