- From: Varun Singh via GitHub <sysbot+gh@w3.org>
- Date: Tue, 08 Sep 2020 12:16:24 +0000
- To: public-webrtc-logs@w3.org
Reviewing what we know presently- 1. The sender and the receiver does not have synchronized clocks. 2. Domhighres just makes sure that the local clock exposed to the application is monotonously increasing 3. To calculate RTT we use RTCP RR, which has sender's sent TS and the The receiver's processing delay (DLSR). If we had synchronized clocks, we could add a receiver sent TS -- which would give us Current RTT = rtcp rr reception time - DSLR - sender sent TS A) OWD upstream = receiver sent TS - DLSR - sender Send TS. B) owd downstream = RTCP RR reception time - receiver sent TS. Caveat This would be only available if the extension is implemented in rtcp and how often the rtcp extension is sent. Modulo the issue with clock sync. -- GitHub Notification of comment by vr000m Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/537#issuecomment-688827899 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 8 September 2020 12:16:26 UTC