Re: [rtcweb] Let's define the purpose of WebRTC

Tim Panton <tim@phonefromhere.com> Sun, 06 November 2011 12:05 UTC

Return-Path: <tim@phonefromhere.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 B192621F8490 for <rtcweb@ietfa.amsl.com>; Sun, 6 Nov 2011 04:05:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.58
X-Spam-Level:
X-Spam-Status: No, score=-2.58 tagged_above=-999 required=5 tests=[AWL=0.019, 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 sKO8zDDhrUaf for <rtcweb@ietfa.amsl.com>; Sun, 6 Nov 2011 04:05:24 -0800 (PST)
Received: from zimbra.westhawk.co.uk (zimbra.westhawk.co.uk [192.67.4.167]) by ietfa.amsl.com (Postfix) with ESMTP id 2BD4221F848D for <rtcweb@ietf.org>; Sun, 6 Nov 2011 04:05:23 -0800 (PST)
Received: from [192.168.157.49] (unknown [93.89.81.113]) by zimbra.westhawk.co.uk (Postfix) with ESMTP id F01F837A902 for <rtcweb@ietf.org>; Sun, 6 Nov 2011 12:18:00 +0000 (GMT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1251.1)
From: Tim Panton <tim@phonefromhere.com>
In-Reply-To: <CALiegfk=oJJ20GhKQBKA7aspHhUyQ-s+DR-qSi4XV455Nj718w@mail.gmail.com>
Date: Sun, 6 Nov 2011 12:05:09 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <9C4C8AE2-4AFF-4553-9D19-556F12AC066E@phonefromhere.com>
References: <CALiegfkVNVAs_MyU_-4koA4zRwSn1-FwLjY9g_oZVkhi9rSK5Q@mail.gmail.com> <CAD5OKxt=k_Mon_GMs1w-bGMgpk12h6ZQ=FkoRVsTp4271iMSLA@mail.gmail.com> <CABcZeBNMTgwH-R_jd-AiEJ8tELTeFMNm-bAJohRg2RxD5e+kZQ@mail.gmail.com> <CAD6AjGRBmrAqB3CEWxtaXnryPA5App13S2jJPAt+7HwWZsQFzA@mail.gmail.com> <CABcZeBNtoizuRymVMxF4CdiLu1Nju63C0xkWJHjoarpxeLXjyA@mail.gmail.com> <CALiegfk=oJJ20GhKQBKA7aspHhUyQ-s+DR-qSi4XV455Nj718w@mail.gmail.com>
To: "<rtcweb@ietf.org>" <rtcweb@ietf.org>
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [rtcweb] Let's define the purpose of WebRTC
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: Sun, 06 Nov 2011 12:05:24 -0000

On 5 Nov 2011, at 15:47, Iñaki Baz Castillo wrote:

> 2011/11/5 Eric Rescorla <ekr@rtfm.com>om>:
>> Good point. Also, of course (unless you use the SRTP header encryption
>> extension) the SRTP header is in the clear, so you mostly just don't get
>> the media itself.
> 
> Hi, please use another thread for discussions about SRTP with no
> encryption. This thread was supposed to discuss the purpose and scope
> of WebRTC :)

"There are a number of proprietary implementations that provide direct
interactive rich communication using audio, video, collaboration,
games, etc. between two peers' web-browsers. These are not
interoperable, as they require non-standard extensions or plugins to
work. There is a desire to standardize the basis for such
communication so that interoperable communication can be established
between any compatible browsers. The goal is to enable innovation on
top of a set of basic components. One core component is to enable
real-time media like audio and video, a second is to enable data
transfer directly between clients."

Seems like time to rewrite the charter - that doesn't even nearly describe
what we have on the table at the moment.

Tim.