Re: [rtcweb] Why are we asking the wrong questions?

Iñaki Baz Castillo <> Thu, 20 October 2011 20:59 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AD50621F8AEA for <>; Thu, 20 Oct 2011 13:59:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.336
X-Spam-Status: No, score=-2.336 tagged_above=-999 required=5 tests=[AWL=-0.259, 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 XcUhrgA5KrzM for <>; Thu, 20 Oct 2011 13:59:52 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id F249821F8557 for <>; Thu, 20 Oct 2011 13:59:51 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so3433534vcb.31 for <>; Thu, 20 Oct 2011 13:59:50 -0700 (PDT)
MIME-Version: 1.0
Received: by with SMTP id p17mr877870vcq.41.1319144390261; Thu, 20 Oct 2011 13:59:50 -0700 (PDT)
Received: by with HTTP; Thu, 20 Oct 2011 13:59:50 -0700 (PDT)
In-Reply-To: <>
References: <> <> <> <> <>
Date: Thu, 20 Oct 2011 22:59:50 +0200
Message-ID: <>
From: Iñaki Baz Castillo <>
To: Roman Shpount <>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [rtcweb] Why are we asking the wrong questions?
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: Thu, 20 Oct 2011 20:59:52 -0000

2011/10/20 Roman Shpount <>:
> On Thu, Oct 20, 2011 at 4:09 PM, Iñaki Baz Castillo <> wrote:
>> Hi Roman, could you please check this short document and specify which
>> "signaling protocol" (of the three appearing in the document) you
>> mean?:
> This document is under password protection and I cannot access it.

Hi Roman, it's not under password protection. But the web has no
favicon and the document root has no index permission, so when your
browser requests the "standard" favicon icon it finds a 401 response.
That's a bug of some web browsers. Please just press "cancel" when
user:passwd is requested.

> P.S. I suggest to stop redefine standard terms for the sake of the working
> group. Signaling protocol is defined in
> and is something like SIP --
> definition of data interactions over a wire.

The document I've written is more that just the definition of
"signaling protocol".

>  A set of JavaScript methods is
> not a signaling protocol -- it is an API. State machine that describes these
> JavaScript methods is still part of the API specification. In my personal
> opinion,

I can agree with this. The important point here is that all the WG
agrees with the term to use in each case.

> there are should be no "signaling protocols" in RTC.

In your previous comment you said:

  "Standard signaling protocol is a convenience feature for RTC."

Could you please clarify if you are in favour of mandating the
in-the-wire signaling protocol or not?

Thanks a lot.

Iñaki Baz Castillo