- From: Josh Ribakoff via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Aug 2020 01:22:59 +0000
- To: public-webrtc-logs@w3.org
Note that NTP times are subject to clock slew and adjustments by NTP, and subject to error due to NTP mis configurations or peering issues The spec for performance.now() (https://developer.mozilla.org/en-US/docs/Web/API/DOMHighResTimeStamp) says not to reply Date.now() or NTP for timing durations of things as it can report negative deltas. The same seems it would be true of anything in webRTC relying on NTP. Ideally this would use a single monotonically increasing clock and have the ability to report a round trip time that allows for placing an upper bounds on the delay. -- GitHub Notification of comment by joshribakoff Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/537#issuecomment-677986197 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 21 August 2020 01:23:02 UTC