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

Iñaki Baz Castillo <ibc@aliax.net> Tue, 18 October 2011 08:48 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 C573121F8C84 for <rtcweb@ietfa.amsl.com>; Tue, 18 Oct 2011 01:48:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.626
X-Spam-Level:
X-Spam-Status: No, score=-2.626 tagged_above=-999 required=5 tests=[AWL=0.051, 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 4UzsbvMLS747 for <rtcweb@ietfa.amsl.com>; Tue, 18 Oct 2011 01:48:46 -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 3878D21F8C83 for <rtcweb@ietf.org>; Tue, 18 Oct 2011 01:48:46 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so352067vcb.31 for <rtcweb@ietf.org>; Tue, 18 Oct 2011 01:48:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.35.34 with SMTP id e2mr1332694vdj.52.1318927725609; Tue, 18 Oct 2011 01:48:45 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Tue, 18 Oct 2011 01:48:45 -0700 (PDT)
In-Reply-To: <2E239D6FCD033C4BAF15F386A979BF51159994@sonusinmail02.sonusnet.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> <0950F0E1-6E4B-407F-9563-654AFE79F64B@ag-projects.com> <2E239D6FCD033C4BAF15F386A979BF51159994@sonusinmail02.sonusnet.com>
Date: Tue, 18 Oct 2011 10:48:45 +0200
Message-ID: <CALiegfm_FN5hTyPupjOHLPwX--YPV-gewusvi9+JtV3i1ONpJw@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Ravindran Parthasarathi <pravindran@sonusnet.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: 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: Tue, 18 Oct 2011 08:48:46 -0000

2011/10/18 Ravindran Parthasarathi <pravindran@sonusnet.com>;:
> Saul,
>
> One minor correction in your mail: I have mentioned "SIP over websocket" is an overkill and not SIP.

Ravindran, please forget "SIP over WebSocket". I've never proposed it
to be a default RTCweb signaling protocol, not at all, so if you don't
like it just don't use it.

BTW what I understand given your insistent proposal is that you need
the RTCweb signaling protocol (messages in-the-wire) to be an IETF
standard so you get a market for building and selling gateway boxes
between such "IETF-RTCweb-Protocol" and other IETF standard protocols
(as SIP). It's clear that you like gateways and you want gateways.


Said that I apologize to this WG for some of my mails yesterday. It
won't happen again.


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