SPRING Problem Statement and Requirements
draft-previdi-spring-problem-statement-04
| Document | Type |
Replaced Internet-Draft
(spring WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Stefano Previdi , Clarence Filsfils , Bruno Decraene , Stephane Litkowski , Martin Horneffer , Ruediger Geib , Rob Shakir , Robert Raszuk | ||
| Last updated | 2014-04-24 | ||
| Replaced by | RFC 7855 | ||
| 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-problem-statement | |
| 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
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
Ruediger Geib
Rob Shakir
Robert Raszuk
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)