From: jb <justin@dslr.net>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] What does cablelabs certification actually do?
Date: Sat, 10 Dec 2016 00:56:31 +1100 [thread overview]
Message-ID: <CAH3Ss97V0o4bHbR1EG6AGf-g9n=xcjenUEm3scuR9Ecj3mc4Ew@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1612090732220.1747@uplift.swm.pp.se>
[-- Attachment #1: Type: text/plain, Size: 1766 bytes --]
So after writing, I discovered they were asked about the problem with the
Puma6 chipset and stated their job as they see it is mainly to test for
standards compliance etc, and they purposely steer clear of performance in
order to encourage competition and variety. Or some punt like that. (I'm
probably mangling the message bit but that was the gist of it).
I guess there are such a huge number of devices and firmware releases it is
an endless job to evaluate each for performance in depth (beyond top
speed). Perhaps they are like cars before Ralph Nader. Unsafe at any speed?
IoT devices would fall into that category for sure!
On Fri, Dec 9, 2016 at 5:39 PM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> On Fri, 9 Dec 2016, jb wrote:
>
> And then wondered why certification can't also include verification for
>> correctly sized buffers as well?
>>
>
> There is nothing stopping this, and it's being worked on (PIE goes into
> DOCSIS 3.1).
>
> http://www.cablelabs.com/wp-content/uploads/2014/06/DOCSIS-AQM_May2014.pdf
> https://www.nanog.org/sites/default/files/20160922_Klatsky_
> First_Steps_In_v1.pdf
>
> Cable Labs (as far as I understand) is an organisation funded by cable
> operators and vendors, and they create standards and tests used by the
> cable industry.
>
> I don't know what tests Cable Labs perform, but there is nothing stopping
> them from validating buffers+AQM in the modems as well, and I do hope they
> do this going forward.
>
> Why not reach out to Greg White who is mentioned in the cablelabs
> DOCSIS-AQM pdf above and ask? Or even better, invite him to this list if
> he's not already here. He's on the IETF AQM WG list, I have posts by him in
> my folder back to 2013.
>
> --
> Mikael Abrahamsson email: swmike@swm.pp.se
>
[-- Attachment #2: Type: text/html, Size: 2661 bytes --]
prev parent reply other threads:[~2016-12-09 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 2:34 jb
2016-12-09 6:39 ` Mikael Abrahamsson
2016-12-09 13:56 ` jb [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='CAH3Ss97V0o4bHbR1EG6AGf-g9n=xcjenUEm3scuR9Ecj3mc4Ew@mail.gmail.com' \
--to=justin@dslr.net \
--cc=bloat@lists.bufferbloat.net \
/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