SCTP-PF: A Quick Failover Algorithm for the Stream Control Transmission Protocol
RFC 7829
|
| Document |
Type |
|
RFC - Proposed Standard
(April 2016; No errata)
|
|
Last updated |
|
2018-12-20
|
|
Replaces |
|
draft-nishida-tsvwg-sctp-failover
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
pdf
html
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Gorry Fairhurst
|
|
Shepherd write-up |
|
Show
(last changed 2015-09-21)
|
| IESG |
IESG state |
|
RFC 7829 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Spencer Dawkins
|
|
Send notices to |
|
(None)
|
| IANA |
IANA review state |
|
Version Changed - Review Needed
|
|
IANA action state |
|
No IANA Actions
|
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
Abstract
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.
Nishida, et 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 Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7829.
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Nishida, et al. Standards Track [Page 2]
RFC 7829 SCTP-PF April 2016
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions and Terminology . . . . . . . . . . . . . . . . . 5
3. SCTP with Potentially Failed (SCTP-PF) Destination State . . 5
3.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Specification of the SCTP-PF Procedures . . . . . . . . . 6
4. Dormant State Operation . . . . . . . . . . . . . . . . . . . 10
4.1. SCTP Dormant State Procedure . . . . . . . . . . . . . . 11
5. Primary Path Switchover . . . . . . . . . . . . . . . . . . . 11
6. Suggested SCTP Protocol Parameter Values . . . . . . . . . . 13
7. Socket API Considerations . . . . . . . . . . . . . . . . . . 13
7.1. Support for the Potentially Failed Path State . . . . . . 14
7.2. Peer Address Thresholds (SCTP_PEER_ADDR_THLDS) Socket
Option . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.3. Exposing the Potentially Failed Path State
(SCTP_EXPOSE_POTENTIALLY_FAILED_STATE) Socket Option . . 16
8. Security Considerations . . . . . . . . . . . . . . . . . . . 16
9. MIB Considerations . . . . . . . . . . . . . . . . . . . . . 17
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
10.1. Normative References . . . . . . . . . . . . . . . . . . 17
Show full document text