RFC 5682: Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP
In plain English — editorial summary, not part of the RFC
The purpose of this document is to move the F-RTO (Forward RTO-Recovery) functionality for TCP in RFC 4138 from Experimental to Standards Track status. The F-RTO support for Stream Control Transmission Protocol (SCTP) in RFC 4138 remains with Experimental status. See Appendix B for the differences between this document and RFC 4138. Spurious retransmission timeouts cause suboptimal TCP performance because they often result in unnecessary retransmission of the last window of data. This document describes the F-RTO detection algorithm for detecting spurious TCP retransmission timeouts. F-RTO is a TCP sender-only algorithm that does not require any TCP options to operate. After retransmitting the first unacknowledged segment triggered by a timeout, the F-RTO algorithm of the TCP sender monitors the incoming acknowledgments to determine whether the timeout was spurious. It then decides whether to send new segments or retransmit unacknowledged segments. The algorithm effectively helps to avoid additional unnecessary retransmissions and thereby improves TCP performance in the case of a spurious timeout. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5682
- Published
- September 2009
- Authors
- P. Sarolahti; M. Kojo; K. Yamamoto; M. Hata
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 19
- Also known as
- —
- Updates:
- RFC 4138
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3522The Eifel Detection Algorithm for TCPCurrent
April 2003
- RFC 2883An Extension to the Selective Acknowledgement (SACK) Option for TCPCurrent
July 2000
- RFC 9937Proportional Rate Reduction (PRR)Current
December 2025
- RFC 5827Early Retransmit for TCP and Stream Control Transmission Protocol (SCTP)Current
April 2010
- RFC 5482TCP User Timeout OptionCurrent
March 2009
- RFC 5925The TCP Authentication OptionCurrent
June 2010
- RFC 5926Cryptographic Algorithms for the TCP Authentication Option (TCP-AO)Current
June 2010
- RFC 6093On the Implementation of the TCP Urgent MechanismObsoleted
January 2011
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?