Source Packet Routing in Networking (SPRING) Problem Statement and Requirements
RFC 7855

Changed author "R. Shakir": changed name from "Rob Shakir" to "R. Shakir", changed affiliation from "Jive Communications" to "Jive Communications, Inc.", cleared country (was "United States"), changed order from "5" to "6"

Changed author "C. Filsfils": changed name from "Clarence Filsfils" to "C. Filsfils", changed is_editor from "False" to "True", changed affiliation from "Cisco Systems" to "Cisco Systems, Inc.", cleared country (was "Belgium"), changed order from "1" to "2"

Changed author "S. Previdi": changed name from "Stefano Previdi" to "S. Previdi", changed is_editor from "False" to "True", changed affiliation from "Cisco Systems" to "Cisco Systems, Inc.", cleared country (was "Italy"), changed order from "0" to "1"

Received changes through RFC Editor sync (changed abstract to '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.')