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 15:51:46 +0200
Message-ID: <CALiegf=9__fah+h-+K1OH0ORDQqof0sZO=g7XgaYVodPODFYdg@mail.gmail.com>
To: Robin Raymond <robin@hookflash.com>
Cc: Martin Steinmann <martin@ezuce.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
2013/7/20 Robin Raymond <robin@hookflash.com>

> FYI - this "revolt" also consists of SIP people who are against this SDP
> mandate too, not just a bunch of 'new' tech guys.



Jose Luis Millan is the main autor of JsSIP [*] and I'm core author. We
both are "SIP guys" and now also "WebRTC guys". And we find that the
current SDP-blob based API is terrible, and the direction of the WG ("let's
add some API methods to avoid having to mangle the SDP") is wrong. We are
fully interested in being able to use SDP as media wire signaling, but
mandating SDP as the API surface for WebRTC is really terrible.

Let W3C experts to define a good JS API for WebRTC (with no SDP), let
MMUSIC WG to define a SDP format for WebRTC, and then let JavaScript SIP
experts to build JS libraries on top of it to play the SDP game, and we all
will be happy. And telcos will be much more happy than they think. Let's
get rid of all the SDP O/A stuff in the browser. The browser is not a phone
and "fixed logic + fixed code" does not work here.


Best regards.


[*] JsSIP:  http://jssip.net


-- 
Iñaki Baz Castillo
<ibc@aliax.net>
Received on Saturday, 20 July 2013 13:52:33 UTC

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