From: kaih@khms.westfalen.de (Kai Henningsen)
To: linux-kernel@vger.kernel.org
Subject: Re: RFC 3168 on The Addition of ECN to IP (fwd)
Date: 21 Sep 2001 09:01:00 +0200 [thread overview]
Message-ID: <89H08dn1w-B@khms.westfalen.de> (raw)
In-Reply-To: <7910.1001049576@kao2.melbourne.sgi.com>
In-Reply-To: <7910.1001049576@kao2.melbourne.sgi.com>
kaos@ocs.com.au (Keith Owens) wrote on 21.09.01 in <7910.1001049576@kao2.melbourne.sgi.com>:
> 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 :).
Guess.
MfG Kai
prev parent reply other threads:[~2001-09-21 7:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-21 5:19 RFC 3168 on The Addition of ECN to IP (fwd) Keith Owens
2001-09-21 7:01 ` Kai Henningsen [this message]
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=89H08dn1w-B@khms.westfalen.de \
--to=kaih@khms.westfalen.de \
--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