RFC 4015: The Eifel Response Algorithm for TCP
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC4015
- Published
- February 2005
- Authors
- R. Ludwig; A. Gurtov
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4138Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP and the Stream Control Transmission Protocol (SCTP)Updated
August 2005
- RFC 3828The Lightweight User Datagram Protocol (UDP-Lite)Updated
July 2004
- RFC 3782The NewReno Modification to TCP's Fast Recovery AlgorithmObsoleted
April 2004
- RFC 3758Stream Control Transmission Protocol (SCTP) Partial Reliability ExtensionCurrent
May 2004
- RFC 3742Limited Slow-Start for TCP with Large Congestion WindowsCurrent
March 2004
- RFC 3708Using TCP Duplicate Selective Acknowledgement (DSACKs) and Stream Control Transmission Protocol (SCTP) Duplicate Transmission Sequence Numbers (TSNs) to Detect Spurious RetransmissionsCurrent
February 2004
- RFC 3649HighSpeed TCP for Large Congestion WindowsCurrent
December 2003
- RFC 4460Stream Control Transmission Protocol (SCTP) Specification Errata and IssuesObsoleted
April 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?