From: Simon Barber <simon@superduper.net>
To: "Eggert, Lars" <lars@netapp.com>
Cc: cake@lists.bufferbloat.net, dpreed@reed.com, "Klatsky,
Carl" <carl_klatsky@cable.comcast.com>,
cerowrt-devel@lists.bufferbloat.net,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Cerowrt-devel] heisenbug: dslreports 16 flow test vs cablemodems
Date: Mon, 18 May 2015 05:30:45 -0700 [thread overview]
Message-ID: <14d67011de0.27f7.e972a4f4d859b00521b2b659602cb2f9@superduper.net> (raw)
In-Reply-To: <EC8BD2B0-F62E-4F0E-BE19-3618304F1A25@netapp.com>
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
I am likely out of date about Windows Update, but there's many other
programs that do background downloads or uploads that don't implement
LEDBAT or similar protection. The current AQM recommendation draft in the
IETF will make things worse, by not drawing attention to the fact that
implementing AQM without implementing a low priority traffic class (such as
DSCP 8 - CS1) will prevent solutions like LEDBAT from working, or there
being any alternative. Would appreciate support on the AQM list in the
importance of this.
Simon
Sent with AquaMail for Android
http://www.aqua-mail.com
On May 18, 2015 4:42:43 AM "Eggert, Lars" <lars@netapp.com> wrote:
> On 2015-5-18, at 07:06, Simon Barber
> <simon@superduper.net<mailto:simon@superduper.net>> wrote:
> Windows update will kill your Skype call.
>
> Really? AFAIK Windows Update has been using a LEDBAT-like scavenger-type
> congestion control algorithm for years now.
>
> Lars
[-- Attachment #2: Type: text/html, Size: 2125 bytes --]
next prev parent reply other threads:[~2015-05-18 12:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 19:13 [Bloat] " Dave Taht
2015-05-15 2:48 ` Greg White
2015-05-15 4:44 ` [Bloat] [Cerowrt-devel] " Aaron Wood
2015-05-15 8:18 ` Eggert, Lars
2015-05-15 8:55 ` Sebastian Moeller
2015-05-15 17:40 ` Rick Jones
2015-05-16 7:25 ` Eggert, Lars
2015-05-15 11:27 ` Bill Ver Steeg (versteb)
2015-05-15 12:19 ` Jonathan Morton
2015-05-15 12:44 ` Eggert, Lars
2015-05-15 13:09 ` Bill Ver Steeg (versteb)
2015-05-15 13:35 ` Jim Gettys
2015-05-15 14:36 ` Simon Barber
2015-05-18 3:30 ` dpreed
2015-05-18 5:06 ` Simon Barber
2015-05-18 9:06 ` Bill Ver Steeg (versteb)
2015-05-18 11:42 ` Eggert, Lars
2015-05-18 11:57 ` luca.muscariello
2015-05-18 12:30 ` Simon Barber [this message]
2015-05-18 15:03 ` Jonathan Morton
2015-05-18 15:09 ` dpreed
2015-05-18 15:26 ` Steinar H. Gunderson
2015-05-18 15:32 ` Simon Barber
2015-05-18 17:21 ` [Bloat] [Cake] " Dave Taht
2015-05-18 15:40 ` [Bloat] " Jonathan Morton
2015-05-18 17:03 ` Sebastian Moeller
2015-05-18 17:17 ` Jonathan Morton
2015-05-18 18:14 ` Sebastian Moeller
2015-05-18 18:37 ` Dave Taht
2015-05-19 16:25 ` [Bloat] [Cake] " Sebastian Moeller
2015-05-15 16:59 ` [Bloat] " Dave Taht
2015-05-15 17:47 ` [Bloat] " Dave Taht
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=14d67011de0.27f7.e972a4f4d859b00521b2b659602cb2f9@superduper.net \
--to=simon@superduper.net \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=carl_klatsky@cable.comcast.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dpreed@reed.com \
--cc=lars@netapp.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