Source Packet Routing in Networking (SPRING) Problem Statement and Requirements (RFC7855)
Original Publication Date: 2016-May-01
Included in the Prior Art Database: 2016-Jun-29
Internet Society Requests For Comment (RFCs)
S. Previdi: AUTHOR [+8]
The ability for a node to specify a unicast forwarding path, other than the normal shortest path, that a particular packet will traverse, benefits a number of network functions, for example:
Internet Engineering Task Force (IETF) S. Previdi, Ed. Request for Comments: 7855 C. Filsfils, Ed. Category: Informational Cisco Systems, Inc. ISSN: 2070-1721 B. Decraene S. Litkowski Orange M. Horneffer Deutsche Telekom R. Shakir Jive Communications, Inc. May 2016
Source Packet Routing in Networking (SPRING) Problem Statement and Requirements
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"; therefore, it is not limited to the originator of the packet (i.e., the node imposing the explicit route may be the ingress node of an operator's network).
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 for this document.
Status of This Memo
This document is not an Internet Standards Track specification; it is published for informational purposes.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
Information about the current status of this document, any errata, ...