IETF Logo Mail Archive

Re: [rtcweb] draft-ibc-rtcweb-sip-websocket -- WebSocket Transport for Session Initiation Protocol (SIP)

"Ravindran Parthasarathi" <pravindran@sonusnet.com> Tue, 13 September 2011 17:41 UTC

Return-Path: <pravindran@sonusnet.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 A15B621F8B82 for <rtcweb@ietfa.amsl.com>; Tue, 13 Sep 2011 10:41:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.342
X-Spam-Level:
X-Spam-Status: No, score=-2.342 tagged_above=-999 required=5 tests=[AWL=-0.043, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 pM5rBXXzxH6W for <rtcweb@ietfa.amsl.com>; Tue, 13 Sep 2011 10:41:50 -0700 (PDT)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id DB56421F8B81 for <rtcweb@ietf.org>; Tue, 13 Sep 2011 10:41:49 -0700 (PDT)
Received: from sonusmail04.sonusnet.com (sonusmail04.sonusnet.com [10.128.32.98]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id p8DHiPjH026874; Tue, 13 Sep 2011 13:44:25 -0400
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail04.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 13 Sep 2011 13:43:00 -0400
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Tue, 13 Sep 2011 23:12:54 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Message-ID: <2E239D6FCD033C4BAF15F386A979BF510F0B37@sonusinmail02.sonusnet.com>
In-Reply-To: <CALiegfk6BhtzErXOQM8iSV7FC6isYUwOS1KPYCw_M1vEcNP6eQ@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rtcweb] draft-ibc-rtcweb-sip-websocket -- WebSocket Transport for Session Initiation Protocol (SIP)
Thread-Index: AcxyOG/sBOMj88yzRPmZLZBdgHCRKAAAxkxQ
References: <CALiegfk6BhtzErXOQM8iSV7FC6isYUwOS1KPYCw_M1vEcNP6eQ@mail.gmail.com>
From: Ravindran Parthasarathi <pravindran@sonusnet.com>
To: Iñaki Baz Castillo <ibc@aliax.net>, rtcweb@ietf.org
X-OriginalArrivalTime: 13 Sep 2011 17:43:00.0849 (UTC) FILETIME=[94E43610:01CC723C]
Subject: Re: [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 17:41:50 -0000

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).

Thanks
Partha
 
>-----Original Message-----
>From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf
>Of Iñaki Baz Castillo
>Sent: Tuesday, September 13, 2011 10:43 PM
>To: rtcweb@ietf.org
>Subject: [rtcweb] draft-ibc-rtcweb-sip-websocket -- WebSocket Transport
>for Session Initiation Protocol (SIP)
>
>Hi all,
>
>A draft describing a mechanism for usage of WebSocket protocol as the
>transport between SIP entities has been submitted and can be found at:
>
>  HTML:  http://tools.ietf.org/html/draft-ibc-rtcweb-sip-websocket-00
>  TXT:     http://www.ietf.org/id/draft-ibc-rtcweb-sip-websocket-00.txt
>
>
>Abstract
>
>   This document specifies a WebSocket subprotocol for a new transport
>   in SIP (Session Initiation Protocol).  The WebSocket protocol enables
>   two-way realtime communication between clients (typically web-based
>   applications) and servers.  The main goal of this specification is to
>   integrate the SIP protocol within web applications.
>
>
>We produced this initial version after implementing a working prototype.
>
>
>Your feedback is always welcome,
>The Authors
>
>
>--
>Iñaki Baz Castillo
><ibc@aliax.net>
>_______________________________________________
>rtcweb mailing list
>rtcweb@ietf.org
>https://www.ietf.org/mailman/listinfo/rtcweb

v2.23.0 | Report a Bug | By Email