From: Dave Taht <dave.taht@gmail.com>
To: ECN-Sane <ecn-sane@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>,
BBR Development <bbr-dev@googlegroups.com>
Subject: [Bloat] BBRv2 presentation in ICCRG video
Date: Mon, 1 Apr 2019 11:58:36 +0200 [thread overview]
Message-ID: <CAA93jw7Hf6+7fkSmr8C+pRLsBkzE7in2H_mbOLB4tfmdB+-w9Q@mail.gmail.com> (raw)
So, it turns out the BBRv2 team was planning on using a
l4s-style/dctcp-ish ecn response. The video is up here:
https://www.youtube.com/watch?v=cJ-0Ti8ZlfE
alternatively, here:
http://mail.taht.net/~iccrg/IETF104-ICCRG-20190328-1610.webm
The Q&A session afterward (about 28 minutes in) showed that the BBRv2 team were
not even testing against fully deployed fq_codel's RFC3168 ecn
response and there were all
sorts of other fun questions following. So I think this answers Vint
"Seersucker"' Cerf's ecn-sane's team's
question "is ECN even needed for BBR?"
I'm SO glad we got our SCE alternative ready for publication in time
to reset the clock by a lot. The preso in tsvwg:
https://www.youtube.com/watch?v=JQmWyr0JDJM&t=1h3m50s
Also...
Over the last week, jonathan, pete, and rodney (and jason?) also got a
modified reno-style transport to
respond properly to SCE:
https://github.com/dtaht/bufferbloat-rfcs/tree/master/sce/results/prototype1
was the first one, the current one is even more excellent.
Fun times in the congestion control universe!
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
reply other threads:[~2019-04-01 9:58 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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw7Hf6+7fkSmr8C+pRLsBkzE7in2H_mbOLB4tfmdB+-w9Q@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bbr-dev@googlegroups.com \
--cc=bloat@lists.bufferbloat.net \
--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