RFC 7829: SCTP-PF: A Quick Failover Algorithm for the Stream Control Transmission Protocol
In plain English — editorial summary, not part of the RFC
The Stream Control Transmission Protocol (SCTP) supports multihoming. However, when the failover operation specified in RFC 4960 is followed, there can be significant delay and performance degradation in the data transfer path failover. This document specifies a quick failover algorithm and introduces the SCTP Potentially Failed (SCTP-PF) destination state in SCTP Path Management. This document also specifies a dormant state operation of SCTP that is required to be followed by an SCTP-PF implementation, but it may equally well be applied by a standard SCTP implementation, as described in RFC 4960. Additionally, this document introduces an alternative switchback operation mode called "Primary Path Switchover" that will be beneficial in certain situations. This mode of operation applies to both a standard SCTP implementation and an SCTP-PF implementation. The procedures defined in the document require only minimal modifications to the specification in RFC 4960. The procedures are sender-side only and do not impact the SCTP receiver.
Document record
- Document ID
- RFC7829
- Published
- April 2016
- Authors
- Y. Nishida; P. Natarajan; A. Caro; P. Amer; K. Nielsen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9079Source-Specific Routing in the Babel Routing ProtocolCurrent
August 2021
- RFC 3257Stream Control Transmission Protocol Applicability StatementCurrent
April 2002
- RFC 7605Recommendations on Using Assigned Transport Port NumbersCurrent
August 2015
- RFC 8899Packetization Layer Path MTU Discovery for Datagram TransportsCurrent
September 2020
- RFC 9000QUIC: A UDP-Based Multiplexed and Secure TransportCurrent
May 2021
- RFC 6633Deprecation of ICMP Source Quench MessagesCurrent
May 2012
- RFC 9260Stream Control Transmission ProtocolCurrent
June 2022
- RFC 9897Datagram Congestion Control Protocol (DCCP) Extensions for Multipath Operation with Multiple AddressesCurrent
January 2026
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?