Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: dpreed@reed.com
To: "Aaron Wood" <woody77@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] comcast provisioned rates?
Date: Sat, 19 Apr 2014 12:21:08 -0400 (EDT)	[thread overview]
Message-ID: <1397924468.489728228@apps.rackspace.com> (raw)
In-Reply-To: <CALQXh-PUA-Pu1kMTAYFCuAvM=GdkytePrvPF-KbA68LV8ejbbQ@mail.gmail.com>

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


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

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

  reply	other threads:[~2014-04-19 16:21 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 [this message]
2014-04-19 16:38   ` Aaron Wood
2014-04-19 17:57     ` Dave Taht
2014-04-19 18:16       ` dpreed
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=1397924468.489728228@apps.rackspace.com \
    --to=dpreed@reed.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=woody77@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