Re: [MMUSIC] [rtcweb] Translating Plan A into No Plan (Was: No Plan)

[Emil Ivov <[e-mail]>]

Hey Eric,

On 04.06.13, 03:47, Eric Rescorla wrote:
> On Mon, Jun 3, 2013 at 2:29 PM, Emil Ivov <[e-mail]> wrote:
<snip>
>         So, just for clarity: you mean that A advertises one m-lin, B
>         accepts,
>         and then A sends some arbitrary number of media flows,
>
>
>     Yes.
>
>         identified
>         by SSRC?
>
>
>     What does "identified" mean?
>
>
> I mean demultiplexed by SSRC.

Demuxing by SSRC, as in being able to distinguish one RTP stream from 
another is totally OK and there's no issue with this in No Plan. SSRCs 
will be different and packets will be assigned to different media 
streams. What isn't OK is the need to know specific SSRC values in order 
to perform the demuxing. This is not necessary for demuxing with No 
Plan. Do you agree?


>         If so, I've got some questions:
>
>         - If B can only display one video stream, how does it say so?
>
>
>     This is something that one app needs to tell another app. They can
>     do so however they wish. As far as browsers are concerned: the
>     transmitter just sends whatever the application instructs. The
>     receiver just handles whatever it can.
>
>
> But there needs to be a complete set of API surfaces that allow
> both sides to do the right thing.

Yes, hence section 7 in No Plan:

http://tools.ietf.org/html/draft-ivov-rtcweb-noplan-00#section-7

>         - How does B tell A not to send various streams?
>
>
>     What does "various" streams mean? If what you have in mind is: How
>     does B tell A: "don't send me SSRCs 1, 2, 3 and 5" but keep 4 going,
>     then B would send the list of SSRCs in app-specific signalling and A
>     would stop sending them.
>
>
> Uh, how does that work? Is there some API that I'm unaware of that
> allows JS to get the SSRCs?

I don't think there is. I believe you can get part of the information 
through the stats API but I don't think this is enough. Hence Section 7.

> And another one that allows the JS
> to say "don't send SSRC A"?

As long as the JS knows the SSRC of a specific track it can just disable 
that specific track. There's no need to tell the browser "don't send 
SSRC A".

> It would be really helpful if you could provide a complete example of
> exactly what each side does. I'm find if you just invent some
> application-specific
> signaling for this purpose, but what I'd like to see is exactly what API
> calls each side makes.

Does the above answer your question, or would you like me to come up 
with an example of how these new APIs could look?

Emil
>
> -Ekr
>
>
>

-- 
https://jitsi.org