RFC 7661: Updating TCP to Support Rate-Limited Traffic
In plain English — editorial summary, not part of the RFC
This document provides a mechanism to address issues that arise when TCP is used for traffic that exhibits periods where the sending rate is limited by the application rather than the congestion window. It provides an experimental update to TCP that allows a TCP sender to restart quickly following a rate-limited interval. This method is expected to benefit applications that send rate-limited traffic using TCP while also providing an appropriate response if congestion is experienced. This document also evaluates the Experimental specification of TCP Congestion Window Validation (CWV) defined in RFC 2861 and concludes that RFC 2861 sought to address important issues but failed to deliver a widely used solution. This document therefore reclassifies the status of RFC 2861 from Experimental to Historic. This document obsoletes RFC 2861.
Document record
- Document ID
- RFC7661
- Published
- October 2015
- Authors
- G. Fairhurst; A. Sathiaseelan; R. Secchi
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- wit
- Pages
- 21
- Also known as
- —
- Obsoletes:
- RFC 2861
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7605Recommendations on Using Assigned Transport Port NumbersCurrent
August 2015
- RFC 7560Problem Statement and Requirements for Increased Accuracy in Explicit Congestion Notification (ECN) FeedbackCurrent
August 2015
- RFC 7765TCP and Stream Control Transmission Protocol (SCTP) RTO RestartCurrent
February 2016
- RFC 8257Data Center TCP (DCTCP): TCP Congestion Control for Data CentersCurrent
October 2017
- RFC 6633Deprecation of ICMP Source Quench MessagesCurrent
May 2012
- RFC 8985The RACK-TLP Loss Detection Algorithm for TCPCurrent
February 2021
- RFC 9235TCP Authentication Option (TCP-AO) Test VectorsCurrent
May 2022
- RFC 6056Recommendations for Transport-Protocol Port RandomizationCurrent
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?