[webrtc-stats] RoundTripTime not defined when the underlying stream can't calculate it from jesup via GitHub on 2017-03-06 (public-webrtc-logs@w3.org from March 2017)

From: jesup via GitHub <sysbot+gh@w3.org>
Date: Mon, 06 Mar 2017 19:32:19 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-212225391-1488828738-sysbot+gh@w3.org>

jesup has just created a new issue for https://github.com/w3c/webrtc-stats:

== RoundTripTime not defined when the underlying stream can't calculate it ==
RoundTripTime can only be calculated after an exchange of RTCP packets with the relevant information.  Until then, it's not possible to calculate.  What should be RoundTripTime have before we know the time?  0?  undefined?  null?  And what will be the impact on existing applications if we choose something like undefined or null?

Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/180 using your GitHub account

Received on Monday, 6 March 2017 19:32:25 UTC