General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Kathleen Nichols <nichols@pollere.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Fixing bufferbloat in 2017
Date: Sun, 27 Nov 2016 18:11:50 -0800	[thread overview]
Message-ID: <65cde0ee-4cc8-22c8-5274-a4eafe9cf338@pollere.com> (raw)
In-Reply-To: <CAA93jw7ue=2mwQ1H9=8RSDPE5Hxtutp9qvWt=orD6vHEeWuNzQ@mail.gmail.com>


I never have any problem hearing you, Dave.

Random stuff in-line.

On 11/27/16 1:24 PM, Dave Taht wrote:
> There *are* 430+ other minds on this mailing list, and probably a few
> AIs.
> 
> Sometimes I worry that most of our postings go into spamboxes now,
> or that we've somehow completely burned people out since our heyday
> in 2012.
> 
> knock, knock - is this mic on?
> 
> On Sat, Nov 26, 2016 at 7:33 AM, Rich Brown <richb.hanover@gmail.com>
> wrote:
...
>> 
>> My impression is that we have reached a strong technical point. We
>> have solved some really hard, really significant problems. We are
>> in a position to Declare Victory on a large part of the problem,
>> even though there are loads of details to clean up.

I think this is important. Some really good work has been done by a lot of
people on this list and I have found it interesting, enlightening and
gratifying to
put some small bit of a solution out there and have people grab it,
improve it,
add to it and make it real. So I think people doing that work should pat
themselves on the
back.
>> 
>> Most of the suggestions in this thread deal with Getting the Word
>> Out. That's good - that's the declaring victory part. The bad news
>> is that this is not our collective skill set.

So that's the hard part. Who do you need to Get the Word Out to and what
do you expect them to do? It sounds like there are some edge router
improvements coming. It's possible that some companies are using the
work but they are advertising what it does for the customer not where it
came from or what it is technically. So that might be a victory.
>> 
...
>> 4) Do we know people at any of the cell phone companies, or router
>> vendors on whom we could try one last push?
>> 
>> As part of organizing my thoughts for this note, I also collected
>> the following ideas from this thread. I add my $0.02 below.

Well, getting cellular networks on board would be a coup.
>> 
>> Rich
>> 
>> 1) I don't see that Ookla has much incentive to include bufferbloat
>> measurements in their test, since they private-label it for lots of
>> ISPs who (presumably) wouldn't want their CPE to be proven crappy.
>> ("It is difficult to get a man to understand something, when his
>> salary depends upon his not understanding it!" -Upton Sinclair)

This is, sadly, likely correct.
>> 
>> 2) The gamer community seems like such a perfect target for these
>> improvements. But I fear that the thought leaders are so wrapped up
>> in the fame generated by their own clever QoS tricks that they
>> can't believe that fq_codel plus the make-wifi-fast fixes could
>> possibly address such a complicated subject. (Upton Sinclair,
>> again.)

But where do you find who benefits and who can have an effect? I don't
know anything about these traffic patterns but would be interested in
seeing them if possible.
>> 
>> 3) On the other hand, Comcast (whose DOCSIS modems *might* someday
>> support PIE or other SQM) is in a position to benefit from an
>> increased awareness of the phenomenon, leaving a little ray of
>> hope.

I don't know. I think it has to be a more serious goal at Comcast. The
bufferbloat measurement devices they sent out were electrically
problematic, taking our signal down and reducing bandwidth.  This seems
like one step above skunkworks.
...
>> 6) It *is* a good idea to think about attracting the attention of
>> vendors who are hurt by bufferbloat - VoIP, video streaming folks,
>> gaming companies, etc. But it feels like the wrong end of the lever
>> - a gaming company can't fix crappy CPE, and they're stuck saying

Yes, it's hard for the victims unless there is an alternative or they
wield a large amount of coordinated monetary power. The video streaming
folks, from my measurements, are trashing themselves. Why are they
creating such huge bursts? Why send out bursts that are going to arrive
at the same time? This isn't a bufferbloat problem really, it's a clue
problem.
>> 
>> 7) Cell phones are another place that obviously would benefit,
>> although, again, it's hard to break through the notion that "It's
>> always been like that..."

Yes, but who would benefit? Is it a content company that could put
pressure on some carrier?
>> 
>> What else?

This is good thinking, Rich, but the business side of the current
"ecosystem" seems disincentivized to progress.
>> 
>> Rich
>> 
>> _______________________________________________ Bloat mailing list 
>> Bloat@lists.bufferbloat.net 
>> https://lists.bufferbloat.net/listinfo/bloat
> 
> 
> 


  reply	other threads:[~2016-11-28  2:11 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.454.1479929363.3555.bloat@lists.bufferbloat.net>
2016-11-26 15:33 ` 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 [this message]
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
     [not found] <mailman.447.1479909940.3555.bloat@lists.bufferbloat.net>
2016-11-23 18:16 ` [Bloat] fixing " 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
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
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

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=65cde0ee-4cc8-22c8-5274-a4eafe9cf338@pollere.com \
    --to=nichols@pollere.com \
    --cc=bloat@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