IPv6 SPRING Use Cases
draft-martin-spring-segment-routing-ipv6-use-cases-01
Document | Type |
Replaced Internet-Draft
(spring WG)
Expired & archived
|
|
---|---|---|---|
Authors | John Jason Brzozowski , John Leddy , Ida Leung , Stefano Previdi , Mark Townsley , Christian Martin , Clarence Filsfils , Roberta Maglione | ||
Last updated | 2014-04-04 | ||
Replaced by | draft-ietf-spring-ipv6-use-cases | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Adopted by a WG | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-spring-ipv6-use-cases | |
Consensus boilerplate | Unknown | ||
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
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.
Authors
John Jason Brzozowski
John Leddy
Ida Leung
Stefano Previdi
Mark Townsley
Christian Martin
Clarence Filsfils
Roberta Maglione
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)