Re: [rtcweb] A plea for simplicity, marketability - and... who are we designing RTCWEB for?

"Aaron Clauson" <aaron@sipsorcery.com> Wed, 19 October 2011 22:38 UTC

Return-Path: <SRS0=DlSx9b=5C=sipsorcery.com=aaron@eigbox.net>
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 5C46521F8A55 for <rtcweb@ietfa.amsl.com>; Wed, 19 Oct 2011 15:38:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 fWParW-xai9l for <rtcweb@ietfa.amsl.com>; Wed, 19 Oct 2011 15:38:27 -0700 (PDT)
Received: from bosmailout07.eigbox.net (bosmailout07.eigbox.net [66.96.188.7]) by ietfa.amsl.com (Postfix) with ESMTP id C961421F8A4E for <rtcweb@ietf.org>; Wed, 19 Oct 2011 15:38:27 -0700 (PDT)
Received: from bosmailscan05.eigbox.net ([10.20.15.5]) by bosmailout07.eigbox.net with esmtp (Exim) id 1RGemI-0007p1-Nz for rtcweb@ietf.org; Wed, 19 Oct 2011 18:38:26 -0400
Received: from bosimpout02.eigbox.net ([10.20.55.2]) by bosmailscan05.eigbox.net with esmtp (Exim) id 1RGemI-0002GR-IZ for rtcweb@ietf.org; Wed, 19 Oct 2011 18:38:26 -0400
Received: from bosauthsmtp11.eigbox.net ([10.20.18.11]) by bosimpout02.eigbox.net with NO UCE id mmeS1h0030EKspE01meS3J; Wed, 19 Oct 2011 18:38:26 -0400
X-EN-OrigOutIP: 10.20.18.11
X-EN-IMPSID: mmeS1h0030EKspE01meS3J
Received: from cpe-124-179-251-124.lns3.dav.bigpond.net.au ([124.179.251.124] helo=AaronPC) by bosauthsmtp11.eigbox.net with esmtpa (Exim) id 1RGemG-0001ks-MW for rtcweb@ietf.org; Wed, 19 Oct 2011 18:38:26 -0400
From: "Aaron Clauson" <aaron@sipsorcery.com>
To: <rtcweb@ietf.org>
References: <9C8CA816-65FB-41A0-999C-4C43128CAAB4@danyork.org>
In-Reply-To: <9C8CA816-65FB-41A0-999C-4C43128CAAB4@danyork.org>
Date: Thu, 20 Oct 2011 09:38:19 +1100
Message-ID: <020001cc8eaf$d08cc850$71a658f0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
thread-index: AcyOYd0kC0dmKnhXQAyGmtiQGZIJWAASxeQQ
Content-Language: en-au
X-EN-UserInfo: 915df896000ea0661f52ada7de781755:376581c79ab009618cc3d679a775619e
X-EN-AuthUser: aaron@sipsorcery.com
Sender: "Aaron Clauson" <aaron@sipsorcery.com>
X-EN-OrigIP: 124.179.251.124
X-EN-OrigHost: cpe-124-179-251-124.lns3.dav.bigpond.net.au
Subject: Re: [rtcweb] A plea for simplicity, marketability - and... who are we designing RTCWEB for?
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: Wed, 19 Oct 2011 22:40:33 -0000

>-----Original Message-----
> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf
Of Dan York
>
> <snip>
> 
> The question is - will the RTCWEB/WEBRTC API/protocol/whatever be so
simple and easy that web developers will choose to use it over 
> Flash/Phono/Twilio/Java/whatever to add RTC functions to their web apps?
>
> </snip>
>
> If the answer is no, what are spending all this time for?

I thought the point of RTCWeb was so I'd be able to set up a voice call
between my browser and my VoIP Phone :). Something I can't do now with
Flash/Phono/Twilio/javascript-libraries et al at least not without one or
more media and signalling proxies in between. I originally thought RTCWeb
was going to be the bridge between the VoIP and the Web Worlds but I must
say I'm now a bit lost as to what it's about with all the different ideas
flying around at lightspeed.

My own very very humble opinion is that RTCWeb should incorporate RTP (over
UDP & TCP), a codec plugin mechanism and mircophone/speaker/camera
integration and bake it all into the browser. Everything else (signalling,
SDP, easy to use APIs etc. etc.) will be sorted out by smart devs coming up
with javascript libraries.

Aaron