General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jim Gettys <jg@freedesktop.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: Jan Ceuleers <jan.ceuleers@gmail.com>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] fixing bufferbloat in 2017
Date: Tue, 22 Nov 2016 11:38:58 -0500	[thread overview]
Message-ID: <CAGhGL2ABDpCiT80LhYYXi9dTAj5-HRdznF9zhstm9PQo=HvwBA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4dsy2TfYU4UOzxA6Xion37UeFErSSmQ0qJv9-rZngw3w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2229 bytes --]

On Tue, Nov 22, 2016 at 11:25 AM, Dave Taht <dave.taht@gmail.com> wrote:

> On Tue, Nov 22, 2016 at 8:19 AM, Jan Ceuleers <jan.ceuleers@gmail.com>
> wrote:
> > On 22/11/16 16:32, Dave Taht wrote:
> >> What's left to do?
> >
> > Furthering adoption of the code that contains the bloat-related
> > improvements.
> >
> > In my view, the single biggest potential contributor towards driving
> > such adoption would be for Ookla to start measuring and reporting
> > bufferbloat, thereby putting it on the agenda of both end users and
> > carriers (who use Ookla's servers to qualify equipment in their labs).
> > That would in turn put it on the agenda of equipment manufacturers.
>

​May not matter too much longer...​


>
> We've been after ookla for years. Samknows, also. The FCC, too. But
> how to raise awareness further? An open letter? A petition to the
> white house? A press release?
>
> Until then, there's always dslreports and a few other sites.
>

​Comcast has/is funding development of an open source speed test, and the
intent is to
have a bufferbloat test in it.

Several ISP's are on board with it in addition to Comcast and are helping
too.

You can improve the code...  I can dig up the link if someone is hot to
trot.
Right now, we're discussing how to license the code, however.  I don't know
what the final
outcome of that will be.
​


>
> I would like to see the industries most affected by bufferbloat -
> voip/videoconferencing/gaming,web gain a good recognition of the
> problem, how to fix it, and who to talk to about it (router makers and
> ISPs)
>

​Getting cellular manufacturers to understand would also be a good thing,
IMHO.
                                               - Jim
​


>
>
>
> > _______________________________________________
> > Bloat mailing list
> > Bloat@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/bloat
>
>
>
> --
> Dave Täht
> Let's go make home routers and wifi faster! With better software!
> http://blog.cerowrt.org
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>

[-- Attachment #2: Type: text/html, Size: 4784 bytes --]

  reply	other threads:[~2016-11-22 16:38 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22 15:32 Dave Taht
2016-11-22 16:19 ` Jan Ceuleers
2016-11-22 16:25   ` Dave Taht
2016-11-22 16:38     ` Jim Gettys [this message]
2016-11-23  8:28     ` Mikael Abrahamsson
2016-11-23 11:04       ` Jonathan Morton
2016-11-23 11:59       ` Kelvin Edmison
2016-11-23 13:31         ` Pedro Tumusok
2016-11-23 14:05           ` Mário Sérgio Fujikawa Ferreira
2016-11-23 17:20           ` Mikael Abrahamsson
2016-11-23 17:27             ` Benjamin Cronce
2016-11-23 17:31               ` Mikael Abrahamsson
2016-11-23 17:40                 ` Sebastian Moeller
2016-11-23 17:50                 ` Noah Causin
2016-11-23 17:56                   ` David Lang
2016-11-23 18:05                     ` Benjamin Cronce
2016-11-23 18:38                       ` David Lang
2016-11-23 19:29                         ` Benjamin Cronce
2016-11-23 19:42                           ` David Lang
2016-11-23 20:20                             ` Dave Taht
2016-11-23 17:54                 ` David Lang
2016-11-23 18:09                   ` Mikael Abrahamsson
2016-11-23 18:18                     ` Sebastian Moeller
2016-11-23 18:24                       ` Dave Taht
2016-11-23 20:39                         ` Toke Høiland-Jørgensen
2016-11-23 19:13                       ` David Lang
2016-11-23 18:17                   ` Dave Taht
2016-11-23 15:32 ` Pedretti Fabio
2016-11-23 19:29   ` Stephen Hemminger
2016-11-23 19:22 ` Dave Taht
     [not found] <mailman.447.1479909940.3555.bloat@lists.bufferbloat.net>
2016-11-23 18:16 ` Rich Brown
2016-11-23 18:46   ` David Lang
2016-11-23 18:58     ` Jonathan Morton
2016-11-23 19:15       ` David Lang
2016-11-23 20:37       ` Toke Høiland-Jørgensen
     [not found] <mailman.454.1479929363.3555.bloat@lists.bufferbloat.net>
2016-11-26 15:33 ` [Bloat] Fixing " Rich Brown
2016-11-27  1:53   ` Aaron Wood
2016-11-27  6:10     ` Mikael Abrahamsson
2016-11-27 21:24   ` Dave Taht
2016-11-28  2:11     ` Kathleen Nichols
2016-11-28  2:16       ` Jim Gettys
2016-11-28  6:00         ` Jan Ceuleers
2016-11-28 12:48           ` David Collier-Brown
2016-11-28 15:12             ` Dave Taht
2016-11-28 15:23               ` Wesley Eddy
2016-11-28 15:35                 ` Dave Taht
2016-11-28 16:58                   ` Stephen Hemminger
2016-11-28 17:07                     ` Dave Taht
2016-11-28 19:02                       ` Jonathan Morton
2016-11-28 17:52                     ` Kathleen Nichols
2016-11-28 15:14             ` Pedro Tumusok
2016-11-28 15:23               ` Dave Taht
2016-11-28 15:10           ` Dave Taht
2016-11-28  2:47       ` David Lang

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='CAGhGL2ABDpCiT80LhYYXi9dTAj5-HRdznF9zhstm9PQo=HvwBA@mail.gmail.com' \
    --to=jg@freedesktop.org \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=jan.ceuleers@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