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

Iñaki Baz Castillo <ibc@aliax.net> Mon, 24 October 2011 10:38 UTC

Return-Path: <ibc@aliax.net>
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 3792521F8CE9 for <rtcweb@ietfa.amsl.com>; Mon, 24 Oct 2011 03:38:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.636
X-Spam-Level:
X-Spam-Status: No, score=-2.636 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, 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 OizWQLGaEc0Q for <rtcweb@ietfa.amsl.com>; Mon, 24 Oct 2011 03:38:38 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id C996821F86A6 for <rtcweb@ietf.org>; Mon, 24 Oct 2011 03:38:31 -0700 (PDT)
Received: by vws5 with SMTP id 5so5178505vws.31 for <rtcweb@ietf.org>; Mon, 24 Oct 2011 03:38:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.28.141 with SMTP id b13mr22075162vdh.128.1319452710136; Mon, 24 Oct 2011 03:38:30 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Mon, 24 Oct 2011 03:38:30 -0700 (PDT)
In-Reply-To: <CAAJUQMiWTZK8XQXcm-FS+BdbjJcTtgYeYcO6k2O7LZUY8R_3Kw@mail.gmail.com>
References: <9C8CA816-65FB-41A0-999C-4C43128CAAB4@danyork.org> <2E239D6FCD033C4BAF15F386A979BF51159B91@sonusinmail02.sonusnet.com> <CAAJUQMjHOJxCUGTwON9PmK-QEN0jM++RTWuRpmsHS-eszcNkXQ@mail.gmail.com> <4EA1B9E5.8030507@jesup.org> <CAAJUQMiWTZK8XQXcm-FS+BdbjJcTtgYeYcO6k2O7LZUY8R_3Kw@mail.gmail.com>
Date: Mon, 24 Oct 2011 12:38:30 +0200
Message-ID: <CALiegfnQ2xn16gvKtuuJv6Ls0nTj8iHugWd7CS2ocBsn-vgf_g@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Wolfgang Beck <wolfgang.beck01@googlemail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: Randell Jesup <randell-ietf@jesup.org>, rtcweb@ietf.org
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: Mon, 24 Oct 2011 10:38:39 -0000

2011/10/24 Wolfgang Beck <wolfgang.beck01@googlemail.com>;:
> On Fri, Oct 21, 2011 at 8:28 PM, Randell Jesup <randell-ietf@jesup.org>; wrote:
>>
>> 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...

> Phonebooks aren't a problem. They're called 'Bookmarks' in my browser.
> Call history doesn't look impossible to me as well. You can either
> just use the browser's
> history or setup some bookmarking web site that keeps track of your calls.

Hi Wolfgang. When you send a text message via Facebook or via Twitter,
can you check later all those messages *together* in some "messages
history" section within your browser? If the answer is not (and it is
not), why do you expect that it should be different for calls?

Also, what do you expect such "call history" to show you? In case you
make an audio call in Facebook its entry in the call-history list
would display your Facebook id as originator and the receiver Facebook
user as destination. But in case you join a web game in which RTCweb
is used for *automatically* receive audio from other gamers, what do
you expect the entry in the call-history to display?

Also the fact that your browser has received a RTCweb audio call from
a web game does not mean that you can make an outgoing call to the
caller (the website could be designed in a way that just calls from
server to clients make sense). It could occur that such incoming call
from the web game has not an "originator" (as such information is up
to the website). Nobody is mandating that a RTCweb call MUST contains
a "From" and a "To". RTC-Web is not SIP and it is not about legacy
telephony, neither it's designed to be an Skype on the web.


> I used to defend Usenet using all of your arguments. The Web has won.

IMHO I'm defending the Web model.


Regards.

-- 
Iñaki Baz Castillo
<ibc@aliax.net>;