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

Re: [rtcweb] draft-ietf-rtcweb-rtp-usage: CSRC in the API?

From: Adam Bergkvist <adam.bergkvist@ericsson.com>
Date: Fri, 22 Feb 2013 13:01:00 +0100
Message-ID: <51275DFC.1000001@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
CC: "public-webrtc@w3.org" <public-webrtc@w3.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
On 2013-02-22 11:22, Magnus Westerlund wrote:
> On 2013-02-22 10:43, Adam Bergkvist wrote:
>>
>> Reading CSRC info:
>> Right now, the SSRC(s) of a track is only exposed via the Stats API. I
>> think that's the right level if we were to support reading CSRC info as
>> well.
>
> I don't see how the Stats API comes in here. The information bit I see
> the CRSC list provides is: These MST(s) was used to produce what you
> get. It is a information about original identity of the media sources.
> Thus I would guess that in the API it might be appropriate to map the
> CSRC list to the MST IDs.

Ok, I was talking about exposing the CSRC values directly. I think that 
and other RTP stuff belongs in the Stats API. However, if we map the 
info the CSRC list provides to track ids (or sourceId), then I agree 
it's a different case.

/Adam
Received on Friday, 22 February 2013 12:01:24 UTC

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