- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 17 Jun 2022 21:13:14 +0000
- To: public-webrtc-logs@w3.org
jan-ivar has just created a new issue for https://github.com/w3c/webrtc-stats: == Do we agree removing "sender", "receiver" and "transceiver" stats is a good idea? == Getting rid of `"sender"`, `"receiver"` and `"transceiver"` stats may be a good idea, but deserves discussion. Unfortunately https://github.com/w3c/webrtc-stats/pull/628 was merged before this discussion could happen, so I'm opening this issue to discuss it now. @alvestrand @aboba @youennf A benefit of the `"sender"`, `"receiver"` and `"transceiver"` stats were their lifetimes matched the sender, receiver and transceiver API objects. They supplanted `"track"` as a more stable starting point for (cross) navigating stats. An argument for their removal seems to be that most metrics they contained have since been moved to RTP stats over the last few years. **But RTP stats lifetimes are tied to RTP**: _"The lifetime of all RTP [monitored object](https://w3c.github.io/webrtc-stats/#dfn-monitored-object)s starts when the [RTP stream](https://w3c.github.io/webrtc-stats/#dfn-rtp-stream) is first used: When the first RTP packet is sent or received on the [SSRC](https://w3c.github.io/webrtc-stats/#dfn-ssrc) it represents, or when the first RTCP packet is sent or received that refers to the [SSRC](https://w3c.github.io/webrtc-stats/#dfn-ssrc) of the [RTP stream](https://w3c.github.io/webrtc-stats/#dfn-rtp-stream)."_ To make things worse, some implementations got the RTP lifetimes wrong #619, which brings into question whether metrics were moved under faulty assumptions and need to be put back if people expect to look them up sooner. This is putting pressure on the model. There are rumblings in #619 of people now wanting RTP stats lifetimes tied to the API objects instead somehow, but so far no-one has opened an issue to propose details of how this would work. We need to figure out the model we want and make sure we all see it the same way this time. Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/643 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 17 June 2022 21:15:27 UTC