Segment Protection for SR-TE Paths
draft-ietf-spring-segment-protection-sr-te-paths-03
| Document | Type |
Expired Internet-Draft
(spring WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Shraddha Hegde , Chris Bowers , Stephane Litkowski , Xiaohu Xu , Feng Xu | ||
| Last updated | 2022-09-08 (Latest revision 2022-03-07) | ||
| Replaces | draft-ietf-spring-node-protection-for-sr-te-paths | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| 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:
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.
Authors
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.)