[rtcweb] draft-ibc-rtcweb-sip-websocket -- WebSocket Transport for Session Initiation Protocol (SIP)
José Luis Millán <jmillan@aliax.net> Tue, 13 September 2011 20:48 UTC
Return-Path: <jmillan@aliax.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 27A9721F8CD5 for <rtcweb@ietfa.amsl.com>; Tue, 13 Sep 2011 13:48:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 UXIn1Vl8bOXr for <rtcweb@ietfa.amsl.com>; Tue, 13 Sep 2011 13:48:48 -0700 (PDT)
Received: from mail-gy0-f194.google.com (mail-gy0-f194.google.com [209.85.160.194]) by ietfa.amsl.com (Postfix) with ESMTP id 1BE9B21F8CD4 for <rtcweb@ietf.org>; Tue, 13 Sep 2011 13:48:48 -0700 (PDT)
Received: by gyd10 with SMTP id 10so132096gyd.1 for <rtcweb@ietf.org>; Tue, 13 Sep 2011 13:50:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.66.14 with SMTP id l14mr9623194ibi.69.1315947054572; Tue, 13 Sep 2011 13:50:54 -0700 (PDT)
Received: by 10.231.36.201 with HTTP; Tue, 13 Sep 2011 13:50:54 -0700 (PDT)
Date: Tue, 13 Sep 2011 22:50:54 +0200
Message-ID: <CABw3bnO+85i-TtuqS+P4n+rYgyxyoASc8HXpADhy4QPTC0_szA@mail.gmail.com>
From: José Luis Millán <jmillan@aliax.net>
To: rtcweb@ietf.org, Markus.Isomaki@nokia.com
Content-Type: multipart/alternative; boundary="00151773e028bb25ca04acd8cc63"
Subject: [rtcweb] draft-ibc-rtcweb-sip-websocket -- WebSocket Transport for Session Initiation Protocol (SIP)
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, 13 Sep 2011 20:48:49 -0000
On Tue, Sep 13, 2011 at 9:25 PM, <Markus.Isomaki@nokia.com> wrote: > Hi Inaki, > > Fully agree about everything you say below. Hi, Sorry if this mail arrives out of the original mail thread. > > It would be interesting to understand the performance differences of the native vs. Javascript SIP stack, if there is anything we should be worried about. This is my only concern when (perhaps one day) applying RTCWeb in devices like smartphones. If the JS stack works in (any of) today's high end smartphones without problems, we should be fine. The are no meaningful performance penalties at all using the JavaScript SIP stack in our prototype. In fact, multiple SIP stack instances can run in a single Web browser freshly. BTW, is there any WebSocket capable web browser for smartphones? > > Markus > > >>-----Original Message----- >>From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf >>Of ext Iñaki Baz Castillo >>Sent: 13 September, 2011 21:23 >>To: Ravindran Parthasarathi >>Cc: rtcweb@ietf.org >>Subject: Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- WebSocket Transport >>for Session Initiation Protocol (SIP) >> >>2011/9/13 Ravindran Parthasarathi <pravindran@sonusnet.com>: >>> Hi Inaki, >>> >>> I like the idea of using SIP between browser & server. >>> >>> I really don't know the strong reason for tunneling SIP message within >>websocket. In fact, we are discussing SIP vs websocket in >>http://www.ietf.org/mail-archive/web/rtcweb/current/msg01071.html mail >>thread as signaling protocol for RTCweb. Could you please mention the >>technical advantage in going in the path of SIP over websocket rather than >>having plain SIP connection over TCP or TLS or (UDP or DTLS). >> >>Hi Ravindran, >> >>SIP is a complex protocol and there are numerous extensions and features in >>many RFC's extending the SIP protocol. Having to rely on the features >>implemented in a native SIP stack within the web-browser seems not enough >>flexible IMHO. I also expect many limitations and lack-of-features in the >>different SIP implementations of each browser (and each version of the >>browser). >> >>In the other side, if the SIP stack is coded within a JavaScript library and makes >>usage of the WebSocket protocol, innovation depends on the developer and >>not on the browser native capabilities. A web page could offer a minimal SIP >>stack just implementing basic outgoing calls (i.e. "Click2Call" buttons in the >>web), while another web page could prefer to provide a powerful SIP stack >>implementing blink/attended transfer, subscription to presence and >>dialogs/calls, conference features, call-pickup, SIP messaging and so on >>(imagine such phone integrated within an enterprise intranet). I don't expect >>that the SIP stack integrated within *every* existing web-browsers would >>implement all those SIP features in a correct way (because that does not >>happen neither when using expensive SIP desktop phones or softphones). >> >>Also, the specification defined in the draft solves NAT issues (at signaling >>level) without requiring server side solutions for fixing NAT in clients. >> >>WebSocket protocol is becoming a new "transport" protocol. >>Implementing SIP protocol on top of it can only bring advantages and new >>possibilities. The specification in the draft is an adaptation of SIP to make use >>of WebSocket, as it already does with UDP, TCP and SCTP transports. >> >> >>BTW, as said in the first mail, we have published the draft after having a >>working prototype making usage of the specification described in the >>document. After that, we see no real advantage on having a native SIP stack >>within a web browser. The prototype will be shown soon. >> >>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 >
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Markus.Isomaki
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Ravindran Parthasarathi
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Roman Shpount
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Iñaki Baz Castillo
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Igor Faynberg
- [rtcweb] draft-ibc-rtcweb-sip-websocket -- WebSoc… Iñaki Baz Castillo
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Markus.Isomaki
- [rtcweb] draft-ibc-rtcweb-sip-websocket -- WebSoc… José Luis Millán
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Markus.Isomaki
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Thomas
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Bernard Aboba
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Dzonatas Sol
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Ravindran Parthasarathi
- [rtcweb] draft-ibc-rtcweb-sip-websocket -- WebSoc… José Luis Millán
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Binod PG
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Patrick McManus
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Hadriel Kaplan
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Binod PG
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Avasarala, Ranjit
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Markus.Isomaki
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Saúl Ibarra Corretgé
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Iñaki Baz Castillo
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Iñaki Baz Castillo
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Christer Holmberg
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Ravindran Parthasarathi
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket José Luis Millán
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Iñaki Baz Castillo
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Christer Holmberg
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Iñaki Baz Castillo
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Iñaki Baz Castillo
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Ravindran Parthasarathi
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Olle E. Johansson
- Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket Tim Panton
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Tim Panton
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Roman Shpount
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Randell Jesup
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Roman Shpount
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Markus.Isomaki
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Roman Shpount
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Igor Faynberg
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Dzonatas Sol
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Randell Jesup
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Markus.Isomaki
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Dzonatas Sol
- [rtcweb] Need for Default signaling protocol for … Ravindran Parthasarathi
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Saúl Ibarra Corretgé
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Markus.Isomaki
- Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- We… Dan Wing