Source Packet Routing in Networking (SPRING) Problem Statement and Requirements
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 19
- 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.
- Publication Date
- 2016-05-01
- Status Note
- Informational
- DOI
10.17487/RFC7855- Link
- https://doi.org/10.17487/RFC7855
- Author(s)
- Stefano PrevidiClarence FilsfilsBruno DecraeneStephane LitkowskiMartin HornefferRob Shakir
Latest version of IETF RFC 7855
Document Versions — IETF RFC 7855
-
▶ IETF RFC 7855 (2016-05-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 2460 [Superseded*]
- IETF RFC 4364 [Active*]
- IETF RFC 4761 [Active*]
- IETF RFC 4762 [Active*]
- IETF RFC 6624 [Active*]
Bibliographic Reference(s)
- IETF.draft-ietf-6man-segment-routing-header-01 — SRH EXTERNAL
- IETF.draft-ietf-idr-add-paths-14 — ADD-PATH EXTERNAL
- IETF.draft-ietf-pce-stateful-pce-14 — STATEFUL-PCE EXTERNAL
- IETF.draft-ietf-spring-oam-usecase-03 — OAM-USE EXTERNAL
- IETF.draft-ietf-spring-resiliency-use-cases-03 — SPRING-RESIL EXTERNAL
- IETF.draft-ietf-spring-segment-routing-central-epe-01 — SR-BGP-EPE EXTERNAL
- IETF.draft-ietf-spring-sr-oam-requirement-01 — SR-OAM EXTERNAL
- IETF RFC 4381 [Active*]
- IETF RFC 5920 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7855.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 7855, Source Packet Routing in Networking (SPRING) Problem Statement and Requirements. Available at https://doi.org/10.17487/RFC7855
Snippet:
IETF RFC 7855, Source Packet Routing in Networking (SPRING) Problem Statement and Requirements. Available at https://doi.org/10.17487/RFC7855
HTML (ISO 690 compliant)
Preview:
IETF RFC 7855, Source Packet Routing in Networking (SPRING) Problem Statement and Requirements. Available at https://doi.org/10.17487/RFC7855
Snippet:
<span class="citation"><cite>IETF RFC 7855</cite>, Source Packet Routing in Networking (SPRING) Problem Statement and Requirements. Available at <a href="https://doi.org/10.17487/RFC7855" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7855</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 7855, Source Packet Routing in Networking (SPRING) Problem Statement and Requirements
doi: 10.17487/RFC7855
url: https://doi.org/10.17487/RFC7855
doi: 10.17487/RFC7855
url: https://doi.org/10.17487/RFC7855
Snippet:
<li> <cite id="bib-rfc7855">IETF RFC 7855</cite>, Source Packet Routing in Networking (SPRING) Problem Statement and Requirements <span class="doi">10.17487/RFC7855</span> </li>
Referenced By
- IETF RFC 8354 [Active*]
- IETF RFC 8355 [Active*]
- IETF RFC 8660 [Active*]
- IETF RFC 8662 [Active*]
- IETF RFC 8665 [Active*]
- IETF RFC 8666 [Active*]
- IETF RFC 8667 [Active*]
- IETF RFC 8919 [Superseded*]
- IETF RFC 8920 [Superseded*]
- IETF RFC 9087 [Active*]
- IETF RFC 9479 [Active*]
- IETF RFC 9492 [Active*]