RFC 2581 on TCP Congestion Control

RFC Editor <rfc-ed@ISI.EDU> Fri, 09 April 1999 00:15 UTC

Received: by ietf.org (8.9.1a/8.9.1a) id UAA08008 for ietf-123-outbound.10@ietf.org; Thu, 8 Apr 1999 20:15:02 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07644 for <all-ietf@ietf.org>; Thu, 8 Apr 1999 19:53:17 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id QAA06554; Thu, 8 Apr 1999 16:53:18 -0700 (PDT)
Message-Id: <199904082353.QAA06554@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2581 on TCP Congestion Control
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 08 Apr 1999 16:53:18 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

A new Request for Comments is now available in online RFC libraries.


        RFC 2581: 

        Title:	    TCP Congestion Control
	Author(s):  M. Allman, V. Paxson, W. Stevens
        Status:     Proposed Standard
	Date:       April 1999
        Mailbox:    mallman@grc.nasa.gov, vern@aciri.org, 
		    rstevens@kohala.com
        Pages:      14	
        Characters: 31351
        Obsoletes:  2001
        I-D Tag:    draft-ietf-tcpimpl-cong-control-05.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2581.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
the IETF.

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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  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.
ftp://ftp.isi.edu/in-notes/rfc2581.txt"><ftp://ftp.isi.edu/in-notes/rfc2581.txt>