- From: henbos via GitHub <noreply@w3.org>
- Date: Thu, 23 Oct 2025 10:35:38 +0000
- To: public-webrtc-logs@w3.org
Websites that use encoded source would be the same websites that arn't using encoded source. Different use cases and features, but same stats pipeline. Introducing new stats types has backwards compatibility problems without any tangible benefit. "inbound-rtp" being a shared object for both RTP and decode stats is not a _new_ problem, or a problem that is only exposed now - you can go back 10 or how ever many years and look at the original "inbound-rtp" stats object and you would see that it has always been a mix of RTP and decode stats. Hindsight is 20/20 but if this was a problem we should have fixed it 10 years ago, not now. "inbound-rtp" defines both audio-only and video-only metrics, but that's not a problem, we just don't set any values for the metrics that are N/A. Same thing here; if RTP stats are N/A, we don't set them. The "only" new problem here is `inbound-rtp.ssrc` being a `required` attribute. I don't know if Encoded Source intents to let you specify SSRC, but if you don't, then this attribute would no longer be `required`. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/816#issuecomment-3436226158 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 23 October 2025 10:35:39 UTC