Source Packet Routing in Networking Problem Statement and Requirements
RFC 7855, “Source Packet Routing in Networking Problem Statement and Requirements”, is an Informational document published in May 2016 by S. Previdi, C. Filsfils, B. Decraene, S. Litkowski, M. Horneffer, R. Shakir. The canonical text is published by the RFC Editor.
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"; 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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 7855 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7854 BGP Monitoring Protocol
- RFC 7856 Softwire Mesh Management Information Base
- RFC 7853 A URN Namespace for Globus
- RFC 7857 Updates to Network Address Translation Behavioral Requirements
- RFC 7852 Additional Data Related to an Emergency Call
- RFC 7858 Specification for DNS over Transport Layer Security
- RFC 7851 Peer-to-Peer Overlay Diagnostics
- RFC 7859 Identity-Based Signatures for Mobile Ad Hoc Network Routing Protocols