Segment Routing interworking with LDP
draft-ietf-spring-segment-routing-ldp-interop-04

The information below is for an old version of the document
Document Type Expired Internet-Draft (spring WG)
Last updated 2017-01-05 (latest revision 2016-07-04)
Replaces draft-filsfils-spring-segment-routing-ldp-interop
Stream IETF
Intended RFC status Proposed Standard
Formats
Expired & archived
plain text pdf html bibtex
Additional URLs
- Mailing list discussion
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
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-ietf-spring-segment-routing-ldp-interop-04.txt

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 (cfilsfil@cisco.com)
Stefano Previdi (sprevidi@cisco.com)
Ahmed Bashandy (bashandy@cisco.com)
Bruno Decraene (bruno.decraene@orange.com)
Stephane Litkowski (stephane.litkowski@orange.com)

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