- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Dec 2016 22:48:25 +0000
- To: public-webrtc@w3.org
taylor-b has just created a new issue for https://github.com/w3c/webrtc-stats: == Should document what RTCRTPStreamStats metrics are valid when `isRemote` is true. == For example: - `targetBitrate` isn't something that's communicated via RTCP (to my knowledge), so I imagine it's only valid when `isRemote` is false. - `roundTripTime`, though it uses RTCP RRs for its calculation, is a property of sent streams and thus only valid when `isRemote` is false. Also: it would be helpful to have a small summary of how `RTCOutboundRTPStreamStats`, `RTCInboundRTPStreamStats`, `isRemote` and `associateStatsId` relate to each other. As I understand, each sent stream will provide an `RTCOutboundRTPStreamStats` where `isRemote` is false and an `RTCInboundRTPStreamStats` where `isRemote` is true. And each received stream will provide an `RTCInboundRTPStreamStats` where `isRemote` is false, and an `RTCOutboundRTPStreamStats` where `isRemote` is true. Which makes me realize: why do we have separate inbound/outbound stats objects that are associated by ID, instead of just putting everything in one object? Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/108 using your GitHub account
Received on Thursday, 15 December 2016 22:48:31 UTC