- From: henbos via GitHub <noreply@w3.org>
- Date: Mon, 25 Aug 2025 07:37:34 +0000
- To: public-webrtc-logs@w3.org
> But the point here is: why was a principle of "no packets no stats" proclaimed for RTP in https://github.com/w3c/webrtc-stats/issues/619 and is not followed by any browser for data channels?
We have abandoned "no packets no stats" for outbound-rtp where we said we can expose them at "stable" whether or not packets have been sent as this turns out to be useful. For inbound-rtp, we still do "no packets no stats" in order to get consistent stats lifetime whether or not SSRCs have been signalled in the SDP. There we also have the case of early media so it's theoretically possible to receive packets before going back to "stable" which means you could have `{direction:'recvonly', currentDirection:null}` and still have data to monitor.
--
GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/805#issuecomment-3219170876 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 25 August 2025 07:37:35 UTC