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

Wolfgang Beck <> Tue, 18 October 2011 18:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3A58B21F8BBB for <>; Tue, 18 Oct 2011 11:29:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 3VZcIkSdGqog for <>; Tue, 18 Oct 2011 11:29:44 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 3493E21F8BBA for <>; Tue, 18 Oct 2011 11:29:44 -0700 (PDT)
Received: by yxj19 with SMTP id 19so1076372yxj.31 for <>; Tue, 18 Oct 2011 11:29:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=wwPlXTV7l4I+DIYHdJoe8NZhwEhVDsWVr0nLlcUa+Bk=; b=YBkpFblJlb2hc4ZhvHKmXJRarezGAklk26ySy0uIIu5uit5LQVjpO0GJO2jMKzhXZG oBOokluiJZDJ4Xvb5nljNWsjd7Zv2bX89D2VLpNEgKU4VqB7Fr1P+Bzo5NeML/9wUqdO Ml7wOuhglve3WdJ5JYHH1FvpNjmSfK+NiyAjs=
MIME-Version: 1.0
Received: by with SMTP id k9mr6656089pbe.90.1318962582175; Tue, 18 Oct 2011 11:29:42 -0700 (PDT)
Received: by with HTTP; Tue, 18 Oct 2011 11:29:42 -0700 (PDT)
In-Reply-To: <>
References: <> <> <>
Date: Tue, 18 Oct 2011 20:29:42 +0200
Message-ID: <>
From: Wolfgang Beck <>
To: Harald Alvestrand <>
Content-Type: text/plain; charset="ISO-8859-1"
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:29:45 -0000

> 1) we have to support both the case of one web server and the case of 2 web
> servers.
If we look at SIP, the trapezoid model hasn't been too sucessful.
Depressingly few SIP providers do interconnection, after all those
Instead, even simple SIP clients support more than one SIP account so
people can reach their contact on different SIP providers.

> 2) when there is only one web server, one of the browsers is Firefox and the
> other one is Chrome, the JS needs to have a standard means of communication
> with the browser. This means a standard.
The chat function of has Firefox and Chrome users.
I'm not aware of any standardized signalling protocol to exchange
the capabilities between the browsers. Instead the JS chat client
queries the browser's capabilities locally and sends them in a
non-standard format
to the web server.

Wolfgang Beck