metasystema.org
CurrentINFORMATIONALIETF stream

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

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC7855
Published
May 2016
Authors
S. Previdi; C. Filsfils; B. Decraene; S. Litkowski; M. Horneffer; R. Shakir
Status
INFORMATIONAL
Stream
IETF
Area
rtg
Pages
19
Also known as
—

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/7855-source-packet-routing-in-networking-spring-problem-statement-and-requirements