Re: [rtcweb] Regarding Federation Arguments
Wolfgang Beck <wolfgang.beck01@googlemail.com> Wed, 09 November 2011 16:56 UTC
Return-Path: <wolfgang.beck01@googlemail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6022221F8C3E for <rtcweb@ietfa.amsl.com>; Wed, 9 Nov 2011 08:56:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.933
X-Spam-Level:
X-Spam-Status: No, score=-2.933 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0R9UG+YReTtv for <rtcweb@ietfa.amsl.com>; Wed, 9 Nov 2011 08:55:59 -0800 (PST)
Received: from mail-pz0-f50.google.com (mail-pz0-f50.google.com [209.85.210.50]) by ietfa.amsl.com (Postfix) with ESMTP id DC81D21F8C34 for <rtcweb@ietf.org>; Wed, 9 Nov 2011 08:55:59 -0800 (PST)
Received: by pzk4 with SMTP id 4so2182280pzk.9 for <rtcweb@ietf.org>; Wed, 09 Nov 2011 08:55:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Q0vZwTQNYJffe42wLSWBb6HBTNuPhoUIbuVCC0FGuxI=; b=JyOKM7hQtzeVjby67eXeQm5jfLLYG0GY6lydD7KQ2uCVRL/I+7fG8KDk+e82KogjXR nk5fmzLP0o76Vwd+fWFVeG7F9qrDGsKmK2QVIWdqZ+POtQPSbxlKK2Z1vUgxlbB7XkFK lfN6nXSkTnQ0KTqyMNkpDbxNy7aNLnNAtwf0s=
MIME-Version: 1.0
Received: by 10.68.52.134 with SMTP id t6mr6418883pbo.96.1320857759373; Wed, 09 Nov 2011 08:55:59 -0800 (PST)
Received: by 10.68.64.66 with HTTP; Wed, 9 Nov 2011 08:55:59 -0800 (PST)
In-Reply-To: <4EBA741A.1010307@alvestrand.no>
References: <4EB26D22.5090000@ericsson.com> <FA65A239-CC86-4AC3-8A5A-91B7701C3FB5@cisco.com> <BLU152-W488BAA56546BEA4D42B4C893DF0@phx.gbl> <4EBA741A.1010307@alvestrand.no>
Date: Wed, 09 Nov 2011 17:55:59 +0100
Message-ID: <CAAJUQMiv3EyT3MzAUCzfXusG2Md-DnkA0sa3Hnx5CGVdh919ag@mail.gmail.com>
From: Wolfgang Beck <wolfgang.beck01@googlemail.com>
To: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Subject: Re: [rtcweb] Regarding Federation Arguments
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Nov 2011 16:56:00 -0000
On Wed, Nov 9, 2011 at 1:37 PM, Harald Alvestrand <harald@alvestrand.no> wrote: > [on Bernard's comments] > can we simply say "Existing protocols (for example SIP or XMPP) could be > used between the servers"? > > between servers, while either a standards-based or proprietary protocol > could be used between the browser and the web server. My concern about this trapezoid style connection of servers is this: in order to limit the number protocol translators, RTCWEB providers will use only a small number of server-to-server protocols, most likely SIP and Jingle. This will inevitably have influence on the JS client / server protocol design: why bother with innovative features that don't translate well to SIP and Jingle anyway? Why not just do Jingle/SIP over Websocket? And the opportunity of RTCWEB will be gone. We will just see browser-based SIP, Jingle clients with fancy CSS themes. This has happened with SIP. As most of the interconnection is done through the PSTN, we don't see many exciting new SIP applications in wide use. It's a pity that the VWRAP people are no longer active in the IETF. They really had a fresh view on those issues. Their interconnection requirements where just to complex for the trapezoid and nobody of them had a limiting telephony background. Wolfgang Beck
- [rtcweb] Regarding Federation Arguments Magnus Westerlund
- Re: [rtcweb] Regarding Federation Arguments Iñaki Baz Castillo
- Re: [rtcweb] Regarding Federation Arguments Ravindran Parthasarathi
- Re: [rtcweb] Regarding Federation Arguments Iñaki Baz Castillo
- Re: [rtcweb] Regarding Federation Arguments Wolfgang Beck
- Re: [rtcweb] Regarding Federation Arguments Cullen Jennings
- Re: [rtcweb] Regarding Federation Arguments Bernard Aboba
- Re: [rtcweb] Regarding Federation Arguments Iñaki Baz Castillo
- Re: [rtcweb] RTCWEB is not SIP Erik Lagerway
- Re: [rtcweb] Regarding Federation Arguments Harald Alvestrand
- Re: [rtcweb] Regarding Federation Arguments Harald Alvestrand
- Re: [rtcweb] Regarding Federation Arguments Wolfgang Beck
- Re: [rtcweb] Regarding Federation Arguments Harald Alvestrand
- Re: [rtcweb] Regarding Federation Arguments Iñaki Baz Castillo
- Re: [rtcweb] Regarding Federation Arguments Ted Hardie
- Re: [rtcweb] Regarding Federation Arguments Ravindran, Parthasarathi
- Re: [rtcweb] Regarding Federation Arguments Iñaki Baz Castillo
- Re: [rtcweb] Regarding Federation Arguments Ravindran, Parthasarathi
- Re: [rtcweb] Regarding Federation Arguments Christer Holmberg
- Re: [rtcweb] RTCWEB is not SIP Bernard Aboba
- Re: [rtcweb] RTCWEB is not SIP Neil Stratford
- Re: [rtcweb] Regarding Federation Arguments Iñaki Baz Castillo
- Re: [rtcweb] Regarding Federation Arguments Iñaki Baz Castillo
- Re: [rtcweb] RTCWEB is not SIP Dan York
- Re: [rtcweb] Regarding Federation Arguments Christer Holmberg
- Re: [rtcweb] RTCWEB is not SIP Tim Panton