IPv6 SPRING Use Cases
draft-ietf-spring-ipv6-use-cases-07
| Document | Type | Expired Internet-Draft (spring WG) | |
|---|---|---|---|
| Authors | John Jason Brzozowski , John Leddy , Mark Townsley , Clarence Filsfils , Roberta Maglione | ||
| Last updated | 2017-01-23 (Latest revision 2016-07-22) | ||
| Replaces | draft-martin-spring-segment-routing-ipv6-use-cases | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
xml
htmlized
pdfized
bibtex
|
||
| Reviews |
GENART Telechat review
(of
-11)
Not Ready
RTGDIR Last Call review
(of
-10)
Has Issues
GENART Last Call review
(of
-10)
Not Ready
OPSDIR Last Call review
(of
-10)
Has Issues
|
||
| Stream | WG state | WG Document | |
| Document shepherd | Bruno Decraene | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | "Bruno Decraene" <bruno.decraene@orange.com> |
https://www.ietf.org/archive/id/draft-ietf-spring-ipv6-use-cases-07.txt
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
Mark Townsley
Clarence Filsfils
Roberta Maglione
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)