- From: henbos via GitHub <noreply@w3.org>
- Date: Thu, 02 Oct 2025 12:21:00 +0000
- To: public-webrtc-logs@w3.org
I'm not opposed to waiting for clarity since this depends on a feature that has not been standardized yet (Encoded Source), but I can say that I would be very much opposed to splitting up the "inbound-rtp" into multiple different stats objects. The inbound-rtp is tied to an RTCRtpReceiver and contains metrics for RTP, decode and arguably its "track". This is a dictionary, so if the RTP metrics arn't applicable, they can simply be missing from the dictionary. The stats type having "rtp" in the name is not such a big evil that we should revisit the entire stats model. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/816#issuecomment-3360947144 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 2 October 2025 12:21:01 UTC