Segment Routing interoperability with LDP
draft-filsfils-spring-segment-routing-ldp-interop-03
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Clarence Filsfils , Stefano Previdi , Ahmed Bashandy , Bruno Decraene , Stephane Litkowski , Martin Horneffer , Igor Milojevic , Rob Shakir , Saku Ytti , Wim Henderickx , Jeff Tantsura , Edward Crabbe | ||
| Last updated | 2015-09-10 (Latest revision 2015-03-09) | ||
| Replaced by | draft-ietf-spring-segment-routing-ldp-interop | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Reviews |
RTGDIR Early review
by Sasha Vainshtein
Has issues
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-spring-segment-routing-ldp-interop | |
| 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
A Segment Routing (SR) node steers a packet through a controlled set of instructions, called segments, by prepending the packet with an SR header. A segment can represent any instruction, topological or service-based. SR allows to enforce a flow through any topological path and service chain while maintaining per-flow state only at the ingress node to the SR domain. The Segment Routing architecture can be directly applied to the MPLS data plane with no change in the forwarding plane. This drafts describes how Segment Routing operates in a network where LDP is deployed and in the case where SR-capable and non-SR-capable nodes coexist.
Authors
Clarence Filsfils
Stefano Previdi
Ahmed Bashandy
Bruno Decraene
Stephane Litkowski
Martin Horneffer
Igor Milojevic
Rob Shakir
Saku Ytti
Wim Henderickx
Jeff Tantsura
Edward Crabbe
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)