%% You should probably cite draft-hu-spring-segment-routing-proxy-forwarding-24 instead of this revision.
@techreport{hu-spring-segment-routing-proxy-forwarding-00,
    number =    {draft-hu-spring-segment-routing-proxy-forwarding-00},
    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/00/},
    author =    {Zhibo Hu and Huaimo Chen and Junda Yao},
    title =     {{Segment Routing Proxy Forwarding}},
    pagetotal = 17,
    year =      ,
    month =     ,
    day =       ,
    abstract =  {Segment Routing Traffic Engineering (SR-TE) supports the creation of explicit paths using adjacency-sids, node-sids, and binding-sids. In the SR-TE path, by providing proxy forwarding to the neighbor nodes of the faulty node, it is ensured that the traffic can reach the neighbor node of the faulty node normally in the case of the SR-TE of the loose path or strict path. If the failed node is a node that provides the Binding-sids service, the neighbor node can perform the binding-sids forwarding behavior to swap the corresponding label stack through the proxy forwarding of the neighbor node. {[}I-D.bashandy-rtgwg-segment-routing-ti-lfa{]} defines the usecase of protecting the node failure of segment list. This document describes how to implement the proxy forwarding mechanism of a faulty node at the neighbor node of the faulty node on the SR-TE path .},
}