Quick Failover Algorithm in SCTP
draft-nishida-tsvwg-sctp-failover-05

 
Document
Type Replaced Internet-Draft (individual)
Last updated 2013-02-13 (latest revision 2012-03-12)
Replaced by draft-ietf-tsvwg-sctp-failover
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream
Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG
IESG state Replaced by draft-ietf-tsvwg-sctp-failover
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
//www.ietf.org/archive/id/draft-nishida-tsvwg-sctp-failover-05.txt

Abstract

One of the major advantages in SCTP is supporting multi-homing communication. If a multi-homed end-point has redundant network connections, SCTP sessions can have a good chance to survive from network failures by migrating inactive network to active one. However, if we follow the SCTP standard, there can be significant delay for the network migration. During this migration period, SCTP cannot transmit much data to the destination. This issue drastically impairs the usability of SCTP in some situations. This memo describes the issue of SCTP failover mechanism and discuss its solutions which require minimal modification to the current standard.

Authors

Yoshifumi Nishida (nishida@wide.ad.jp)
Preethi Natarajan (prenatar@cisco.com)
Armando Caro (acaro@bbn.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)