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

Iñaki Baz Castillo <ibc@aliax.net> Thu, 20 October 2011 14:52 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 17D4921F8BA4 for <rtcweb@ietfa.amsl.com>; Thu, 20 Oct 2011 07:52:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.629
X-Spam-Level:
X-Spam-Status: No, score=-2.629 tagged_above=-999 required=5 tests=[AWL=0.048, 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 ca4C-MEVgeNL for <rtcweb@ietfa.amsl.com>; Thu, 20 Oct 2011 07:52:23 -0700 (PDT)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5FAE521F8B87 for <rtcweb@ietf.org>; Thu, 20 Oct 2011 07:52:23 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so3038946vcb.31 for <rtcweb@ietf.org>; Thu, 20 Oct 2011 07:52:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.73.166 with SMTP id m6mr10988608vdv.18.1319122342756; Thu, 20 Oct 2011 07:52:22 -0700 (PDT)
Received: by 10.220.118.143 with HTTP; Thu, 20 Oct 2011 07:52:22 -0700 (PDT)
In-Reply-To: <6DFC5313-2991-4FB5-811D-FC99D31F9298@edvina.net>
References: <9C8CA816-65FB-41A0-999C-4C43128CAAB4@danyork.org> <BLU152-W43CB8DACCEA54AA5558B2493EA0@phx.gbl> <E857C96A-0E73-486F-BF23-36BA897B449C@cisco.com> <BLU152-W19B31DA6C6DB2FE60FC51C93EB0@phx.gbl> <CALiegfkKhWwr4yY2vV-x2+01dys57_sYsSsoof=kEu5G3CL5oA@mail.gmail.com> <6DFC5313-2991-4FB5-811D-FC99D31F9298@edvina.net>
Date: Thu, 20 Oct 2011 16:52:22 +0200
Message-ID: <CALiegf=e05G3fwOZoKOYqtE7voPkanYEgWmGYJVSrFpiuJD-TQ@mail.gmail.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
To: Bernard Aboba <bernard_aboba@hotmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: 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: Thu, 20 Oct 2011 14:52:25 -0000

2011/10/20 Olle E. Johansson <oej@edvina.net>;:
> 20 okt 2011 kl. 16:39 skrev Iñaki Baz Castillo:
>
>> 2011/10/20 Bernard Aboba <bernard_aboba@hotmail.com>;:
>>> the APIs should also enable media to be sent over a websocket
>>
>> WHAT??
>>
> A more specific question: What are the use cases?
>
> I understand that media over TCP is used in many apps today. While media over websocket over tcp over IP sounds just a bit too much, I am very curious on the use case.


There is no use case. WebSocket is NOT designed for carrying media.

WebSocket is designed for sending and receiving *boundary* messages
(with any application content up to the developer) over an existing
TCP connection between client and server, in both directions. When a
WebSocket message arrives to the browser, a JavaScript callback
onmessage(data) is called, so the custom JavaScript code can read it,
parse it and react according.

This stuff is NOT designed for media !

Please read:

http://tools.ietf.org/html/draft-ietf-hybi-thewebsocketprotocol-17
http://dev.w3.org/html5/websockets/#the-websocket-interface


I strongly hope this WG will not waste time in discussions about "RTP
over WebSocket", or it will become surrealist.

Regards.


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