W3C home > Mailing lists > Public > public-webrtc@w3.org > June 2012

Re: CSSRC / SSRC

From: Stefan Hakansson LK <stefan.lk.hakansson@ericsson.com>
Date: Wed, 13 Jun 2012 08:29:26 +0200
Message-ID: <4FD83346.5000909@ericsson.com>
To: public-webrtc@w3.org
On 06/12/2012 03:22 PM, Justin Uberti wrote:
>
>
> On Tue, Jun 12, 2012 at 9:15 AM, Cullen Jennings <fluffy@cisco.com
> <mailto:fluffy@cisco.com>> wrote:
>
>
>     Given the discussion at IETF, it seems like it would be good for the
>     API to support an JS App:
>
>     1) setting the list of CSRC to be set on RTP packets sent for a
>     given track
>
>
> Do you mean getting or setting? Getting seems more useful than setting.
>
>
>     2) setting the SSRC a track should use (and the app has to set it to
>     a random number)
>
>
> This seems like it can be done via SDP (a=ssrc attribute). I don't think
> we need to enforce randomness, if the app wants to set everything to 1,
> that's its problem.

Agree. But for my clarification: the browser _will_ generate ssrc whon 
the app does "createOffer", right? In other words, setting ssrc is only 
necessary if the app wants another ssrc to be used.

>
>
>     3) reading the SSRC of an incoming track
>
>
> Need to think about what this means for tracks that have multiple SSRCs
> (i.e. from ssrc grouping)
>
>
>     Cullen
>
>
>
Received on Wednesday, 13 June 2012 06:29:52 UTC

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