Re: [webrtc-provisional-stats] Identify the state of provisional stats (#43)

According to [Chromium's WebIDL](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/modules/peerconnection/rtc_stats_report.idl), the metrics that have been implemented from the _provisional_ stats spec are:
- [contentType](https://w3c.github.io/webrtc-provisional-stats/#dom-rtcoutboundrtpstreamstats-contenttype)
- [rtcpTransportStatsId](https://w3c.github.io/webrtc-provisional-stats/#dom-rtctransportstats-rtcptransportstatsid)
- [networkType](https://w3c.github.io/webrtc-provisional-stats/#dom-rtciceserverstats-networktype)

In addition, these have also been implemented but are not defined in any of the two specs:
- googTimingFrameInfo: from legacy getStats, see [issue](https://github.com/w3c/webrtc-provisional-stats/issues/40).
- isRemote: removed from spec a long time ago because type == 'local-candidate' or 'remote-candidate' reveals same info.
- ip: removed from spec a long time ago because it was renamed address.
- writable: not in any spec, probably a remnant of legacy getStats.
- priority: not in any spec, probably a remnant of legacy getStats.

**Proposal:**
- Move contentType, rtcpTransportStatsId and networkType to the main spec with an "At Risk" note.
- The remaining ones should probably be deprecated and removed, though I don't see `googTimingFrameInfo` going away without a replacement. The other ones seems ready to Intent to Deprecate though IIUC.

If we do this, https://w3c.github.io/webrtc-stats/ will reflect implementations and this provisional stat specs can remain an idea document used for inspiration, but not something that the WG advocates implementing unless a WG meeting is hold about wanting to implement one of the metrics. WDYT @alvestrand @vr000m @youennf @jan-ivar ?

-- 
GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-provisional-stats/issues/43#issuecomment-1757064173 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 11 October 2023 07:58:00 UTC