<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.nishida-natarajan-sctp-failover" target="https://datatracker.ietf.org/doc/html/draft-nishida-natarajan-sctp-failover-00">
   <front>
      <title>Quick Failover Algorithm in SCTP</title>
      <author initials="Y." surname="Nishida" fullname="Yoshifumi Nishida">
         <organization>WIDE Project</organization>
      </author>
      <author initials="P." surname="Natarajan" fullname="Preethi Natarajan">
         <organization>Cisco Systems</organization>
      </author>
      <date month="February" day="22" year="2010" />
      <abstract>
	 <t>   One of the major advantages in SCTP is supporting multi-homing
   communication.  If an 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.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-nishida-natarajan-sctp-failover-00" />
   
</reference>
