From: dpreed@reed.com
To: "Dave Taht" <dave.taht@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] comcast provisioned rates?
Date: Sat, 19 Apr 2014 14:16:35 -0400 (EDT) [thread overview]
Message-ID: <1397931395.018720381@apps.rackspace.com> (raw)
In-Reply-To: <CAA93jw5gkLxUkB=fwTP4X0fARd4hVWpxs2uNmutgaXJO=5uqEg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4380 bytes --]
Very good. So the idea, rather than Comcast implementing codel or something proper in the DOCSIS 3.0 systems they have in the field, is to emulate power boost to "impedance match" the add-on router-based codel approach to some kind of knowledge of what the DOCSIS CMTS buffering state looks like....
And of course nothing can be done about "downstream" bufferbloat in the Comcast DOCSIS deployment.
So instead of fixing Comcast's stuff "correctly", we end up with a literal "half measure".
Who does Comcast buy its CMTS gear from, and if it has a Heartbleed bug, maybe some benevolent hacker should just fix it for them?
It's now been 2 years since Comcast said they were deploying a fix. Was that just them hoping the critics would dissipate their time and effort? And is Comcast still using its Sandvine DPI gear?
I'm afraid that monopolists really don't care. Even friendly-sounding ones. Especially when they can use their technical non-deployments to get paid more by Netflix.
On Saturday, April 19, 2014 1:57pm, "Dave Taht" <dave.taht@gmail.com> said:
> The features of the PowerBoost feature are well documented at this
> point. A proper
> emulation of them is in the ns2 code. It has been a persistent feature
> request, to
> add support to some Linux rate shaper to properly emulate PowerBoost,
> but no funding
> ever arrived.
>
> Basically you get 10 extra megabytes above the base rate at whatever
> rate the line
> can sustain before it settles back to the base rate.
>
> You can also see that as presently implemented, at least on a short
> RTT path, the feature
> does not prevent bufferbloat.
>
> http://snapon.lab.bufferbloat.net/~cero2/jimreisert/results.html
>
> I'd like a faster, less cpu intense rate shaper than sch_htb in
> general, and powerboost emulation would be nice.
>
>
> On Sat, Apr 19, 2014 at 9:38 AM, Aaron Wood <woody77@gmail.com> wrote:
> > Based on these results:
> >
> > http://snapon.lab.bufferbloat.net/~cero2/jimreisert/results.html
> >
> > And talking off-list with Jim, I think that the "PowerBoost" is above the
> > quoted rate, as the 24/4 service hits >36Mbps TCP data rate. I'm
> definitely
> > sad that using SQM in the router instead of the modem loses features like
> > that. But I'll just be happy to have upload over 1Mbps again.
> >
> > I do know that the FCC was cracking down on advertised vs. actual rates, and
> > started a "measuring broadband in America" project:
> >
> > http://www.fcc.gov/measuring-broadband-america
> >
> > -Aaron
> >
> >
> > On Sat, Apr 19, 2014 at 6:21 PM, <dpreed@reed.com> wrote:
> >>
> >> As a non-Comcast-customer, I am curious too. I had thought their
> "boost"
> >> feature allowed temporary rates *larger* than the quoted "up to" rates.
> >> (but I remember the old TV-diagonal games and disk capacity games, where
> any
> >> way to get a larger number was used in the advertising, since the FTC
> didn't
> >> have a definition that could be applied).
> >>
> >>
> >>
> >> I wonder if some enterprising lawyer might bring the necessary consumer
> >> fraud class-action before the FTC to get clear definitions of the
> numbers?
> >> It's probably too much to ask for Comcast to go on the record with a
> precise
> >> definition.
> >>
> >>
> >>
> >>
> >>
> >> On Saturday, April 19, 2014 8:55am, "Aaron Wood"
> <woody77@gmail.com> said:
> >>
> >> I'm setting up new service in the US, and I'm currently assuming that
> all
> >> of Comcast's rates are "boosted" rates, not the "provisioned" rates.
> >> So if they quote 50/10Mbps, I assume that's not what will need to be set
> >> in SQM with CeroWRT.
> >> Does anyone have good info on the "provisioned" rates that go with each
> of
> >> the Comcast tiers?
> >> Basically, I'm trying to get to an apples-to-apples comparison with
> >> Sonic.net DSL (I'll be close enough to the CO to run in Annex M "upload
> >> priority" mode and get ~18/2 service).
> >> Thanks,
> >> Aaron
> >
> >
> >
> > _______________________________________________
> > Cerowrt-devel mailing list
> > Cerowrt-devel@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/cerowrt-devel
> >
>
>
>
> --
> Dave Täht
>
> NSFW:
> https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
>
[-- Attachment #2: Type: text/html, Size: 5977 bytes --]
next prev parent reply other threads:[~2014-04-19 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-19 12:55 Aaron Wood
2014-04-19 16:21 ` dpreed
2014-04-19 16:38 ` Aaron Wood
2014-04-19 17:57 ` Dave Taht
2014-04-19 18:16 ` dpreed [this message]
2014-04-19 18:40 ` Dave Taht
2014-04-19 18:57 ` Dave Taht
2014-04-20 20:35 ` 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=1397931395.018720381@apps.rackspace.com \
--to=dpreed@reed.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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