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:31 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 AC50021F8AEA for <rtcweb@ietfa.amsl.com>; Fri, 16 Sep 2011 01:31:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level:
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[AWL=-0.272, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_46=0.6, 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 rDUUNb2QA8Fs for <rtcweb@ietfa.amsl.com>; Fri, 16 Sep 2011 01:31:50 -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 EE7F221F8557 for <rtcweb@ietf.org>; Fri, 16 Sep 2011 01:31:49 -0700 (PDT)
Received: by qyk33 with SMTP id 33so3657962qyk.10 for <rtcweb@ietf.org>; Fri, 16 Sep 2011 01:34:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.67.105 with SMTP id q41mr1671708qci.216.1316162043602; Fri, 16 Sep 2011 01:34:03 -0700 (PDT)
Received: by 10.229.79.207 with HTTP; Fri, 16 Sep 2011 01:34:03 -0700 (PDT)
In-Reply-To: <16880306-5B3A-4EFD-ADE4-1201138D9182@acmepacket.com>
References: <CALiegfnOCxyTo9ffQ272+ncdu5UdgrtDT-dn10BWGTZMEjZoCg@mail.gmail.com> <2E239D6FCD033C4BAF15F386A979BF510F0C0A@sonusinmail02.sonusnet.com> <05CAC192-E462-421F-B1E5-B78DC8F60306@ag-projects.com> <2E239D6FCD033C4BAF15F386A979BF510F0C93@sonusinmail02.sonusnet.com> <16880306-5B3A-4EFD-ADE4-1201138D9182@acmepacket.com>
Date: Fri, 16 Sep 2011 10:34:03 +0200
Message-ID: <CALiegfmNFArx7sdc9PmdZpa96NmS69aiNraL5nxj2mV5wAE_tQ@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "<rtcweb@ietf.org>" <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:31:50 -0000

2011/9/16 Hadriel Kaplan <HKaplan@acmepacket.com>;:
> The only thing we need to do for rtcweb is make sure the RTP library built into the browser supports media in such a way that it can communicate with other RTP peers at a media plane, regardless of what signaling protocol those peers might be using, preferably without going through media gateways.  And obviously since SIP is a very common protocol and defined by the IETF we need to make sure it's possible to use SIP on the rtcweb server, but we can't *mandate* that it be used or supported, and if we did it wouldn't change anything.

+1

The only I expect is that a WebRTC web-browser can establish a RTP
session with a remote SIP or XMPP+Jingle endpoint (without requiring
media gateways !!). How the signaling (SIP or XMPP) is carried between
the real SIP/XMPP endpoint and the browser should be out of the scope
of rtcweb (IMHO). Having said that, we have already shown a working
solution for carrying SIP between web-browsers and real SIP entities
out there (SIP over WebSocket). The same can be done for any other
protocol (it's already specified also for XMPP).

Regards.



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