RFC Editor: RFC 2581 on TCP Congestion Control
------- Forwarded Message
Subject: RFC 2581 on TCP Congestion Control
Date: Thu, 08 Apr 1999 16:53:18 -0700
From: RFC Editor <rfc-ed@...>
A new Request for Comments is now available in online RFC libraries.
Title: TCP Congestion Control
Author(s): M. Allman, V. Paxson, W. Stevens
Status: Proposed Standard
Date: April 1999
Mailbox: mallman@..., vern@...,
I-D Tag: draft-ietf-tcpimpl-cong-control-05.txt
his document defines TCP's four intertwined congestion control
algorithms: slow start, congestion avoidance, fast retransmit, and
fast recovery. In addition, the document specifies how TCP should
begin transmission after a relatively long idle period, as well as
discussing various acknowledgment generation methods.
This document is a product of the TCP Implementation Working Group of
This is now a Proposed Standard Protocol.
This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol. Distribution
of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@.... Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@....
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@... with the message body
help: ways_to_get_rfcs. For example:
Subject: getting rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@.... Unless
specifically noted otherwise on the RFC itself, all RFCs are for
Submissions for Requests for Comments should be sent to
RFC-EDITOR@.... Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute
Below is the data which will enable a MIME compliant Mail Reader
implementation to automatically retrieve the ASCII version
of the RFCs.
Content-Type: Multipart/Alternative; Boundary="OtherAccess"
------- End of Forwarded Message