From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: RFC 3168 on The Addition of ECN to IP (fwd)
Date: Fri, 21 Sep 2001 15:19:36 +1000 [thread overview]
Message-ID: <7910.1001049576@kao2.melbourne.sgi.com> (raw)
For those people who complained that ECN was only a draft, it is now a
proposed standard. I wonder what excuse will be used now for not
upgrading the broken routers :).
------- Forwarded Message
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/Obsoletes/SeeAlso: None
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.
------- End of Forwarded Message
next reply other threads:[~2001-09-21 5:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-21 5:19 Keith Owens [this message]
2001-09-21 7:01 ` RFC 3168 on The Addition of ECN to IP (fwd) Kai Henningsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7910.1001049576@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox