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

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…

Read RFC 5682 on the RFC Editor

Outgoing relationships (9 related RFCs)

Updates, Informative reference — RFC 4138: Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP and the Stream Control Transmission Protocol (SCTP)
Informative reference — RFC 4960: Stream Control Transmission Protocol
Informative reference — RFC 1323: TCP Extensions for High Performance
Informative reference — RFC 896: Congestion Control in IP/TCP Internetworks
Informative reference — RFC 3042: Enhancing TCP's Loss Recovery Using Limited Transmit
Informative reference — RFC 2883: An Extension to the Selective Acknowledgement (SACK) Option for TCP
Informative reference — RFC 3522: The Eifel Detection Algorithm for TCP
Informative reference — RFC 3708: Using TCP Duplicate Selective Acknowledgement (DSACKs) and Stream Control Transmission Protocol (SCTP) Duplicate Transmission Sequence Numbers (TSNs) to Detect Spurious Retransmissions
Informative reference — RFC 4015: The Eifel Response Algorithm for TCP

Incoming relationships (4 related RFCs)

Normatively referenced by — RFC 7414: A Roadmap for Transmission Control Protocol (TCP) Specification Documents
Normatively referenced by — RFC 9438: CUBIC for Fast and Long-Distance Networks
Informatively referenced by — RFC 8961: Requirements for Time-Based Loss Detection
Informatively referenced by — RFC 7786: TCP Modifications for Congestion Exposure (ConEx)