From: Jim Gettys <jg@freedesktop.org>
To: JF Tremblay <jean-francois.tremblay@viagenie.ca>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] DOCSIS 3+ recommendation?
Date: Thu, 19 Mar 2015 11:40:42 -0400 [thread overview]
Message-ID: <CAGhGL2AC2pgJLxUoE67uBrwvhH1ZVDU15vDvhCoS02PhwACtvg@mail.gmail.com> (raw)
In-Reply-To: <88375E7E-8656-4DB6-8389-89C7B9DD7DF4@viagenie.ca>
[-- Attachment #1: Type: text/plain, Size: 3051 bytes --]
On Thu, Mar 19, 2015 at 10:11 AM, JF Tremblay <
jean-francois.tremblay@viagenie.ca> wrote:
>
> > 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?
>
They had hoped to be able to use a feature in DOCSIS to at least set the
buffering to the "correct" size for the provisioned bandwidth. While not
fixing bufferbloat, it would have made a big difference (getting latency
down to the 100ms range; that would have taken my original 1.2 seconds of
bloat down to 100ms).
When they went and tested that feature, the actual implementations weren't
there and were so buggy, they couldn't turn it on.
Moral 1: anything not tested by being used on an ongoing basis, doesn't
work.
Moral 2: Companies like Comcast do not (currently) control their own
destiny, since they outsourced too much of the technology to others.
> 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.
>
Yup.
>
> > 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…
>
Yup.
And I agree with Dave Taht, Comcast has had a lot more technical clue than
most other ISP's we've interacted with.
And these industries are captive to the practices of the companies that
make the gear, and as I've said in public at the Berkman Center, this has
really bad and dangerous consequences for the Internet. I'll post a new
version of that talk, maybe later today.
Now, I've yet to detect any clue it cellular ISP's.... And there, dpr's
complaints I believe are correct.
- Jim
> JF
> (a former cable operator)
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 5616 bytes --]
next prev parent reply other threads:[~2015-03-19 15:40 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
2015-03-19 15:40 ` Jim Gettys [this message]
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=CAGhGL2AC2pgJLxUoE67uBrwvhH1ZVDU15vDvhCoS02PhwACtvg@mail.gmail.com \
--to=jg@freedesktop.org \
--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