- From: Varun Singh via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Nov 2022 12:56:16 +0000
- To: public-webrtc-logs@w3.org
Curious why the measurement in (1) would not be sufficient? Especially, if the receiver is making a local decision based on the data that it can calculate. On further thought, one reason that I could see is if you want to correlate fractionLost received in RTCP RR at the sender (in inbound-remote, the same place we have roundTripTime) with what was measured at the receiver. For this case, I would need clarification from the current implementors-- does Chrome/Firefox keep a running counter for `fractionLost` or only calculate the metric when the RTCP RR is sent? The former case would not help correlate, but the latter will need an RTCP RR timestamp in addition to the fractionLost metric? cc: @henbos @jan-ivar -- GitHub Notification of comment by vr000m Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/706#issuecomment-1316979893 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 November 2022 12:56:18 UTC