From: "David L. Nicol" <david@kasey.umkc.edu>
To: Mark Hahn <hahn@coffee.psychology.mcmaster.ca>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: When will ETCP be in linux kernels? Is there a patch?
Date: Mon, 30 Jul 2001 16:28:48 -0500 [thread overview]
Message-ID: <3B65D190.BBF4C79A@kasey.umkc.edu> (raw)
In-Reply-To: <Pine.LNX.4.10.10107300127170.13088-100000@coffee.psychology.mcmaster.ca>
Mark Hahn wrote:
>
> > > > Will ETCP
> > > > http://www.chem.ucla.edu/~beichuan/etcp/
> > > > be appearing in linux kernels any time soon? We have ECN...
> > >
> > > isn't it just a draft? I though ECN was considerably further along...
> >
> > No, it works -- if you set up a BSD system and apply their patch,
> > the second image loads fully too -- I did it once, and it worked
> > just like it is supposed to.
>
> that wasn't the question: is it just a draft, or a standard like ECN?
> whether there's working code is orthogonal to it's standardization...
A working implementation (blessed by Christian Huitama) is IMO a defacto
standard.
I inquired of the TCP-IMPL working group about setting something like
ETCP up, to the point of submitting an independent proposal pretty much
describing it, and was referred to the ETCP demonstration.
--
David Nicol 816.235.1187
Cell phones are pretty much what Marconi had in mind, you know?
next parent reply other threads:[~2001-07-30 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10107300127170.13088-100000@coffee.psychology.mcmaster.ca>
2001-07-30 21:28 ` David L. Nicol [this message]
[not found] <Pine.LNX.4.10.10107240243420.30900-100000@coffee.psychology.mcmaster.ca>
2001-07-24 20:56 ` David L. Nicol
2001-07-24 2:03 David L. Nicol
2001-07-24 17:14 ` Rik van Riel
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=3B65D190.BBF4C79A@kasey.umkc.edu \
--to=david@kasey.umkc.edu \
--cc=hahn@coffee.psychology.mcmaster.ca \
--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
all inboxes | Powered by JetHome®