From: Greg White <g.white@CableLabs.com>
To: Noah Causin <n0manletter@gmail.com>,
"bloat@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Good Cable Modems?
Date: Wed, 22 Jun 2016 22:01:37 +0000 [thread overview]
Message-ID: <C88154B7-15A5-47EE-8450-3C972CC79808@cablelabs.com> (raw)
In-Reply-To: <f27af240-0999-bbd4-72a2-30d2504a56bc@gmail.com>
While I can’t direct you to any specific DOCSIS 3.0 modem, I can answer/clarify a couple of things.
For D3.1, the cable modem is required to implement DOCSIS-PIE to manage upstream queues (a variant of PIE, google it if you want the details). The manufacturer can optionally implement other algorithms if they choose to, but DOCSIS-PIE is required to be the default AQM. The CMTS in D3.1 is required to implement AQM to manage downstream queues, but the algorithm choice is left to the manufacturer.
While different D3.0 modems will likely show different amounts of upstream bufferbloat, they will not have any impact on downstream bufferbloat.
-Greg
On 6/22/16, 3:37 PM, "Bloat on behalf of Noah Causin" <bloat-bounces@lists.bufferbloat.net on behalf of n0manletter@gmail.com> wrote:
>Hi,
>
>I was wondering if anyone knew about any good current DOCSIS 3.0 Cable
>modems. I'm aware that AQM will land in DOCSIS 3.1 cable modems (By the
>way, is the AQM manufacturer's choice or just Cisco PIE?)
>
>I was going to choose a Motorola surfboard, but I know from experience
>that the buffering is excessive. (about 4000ms with CMTS Bloat).
>
>I'm going to be setting up SQM, but I just wanted to be aware of a
>better product.
>
>Noah
>
>
>_______________________________________________
>Bloat mailing list
>Bloat@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/bloat
prev parent reply other threads:[~2016-06-22 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 21:37 Noah Causin
2016-06-22 22:01 ` Greg White [this message]
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C88154B7-15A5-47EE-8450-3C972CC79808@cablelabs.com \
--to=g.white@cablelabs.com \
--cc=bloat@lists.bufferbloat.net \
--cc=n0manletter@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