<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-spring-segment-protection-sr-te-paths" target="https://datatracker.ietf.org/doc/html/draft-ietf-spring-segment-protection-sr-te-paths-08">
   <front>
      <title>Segment Protection for SR-TE Paths</title>
      <author initials="S." surname="Hegde" fullname="Shraddha Hegde">
         <organization>Juniper Networks Inc.</organization>
      </author>
      <author initials="C." surname="Bowers" fullname="Chris Bowers">
         <organization>Juniper Networks Inc.</organization>
      </author>
      <author initials="S." surname="Litkowski" fullname="Stephane Litkowski">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="X." surname="Xu" fullname="Xiaohu Xu">
         <organization>China Mobile Inc.</organization>
      </author>
      <author initials="F." surname="Xu" fullname="Feng Xu">
         <organization>Tencent</organization>
      </author>
      <date month="June" day="29" year="2025" />
      <abstract>
	 <t>   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-spring-segment-protection-sr-te-paths-08" />
   
</reference>
