Re: [rtcweb] My Opinion: Why I think a negotiating protocol is a Good Thing

Iñaki Baz Castillo <> Tue, 18 October 2011 18:43 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AD84321F8CA4 for <>; Tue, 18 Oct 2011 11:43:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.634
X-Spam-Status: No, score=-2.634 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tyPRzvjNKvf9 for <>; Tue, 18 Oct 2011 11:43:35 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 1F6BA21F8B53 for <>; Tue, 18 Oct 2011 11:43:35 -0700 (PDT)
Received: by vws5 with SMTP id 5so800651vws.31 for <>; Tue, 18 Oct 2011 11:43:34 -0700 (PDT)
MIME-Version: 1.0
Received: by with SMTP id et7mr3895014vdc.35.1318963414421; Tue, 18 Oct 2011 11:43:34 -0700 (PDT)
Received: by with HTTP; Tue, 18 Oct 2011 11:43:34 -0700 (PDT)
In-Reply-To: <>
References: <> <> <> <> <>
Date: Tue, 18 Oct 2011 20:43:34 +0200
Message-ID: <>
From: Iñaki Baz Castillo <>
To: Harald Alvestrand <>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: "" <>
Subject: Re: [rtcweb] My Opinion: Why I think a negotiating protocol is a Good Thing
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: Tue, 18 Oct 2011 18:43:35 -0000

2011/10/18 Harald Alvestrand <>:
>> Anyhow, the point here is: are you advocating for having a default
>> signaling protocol in-the-wire or not? It's a bit unclear from your
>> first mail given the ammount of signaling fragments in the whole
>> RTCweb picture.
> I'm advocating a single protocol between the Javascript and the Web browser.

Well, so instead of managing a simple JS API you mean a JS API with
memory and state, so let's call it "protocol". Then I strongly think
that what you suggest is the same as ROAP. And I do agree with such

> It's a viable option for some applications to run that protocol from one
> browser to the other browser over a mechanism of their choice; many
> applications will make other choices, including those who choose to
> implement SIP in Javascript.

There is a risk here. If the specs and the API are based on that
signaling protocol, maybe they just fullfit the requirements of that
protocol and forget other possible solutions. Just wondering. But
there will be people ensuring that does not happen ;)

Iñaki Baz Castillo