SPRING Problem Statement and Requirements
draft-ietf-spring-problem-statement-03
| Document | Type | Expired Internet-Draft (spring WG) | |
|---|---|---|---|
| Authors | Stefano Previdi , Clarence Filsfils , Bruno Decraene , Stephane Litkowski , Martin Horneffer , Rob Shakir | ||
| Last updated | 2015-04-26 (Latest revision 2014-10-23) | ||
| Replaces | draft-previdi-spring-problem-statement | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Reviews |
GENART Telechat review
(of
-06)
Ready with Nits
OPSDIR Last Call review
(of
-06)
Has Issues
GENART Last Call review
(of
-06)
Ready with Nits
SECDIR Last Call review
(of
-06)
Has Nits
GENART Telechat review
(of
-06)
Ready with Nits
|
||
| Stream | WG state | In WG Last Call | |
| Document shepherd | Alvaro Retana | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
https://www.ietf.org/archive/id/draft-ietf-spring-problem-statement-03.txt
Abstract
The ability for a node to specify a forwarding path, other than the normal shortest path, that a particular packet will traverse, benefits a number of network functions. Source-based routing mechanisms have previously been specified for network protocols, but have not seen widespread adoption. In this context, the term 'source' means 'the point at which the explicit route is imposed'. This document outlines various use cases, with their requirements, that need to be taken into account by the Source Packet Routing in Networking (SPRING) architecture for unicast traffic. Multicast use- cases and requirements are out of scope of this document.
Authors
Stefano Previdi
Clarence Filsfils
Bruno Decraene
Stephane Litkowski
Martin Horneffer
Rob Shakir
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)