From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Dave Taht via Bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [EXTERNAL] Re: Another Measurement Program
Date: Mon, 20 Feb 2023 20:20:41 +0000 [thread overview]
Message-ID: <8FA85E1E-1377-4418-A854-72485DD8CD0B@cable.comcast.com> (raw)
In-Reply-To: <CAA93jw4vCDZXKmU4o0EcHyYaEMH78d2_UdbYnmpspPQW7T42pg@mail.gmail.com>
> My principal issue with all this wonderful activity, is I would like,
rather desparately, for all the researchers involved to discuss their
methods, and try to calibrate them against a reference of some kind.
I think researchers & industry are in the 'storming' phase and not yet ready for 'norming', so to speak. It will probably happen in time. As papers come out, it will be helpful to examine methodologies & learn from them to move the state of the art forward.
> Is anyone testing videoconferencing quality? A mere MOS out of
videoconferencing traffic relative to other load would please me.
I think SamKnows have a video streaming quality test [1]. And IIRC there is research into passive measurement of video streams to infer quality, but I don’t recall any recent papers off hand.
Jason
[1] See:
https://samknows.com/tests/video-streaming
https://samknows.com/blog/new-streaming-test
https://samknows.com/blog/critical-services-tracker-video-streaming-uk
next prev parent reply other threads:[~2023-02-20 20:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 16:14 [Bloat] " Livingood, Jason
2023-02-20 16:49 ` Dave Taht
2023-02-20 20:20 ` Livingood, Jason [this message]
2023-02-28 17:21 ` Livingood, Jason
2023-03-01 14:02 ` Nathan Owens
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=8FA85E1E-1377-4418-A854-72485DD8CD0B@cable.comcast.com \
--to=jason_livingood@comcast.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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