Re: [webrtc-stats] Add estimatedClockSkew

This would be the difference in the NTP timestamps from the sender and receiver, calculated by the receiver. Nominally it would be approximately 1/2 the RTT, but the RTT measurement is calculated to provide an instantaneous value, this could be calculated with the understanding that clocks drift rather then jump and can utilize a smoother algorithm. The current RTT measurements are also only valid for sending clients. This would allow for utilizing other mechanisms for calculating RTT for receiving clients (like https://tools.ietf.org/html/rfc3611#section-4.4) in order to calculate this in more places.

-- 
GitHub Notification of comment by icydragons
Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/258#issuecomment-346421105 using your GitHub account

Received on Wednesday, 22 November 2017 17:30:33 UTC