Re: [rtcweb] Review request for RTCWeb standard signaling protocol

Iñaki Baz Castillo <ibc@aliax.net> Mon, 17 October 2011 17:21 UTC

Return-Path: <ibc@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 F32B221F8BBB for <rtcweb@ietfa.amsl.com>; Mon, 17 Oct 2011 10:21:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.591
X-Spam-Level:
X-Spam-Status: No, score=-2.591 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 swwJIhWoZCRV for <rtcweb@ietfa.amsl.com>; Mon, 17 Oct 2011 10:21:12 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 70CF221F8B94 for <rtcweb@ietf.org>; Mon, 17 Oct 2011 10:21:12 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so3329918vcb.31 for <rtcweb@ietf.org>; Mon, 17 Oct 2011 10:21:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.73.166 with SMTP id m6mr4632935vdv.18.1318872071649; Mon, 17 Oct 2011 10:21:11 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Mon, 17 Oct 2011 10:21:11 -0700 (PDT)
In-Reply-To: <1F2A2C70609D9E41844A2126145FC0980416C9DD@HKGMBOXPRD22.polycom.com>
References: <2E239D6FCD033C4BAF15F386A979BF510F1367@sonusinmail02.sonusnet.com> <4E8AC222.4050308@alvestrand.no> <2E239D6FCD033C4BAF15F386A979BF510F14CE@sonusinmail02.sonusnet.com> <CALiegf=ejF2kUC1m=74o9eprF1M8wYtgE-Crwa1x14rzDOf+gQ@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF510F14FD@sonusinmail02.sonusnet.com> <393F1888-F834-4DAE-B6B1-1C5D35EE3292@phonefromhere.com> <CAOg=WDcC9t2KhQUg0gDJ60gO_2mNyMv9HKt=otCdPDfj4TnoTg@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF510F152B@sonusinmail02.sonusnet.com> <CABRok6mM7TfbLgGhoQvdRh1Kwoi5BhRweLcqWg7VZOFnaa8VOw@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF510F1532@sonusinmail02.sonusnet.com> <CABRok6n33QK0Si1Y0kT7+U0zgAWsJ4d5GENK_KL-JPx5a4erYg@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF511598EE@sonusinmail02.sonusnet.com> <665A16AB-AAD8-42B3-AC17-7E629EA2DE35@phonefromhere.com> <2E239D6FCD033C4BAF15F386A979BF5115992E@sonusinmail02.sonusnet.com> <CALiegfmrncjsLVSiWk0tEgzwB00YaBGiqj0SDf9JTm9p1ZNoVA@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF51159950@sonusinmail02.sonusnet.com> <1F2A2C70609D9E41844A2126145FC0980416C9DD@HKGMBOXPRD22.polycom.com>
Date: Mon, 17 Oct 2011 19:21:11 +0200
Message-ID: <CALiegfn0XqaR3Y7EaB9bKXq_FAjm3WD5OrVaV+CQzuLigYhf2g@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: "Avasarala, Ranjit" <Ranjit.Avasarala@polycom.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Review request for RTCWeb standard signaling protocol
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: Mon, 17 Oct 2011 17:21:13 -0000

2011/10/17 Avasarala, Ranjit <Ranjit.Avasarala@polycom.com>;:
> Though I agree with you that SIP over Websockets is an overkill on web browsers,

And you can assert that because.... oh, you cannot! or have you tried it?


> My point is there is a need for some kind of signaling protocol to be used over Websockets - be it SIP or XMPP -  but these should be used as Websocket sub protocol

Sure. Check http://tools.ietf.org/html/draft-ibc-rtcweb-sip-websocket-00

-----------------------------------------
Abstract

   This document specifies a WebSocket subprotocol for a new transport
   in SIP (Session Initiation Protocol). [...]
------------------------------------------


-- 
Iñaki Baz Castillo
<ibc@aliax.net>;