- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Tue, 30 Aug 2022 12:14:42 +0000
- To: public-webrtc-logs@w3.org
I think the spec is in a pretty good state now, though we should sanity check by going over them again. Also I filed #660 as a follow-up since some metrics are kind-specific in the implementations. Regarding the [implementation report](https://w3c.github.io/webrtc-interop-reports/webrtc-stats-report.html) (nice work!), the status on "without implementation" metrics AFAIK: - `remote-inbound-rtp.framesDropped`: While framesDropped is implemented for inbound-rtp, this does not exist in remote-inbound-rtp. I filed #661 to make spec match. - `remote-outbound-rtp.roundTripTime`: It [looks like chromium sets it for audio according to code search](https://source.chromium.org/chromium/chromium/src/+/main:third_party/webrtc/pc/rtc_stats_collector.cc;l=519;drc=7267e612666ee78e5809dcc48253af2857989a47) but I was unable to repro in a WPT so not sure how to trigger it being set... @alvestrand any ideas? - `certificate.issuerCertificateId`: There is code for it, but I don't know how to trigger it in practise. @alvestrand know if its possible? To me, the big issue is "when to delete RTP metrics?" (spec says never, implementation deletes as soon as a stream goes away). I ramble about it in #643 but we may want to split that up into separate creation vs destruction issues to avoid wall of text. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/595#issuecomment-1231583669 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 30 August 2022 12:14:44 UTC