RFC 8355: Resiliency Use Cases in Source Packet Routing in Networking (SPRING) Networks
In plain English — editorial summary, not part of the RFC
This document identifies and describes the requirements for a set of use cases related to Segment Routing network resiliency on Source Packet Routing in Networking (SPRING) networks.
Document record
- Document ID
- RFC8355
- Published
- March 2018
- Authors
- C. Filsfils; S. Previdi; B. Decraene; R. Shakir
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9855Topology Independent Fast Reroute Using Segment RoutingCurrent
October 2025
- RFC 8383Transparent Interconnection of Lots of Links (TRILL): Address Flush MessageCurrent
May 2018
- RFC 8287Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data PlanesUpdated
December 2017
- RFC 8104Pseudowire (PW) Endpoint Fast Failure ProtectionCurrent
March 2017
- RFC 8665OSPF Extensions for Segment RoutingCurrent
December 2019
- RFC 8666OSPFv3 Extensions for Segment RoutingCurrent
December 2019
- RFC 8667IS-IS Extensions for Segment RoutingCurrent
December 2019
- RFC 7884OSPF Extensions to Advertise Seamless Bidirectional Forwarding Detection (S-BFD) Target DiscriminatorsCurrent
July 2016
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?