Node Protection for SR-TE Paths
draft-hegde-spring-node-protection-for-sr-te-paths-04

Document Type Expired Internet-Draft (individual)
Last updated 2019-04-20 (latest revision 2018-10-17)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-hegde-spring-node-protection-for-sr-te-paths-04.txt

Abstract

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.

Authors

Shraddha Hegde (shraddha@juniper.net)
Chris Bowers (cbowers@juniper.net)
Stephane Litkowski (stephane.litkowski@orange.com)
Xiaohu Xu (xiaohu.xxh@alibaba-inc.com)
Feng Xu (oliverxu@tencent.com)

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