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


From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 12 Jun 2012 15:41:13 -0700
Message-ID: <CABkgnnWR6WQ9G-hFfvEGsQhwZbGvQ+0MPUJHdqVZf-mey_-gDg@mail.gmail.com>
To: Cullen Jennings <fluffy@cisco.com>
Cc: public-webrtc@w3.org, jonathan <jonathan@vidyo.com>
On 12 June 2012 06:15, Cullen Jennings <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

I could care less because I don't see this being used, but if people
want it, sure.

> 2) setting the SSRC a track should use (and the app has to set it to a random number)

At what time?  I'd say that any time is OK.

> 3) reading the SSRC of an incoming track

Is this going to work for streams that haven't been signaled yet?  I'm
guessing no for a host of reasons including the multiple RTP streams
for a single MediaStreamTrack problem with layered codecs.

4) setting the no-go set for the RTP session?
Received on Tuesday, 12 June 2012 22:41:43 UTC

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