From: Greg White <g.white@CableLabs.com>
To: bloat <bloat@lists.bufferbloat.net>, "aqm@ietf.org" <aqm@ietf.org>
Subject: [Bloat] New white paper on AQM in DOCSIS
Date: Wed, 4 Jun 2014 21:56:19 +0000 [thread overview]
Message-ID: <CFB4F221.361D0%g.white@cablelabs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 577 bytes --]
FYI, I've put up a new white paper on the AQM algorithm details for DOCSIS. It covers the factors that went into the selection of a mandatory AQM algorithm for DOCSIS 3.0 and 3.1 modems, as well as the ways in which we customized the PIE algorithm in order to take advantage of awareness of the DOCSIS MAC layer. Some of this is a repeat of the contents of my I-D, but in large part the paper provides new info.
It can be found here: Active Queue Management in DOCSIS 3.x Cable Modems<http://www.cablelabs.com/wp-content/uploads/2014/06/DOCSIS-AQM_May2014.pdf>
-Greg
[-- Attachment #2: Type: text/html, Size: 970 bytes --]
reply other threads:[~2014-06-04 21:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CFB4F221.361D0%g.white@cablelabs.com \
--to=g.white@cablelabs.com \
--cc=aqm@ietf.org \
--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