Hello All , Well ECN is now an RFC . Twyl , JimL
ps: About bloody time .
+------------------------------------------------------------------+
| James W. Laferriere | System Techniques | Give me VMS |
| Network Engineer | P.O. Box 854 | Give me Linux |
| babydr@baby-dragons.com | Coudersport PA 16915 | only on AXP |
+------------------------------------------------------------------+
---------- Forwarded message ----------
Date: Fri, 19 Oct 2001 15:49:11 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
To: IETF-Announce: ;
Cc: rfc-ed@ISI.EDU, tsvwg@ietf.org
Subject: RFC 3168 on The Addition of ECN to IP
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.
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/rfc3168.txt>
-
