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 _______________________________________________ Bloat mailing list [email protected] https://lists.bufferbloat.net/listinfo/bloat
