Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: dpreed@reed.com
To: "JF Tremblay" <jean-francois.tremblay@viagenie.ca>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] DOCSIS 3+ recommendation?
Date: Thu, 19 Mar 2015 11:38:19 -0400 (EDT)	[thread overview]
Message-ID: <1426779499.26479897@apps.rackspace.com> (raw)
In-Reply-To: <88375E7E-8656-4DB6-8389-89C7B9DD7DF4@viagenie.ca>

I'll look up the quote, when I get home from California, in my email archives.  It may have been private email from Richard Woundy (an engineering SVP at Comcast who is the person who drove the CableLabs effort forward, working with Jim Gettys - doing the in-house experiments...). To be clear, I am not blaming Comcast's engineers or technologists for the most part. I *am* blaming the failure of the Comcast leadership to invest in deploying the solution their own guys developed. I was skeptical at the time (and I think I can find that email to Rich Woundy, too, as well as a note to Jim Gettys expressing the same skepticism when he was celebrating the CableLabs experiments and their "best practices" regarding AQM).

It's worth remembering that CableLabs, while owned jointly by all cable operators, does not actually tell the operators what to do in any way.  So recommendations are routinely ignored in favor of profitable operations.  I'm sure you know that.  It's certainly common knowledge among those who work at CableLabs (I had a number of conversations with Richard Green when he ran the place on this very subject).

So like any discussion where we anthropomorphize companies, it's probably not useful to "pin blame".

I wasn't trying to pin blame anywhere in particular - just observing that Cable companies still haven't deployed the actual AQM options they already have.

Instead the cable operators seem obsessed with creating a semi-proprietary "game lane" that involves trying to use diffserv, even though they don't (and can't) have end-to-end agreement on the meaning of the DCP used, and therefore will try to use that as a basis for requiring gaming companies to directly peer with the cable distribution network, where the DCP will work (as long as you buy only "special" gear) to give the gaming companies a "fast lane" that they have to pay for (to bypass the bloat that they haven't eliminated by upgrading their deployments).

Why will the game providers not be able to just use the standard Internet access service, without peering to every cable company directly?  Well, because when it comes to spending money on hardware upgrades, there's more money in it to pay for the upgrade.

That's just business logic, when you own a monopoly on Internet access.  You want to maximize the profits from your monopoly, because competition csn't exist. [Fixing bufferbloat doesn't increase profits for a monopoly. In fact it discourages people from buying more expensive service, so it probably decreases profits.]

It's counterintuitive, I suppose, to focus on the business ecology distortions caused by franchise monopolies in a technical group. But engineering is not just technical - it's about economics in a very fundamental way.  Network engineering in particular.

If you want better networks, eliminate the monopolies who have no interest in making them better for users.

On Thursday, March 19, 2015 10:11am, "JF Tremblay" <jean-francois.tremblay@viagenie.ca> said:

> 
>> On Mar 19, 2015, at 9:53 AM, dpreed@reed.com wrote:
>>
>> How many years has it been since Comcast said they were going to fix bufferbloat
>> in their network within a year?
> 
> Any quote on that?
> 
>> THat's a sign that the two dominant sectors of "Internet Access" business are
>> refusing to support quality Internet service.
> 
> I’m not sure this is a fair statement. Comcast is a major (if not
> “the” player) in CableLabs, and they made it clear that for Docsis
> 3.1, aqm was one of the important target. This might not have happened without all
> the noise around bloat that Jim and Dave made for years. (now peering and transit
> disputes are another ball game)
> 
> While cable operators started pretty much with a blank slate in the early days of
> Docsis, they now have to deal with legacy and a huge tail of old devices. So in
> this respect, yes they are now a bit like the DSL incumbents, introduction of new
> technologies is over a 3-4 years timeframe at least.
> 
>> It's almost as if the cable companies don't want OTT video or simultaneous FTP
>> and interactive gaming to work. Of course not. They'd never do that.
> 
> 
> You might be surprised at how much they care for gamers, these are often their
> most vocal users. And those who will call to get things fixed. Support calls and
> truck rolls are expensive and touch the bottom line, where it hurts…
> 
> JF
> (a former cable operator)
> 
> 
> 



  reply	other threads:[~2015-03-19 15:38 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16 20:35 Matt Taggart
2015-03-17 23:32 ` Valdis.Kletnieks
2015-03-18  4:34   ` David P. Reed
2015-03-18  6:26     ` Jonathan Morton
2015-03-18 19:38       ` JF Tremblay
2015-03-18 19:50         ` Jonathan Morton
2015-03-19 13:53           ` dpreed
2015-03-19 14:11             ` JF Tremblay
2015-03-19 15:38               ` dpreed [this message]
2015-03-19 15:40               ` Jim Gettys
2015-03-19 17:04                 ` Michael Richardson
2015-03-19 17:14                   ` Jonathan Morton
2015-03-19 17:11             ` Dave Taht
2015-03-19 19:58               ` [Cerowrt-devel] [Bloat] " Livingood, Jason
2015-03-19 20:29                 ` dpreed
2015-03-19 23:18                   ` Greg White
2015-03-20  8:18                     ` MUSCARIELLO Luca IMT/OLN
2015-03-20 13:31                       ` David P. Reed
2015-03-20 13:46                         ` Sebastian Moeller
2015-03-20 14:05                         ` MUSCARIELLO Luca IMT/OLN
2015-03-20 10:07                     ` Sebastian Moeller
2015-03-20 13:50                     ` [Cerowrt-devel] Latency Measurements in Speed Test suites (was: DOCSIS 3+ recommendation?) Rich Brown
2015-03-29 17:36                       ` [Cerowrt-devel] [Bloat] " Pedro Tumusok
2015-03-30  7:06                         ` Jonathan Morton
2015-03-20 13:57                     ` [Cerowrt-devel] [Bloat] DOCSIS 3+ recommendation? Livingood, Jason
2015-03-20 14:08                       ` David P. Reed
2015-03-20 14:14                         ` MUSCARIELLO Luca IMT/OLN
2015-03-20 14:48                           ` Matt Mathis
2015-03-20 18:04                         ` Valdis.Kletnieks
2015-03-20 13:48                 ` Jim Gettys
2015-03-20 14:11                   ` Livingood, Jason
2015-03-20 14:54                     ` Michael Welzl
2015-03-20 15:31                       ` Jim Gettys
2015-03-20 15:39                         ` Michael Welzl
2015-03-20 16:31                       ` Jonathan Morton
2015-03-20 20:59                         ` Michael Welzl
2015-03-20 23:47                           ` David P. Reed
2015-03-21  0:08                             ` Michael Welzl
2015-03-21  0:03                           ` David Lang
2015-03-21  0:13                             ` Steinar H. Gunderson
2015-03-21  0:25                               ` David Lang
2015-03-21  0:34                                 ` Jonathan Morton
2015-03-21  0:38                                   ` David Lang
2015-03-21  0:43                                     ` Jonathan Morton
2015-03-22  4:15                                 ` Michael Welzl
2015-03-21  0:15                             ` Michael Welzl
2015-03-21  0:29                               ` David Lang
2015-03-22  4:10                                 ` Michael Welzl
2015-03-20 18:14                     ` Jonathan Morton
2015-03-18  8:06     ` [Cerowrt-devel] " Sebastian Moeller

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/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to=1426779499.26479897@apps.rackspace.com \
    --to=dpreed@reed.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=jean-francois.tremblay@viagenie.ca \
    /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