%% You should probably cite draft-ietf-spring-segment-protection-sr-te-paths-06 instead of this revision.
@techreport{ietf-spring-segment-protection-sr-te-paths-01,
    number =    {draft-ietf-spring-segment-protection-sr-te-paths-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-spring-segment-protection-sr-te-paths/01/},
    author =    {Shraddha Hegde and Chris Bowers and Stephane Litkowski and Xiaohu Xu and Feng Xu},
    title =     {{Segment Protection for SR-TE Paths}},
    pagetotal = 19,
    year =      2021,
    month =     jul,
    day =       11,
    abstract =  {Segment routing supports the creation of explicit paths using Adj- Segment-ID (SID), Node-SIDs, and BSIDs. It is important to provide fast reroute (FRR) mechanisms to respond to failures of links and nodes in the Segment-Routed Traffic-Engineered(SR-TE) path. A point of local repair (PLR) can provide FRR protection against the failure of a link in an SR-TE path by examining only the first (top) label in the SR label stack. In order to protect against the failure of a node, a PLR may need to examine the second label in the stack as well, in order to determine SR-TE path beyond the failed node. This document specifies how a PLR can use the first and second label in the SR-MPLS label stack describing an SR-TE path to provide protection against node failures.},
}