Re: [rtcweb] RTCWeb default signaling protocol [was RE: About defining a signaling protocol for WebRTC (or not)]

Iñaki Baz Castillo <ibc@aliax.net> Fri, 16 September 2011 08:59 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 6351621F8BB9 for <rtcweb@ietfa.amsl.com>; Fri, 16 Sep 2011 01:59:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.648
X-Spam-Level:
X-Spam-Status: No, score=-2.648 tagged_above=-999 required=5 tests=[AWL=0.029, 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 wOiKeYXxpY2B for <rtcweb@ietfa.amsl.com>; Fri, 16 Sep 2011 01:59:47 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by ietfa.amsl.com (Postfix) with ESMTP id CA48C21F8A7A for <rtcweb@ietf.org>; Fri, 16 Sep 2011 01:59:47 -0700 (PDT)
Received: by qyk33 with SMTP id 33so3680471qyk.10 for <rtcweb@ietf.org>; Fri, 16 Sep 2011 02:02:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.66.144 with SMTP id n16mr1336600qci.178.1316163721491; Fri, 16 Sep 2011 02:02:01 -0700 (PDT)
Received: by 10.229.79.207 with HTTP; Fri, 16 Sep 2011 02:02:01 -0700 (PDT)
In-Reply-To: <2E239D6FCD033C4BAF15F386A979BF510F0C93@sonusinmail02.sonusnet.com>
References: <CALiegfnOCxyTo9ffQ272+ncdu5UdgrtDT-dn10BWGTZMEjZoCg@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF510F0C0A@sonusinmail02.sonusnet.com> <05CAC192-E462-421F-B1E5-B78DC8F60306@ag-projects.com> <2E239D6FCD033C4BAF15F386A979BF510F0C93@sonusinmail02.sonusnet.com>
Date: Fri, 16 Sep 2011 11:02:01 +0200
Message-ID: <CALiegfkURM10NXrdOYWmk4hx=takPfN=sO+hbzF-DXBA=_6i3A@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] RTCWeb default signaling protocol [was RE: About defining a signaling protocol for WebRTC (or not)]
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: Fri, 16 Sep 2011 08:59:48 -0000

2011/9/16 Ravindran Parthasarathi <pravindran@sonusnet.com>;:
> I really didn't get your argument fully because in case there is no default signaling protocol, it is unavoidable to have island of devices without gateways but you argue other way around.

A centralized signaling point is required (think about NAT). Signaling
is just supposed to be present between web-browsers visiting the same
web site, so the signaling can be perfectly carried within HTTP or
WebSocket protocol and be centralized in that server. Otherwise, are
you proposing the existence of a global/unique SIP proxy in the world
for all the web-browsers to intercommunicate?

WebRTC is not about communication between web-browsers as if they were
generic SIP phones contacting directly one to other.




> I specifically asked for the scope of your opinion on RTCWeb work is between browser-to-browser or browser-to-other end-point to know whether parallel universe has to be build or not. In case there is no default signaling protocol, it is impossible to communicate between browser-to-endpoint without gateways

Why is it impossible? If WebSocket is used as a new transport for SIP
and XMPP then web-browsers can establish a pure SIP or XMPP session
with a SIP/XMPP server implementing WebSocket transport. And for sure
that works.


Best regards.


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