Re: [rtcweb] A plea for simplicity, marketability - and... who are we designing RTCWEB for?

Randell Jesup <randell-ietf@jesup.org> Fri, 21 October 2011 18:33 UTC

Return-Path: <randell-ietf@jesup.org>
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 9A4F721F8AFE for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 11:33:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level:
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599]
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 KpQ0dD-6RfxF for <rtcweb@ietfa.amsl.com>; Fri, 21 Oct 2011 11:33:38 -0700 (PDT)
Received: from r2-chicago.webserversystems.com (r2-chicago.webserversystems.com [173.236.101.58]) by ietfa.amsl.com (Postfix) with ESMTP id 26AD421F8AFC for <rtcweb@ietf.org>; Fri, 21 Oct 2011 11:33:37 -0700 (PDT)
Received: from pool-173-49-141-165.phlapa.fios.verizon.net ([173.49.141.165] helo=[192.168.1.12]) by r2-chicago.webserversystems.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <randell-ietf@jesup.org>) id 1RHJuT-0000w0-3C for rtcweb@ietf.org; Fri, 21 Oct 2011 13:33:37 -0500
Message-ID: <4EA1B9E5.8030507@jesup.org>
Date: Fri, 21 Oct 2011 14:28:53 -0400
From: Randell Jesup <randell-ietf@jesup.org>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <9C8CA816-65FB-41A0-999C-4C43128CAAB4@danyork.org> <2E239D6FCD033C4BAF15F386A979BF51159B91@sonusinmail02.sonusnet.com> <CAAJUQMjHOJxCUGTwON9PmK-QEN0jM++RTWuRpmsHS-eszcNkXQ@mail.gmail.com>
In-Reply-To: <CAAJUQMjHOJxCUGTwON9PmK-QEN0jM++RTWuRpmsHS-eszcNkXQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - r2-chicago.webserversystems.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jesup.org
X-Source:
X-Source-Args:
X-Source-Dir:
Subject: Re: [rtcweb] A plea for simplicity, marketability - and... who are we designing RTCWEB for?
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: Fri, 21 Oct 2011 18:33:38 -0000

On 10/21/2011 8:25 AM, Wolfgang Beck wrote:
> At the layer of call signaling messages are ultimately exchanged
> between two JS clients running on browsers. If we have different JS
> clients here, we need a standardized protocol between them. With
> trapezoid interconnection, we can hide this to some extent by doing
> protocol translations between JS client A / RTCWEB Server A and Server
> B / JS client B. Some
> information will get lost in translation.
>
> But as browsers can load JS on the fly,  user A could simply point her
> browser to Server B and use the same client as user B. Now all
> components at the signaling layer are provided by a single vendor and
> no standardized protocol is required. There is no loss of information
> as there are no protocol translators.

This is the rough equivalent to saying "instead of exchanging email in a 
standard format, and letting people use whatever client/webmail-client 
they want to read it; if you want to read an email from a gmail user you 
should log into gmail using their interface; from an aol user log into 
AOL and their interface, etc.  Oh, and history, phonebooks, etc would 
all be separate."  Yes, it avoids standard 'federation' formats and 
conversions, but...


-- 
Randell Jesup
randell-ietf@jesup.org