The Addition of Explicit Congestion Notification (ECN) to IP
draft-ietf-tsvwg-ecn-04

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3168.
Authors Sally Floyd, Dr. K. K. Ramakrishnan , David L. Black
Last updated 2020-01-21 (Latest revision 2001-06-08)
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status Proposed Standard
Formats
txt htmlized pdf bibtex bibxml
Additional resources Mailing list discussion
Stream WG state (None)
Document shepherd (None)
IESG IESG state Became RFC 3168 (Proposed Standard)
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)
Email authors Email WG IPR References Referenced by Nits Search email archive
draft-ietf-tsvwg-ecn-04 
A new Request for Comments is now available in online RFC libraries.

        RFC 3168

        Title:      The Addition of Explicit Congestion Notification
                    (ECN) to IP
        Author(s):  K. Ramakrishnan, S. Floyd, D. Black
        Status:     Standards Track
        Date:       September 2001
        Mailbox:    kk@teraoptic.com, floyd@aciri.org,
                    black_david@emc.com 
        Pages:      63
        Characters: 170966
        Updates:    2474, 2401, 793
        Obsoletes:  2481 

        I-D Tag:    draft-ietf-tsvwg-ecn-04.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3168.txt

This memo specifies the incorporation of ECN (Explicit Congestion
Notification) to TCP and IP, including ECN's use of two bits in the
IP header.

This document is a product of the Transport Area 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.