IETF Logo Mail Archive

Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket

Hadriel Kaplan <HKaplan@acmepacket.com> Wed, 14 September 2011 05:21 UTC

Return-Path: <HKaplan@acmepacket.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 C98B421F8C66 for <rtcweb@ietfa.amsl.com>; Tue, 13 Sep 2011 22:21:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.511
X-Spam-Level:
X-Spam-Status: No, score=-2.511 tagged_above=-999 required=5 tests=[AWL=0.088, 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 6X6iadM0LEv5 for <rtcweb@ietfa.amsl.com>; Tue, 13 Sep 2011 22:21:00 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id 96CE121F8C6C for <rtcweb@ietf.org>; Tue, 13 Sep 2011 22:21:00 -0700 (PDT)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Wed, 14 Sep 2011 01:23:05 -0400
Received: from MAIL1.acmepacket.com ([169.254.1.150]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Wed, 14 Sep 2011 01:23:05 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Binod PG <binod.pg@oracle.com>
Thread-Topic: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket
Thread-Index: AQHMcp5hzWFMPh2uPkK6gmL4ZhCr6Q==
Date: Wed, 14 Sep 2011 05:23:04 +0000
Message-ID: <7B7B2040-1523-4C10-8B9B-D4EE3FB541A9@acmepacket.com>
References: <CALiegfk6BhtzErXOQM8iSV7FC6isYUwOS1KPYCw_M1vEcNP6eQ@mail.gmail.com>, <2E239D6FCD033C4BAF15F386A979BF510F0B37@sonusinmail02.sonusnet.com>, <E44893DD4E290745BB608EB23FDDB7620AEC41@008-AM1MPN1-043.mgdnok.nokia.com> <BLU152-W91B8D02E434D6209F379393050@phx.gbl> <1810E0F6-9600-4BF5-82A9-ADCC07103999@oracle.com>
In-Reply-To: <1810E0F6-9600-4BF5-82A9-ADCC07103999@oracle.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4BFF11ACBA75E547AEBD74B2A4F2AFCB@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Subject: Re: [rtcweb] draft-ibc-rtcweb-sip-vs-websocket
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, 14 Sep 2011 05:21:01 -0000

On Sep 14, 2011, at 12:38 AM, Binod PG wrote:

> 
> On 14-Sep-11, at 3:34 AM, Bernard Aboba wrote:
>> 
>> [BA] That may be your opinion.  Others may choose to transport SIP over HTTP or HTTPS, or choose some other signaling protocol entirely (e.g. XMPP).  The beauty of RTCWEB is to enable the choice to be made by application developers according to their needs. 
> 
> How do you see a media gateway library in the (web) server handle all such signaling protocols/transport? Would RTCWeb provide/have a mechanism
> to indicate the protocol/signal chosen by the application?

No.  The server is deployed by the same people who deploy the javascript, since by definition the javascript is provided by that server.  It's not a mystery to the web server what the "signaling protocol" used between the javascript and the server is - its whatever the developer of the javascript and server-side code decides it to be.  It doesn't have to be any standard whatsoever, because there is no interoperability problem to solve between them.  It could be XMPP, or it could be SIP, or it could be MGCP, or it could be Skinny/SCCP, or it could be create-your-own.  There may well be pre-packaged js libraries available which do it all for you, but they can do it however they like. 

-hadriel

v2.23.0 | Report a Bug | By Email