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

Hadriel Kaplan <HKaplan@acmepacket.com> Thu, 10 November 2011 19:47 UTC

Return-Path: <HKaplan@acmepacket.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 D093821F8ACE for <rtcweb@ietfa.amsl.com>; Thu, 10 Nov 2011 11:47:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.315
X-Spam-Level:
X-Spam-Status: No, score=-2.315 tagged_above=-999 required=5 tests=[AWL=-0.016, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
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 t0l72wJcgCTW for <rtcweb@ietfa.amsl.com>; Thu, 10 Nov 2011 11:47:22 -0800 (PST)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id E2FD221F84FB for <rtcweb@ietf.org>; Thu, 10 Nov 2011 11:47:21 -0800 (PST)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Thu, 10 Nov 2011 14:47:19 -0500
Received: from MAIL1.acmepacket.com ([169.254.1.232]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Thu, 10 Nov 2011 14:47:20 -0500
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>
Thread-Topic: [rtcweb] Let's define the purpose of WebRTC
Thread-Index: AQHMn+GOqLofpooW1EaoUUdNIhGp3Q==
Date: Thu, 10 Nov 2011 19:47:19 +0000
Message-ID: <8C3CF53E-7DAC-4E87-9C00-7884A01B29BA@acmepacket.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> <1D062974A4845E4D8A343C653804920206D3BA57@XMB-BGL-414.cisco.com> <CALiegfkWnRT8m4S9pXTxuLsc-p_bhkG3d=PX3qgiFFt5gW5yfw@mail.gmail.com> <1D062974A4845E4D8A343C653804920206D3BA71@XMB-BGL-414.cisco.com> <CALiegfkfqjChNkGJfQQ2SZT==UkmKD4=k_A8i7U0xkqgjeEgOQ@mail.gmail.com>
In-Reply-To: <CALiegfkfqjChNkGJfQQ2SZT==UkmKD4=k_A8i7U0xkqgjeEgOQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [216.41.24.34]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <93DD87B2A25BD040933C3FC3D62E0DAC@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "<rtcweb@ietf.org>" <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 19:47:22 -0000

On Nov 9, 2011, at 10:05 AM, Iñaki Baz Castillo wrote:

> Implementing SRTP is really easier and cheap. There is no reason at
> all not to mandate it in a new specification, even less when it's
> designed to work in the open (and untrusted) Internet.
> 
> So bad luck. You, telcos, have the specs and the tools to upgrade your
> non-secure SIP devices. Do it.

Several people have made this SRTP discussion into a "Telco" issue, and I don't think it is.  First, because if a Telco doesn't care about securing the media, they'll likely put the burden of making it plaintext RTP on the WebRTC domain owner, so it still won't be "their problem".  But more importantly, because I expect a lot of Telco's to actually *require* WebRTC media communications to/from them be secure in some fashion or other, specifically because it can be run to/from anywhere on the public Internet. [they won't do SRTP all the way to their own SIP endpoints, but that doesn't matter]  

So for Telco's I don't think mandating SRTP be used is a non-starter, though the form of key exchange might be a big sticking point.

But something to consider is if doing SRTP is a burden or not on web applications that know a priori that they don't need it.  In particular I mean ones that need to use media servers so it's not simply browser-to-browser, and they use HTTP because their use-case isn't one of a sensitive nature.  

-hadriel
p.s. BTW, I didn't mean to start a religious war on this topic - I was just pointing out that a requirement to use ICE and a requirement to use SRTP aren't tied together, and that we need to still get consensus on mandating SRTP to-use vs. only to-implement.