Implementing non protected paths using SPRING
draft-litkowski-spring-non-protected-paths-02

Document Type Expired Internet-Draft (individual)
Last updated 2018-04-19 (latest revision 2017-08-09)
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-litkowski-spring-non-protected-paths-02.txt

Abstract

Segment Routing (SR) leverages the source routing paradigm. A node can steer a packet on a specific path by prepending the packet with an SR header. In the framework of traffic-engineering use cases, a customer may request its service provider to implement some non protected paths. This means that in case of a failure within the network, fast-reroute (or similar) techniques should not be activated for those paths. This document analyzes the different options to implement a non protected path with Segment Routing and in a future release will provide a recommandation on the best option.

Authors

Stephane Litkowski (stephane.litkowski@orange.com)
Mustapha Aissaoui (mustapha.aissaoui@nokia.com)

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