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

Tim Panton <> Mon, 17 October 2011 07:57 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C0C3E21F8B12 for <>; Mon, 17 Oct 2011 00:57:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id gVuGbr7Vrjge for <>; Mon, 17 Oct 2011 00:57:17 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id EBEDC21F8801 for <>; Mon, 17 Oct 2011 00:57:16 -0700 (PDT)
Received: from [] (unknown []) by (Postfix) with ESMTP id 62CBD37A907; Mon, 17 Oct 2011 09:10:02 +0100 (BST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/alternative; boundary="Apple-Mail=_0C231C42-B1BD-45FA-95E8-210FEF0C398E"
From: Tim Panton <>
In-Reply-To: <>
Date: Mon, 17 Oct 2011 08:57:13 +0100
Message-Id: <>
References: <><><><><><><><><><> <> <>
To: Ravindran Parthasarathi <>
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [rtcweb] Review request for RTCWeb standard signaling protocol
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: Mon, 17 Oct 2011 07:57:17 -0000

On 17 Oct 2011, at 08:45, Ravindran Parthasarathi wrote:

> RTCWeb server signaling plays the key role which calls for standardization as browser & RTCWebserver is not required from the same vendor.

And that is where we differ. The web server can _serve_ it's javascript to the browser. 
So the only standards needed are the pre-existing web standards of javascript and http.

The browser only has to be capable of running the javascript served to ensure compatibility.
That's the way that everything on the web works these days, from shopping carts to realtime 
chat. The browser is given site-specific code to run that interacts with site-specific code on
the web server. The web server may choose to convert those requests into a standard protocol 
for further processing (e.g. SQL), or may deal with the request internally.

Note, I'm not ruling out the use of SIP, but as  Iñaki Baz Castillo has demonstrated, that too
can be accomplished purely with existing web technologies. No embedded signalling code 
is needed.