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

Roman Shpount <roman@telurix.com> Thu, 10 November 2011 05:48 UTC

Return-Path: <roman@telurix.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 1B68821F84A7 for <rtcweb@ietfa.amsl.com>; Wed, 9 Nov 2011 21:48:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.889
X-Spam-Level:
X-Spam-Status: No, score=-2.889 tagged_above=-999 required=5 tests=[AWL=0.087, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 gK5sCOtVELOE for <rtcweb@ietfa.amsl.com>; Wed, 9 Nov 2011 21:48:52 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5B0B921F87FA for <rtcweb@ietf.org>; Wed, 9 Nov 2011 21:48:52 -0800 (PST)
Received: by ggnr4 with SMTP id r4so1156765ggn.31 for <rtcweb@ietf.org>; Wed, 09 Nov 2011 21:48:51 -0800 (PST)
Received: by 10.101.171.34 with SMTP id y34mr2681655ano.8.1320904130934; Wed, 09 Nov 2011 21:48:50 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by mx.google.com with ESMTPS id o64sm11034430yhk.3.2011.11.09.21.48.49 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 09 Nov 2011 21:48:50 -0800 (PST)
Received: by ywt34 with SMTP id 34so345842ywt.31 for <rtcweb@ietf.org>; Wed, 09 Nov 2011 21:48:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.68.16.3 with SMTP id b3mr11390714pbd.86.1320904129099; Wed, 09 Nov 2011 21:48:49 -0800 (PST)
Received: by 10.68.62.170 with HTTP; Wed, 9 Nov 2011 21:48:48 -0800 (PST)
In-Reply-To: <CABcZeBOiPxz_swdaG6Aqoch1WAUtjNh4eOQy1QObCDXT_B8azg@mail.gmail.com>
References: <CALiegfkVNVAs_MyU_-4koA4zRwSn1-FwLjY9g_oZVkhi9rSK5Q@mail.gmail.com> <8A61D801-D14D-408B-9875-63C37D0CC166@acmepacket.com> <CABw3bnPE=OY_h5bM7GA6wgrXiOBL8P4J0kw1jLv-GSpHAbg=Cg@mail.gmail.com> <CABcZeBNqdkh8u=gwOvKfDCQA7rXdAyQkfaM1r2Sx10787btP6A@mail.gmail.com> <B10FEFF6-0ADC-4DB1-83BB-50A11C65EC35@acmepacket.com> <CABcZeBNSXtim_VqzqAd8Z-u4zWSjaYmsVZPN=7sDYkJsgtRAHA@mail.gmail.com> <4EB7E6A5.70209@alvestrand.no> <F8003BA9-BCD8-4F02-B514-8B883FF90F91@acmepacket.com> <387F9047F55E8C42850AD6B3A7A03C6C01349D81@inba-mail01.sonusnet.com> <845C03B2-1975-4145-8F52-8CEC9E360AF3@edvina.net> <5454E693-5C34-4C77-BA07-2A9EE9EE4AFD@cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01349FFE@inba-mail01.sonusnet.com> <1D062974A4845E4D8A343C653804920206D3B7FD@XMB-BGL-414.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C0134A105@inba-mail01.sonusnet.com> <1F2A2C70609D9E41844A2126145FC09804691DA2@HKGMBOXPRD22.polycom.com> <CALiegfmf59jb4asUu9LA6YY_aMtKEnM1Wy34KbuLEn3_h1xBXA@mail.gmail.com> <CALiegfmM1PB=VAQjfh4rW3-3C8aumHdWy9nZxD0-BWBq9Kq_tg@mail.gmail.com> <1D062974A4845E4D8A343C653804920206D3BA57@XMB-BGL-414.cisco.com> <CALiegfkWnRT8m4S9pXTxuLsc-p_bhkG3d=PX3qgiFFt5gW5yfw@mail.gmail.com> <CAD5OKxvQYVKOZF88WLCiRseg-qXQdOpKeDU_t9b-yA2GcDBT-w@mail.gmail.com> <CABcZeBOiPxz_swdaG6Aqoch1WAUtjNh4eOQy1QObCDXT_B8azg@mail.gmail.com>
Date: Thu, 10 Nov 2011 00:48:48 -0500
Message-ID: <CAD5OKxtp+LQBRCHgbWdJyrSRcpNQ82i64TJgGtGPrE7+GKcEog@mail.gmail.com>
From: Roman Shpount <roman@telurix.com>
To: Eric Rescorla <ekr@rtfm.com>
Content-Type: multipart/alternative; boundary=bcaec5215f7365b79904b15af543
Cc: rtcweb@ietf.org
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: Thu, 10 Nov 2011 05:48:53 -0000

On Thu, Nov 10, 2011 at 12:20 AM, Eric Rescorla <ekr@rtfm.com> wrote:

> The point is that it's very hard to anticipate which communications media
> will be used for sensitive information. To say "we don't need security
> in this application because nobody will ever use it to discuss sensitive
> stuff" is short-sighted. Better simply to be secure all the time.
>
>
So why is 99% of the web traffic is HTTP? Do you want to force everybody to
use HTTPS? I think your argument is simply stating encryption is good, no
encryption bad, even if it is not needed or if it does not protect anything
(WebRTC application delivered over HTTP).
_____________
Roman Shpount