IS-IS Extensions for Segment Routing
draft-previdi-isis-segment-routing-extensions-05
| Document | Type | Replaced Internet-Draft (isis WG) | |
|---|---|---|---|
| Last updated | 2014-08-17 (latest revision 2014-02-13) | ||
| Replaced by | draft-ietf-isis-segment-routing-extensions | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Replaced by draft-ietf-isis-segment-routing-extensions | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-previdi-isis-segment-routing-extensions-05.txt
Abstract
Segment Routing (SR) allows for a flexible definition of end-to-end paths within IGP topologies by encoding paths as sequences of topological sub-paths, called "segments". These segments are advertised by the link-state routing protocols (IS-IS and OSPF). This draft describes the necessary IS-IS extensions that need to be introduced for Segment Routing.
Authors
Stefano Previdi
(sprevidi@cisco.com)
Clarence Filsfils
(cfilsfil@cisco.com)
Ahmed Bashandy
(bashandy@cisco.com)
Hannes Gredler
(hannes@juniper.net)
Stephane Litkowski
(stephane.litkowski@orange.com)
Jeff Tantsura
(jeff.tantsura@ericsson.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)