Segment Routing Use Cases

Document Type Replaced Internet-Draft (individual)
Authors Clarence Filsfils  , Pierre Francois  , Stefano Previdi  , Bruno Decraene  , Stephane Litkowski  , Martin Horneffer  , Igor Milojevic  , Rob Shakir  , Saku Ytti  , Wim Henderickx  , Jeff Tantsura  , Sriganesh Kini  , Edward Crabbe 
Last updated 2014-05-14 (latest revision 2013-10-21)
Replaced by draft-filsfils-spring-segment-routing-use-cases
Stream (None)
Intended RFC status (None)
Expired & archived
plain text xml htmlized pdfized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-filsfils-spring-segment-routing-use-cases
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


Segment Routing (SR) leverages the source routing and tunneling paradigms. A 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 of the SR domain. The Segment Routing architecture can be directly applied to the MPLS dataplane with no change on the forwarding plane. It requires minor extension to the existing link-state routing protocols. Segment Routing can also be applied to IPv6 with a new type of routing extension header.


Clarence Filsfils (
Pierre Francois (
Stefano Previdi (
Bruno Decraene (
Stephane Litkowski (
Martin Horneffer (
Igor Milojevic (
Rob Shakir (
Saku Ytti (
Wim Henderickx (
Jeff Tantsura (
Sriganesh Kini (
Edward Crabbe (

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