RFC 3465: TCP Congestion Control with Appropriate Byte Counting (ABC)
In plain English — editorial summary, not part of the RFC
This document proposes a small modification to the way TCP increases its congestion window. Rather than the traditional method of increasing the congestion window by a constant amount for each arriving acknowledgment, the document suggests basing the increase on the number of previously unacknowledged bytes each ACK covers. This change improves the performance of TCP, as well as closes a security hole TCP receivers can use to induce the sender into increasing the sending rate too rapidly. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC3465
- Published
- February 2003
- Authors
- M. Allman
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- —
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3430Simple Network Management Protocol Over Transmission Control Protocol Transport MappingCurrent
December 2002
- RFC 3517A Conservative Selective Acknowledgment (SACK)-based Loss Recovery Algorithm for TCPObsoleted
April 2003
- RFC 3522The Eifel Detection Algorithm for TCPCurrent
April 2003
- RFC 3390Increasing TCP's Initial WindowCurrent
November 2002
- RFC 3540Robust Explicit Congestion Notification (ECN) Signaling with NoncesCurrent
June 2003
- RFC 3347Small Computer Systems Interface protocol over the Internet (iSCSI) Requirements and Design ConsiderationsCurrent
July 2002
- RFC 3293General Switch Management Protocol (GSMP) Packet Encapsulations for Asynchronous Transfer Mode (ATM), Ethernet and Transmission Control Protocol (TCP)Current
June 2002
- RFC 3649HighSpeed TCP for Large Congestion WindowsCurrent
December 2003
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?