Re: [rtcweb] JSEP question: How to set up simulcast for server-originated calls?

On 11/07/2018 08:39 AM, Stefan Håkansson LK wrote:
> If memory serves, we originally had the model that the author of the
> web app and the developer of the receiver of simulcast would cooperate,
> in other words the simulcast receiver would send enough info (in form
> of whatever) for the web app to correctly set up simulcast using the
> available APIs and then send an offer SDP. I think this is what Inaki
> is saying.

This works as long as the initial offer is generated by the browser.

>
> If this now has changed, and we can have the simulcast receiver send an
> SDP offer that is applied in the browser and things work (perhaps with
> some web app intervention), and we have people interested in
> implementing this, I personally see no reason why that should not be
> pursued.
Yes, there appears to be strong interest.

>
> Br, Stefan
>
> On tis, 2018-11-06 at 22:09 -0500, Bernard Aboba wrote:
>> Cullen said: 
>>
>> "Let me put this as politely and straight forward as I can.  You are
>> wrong."
>>
>> [BA] I would agree that API interoperability is needed for simulcast,
>> even if it doesn't yet exist because we're still ironing out the
>> Issues.  The interest in implementation appears to be quite high, so
>> once we figure these things out (assuming we make the specification
>> clear enough to avoid further confusion), we stand a chance of
>> interoperablity in both APIs and protocols, which is after all, the
>> point of developing a standard. 
>>
>> In that respect, I would prefer if JSEP would include some guidance
>> we could cite in WebRTC-PC, rather than having to provide
>> clarifications within the API document itself.
>>
>> On Tue, Nov 6, 2018 at 9:15 PM Cullen Jennings <fluffy@iii.ca> wrote:
>>>> On Nov 5, 2018, at 7:14 PM, Iñaki Baz Castillo <ibc@aliax.net>
>>>> wrote:
>>>>
>>>> If you excluded the word "interop" from any rationale, life would
>>>> be
>>>> much better, specially here where such an interop:
>>>>
>>>> 1) does not exist
>>>> 2) is not needed
>>>>
>>>> To be clear: No app in the world is or will be NEVER ready to
>>>> enable
>>>> simulcast auto-magically just because it eventually receives a
>>>> different SDP offer from the remote. The app developers would
>>>> already
>>>> figured out different ways to enable simulcast that would just
>>>> not
>>>> allow such an auto-magic "upgrade".
>>>>
>>> Let me put this as politely and straight forward as I can. You are
>>> wrong. 
>>>
>>>
>>>
>>>
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

-- 
Surveillance is pervasive. Go Dark.