Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: "David P. Reed" <dpreed@deepplum.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
Cc: "Sebastian Moeller" <moeller0@gmx.de>,
	"Jonathan Morton" <chromatix99@gmail.com>,
	"ecn-sane@lists.bufferbloat.net" <ecn-sane@lists.bufferbloat.net>,
	"tsvwg IETF list" <tsvwg@ietf.org>
Subject: Re: [Ecn-sane] [tsvwg] per-flow scheduling
Date: Thu, 27 Jun 2019 17:31:01 -0400 (EDT)	[thread overview]
Message-ID: <1561671061.42671176@apps.rackspace.com> (raw)
In-Reply-To: <2382048d-25de-df7e-f787-8ab0d606d3dc@gmail.com>

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


It's even worse. The FCC got focused on max speeds back in the day as its only way to think about Internet Access service. And I was serving on the FCC Technological Advisory Committee and also in its Spectrum Policy Task Force, then later involved in the rather confused discussions of Network Neutrality, where again "speed" in the "up-to" sense was the sole framing of the discussion.
 
Because it was mostly lawyers and lobbyists (not network engineers), this focus on max speed as the sole measure of quality ended up with a huge distortion of the discussion, strongly encouraged by the lobbyists who love confusion.
 
That said, max speed plays a role at all time scales in minimizing response time, but queuing delay has no constituency, even though its impact is FAR worse in real situations.
 
If the FCC and regulators (or even the DoD communications management layers)  ever start talking about queueing delay in shared network services, I will die of shock.
 
But we did have one HUGE temporary success. The speed test at DSL Reports measures lag under load, and calls it bufferbloat, and gives a reasonably scaled score.
 
When I talk to people who are interested in quality of Internet service, I point them at DSL Reports' speed test.
 
That is a big win.  However, marketers of Internet access services don't compete to get good scores at DSL Reports. Even "business" providers provide crappy scores.
 
Comcast Business in the South Bay does very poorly on bufferbloat for its high speed business services, for example. This is based on my measurements at my company.  I know some very high executives there, and Comcast is the only real game in town for us, so I tried to get the folks in Philadelphia to talk to the local managers. Turns out the local managers just refused to listen to the headquarters execs. They saw no monetary benefit in fixing anything (going from DOCSIS 2 to DOCSIS 3.1 which had already been on the market for several years would have fixed it, probably).
 
On Thursday, June 27, 2019 4:33pm, "Brian E Carpenter" <brian.e.carpenter@gmail.com> said:



> On 27-Jun-19 19:49, Sebastian Moeller wrote:
> ...
> > a considerable fraction of home-users seem obsessed in maxing out their
> access links and compare achievable rates; whether such behaviour shoud be
> encouraged is a different question.
> 
> I think this is encouraged by, or is even a direct result of, so called "speed
> tests" for use by consumers (such as https://www.speedtest.net/), and the way
> connectivity "speed" has been used as a marketing tool. At least where I live,
> "speed" is the main marketing tool for switching users to fibre instead of copper.
> No doubt it will be used as the main marketing tool for 5G too.
> 
> It's almost as if those marketing people don't understand queueing theory.
> 
> Brian
> 
> 
> 

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

  reply	other threads:[~2019-06-27 21:31 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-19 14:12 [Ecn-sane] " Bob Briscoe
2019-06-19 14:20 ` [Ecn-sane] [tsvwg] " Kyle Rose
2019-06-21  6:59 ` [Ecn-sane] " Sebastian Moeller
2019-06-21  9:33   ` Luca Muscariello
2019-06-21 20:37     ` [Ecn-sane] [tsvwg] " Brian E Carpenter
2019-06-22 19:50       ` David P. Reed
2019-06-22 20:47         ` Jonathan Morton
2019-06-22 22:03           ` Luca Muscariello
2019-06-22 22:09           ` David P. Reed
2019-06-22 23:07             ` Jonathan Morton
2019-06-24 18:57               ` David P. Reed
2019-06-24 19:31                 ` Jonathan Morton
2019-06-24 19:50                   ` David P. Reed
2019-06-24 20:14                     ` Jonathan Morton
2019-06-25 21:05                       ` David P. Reed
2019-06-24 21:25                   ` Luca Muscariello
2019-06-26 12:48             ` Sebastian Moeller
2019-06-26 16:31               ` David P. Reed
2019-06-26 16:53                 ` David P. Reed
2019-06-27  7:54                   ` Sebastian Moeller
2019-06-27  7:49                 ` Sebastian Moeller
2019-06-27 20:33                   ` Brian E Carpenter
2019-06-27 21:31                     ` David P. Reed [this message]
2019-06-28  7:49                       ` Toke Høiland-Jørgensen
2019-06-27  7:53                 ` Bless, Roland (TM)
2019-06-22 21:10         ` Brian E Carpenter
2019-06-22 22:25           ` David P. Reed
2019-06-22 22:30             ` Luca Muscariello
2019-07-17 21:33 ` [Ecn-sane] " Sebastian Moeller
2019-07-17 22:18   ` David P. Reed
2019-07-17 22:34     ` David P. Reed
2019-07-17 23:23       ` Dave Taht
2019-07-18  0:20         ` Dave Taht
2019-07-18  5:30           ` Jonathan Morton
2019-07-18 15:02         ` David P. Reed
2019-07-18 16:06           ` Dave Taht
2019-07-18  4:31     ` Jonathan Morton
2019-07-18 15:52       ` David P. Reed
2019-07-18 18:12         ` [Ecn-sane] [tsvwg] " Dave Taht
2019-07-18  5:24     ` [Ecn-sane] " Jonathan Morton
2019-07-22 13:44       ` Bob Briscoe
2019-07-23  5:00         ` Jonathan Morton
2019-07-23 11:35           ` [Ecn-sane] CNQ cheap-nasty-queuing (was per-flow queuing) Luca Muscariello
2019-07-23 20:14           ` [Ecn-sane] per-flow scheduling Bob Briscoe
2019-07-23 22:24             ` Jonathan Morton
2019-07-23 15:12         ` [Ecn-sane] [tsvwg] " Kyle Rose
2019-07-25 19:25           ` Holland, Jake
2019-07-27 15:35             ` Kyle Rose
2019-07-27 19:42               ` Jonathan Morton

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/ecn-sane.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1561671061.42671176@apps.rackspace.com \
    --to=dpreed@deepplum.com \
    --cc=brian.e.carpenter@gmail.com \
    --cc=chromatix99@gmail.com \
    --cc=ecn-sane@lists.bufferbloat.net \
    --cc=moeller0@gmx.de \
    --cc=tsvwg@ietf.org \
    /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