SCTP-PF: A Quick Failover Algorithm for the Stream Control Transmission Protocol (RFC7829)
Original Publication Date: 2016-Apr-01
Included in the Prior Art Database: 2016-Jun-29
Internet Society Requests For Comment (RFCs)
Y. Nishida: AUTHOR [+5]
The Stream Control Transmission Protocol (SCTP) specified in [RFC4960] supports multihoming at the transport layer. SCTP's multihoming features include failure detection and failover procedures to provide network interface redundancy and improved end- to-end fault tolerance. In SCTP's current failure detection procedure, the sender must experience Path.Max.Retrans (PMR) number of consecutive failed timer-based retransmissions on a destination address before detecting a path failure. Until detecting the path failure, the sender continues to transmit data on the failed path. The prolonged time in which SCTP as described in [RFC4960] continues to use a failed path severely degrades the performance of the protocol. To address this problem, this document specifies a quick failover algorithm called "SCTP-PF" based on the introduction of a new Potentially Failed (PF) path state in SCTP path management. The
Internet Engineering Task Force (IETF) Y. Nishida Request for Comments: 7829 GE Global Research Category: Standards Track P. Natarajan ISSN: 2070-1721 Cisco Systems A. Caro BBN Technologies P. Amer University of Delaware K. Nielsen Ericsson April 2016
SCTP-PF: A Quick Failover Algorithm for the Stream Control Transmission Protocol
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.
al. Standards Track [Page 1]
RFC 7829 SCTP-PF April 2016
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the...