From: Dave Taht <dave.taht@gmail.com>
To: ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: [Ecn-sane] sally floyd's ecn stuff
Date: Wed, 28 Aug 2019 18:17:46 -0700 [thread overview]
Message-ID: <CAA93jw4s+o544=M64YNE4gc184Xmf_Z84Dkj6ZDyekyfdwghAQ@mail.gmail.com> (raw)
vcp shows slow convergence times:
http://conferences.sigcomm.org/sigcomm/2005/paper-XiaSub.pdf
chock full of good stuff:
http://www.icir.org/floyd/ecn.html#alternate
and: http://www.icir.org/floyd/email/sf.97dec01.txt
"Somehow, it is still the case that roughly 95\% of the
traffic seems to be using some form of vaguely-conformant TCP,
the steady-state packet drop rate is not spiralling up to 10 or 20
percent, and congestion collapse has not yet hit. I think that we
shouldn't press our luck, and I think that deterrents are indeed
necessary, but I don't think that the addition of ECN makes the job of
providing such deterrents any more difficult, or any more pressing.
I think that the need for such deterrents is already pretty pressing..."
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
reply other threads:[~2019-08-29 1:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
List information: https://lists.bufferbloat.net/postorius/lists/ecn-sane.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw4s+o544=M64YNE4gc184Xmf_Z84Dkj6ZDyekyfdwghAQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=ecn-sane@lists.bufferbloat.net \
/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