W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2013

Re: On babies and bathwater (was Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface)

From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Sat, 20 Jul 2013 16:12:03 +0200
Message-ID: <CALiegfkLic4WMA9PDqPTDvGH7tDyO5mdpxwoaVct9rZmGrb1Ww@mail.gmail.com>
To: Cullen Jennings <fluffy@iii.ca>
Cc: Martin Thomson <martin.thomson@gmail.com>, Adam Roach <adam@nostrum.com>, "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>, "<rtcweb@ietf.org>" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
2013/7/20 Iñaki Baz Castillo <ibc@aliax.net>:
> 2013/7/20 Cullen Jennings <fluffy@iii.ca>:
>> It's not true when a browser from one vendor running an application from a scone vendor needs to talk to video conferencing system from a third vendor.
>
> In the WWW, the servide provider provides both the server side (in
> this case the Web and the video conference server) and the client side
> (the JS). Your concern is good for a SIP phone but not for a browser
> nor for a JS custom application controlled and designed by the
> provider.

Cullen, could you please give your opinion about what I've said above?
I also would like to know what happens if the video conference server
uses Jingle or any future RTC protocol (which uses RTP but no SDP for
media sig).

Thanks a lot.


--
Iñaki Baz Castillo
<ibc@aliax.net>
Received on Saturday, 20 July 2013 14:12:50 UTC

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