The Eifel Response Algorithm for TCP
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 13
- Abstract
- Based on an appropriate detection algorithm, the Eifel response algorithm provides a way for a TCP sender to respond to a detected spurious timeout. It adapts the retransmission timer to avoid further spurious timeouts and (depending on the detection algorithm) can avoid the often unnecessary go-back-N retransmits that would otherwise be sent. In addition, the Eifel response algorithm restores the congestion control state in such a way that packet bursts are avoided. [STANDARDS-TRACK]
- Publication Date
- 2005-02-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC4015- Link
- https://doi.org/10.17487/RFC4015
- Author(s)
- Ludwig ReinerAndrei Gurtov
- Keyword(s)
- TCP
Latest version of IETF RFC 4015
Document Versions — IETF RFC 4015
-
▶ IETF RFC 4015 (2005-02-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 793 [Superseded*]
- IETF RFC 2119 [Active*]
- IETF RFC 2581 [Superseded*]
- IETF RFC 2861 [Superseded*]
- IETF RFC 2988 [Superseded*]
- IETF RFC 3168 [Active*]
- IETF RFC 3390 [Active*]
- IETF RFC 3522 [Active*]
- IETF RFC 3782 [Superseded*]
Bibliographic Reference(s)
- Blanton, E. and M. Allman, On Making TCP More Robust to Packet Reordering, ACM Computer Communication Review, Vol. 32, No. 1, January 2002. EXTERNAL
- Jacobson, V., Congestion Avoidance and Control, In Proceedings of ACM SIGCOMM 88. EXTERNAL
- Karn, P. and C. Partridge, Improving Round-Trip Time Estimates in Reliable Transport Protocols, In Proceedings of ACM SIGCOMM 87. EXTERNAL
- Ekstrom, H. and R. Ludwig, The Peak-Hopper: A New End-to- End Retransmission Timer for Reliable Unicast Transport, In Proceedings of IEEE INFOCOM 04, March 2004. EXTERNAL
- Gurtov, A. and R. Ludwig, Evaluating the Eifel Algorithm for TCP in a GPRS Network, In Proceedings of the European Wireless Conference, February 2002. EXTERNAL
- Ludwig, R. and R. H. Katz, The Eifel Algorithm: Making TCP Robust Against Spurious Retransmissions, ACM Computer Communication Review, Vol. 30, No. 1, January 2000. EXTERNAL
- Gurtov, A. and R. Ludwig, Responding to Spurious Timeouts in TCP, In Proceedings of IEEE INFOCOM 03, April 2003. EXTERNAL
- Allman, M., Avrachenkov, K., Ayesta, U., and J. Blanton, Early Retransmit for TCP and SCTP, Work in Progress, July 2004. EXTERNAL
- Zhang, L., Why TCP Timers Don't Work Well, In Proceedings of ACM SIGCOMM 88. EXTERNAL
- Sarolahti, P. and M. Kojo, F-RTO: An Algorithm for Detecting Spurious Retransmission Timeouts with TCP and SCTP, Work in Progress, November 2004. EXTERNAL
- Wright, G. R. and W. R. Stevens, TCP/IP Illustrated, Volume 2 (The Implementation), Addison Wesley, January 1995. EXTERNAL
- IETF RFC 1323 [Superseded*]
- IETF RFC 2883 [Active*]
- IETF RFC 3042 [Active*]
- IETF RFC 3517 [Superseded*]
- IETF RFC 3708 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4015.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 4015, The Eifel Response Algorithm for TCP. Available at https://doi.org/10.17487/RFC4015
Snippet:
IETF RFC 4015, The Eifel Response Algorithm for TCP. Available at https://doi.org/10.17487/RFC4015
HTML (ISO 690 compliant)
Preview:
IETF RFC 4015, The Eifel Response Algorithm for TCP. Available at https://doi.org/10.17487/RFC4015
Snippet:
<span class="citation"><cite>IETF RFC 4015</cite>, The Eifel Response Algorithm for TCP. Available at <a href="https://doi.org/10.17487/RFC4015" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4015</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 4015, The Eifel Response Algorithm for TCP
doi: 10.17487/RFC4015
url: https://doi.org/10.17487/RFC4015
doi: 10.17487/RFC4015
url: https://doi.org/10.17487/RFC4015
Snippet:
<li> <cite id="bib-rfc4015">IETF RFC 4015</cite>, The Eifel Response Algorithm for TCP <span class="doi">10.17487/RFC4015</span> </li>
Referenced By
- IETF RFC 4138 [Active*]
- IETF RFC 4614 [Superseded*]
- IETF RFC 4653 [Active*]
- IETF RFC 5682 [Active*]
- IETF RFC 6069 [Active*]
- IETF RFC 7323 [Active*]
- IETF RFC 7414 [Active*]
- IETF RFC 9438 [Active*]