From: Mikael Abrahamsson <swmike@swm.pp.se>
To: jb <justin@dslr.net>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] What does cablelabs certification actually do?
Date: Fri, 9 Dec 2016 07:39:38 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.02.1612090732220.1747@uplift.swm.pp.se> (raw)
In-Reply-To: <CAH3Ss94ySeh4vSiCqi8t2SRc5Eojk9wmHOhk40i4gfe44P4qOw@mail.gmail.com>
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
next prev parent reply other threads:[~2016-12-09 6:39 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 [this message]
2016-12-09 13:56 ` jb
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=alpine.DEB.2.02.1612090732220.1747@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=bloat@lists.bufferbloat.net \
--cc=justin@dslr.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