RFC 3649: HighSpeed TCP for Large Congestion Windows
In plain English — editorial summary, not part of the RFC
The proposals in this document are experimental. While they may be deployed in the current Internet, they do not represent a consensus that this is the best method for high-speed congestion control. In particular, we note that alternative experimental proposals are likely to be forthcoming, and it is not well understood how the proposals in this document will interact with such alternative proposals. This document proposes HighSpeed TCP, a modification to TCP's congestion control mechanism for use with TCP connections with large congestion windows. The congestion control mechanisms of the current Standard TCP constrains the congestion windows that can be achieved by TCP in realistic environments. For example, for a Standard TCP connection with 1500-byte packets and a 100 ms round-trip time, achieving a steady-state throughput of 10 Gbps would require an average congestion window of 83,333 segments, and a packet drop rate of at most one congestion event every 5,000,000,000 packets (or equivalently, at most one congestion event every 1 2/3 hours). This is widely acknowledged as an unrealistic constraint. To address his limitation of TCP, this document proposes HighSpeed TCP, and solicits experimentation and feedback from the wider community.
Document record
- Document ID
- RFC3649
- Published
- December 2003
- Authors
- S. Floyd
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- wit
- Pages
- 34
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3742Limited Slow-Start for TCP with Large Congestion WindowsCurrent
March 2004
- RFC 3540Robust Explicit Congestion Notification (ECN) Signaling with NoncesCurrent
June 2003
- RFC 3522The Eifel Detection Algorithm for TCPCurrent
April 2003
- RFC 3517A Conservative Selective Acknowledgment (SACK)-based Loss Recovery Algorithm for TCPObsoleted
April 2003
- RFC 3782The NewReno Modification to TCP's Fast Recovery AlgorithmObsoleted
April 2004
- RFC 3390Increasing TCP's Initial WindowCurrent
November 2002
- RFC 4138Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP and the Stream Control Transmission Protocol (SCTP)Updated
August 2005
- RFC 3042Enhancing TCP's Loss Recovery Using Limited TransmitCurrent
January 2001
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?