Re: [rtcweb] SIP MUST NOT be used in browser?

"Aaron Clauson" <aaron@sipsorcery.com> Fri, 09 September 2011 13:54 UTC

Return-Path: <SRS0=7mxL/o=32=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 5A10321F8B3E for <rtcweb@ietfa.amsl.com>; Fri, 9 Sep 2011 06:54:07 -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 zxwquSeyNaYn for <rtcweb@ietfa.amsl.com>; Fri, 9 Sep 2011 06:54:06 -0700 (PDT)
Received: from bosmailout03.eigbox.net (bosmailout03.eigbox.net [66.96.190.3]) by ietfa.amsl.com (Postfix) with ESMTP id 745AD21F8AFA for <rtcweb@ietf.org>; Fri, 9 Sep 2011 06:54:06 -0700 (PDT)
Received: from bosmailscan17.eigbox.net ([10.20.15.17]) by bosmailout03.eigbox.net with esmtp (Exim) id 1R21Ym-0004Cl-MR for rtcweb@ietf.org; Fri, 09 Sep 2011 09:56:00 -0400
Received: from bosimpout01.eigbox.net ([10.20.55.1]) by bosmailscan17.eigbox.net with esmtp (Exim) id 1R21Yl-0000Bs-FA for rtcweb@ietf.org; Fri, 09 Sep 2011 09:55:59 -0400
Received: from bosauthsmtp09.eigbox.net ([10.20.18.9]) by bosimpout01.eigbox.net with NO UCE id Wdvz1h00B0BkY8i01dvzsg; Fri, 09 Sep 2011 09:55:59 -0400
X-EN-OrigOutIP: 10.20.18.9
X-EN-IMPSID: Wdvz1h00B0BkY8i01dvzsg
Received: from cpe-124-179-251-248.lns3.dav.bigpond.net.au ([124.179.251.248] helo=AaronPC) by bosauthsmtp09.eigbox.net with esmtpa (Exim) id 1R21Yk-0003Ki-8S for rtcweb@ietf.org; Fri, 09 Sep 2011 09:55:59 -0400
From: "Aaron Clauson" <aaron@sipsorcery.com>
To: <rtcweb@ietf.org>
References: <A444A0F8084434499206E78C106220CA0B00FDB08B@MCHP058A.global-ad.net> <89177AB2-F721-47E4-8471-2180EDA10615@voxeo.com> <A444A0F8084434499206E78C106220CA0B00FDB34D@MCHP058A.global-ad.net> <496EE152-41F2-49AB-A136-05735FE5A9F9@voxeo.com><101C6067BEC68246B0C3F6843BCCC1E31018BF6BE2@MCHP058A.global-ad.net> <4E540FE2.7020605@alcatel-lucent.com> <2E239D6FCD033C4BAF15F386A979BF5106423F@sonusinmail02.sonusnet.com> <4E6595E7.7060503@skype.net> <4E661C83.5000103@alcatel-lucent.com> <4E668FB3.9020601@skype.net> <2E239D6FCD033C4BAF15F386A979BF510F08FE@sonusinmail02.sonusnet.com> <4E67AD3D.9000005@alvestrand.no> <2E239D6FCD033C4BAF15F386A979BF510F090F@sonusinmail02.sonusnet.com> <4E686663.1050900@alvestrand.no> <4E68CB68.3020100@alcatel-lucent.com> <4E68D182.2090003@alvestrand.no> <4E68D742.4010203@alcatel-lucent.com> <4E68D8B5.7010602@alvestrand.no> <4E6915F2.5000007@alcatel-lucent.com> <4E691CC6.9050905@stpeter.im> <4E695648.2000001@alcatel-lucent.com>
In-Reply-To: <4E695648.2000001@alcatel-lucent.com>
Date: Fri, 9 Sep 2011 23:55:49 +1000
Message-ID: <017201cc6ef8$33f571d0$9be05570$@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: AcxugwPGZZwx2t5GRiO1eoON13qQJAAcqVZQ
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.248
X-EN-OrigHost: cpe-124-179-251-248.lns3.dav.bigpond.net.au
Subject: Re: [rtcweb] SIP MUST NOT be used in browser?
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: Fri, 09 Sep 2011 13:57:13 -0000

Another 2 cents from a SIP person.

I think attempting to incorporate SIP (or Jingle et al) into RTCWeb would be
a bad idea for the reason that it would significantly slow down and
complicate the standard. If SIP is included in RTCWeb then there will need
to be a discussion, already emerging here, about which parts of SIP to
include and all the other intricacies of SIP; transports, sips vs sip,
request routing etc etc. 

Writing a javascript SIP stack is a small task compared to getting the
RTCWeb media capabilities built into browsers. As soon as the first browser
appears that supports RTP then javascript SIP stacks will start popping up
all over the place.

I for one would love to be able to process calls in my browser and to be
able to do it yesterday. Slowing the RTCWeb process down for something that
will take care of itself anyway, namely readily available javascript
signalling libraries, would be a shame.

Aaron