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

Iñaki Baz Castillo <> Fri, 16 September 2011 08:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AC50021F8AEA for <>; Fri, 16 Sep 2011 01:31:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.349
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id rDUUNb2QA8Fs for <>; Fri, 16 Sep 2011 01:31:50 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id EE7F221F8557 for <>; Fri, 16 Sep 2011 01:31:49 -0700 (PDT)
Received: by qyk33 with SMTP id 33so3657962qyk.10 for <>; Fri, 16 Sep 2011 01:34:03 -0700 (PDT)
MIME-Version: 1.0
Received: by with SMTP id q41mr1671708qci.216.1316162043602; Fri, 16 Sep 2011 01:34:03 -0700 (PDT)
Received: by with HTTP; Fri, 16 Sep 2011 01:34:03 -0700 (PDT)
In-Reply-To: <>
References: <> <> <> <> <>
Date: Fri, 16 Sep 2011 10:34:03 +0200
Message-ID: <>
From: Iñaki Baz Castillo <>
To: Hadriel Kaplan <>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: "<>" <>
Subject: Re: [rtcweb] RTCWeb default signaling protocol [was RE: About defining a signaling protocol for WebRTC (or not)]
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 16 Sep 2011 08:31:50 -0000

2011/9/16 Hadriel Kaplan <>:
> 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.


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).


Iñaki Baz Castillo