[webrtc-extensions] captureTimestamp seems to have an inconsistent clock base (#97)

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

== captureTimestamp seems to have an inconsistent clock base ==
A straightforward reading of https://w3c.github.io/webrtc-extensions/#dom-rtcrtpcontributingsource-capturetimestamp seems to indicate that this clock is reading out in the NTP timebase (seconds since 1900), while all other times, including "timestamp" in the same dictionary, are represented in the Unix timebase (seconds since 1970).

This seems like a silly inconsistency that makes the value harder to use. Should we fix it?


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config