From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>, "aqm@ietf.org" <aqm@ietf.org>
Subject: [Bloat] The Impact of Active Queue Management on DASH-based Content Delivery
Date: Tue, 10 Jan 2017 08:08:27 -0800 [thread overview]
Message-ID: <CAA93jw7kWJhmr-Su+BptKYo7P7DUmo5vsLDswBcpZSia+KvyjA@mail.gmail.com> (raw)
This was quite good. I particularly liked the invention of the
"instability index".
Jonathan Kua, Grenville Armitage and Philip Branch, "The Impact of
Active Queue Management on DASH-based Content Delivery," in 41st
Annual IEEE Conference on Local Computer Networks (LCN), Dubai, UAE, 7
- 10 November 2016, https://doi.org/10.1109/LCN.2016.24
(more easily available via: http://sci-hub.bz/10.1109/LCN.2016.24# )
I hope a test like this gets repeated against BBR (and for that
matter, cake), and against a larger dynamic range of bandwidths (4k
video, anyone)?
next reply other threads:[~2017-01-10 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 16:08 Dave Taht [this message]
2017-01-10 17:37 ` [Bloat] [ALU] [aqm] The Impact of Active Queue Management on DASH-based ContentDelivery Francini, Andrea (Nokia - US)
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=CAA93jw7kWJhmr-Su+BptKYo7P7DUmo5vsLDswBcpZSia+KvyjA@mail.gmail.com \
--to=dave.taht@gmail.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