IPv6 SPRING Use Cases

The information below is for an old version of the document
Document Type Expired Internet-Draft (spring WG)
Last updated 2017-01-23 (latest revision 2016-07-22)
Replaces draft-martin-spring-segment-routing-ipv6-use-cases
Stream IETF
Intended RFC status Informational
Expired & archived
pdf htmlized bibtex
Stream WG state WG Document
Revised I-D Needed - Issue raised by WG
Document shepherd Bruno Decraene
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Bruno Decraene" <bruno.decraene@orange.com>

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


Source Packet Routing in Networking (SPRING) architecture leverages the source routing paradigm. A node steers a packet through a controlled set of instructions, called segments, by prepending the packet with SPRING header. A segment can represent any instruction, topological or service-based. A segment can have a local semantic to the SPRING node or global within the SPRING domain. SPRING allows to enforce a flow through any topological path and service chain while maintaining per-flow state only at the ingress node to the SPRING domain. The objective of this document is to illustrate some use cases that need to be taken into account by the Source Packet Routing in Networking (SPRING) architecture.


John Brzozowski (john_brzozowski@cable.comcast.com)
John Leddy (john_leddy@cable.comcast.com)
Mark Townsley (townsley@cisco.com)
Clarence Filsfils (cfilsfil@cisco.com)
Roberta Maglione (robmgl@cisco.com)

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