RFC 2481 on ECN to IP

RFC Editor <rfc-ed@ISI.EDU> Sat, 16 January 1999 01:15 UTC

Message-Id: <199901152045.MAA20908@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2481 on ECN to IP
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 15 Jan 1999 12:45:16 -0800
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 2481:

        Title:      A Proposal to add Explicit Congestion Notification
		    (ECN) to IP
	Author(s):  K. Ramakrishnan, S. Floyd
	Status:     Experimental
	Date:       January 1999
        Mailbox:    kkrama@research.att.com, floyd@ee.lbl.gov
	Pages:      25
        Characters: 64559
        Updates/Obsoletes/See Also: None 
        I-D Tag:    draft-kksjf-ecn-03.txt


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


This note describes a proposed addition of ECN (Explicit Congestion
Notification) to IP.  TCP is currently the dominant transport
protocol used in the Internet. We begin by describing TCP's use of
packet drops as an indication of congestion.  Next we argue that with
the addition of active queue management (e.g., RED) to the Internet
infrastructure, where routers detect congestion before the queue
overflows, routers are no longer limited to packet drops as an
indication of congestion.  Routers could instead set a Congestion
Experienced (CE) bit in the packet header of packets from ECN-capable
transport protocols.  We describe when the CE bit would be set in the
routers, and describe what modifications would be needed to TCP to
make it ECN-capable.  Modifications to other transport protocols
(e.g., unreliable unicast or multicast, reliable multicast, other
reliable unicast transport protocols) could be considered as those
protocols are developed and advance through the standards process.
 
This memo defines an Experimental Protocol for the Internet community.
It does not specify an Internet standard of any kind.  Discussion and 
suggestions for improvement are requested.  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/rfc2481.txt"><ftp://ftp.isi.edu/in-notes/rfc2481.txt>

RFC 2481 on ECN to IP RFC Editor