From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
starlink@lists.bufferbloat.net, Rpm <rpm@lists.bufferbloat.net>
Subject: [Rpm] measurement lab research fellowship call 2022
Date: Fri, 5 Nov 2021 09:20:08 -0700 [thread overview]
Message-ID: <CAA93jw6b4tGyXg=04U6DQNKAQ3ySHdav+7rHOjDOPEGmd9vk6w@mail.gmail.com> (raw)
One of the things that Matt Mathis pointed out in the associated
workshop ( https://www.youtube.com/watch?v=GW5C24YKAh8&t=850s ) is
how important new tools for measuring QoE "not cry wolf"; that they
point to the point of actual congestion and other problems.
Topics of interest include but are not limited to:
Relation between QoE and network metrics like bandwidth/latency/loss
Novel metrics that can be computed on existing NDT data
New measurements/experiments that could be deployed on M-Lab to
diagnose network bottlenecks
Characterizing paths measured by M-Lab clients; stability of paths,
relation to paths of interest (eg., paths to content) or network
characterization
Proposals for new experiments to be hosted on the M-Lab platform
Identification of biases in M-Lab data
Implementing ideas introduced during M-Lab’s Community Call on
Latency, Bufferbloat and Responsiveness and/or the IAB workshop on
Network Quality
For more details see:
see: https://www.measurementlab.net/blog/research-fellowship-call/
--
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
Dave Täht CEO, TekLibre, LLC
reply other threads:[~2021-11-05 16:20 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/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6b4tGyXg=04U6DQNKAQ3ySHdav+7rHOjDOPEGmd9vk6w@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=rpm@lists.bufferbloat.net \
--cc=starlink@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