From: Yee-Ting Li <Yee-Ting.Li@nuim.ie>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Douglas Leith <doug.leith@nuim.ie>,
linux-net@vger.kernel.org, rhee@ncsu.edu,
Yee-Ting Li <Yee-Ting.Li@nuim.ie>,
linux-kernel@vger.kernel.org, Baruch Even <baruch@ev-en.org>,
Les Cottrell <cottrell@slac.stanford.edu>,
Richard Hughes-Jones <r.hughes-jones@man.ac.uk>,
davem@davemloft.net
Subject: Re: BicTCP Implementation Bug
Date: Mon, 21 Feb 2005 16:15:16 +0000 [thread overview]
Message-ID: <0d8ea68bba9feb62ffd08d085b47e48c@may.ie> (raw)
In-Reply-To: <421A0337.6020601@osdl.org>
We just wanted to be sure of the implementation against the official
BicTCP versions and that it was a real bug.
We are particularly concerned that the deployment of these experimental
protocols (and they're not even RFCs) are too premature and that we
think that they should be switched OFF by default to prevent
undesirable consequences to network stability. One concern is that such
protocols will steal (sometimes a lot of) bandwidth from normal network
traffic.
We wrote the paper as we (amongst others) are in the process of
rigourously validating and testing these TCP proposals over a wide
range of network environments There are also numerous other proposals
around (HSTCP, ScalableTCP, HTCP, FAST etc) that we are also testing
and we would be more than happy to provide patches (excluding FAST) and
experimental results as they become available.
Yee.
On Feb 21, 2005, at 15:50, Stephen Hemminger wrote:
> Yes, this looks like a bug, let me verify it first.
> Why did you sit on this so long and go to all the trouble of making a
> paper out of it?
>
next prev parent reply other threads:[~2005-02-21 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 13:47 BicTCP Implementation Bug Yee-Ting Li
2005-02-21 15:50 ` Stephen Hemminger
2005-02-21 16:15 ` Yee-Ting Li [this message]
2005-02-21 17:06 ` Gene Heskett
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=0d8ea68bba9feb62ffd08d085b47e48c@may.ie \
--to=yee-ting.li@nuim.ie \
--cc=baruch@ev-en.org \
--cc=cottrell@slac.stanford.edu \
--cc=davem@davemloft.net \
--cc=doug.leith@nuim.ie \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=r.hughes-jones@man.ac.uk \
--cc=rhee@ncsu.edu \
--cc=shemminger@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.