IPv6 SPRING Use Cases

Document Type Replaced Internet-Draft (spring WG)
Authors John Brzozowski  , John Leddy  , Ida Leung  , Stefano Previdi  , Mark Townsley  , Christian Martin  , Clarence Filsfils  , Roberta Maglione 
Last updated 2014-04-04
Replaced by RFC 8354
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Expired & archived
plain text xml pdf htmlized bibtex
Stream WG state Adopted by a WG
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-spring-ipv6-use-cases
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


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)
Ida Leung (ida.leung@rci.rogers.com)
Stefano Previdi (sprevidi@cisco.com)
Mark Townsley (townsley@cisco.com)
Christian Martin (martincj@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.)