Re: it's time to expel SDP from our lives

Iñaki Baz Castillo <[email protected]>
Newsgroups gmane.ietf.mmusic
Message-ID <CALiegfnnXOYxHhsB_SewU2XqNGd_+LAWwsBuw8U5kKBW5Of07g@mail.gmail.com>
2017-06-14 13:05 GMT+02:00 Christer Holmberg <[email protected]>:
>>As said in a previous comments, there is no need for a SDP
>>replacement. Nobody is asking for SDP 2.0 but, instead, "define the
>>multimedia parameters and let me signal them in my preferred way".
>
> Well, in order to have interoperability, people need to have a common
> preferred way. That¹s why we do standardisation.

And that's why SDP already exists. But that does not mean that we need
that WebRTC is SDP based.


> In WebRTC, if people download the same web site, they will automatically
> get the same parameter signalling mechanism, no matter whether it¹s
> standardised or not. But, if people download different web each may come
> with different mechanisms, in which case they won¹t interop.

Sure, but I'm talking about that. I just focus on the communication
between the JS application and the browser's WebRTC engine, which is
made via JS API by exchanging SDP blobs.




-- 
Iñaki Baz Castillo
<[email protected]>

_______________________________________________
mmusic mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/mmusic
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.