Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface

Hadriel Kaplan <hadriel.kaplan@oracle.com> Tue, 23 July 2013 19:37 UTC

Return-Path: <hadriel.kaplan@oracle.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5315811E8379 for <rtcweb@ietfa.amsl.com>; Tue, 23 Jul 2013 12:37:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.409
X-Spam-Level:
X-Spam-Status: No, score=-6.409 tagged_above=-999 required=5 tests=[AWL=-0.110, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YReIC5HoIS2m for <rtcweb@ietfa.amsl.com>; Tue, 23 Jul 2013 12:37:20 -0700 (PDT)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) by ietfa.amsl.com (Postfix) with ESMTP id D440F11E80D5 for <rtcweb@ietf.org>; Tue, 23 Jul 2013 12:37:19 -0700 (PDT)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r6NJbG5W023761 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 23 Jul 2013 19:37:16 GMT
Received: from userz7022.oracle.com (userz7022.oracle.com [156.151.31.86]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r6NJbCLJ001810 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Jul 2013 19:37:15 GMT
Received: from abhmt102.oracle.com (abhmt102.oracle.com [141.146.116.54]) by userz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r6NJbBqU015567; Tue, 23 Jul 2013 19:37:11 GMT
Received: from [10.1.21.23] (/10.5.21.23) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 23 Jul 2013 12:37:11 -0700
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Hadriel Kaplan <hadriel.kaplan@oracle.com>
In-Reply-To: <CALiegfmybzZTS9CG2k3gLdD7ic2hjDfivySWMVFi59eZchHgcA@mail.gmail.com>
Date: Tue, 23 Jul 2013 15:37:09 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <CA747A43-9E1A-418C-8A7F-92E17B2422C5@oracle.com>
References: <CAJrXDUGMohpBdi-ft-o_uE7ewFkw7wRY9x7gYEncjov7qi-Bew@mail.gmail.com> <CABcZeBPa4wBS8pYq=0wesMOfL6TkeC7QGAZ8pWwOcnkhkJqWfA@mail.gmail.com> <CAJrXDUFxo8P8wxh8jX3019yPQOuwQ0eVdsFmRXsbWdWinnc5oA@mail.gmail.com> <CABcZeBOTKpmFC34waqZ4kA-P8t+E6yY9gX1JFCHhsBH0+CF-Qw@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C30BC0F@ESESSMB209.ericsson.se> <CAD5OKxtKLMf_d=8GSMrqfNhDHPe9MFP2ZTKzZHFn9CyMr-gSVQ@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C30C833@ESESSMB209.ericsson.se> <CAJrXDUHOZf21aXgQMrdjTV8Fok+fVp-2SuhTra0JGy0Jq=Wi0Q@mail.gmail.com> <CAHp8n2mNdNiXCCNUdEvKgAsh_pPn=jNs+56VCg4PMKbUmOGztQ@mail.gmail.com> <CABkgnnUZMAuDocwZWXn9a+Xj3kkcX0uyRgjDmy-hQxpTDKWj3w@mail.gmail.com> <1447FA0C20ED5147A1AA0EF02890A64B1C30CF49@ESESSMB209.ericsson.se> <CALiegfmiRsOXL97XDzMRQ_Vvbk9zaDBBvCPxr_=zbDJbnMZ_8A@mail.gmail.com> <E795F35A-B0A5-4BD8-B807-C97B76EC586B@iii.ca> <CAJrXDUHi3Rs4ioWqX4-ACF4crfDJT5Z71pvzzQvW_HqGqUH0VQ@mail.gmail.com> <0D2B47D9-25BF-40C1-AC41-DF65093A6B94@iii.c! a> <CALiegfmybzZTS9CG2k3gLdD7ic2hjDfivySWMVFi59eZchHgcA@mail.gmail.com>
To: =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
X-Mailer: Apple Mail (2.1508)
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Summary of Application Developers' opinions of the current WebRTC API and SDP as a control surface
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jul 2013 19:37:27 -0000

On Jul 20, 2013, at 10:26 AM, Iñaki Baz Castillo <ibc@aliax.net>; wrote:

> 2013/7/20 Cullen Jennings <fluffy@iii.ca>;:
>> I will note that over half of that very small sample set is folks that have been long termed involved in SIP and VoIP so, uh, might not be a representative sample of type of people you are portraying it as.
> 
> It is even worse if people interested and expert in SIP tells you that
> the current SDP-blob-based API is really wrong for using SIP in
> WebRTC, don't you think?

No, not at all - we're all jaded from past experience and we know how bad it is already, so Cullen's right we're all tainted.  Hopefully if we ask new people, they won't know the truth and give us much more positive results instead.  Or new people might even see the SDP-based "API" and think: "Oh cool, the API is a string blob of stuff in some archaic inconsistent syntax format with hidden state-based dependencies and rules... awesome!  I always wanted to party like it's 1999, and here's my chance!"

-hadriel