From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] geoff huston's take on BBR
Date: Tue, 12 Jun 2018 05:58:22 +0000 [thread overview]
Message-ID: <E42E4246-E107-4A04-B1B2-7486B59EC39C@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAA93jw48Eh4EAuinccfnn9hs77BzBERCSsc4errdnumd8BgTOw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 629 bytes --]
> On 11 Jun 2018, at 22:27, Dave Taht <dave.taht@gmail.com> wrote:
>
> https://ripe76.ripe.net/presentations/10-2018-05-15-bbr.pdf
Fascinating!
" • BBR changes all those assumptions, and could potentially push many networks into sustained instability
• – We cannot use the conventional network control mechanisms to regulate BBR flows
• Selective packet drop just won’t create back pressure on the flow”
And I keep on seeing questions on whether BBR understands ECN - if not…. well I think we see the results.
Cheers,
Kevin D-B
012C ACB2 28C6 C53E 9775 9123 B3A2 389B 9DE2 334A
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-06-12 5:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 21:27 Dave Taht
2018-06-12 0:42 ` Toke Høiland-Jørgensen
2018-06-12 5:09 ` Matthias Tafelmeier
2018-06-12 7:36 ` Bless, Roland (TM)
2018-06-12 11:40 ` Dave Taht
2018-06-12 12:00 ` Dave Taht
2018-06-12 17:06 ` Matthias Tafelmeier
2018-06-12 5:58 ` Kevin Darbyshire-Bryant [this message]
2018-06-12 6:55 Dave Taht
2018-06-12 7:49 ` Geoff Huston
2018-06-12 11:25 ` Dave Taht
2018-06-12 15:58 ` Bless, Roland (TM)
2018-06-12 23:02 ` Geoff Huston
2018-06-13 7:56 ` Bless, Roland (TM)
2018-06-12 22:28 ` Greg White
2018-06-12 23:04 ` Anna Brunstrom
2018-06-12 14:29 ` Jim Gettys
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=E42E4246-E107-4A04-B1B2-7486B59EC39C@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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