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 12:13:19 +0100
Message-ID: <512752CF.1010700@ericsson.com>
To: Harald Alvestrand <harald@alvestrand.no>
CC: Magnus Westerlund <magnus.westerlund@ericsson.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On 2013-02-22 12:08, Harald Alvestrand wrote:
> On 02/22/2013 11:22 AM, 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.
> Can you expand MST, please?
> My googling for "CSRC" and "MST" together only came up with
> "Multi-Session Transmission" (from the COP draft), and that doesn't seem
> to fit.

My interpretation: MST = MediaStreamTrack (in this context)

Received on Friday, 22 February 2013 11:13:42 UTC

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