Re: [Bloat] Fixing bufferbloat in 2017

2016-11-27 Thread Jan Ceuleers
On 28/11/16 03:16, Jim Gettys wrote: > Ookla may have made themselves long term irrelevant by their recent > behavior. When your customers start funding development of a > replacement (as Comcast has), you know they aren't happy. > > So I don't sweat Ookla: helping out the Comcast test effort is

Re: [Bloat] Fixing bufferbloat in 2017

2016-11-27 Thread David Lang
On Sun, 27 Nov 2016, Kathleen Nichols wrote: 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

Re: [Bloat] Fixing bufferbloat in 2017

2016-11-27 Thread Jim Gettys
This went by in a previous posting I made: Ookla may have made themselves long term irrelevant by their recent behavior. When your customers start funding development of a replacement (as Comcast has), you know they aren't happy. So I don't sweat Ookla: helping out the Comcast test effort is

Re: [Bloat] Fixing bufferbloat in 2017

2016-11-27 Thread Kathleen Nichols
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

Re: [Bloat] Fixing bufferbloat in 2017

2016-11-27 Thread Dave Taht
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