BCP 41, RFC 2914 on Congestion Control Principles

RFC Editor <rfc-ed@ISI.EDU> Fri, 15 September 2000 01:05 UTC

Message-Id: <200009150036.RAA25606@boreas.isi.edu>
To: IETF-Announce:;
Subject: BCP 41, RFC 2914 on Congestion Control Principles
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 14 Sep 2000 17:36:03 -0700
From: RFC Editor <rfc-ed@ISI.EDU>

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


        BCP 41
        RFC 2914

        Title:	    Congestion Control Principles
        Author(s):  S. Floyd
        Status:     Best Current Practice
	Date:       September 2000
        Mailbox:    floyd@aciri.org
        Pages:      17
        Characters: 43823
        Updates/Obsoletes/SeeAlso:  None

        I-D Tag:    draft-floyd-cong-04.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2914.txt


The goal of this document is to explain the need for congestion
control in the Internet, and to discuss what constitutes correct
congestion control.  One specific goal is to illustrate the dangers
of neglecting to apply proper congestion control.  A second goal is
to discuss the role of the IETF in standardizing new congestion
control protocols.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  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 Sandy Ginoza
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/rfc2914.txt"><ftp://ftp.isi.edu/in-notes/rfc2914.txt>

BCP 41, RFC 2914 on Congestion Control Principles RFC Editor