API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 5682
[ACTIVE]

Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP

Metadata

Publisher
IETF
Doc Type
Standard
Pages
19
Abstract
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]
Publication Date
2009-09-01
Status Note
Proposed Standard
DOI
10.17487/RFC5682
Link
https://doi.org/10.17487/RFC5682
Author(s)
Pasi Sarolahti
Markku Kojo
Kazunori Yamamoto
Max Hata
Keyword(s)
SACK, TCP Loss Recovery
Latest version of IETF RFC 5682

Document Versions — IETF RFC 5682

  • ▶ IETF RFC 5682 (2009-09-01)
    THIS DOC [ACTIVE] [LATEST VERSION]

Normative Reference(s)

Bibliographic Reference(s)

  • Sarolahti, P., Kojo, M., and K. Raatikainen, "F-RTO: An Enhanced Recovery Algorithm for TCP Retransmission Timeouts", ACM SIGCOMM Computer Communication Review, 33(2), April 2003. EXTERNAL
  • Gurtov A. and R. Ludwig, "Evaluating the Eifel Algorithm for TCP in a GPRS Network", In Proc. European Wireless, Florence, Italy, February 2002. EXTERNAL
  • Ludwig R. and R.H. Katz, "The Eifel Algorithm: Making TCP Robust Against Spurious Retransmissions", ACM SIGCOMM Computer Communication Review, 30(1), January 2000. EXTERNAL
  • Yamamoto, K., et al., "Effects of F-RTO and Eifel Response Algorithms for W-CDMA and HSDPA networks", In Proc. Wireless Personal Multimedia Communications (WPMC'05), September 2005. EXTERNAL
  • Gurtov A. and R. Ludwig, "Responding to Spurious Timeouts in TCP", In Proc. IEEE INFOCOM 03, San Francisco, CA, USA, March 2003. EXTERNAL
  • Swami Y. and K. Le, "DCLOR: De-correlated Loss Recovery using SACK Option for spurious timeouts", Work in Progress, September 2003. EXTERNAL
  • Hokamura, A., et al., "Performance Evaluation of F-RTO and Eifel Response Algorithms over W-CDMA packet network", In Proc. Wireless Personal Multimedia Communications (WPMC'05), Sept. 2005. EXTERNAL
  • Jacobson, V., "Congestion Avoidance and Control", In Proc. ACM SIGCOMM 88. EXTERNAL
  • Sarolahti, P., "Congestion Control on Spurious TCP Retransmission Timeouts", In Proc. of IEEE Globecom 2003, San Francisco, CA, USA. December 2003. EXTERNAL
  • Blanton, J., Blanton, E., and M. Allman, "Using Spurious Retransmissions to Adapt the Retransmission Timeout", Work in Progress, December 2006. EXTERNAL
  • IETF RFC 896 [Superseded*]
  • IETF RFC 1323 [Superseded*]
  • IETF RFC 2883 [Active*]
  • IETF RFC 3042 [Active*]
  • IETF RFC 3522 [Active*]
  • IETF RFC 3708 [Active*]
  • IETF RFC 4015 [Active*]
  • IETF RFC 4138 [Active*]
  • IETF RFC 4960 [Superseded*]
Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC5682.json

Amends:
IETF RFC 4138 [Active*]

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 5682, Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP. Available at https://doi.org/10.17487/RFC5682
Snippet:
IETF RFC 5682, Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP. Available at https://doi.org/10.17487/RFC5682

HTML (ISO 690 compliant)

Preview:
IETF RFC 5682, Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP. Available at https://doi.org/10.17487/RFC5682
Snippet:
<span class="citation"><cite>IETF RFC 5682</cite>, Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP. Available at <a href="https://doi.org/10.17487/RFC5682" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5682</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 5682, Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP
doi: 10.17487/RFC5682
url: https://doi.org/10.17487/RFC5682
Snippet:
<li>
<cite id="bib-rfc5682">IETF RFC 5682</cite>, Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP
<span class="doi">10.17487/RFC5682</span>
</li>

Referenced By