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

Cullen Jennings <fluffy@iii.ca> Sat, 20 July 2013 01:20 UTC

Return-Path: <fluffy@iii.ca>
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 31E9311E8191 for <rtcweb@ietfa.amsl.com>; Fri, 19 Jul 2013 18:20:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.352
X-Spam-Level:
X-Spam-Status: No, score=-2.352 tagged_above=-999 required=5 tests=[AWL=0.247, BAYES_00=-2.599]
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 hgm4+LHEgeRK for <rtcweb@ietfa.amsl.com>; Fri, 19 Jul 2013 18:19:58 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 5284511E8160 for <rtcweb@ietf.org>; Fri, 19 Jul 2013 18:19:58 -0700 (PDT)
Received: from sjc-vpn5-843.cisco.com (unknown [128.107.239.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 9181C22E1FA; Fri, 19 Jul 2013 21:19:57 -0400 (EDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <CAJrXDUHi3Rs4ioWqX4-ACF4crfDJT5Z71pvzzQvW_HqGqUH0VQ@mail.gmail.com>
Date: Fri, 19 Jul 2013 18:20:07 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <0D2B47D9-25BF-40C1-AC41-DF65093A6B94@iii.ca>
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>
To: Peter Thatcher <pthatcher@google.com>
X-Mailer: Apple Mail (2.1508)
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: Sat, 20 Jul 2013 01:20:03 -0000

Thanks, 

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. 


On Jul 19, 2013, at 7:51 AM, Peter Thatcher <pthatcher@google.com>; wrote:

> Here you go:
> 
> 
> 
> 
> On Fri, Jul 19, 2013 at 7:00 AM, Cullen Jennings <fluffy@iii.ca>; wrote:
> Can someone please email a full copy of the spreadsheet to the list so it is in the archives - thanks
> 
> On Jul 9, 2013, at 3:18 AM, Iñaki Baz Castillo <ibc@aliax.net>; wrote:
> 
> > 2013/7/9 Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>;:
> >> I want to be very clear and careful on what I say. So I am repeating:
> >>
> >> * My comment that I think Eric is right in that there is consensus on
> >> providing APIs that allow most use-cases to be met without SDP mangling
> >> is meant only in that context: SDP O/A is kept (and PeerConnection more
> >> or less as is and so on).
> >
> > Hi Stefan,
> >
> > You insist that "there is consensus on keeping SDP O/A but providing a
> > better API". Given current discussions IMHO it is clear there is not
> > such a consensus (not at all). Or may be you are just talking about
> > two years ago in some IETF meeting (if so I'm sorry).
> >
> > Please review the results in
> > https://docs.google.com/a/aliax.net/spreadsheet/ccc?key=0AuaKXw3SkHMSdHlZdV9RN0xSWFhybVl4anJLRkVPV0E#gid=1
> >
> >  Bad for advanced stuff: 94%
> >  OK for 1.0: 40%
> >
> > IMHO such a result indicates all but "let's keep SDP O/A and improve a
> > bit the API" (I mean now, in July 2013).
> >
> >
> > Best regards.
> >
> >
> >
> > --
> > Iñaki Baz Castillo
> > <ibc@aliax.net>;
> > _______________________________________________
> > 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
> 
> <Input from JS Developers on their experience with the WebRTC API - Inputs.csv>