Skip to main content

Node Protection for SR-TE Paths

Document Type Replaced Internet-Draft (spring WG)
Expired & archived
Authors Shraddha Hegde , Chris Bowers , Stephane Litkowski , Xiaohu Xu , Feng Xu
Last updated 2020-09-09 (Latest revision 2020-07-30)
Replaced by draft-ietf-spring-node-protection-for-sr-te-paths
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Additional resources Mailing list discussion
Stream WG state Adopted by a WG
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-spring-node-protection-for-sr-te-paths
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


Segment routing supports the creation of explicit paths using adjacency-sids, node-sids, and binding-sids. 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 label stack describing an SR-TE path to provide protection against node failures.


Shraddha Hegde
Chris Bowers
Stephane Litkowski
Xiaohu Xu
Feng Xu

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)