%% You should probably cite draft-ietf-tsvwg-sctp-failover instead of this I-D. @techreport{nishida-tsvwg-sctp-failover-05, number = {draft-nishida-tsvwg-sctp-failover-05}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-nishida-tsvwg-sctp-failover/05/}, author = {Yoshifumi Nishida and Preethi Natarajan and Armando L. Caro}, title = {{Quick Failover Algorithm in SCTP}}, pagetotal = 17, year = 2012, month = mar, day = 12, 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.}, }