W3C home > Mailing lists > Public > public-webrtc@w3.org > October 2013

Comments on the stats api on the webRTC wiki...

From: Göran Eriksson AP <goran.ap.eriksson@ericsson.com>
Date: Fri, 18 Oct 2013 21:54:56 +0000
To: "Harald Alvestrand (harald@alvestrand.no)" <harald@alvestrand.no>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <532A6DC6F9C115439C41705FF73D13871C405D8F@ESESSMB209.ericsson.se>
Hi Harald,

Great to see the updated proposal for stats parameters uploaded on the W3C WebRTC Wiki, http://www.w3.org/2011/04/webrtc/wiki/Stats- this makes it much easier to discuss it before it ends up in the spec. It would be nice to see some other outstanding stuff there as well in time for TPAC.

Now, a few comments and questions (not a complete list, :-)):

1. Have You considered stats for RTCDataChannel? 

2. RTCRTPStreamStats
It is not obvious to me what "transportId" is about, especially since nothing like a "transport object" is in the API.

3. RTCInboundRTPStreamStats
Perhaps a comment about meaning of "jitter" and how it is measured/calculated (unless obvious from context in spec) would be helpful?

4. RTCMediaStreamTracks
I note that frames received and decoded are included. In Media Source Extentions, there are possibilities to get stats on the video element about frames dropped, corrupted, displayed, etc (https://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-source.html#htmlvideoelement-extensions)- I believe it would be good if we try to align with that API, at least when it comes to parameters.'

5. RTCTransport
I was looking for information for which DSCP class that was used for a track and thought it may be in this dictionary. Such information could become useful in debugging an application I expect.

Many Regards
Göran
Received on Friday, 18 October 2013 21:55:21 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:36 UTC