RFC 8985: The RACK-TLP Loss Detection Algorithm for TCP
In plain English — editorial summary, not part of the RFC
This document presents the RACK-TLP loss detection algorithm for TCP. RACK-TLP uses per-segment transmit timestamps and selective acknowledgments (SACKs) and has two parts. Recent Acknowledgment (RACK) starts fast recovery quickly using time-based inferences derived from acknowledgment (ACK) feedback, and Tail Loss Probe (TLP) leverages RACK and sends a probe packet to trigger ACK feedback to avoid retransmission timeout (RTO) events. Compared to the widely used duplicate acknowledgment (DupAck) threshold approach, RACK-TLP detects losses more efficiently when there are application-limited flights of data, lost retransmissions, or data packet reordering events. It is intended to be an alternative to the DupAck threshold approach.
Document record
- Document ID
- RFC8985
- Published
- February 2021
- Authors
- Y. Cheng; N. Cardwell; N. Dukkipati; P. Jha
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 29
- Also known as
- —
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 9235TCP Authentication Option (TCP-AO) Test VectorsCurrent
May 2022
- RFC 9406HyStart++: Modified Slow Start for TCPCurrent
May 2023
- RFC 8257Data Center TCP (DCTCP): TCP Congestion Control for Data CentersCurrent
October 2017
- RFC 9937Proportional Rate Reduction (PRR)Current
December 2025
- RFC 7765TCP and Stream Control Transmission Protocol (SCTP) RTO RestartCurrent
February 2016
- RFC 7661Updating TCP to Support Rate-Limited TrafficCurrent
October 2015
- RFC 7605Recommendations on Using Assigned Transport Port NumbersCurrent
August 2015
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?