RFC 6069: Making TCP More Robust to Long Connectivity Disruptions (TCP-LCD)
In plain English — editorial summary, not part of the RFC
Disruptions in end-to-end path connectivity, which last longer than one retransmission timeout, cause suboptimal TCP performance. The reason for this performance degradation is that TCP interprets segment loss induced by long connectivity disruptions as a sign of congestion, resulting in repeated retransmission timer backoffs. This, in turn, leads to a delayed detection of the re-establishment of the connection since TCP waits for the next retransmission timeout before it attempts a retransmission. This document proposes an algorithm to make TCP more robust to long connectivity disruptions (TCP-LCD). It describes how standard ICMP messages can be exploited during timeout-based loss recovery to disambiguate true congestion loss from non-congestion loss caused by connectivity disruptions. Moreover, a reversion strategy of the retransmission timer is specified that enables a more prompt detection of whether or not the connectivity to a previously disconnected peer node has been restored. TCP-LCD is a TCP sender- only modification that effectively improves TCP performance in the case of connectivity disruptions. This document defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC6069
- Published
- December 2010
- Authors
- A. Zimmermann; A. Hannemann
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- wit
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8095Services Provided by IETF Transport Protocols and Congestion Control MechanismsCurrent
March 2017
- RFC 6056Recommendations for Transport-Protocol Port RandomizationCurrent
January 2011
- RFC 6083Datagram Transport Layer Security (DTLS) for Stream Control Transmission Protocol (SCTP)Updated
January 2011
- RFC 6093On the Implementation of the TCP Urgent MechanismObsoleted
January 2011
- RFC 6096Stream Control Transmission Protocol (SCTP) Chunk Flags RegistrationObsoleted
January 2011
- RFC 6040Tunnelling of Explicit Congestion NotificationUpdated
November 2010
- RFC 6016Support for the Resource Reservation Protocol (RSVP) in Layer 3 VPNsCurrent
October 2010
- RFC 5961Improving TCP's Robustness to Blind In-Window AttacksUpdated
August 2010
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?