- From: Dominique Hazael-Massieux via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 Feb 2021 12:14:15 +0000
- To: public-webrtc-logs@w3.org
I've built a basis analysis of the callstats.io report to see how it informs us about what's in the spec and what's actually implemented: https://w3c.github.io/webrtc-interop-reports/webrtc-stats-report.html Before diving into analysis of what's implemented or not, the first thing to note is that the callstats.io report does not seem aligned with the hierarchy in the spec - the first list in the document above shows which fields of which types from the spec aren't listed in the report. In particular, it's missing data on the high level types `data-channel`, `transceiver`, `sctp-transport` and `ice-server`. I'm not sure if we should look into fixing the callstats.io report (if that's even a possibility) or if we should look at taking the approach that was taken for [MTI stats in WPT](https://github.com/web-platform-tests/wpt/blob/master/webrtc/RTCPeerConnection-mandatory-getStats.https.html) and extend it to the full stats hierarchy (and then based our further analysis on the data collected in WPT.fyi). Thoughts? -- GitHub Notification of comment by dontcallmedom Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/595#issuecomment-776666418 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 10 February 2021 12:14:18 UTC