Search RFCs

RFC Editor

File formats:

Status:

INFORMATIONAL

Authors:

S. Previdi, Ed.
C. Filsfils, Ed.
B. Decraene
S. Litkowski
M. Horneffer
R. Shakir

Stream:

IETF

Source:

spring (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC7855

Discuss this RFC: Send questions or comments to the mailing listspring@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 7855

Abstract

The ability for a node to specify a forwarding path, other than thenormal shortest path, that a particular packet will traverse,benefits a number of network functions. Source-based routingmechanisms have previously been specified for network protocols buthave 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 anoperator's network).

This document outlines various use cases, with their requirements,that need to be taken into account by the Source Packet Routing inNetworking (SPRING) architecture for unicast traffic. Multicast usecases and requirements are out of scope for this document.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.