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

"Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com> Wed, 09 November 2011 10:57 UTC

Return-Path: <mperumal@cisco.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 505E621F8C14 for <rtcweb@ietfa.amsl.com>; Wed, 9 Nov 2011 02:57:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level:
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[AWL=-0.611, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 bSRX3IHx896o for <rtcweb@ietfa.amsl.com>; Wed, 9 Nov 2011 02:57:34 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 68BC821F8C13 for <rtcweb@ietf.org>; Wed, 9 Nov 2011 02:57:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=mperumal@cisco.com; l=2448; q=dns/txt; s=iport; t=1320836254; x=1322045854; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=jgQCPMRkLcOiRR0mD/YBqzlsLwr75YoTzS2v+VHQAxk=; b=YdOjjmB2Cw1gt/N2q6HQBn3dH8Al+RHRPdsUMpGotI5iqJNW4hF/ZTCc uTwhSnTUwYQTJ5nJpYoGeVJHlnsAmkrGVHYYzFSyaQFdVj8PqoJHQ83Px OvZZDyG+6Ia1au7hQx4G24WwonY240hBhxOiuLhV4X27HmkMXwSYhSpBS E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvMAAC9cuk5Io8UR/2dsb2JhbABChH2VKY50gQKBBYFyAQEBBBIBEA0ERQwEAgEIEQQBAQMCBgYXAQICAgEBRAkIAQEECwgIGqEaAYxZkkSBMIc5M2MEiAqRWYw8
X-IronPort-AV: E=Sophos;i="4.69,483,1315180800"; d="scan'208";a="2712216"
Received: from bgl-core-2.cisco.com ([72.163.197.17]) by ams-iport-3.cisco.com with ESMTP; 09 Nov 2011 10:57:32 +0000
Received: from xbh-bgl-412.cisco.com (xbh-bgl-412.cisco.com [72.163.129.202]) by bgl-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pA9AvV9j011723; Wed, 9 Nov 2011 10:57:31 GMT
Received: from xmb-bgl-414.cisco.com ([72.163.129.210]) by xbh-bgl-412.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 9 Nov 2011 16:27:31 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Date: Wed, 9 Nov 2011 16:27:28 +0530
Message-ID: <1D062974A4845E4D8A343C653804920206D3B9C1@XMB-BGL-414.cisco.com>
In-Reply-To: <CALiegfmf59jb4asUu9LA6YY_aMtKEnM1Wy34KbuLEn3_h1xBXA@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rtcweb] Let's define the purpose of WebRTC
Thread-Index: AcyewttF81xR6ZeeT5K2GLper1nh6AABIbBA
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>
From: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
To: =?utf-8?B?ScOxYWtpIEJheiBDYXN0aWxsbw==?= <ibc@aliax.net>, "Avasarala, Ranjit" <Ranjit.Avasarala@polycom.com>
X-OriginalArrivalTime: 09 Nov 2011 10:57:31.0431 (UTC) FILETIME=[60F96370:01CC9ECE]
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: Wed, 09 Nov 2011 10:57:35 -0000

|The "application" is untrusted by nature, and we don't want 
|to make the end-user to decide whether to trust it or not. 
|Explained many times in this maillist.

I am thinking we could burn SRTP into the browser such that the decision of whether or not to use SRTP vests solely with the browser. If a WebRTC browser is exchanging media with another WebRTC browser they always do SRTP/SRTCP. If either side isn't WebRTC compliant they end up with RTP/RTCP. This way we don't need to trust the JS, instead trust only the browser. We can also interoperate with legacy devices without taxing them.

Muthu

|-----Original Message-----
|From: Iñaki Baz Castillo [mailto:ibc@aliax.net]
|Sent: Wednesday, November 09, 2011 3:05 PM
|To: Avasarala, Ranjit
|Cc: Ravindran Parthasarathi; Muthu Arul Mozhi Perumal (mperumal); Cullen Jennings (fluffy); Olle E.
|Johansson; rtcweb@ietf.org
|Subject: Re: [rtcweb] Let's define the purpose of WebRTC
|
|2011/11/9 Avasarala, Ranjit <Ranjit.Avasarala@polycom.com>om>:
|> I feel including all kinds of security mechanisms like SRTP, TLS, etc in browser would make the
|browser very bulky.
|
|Including TLS in a browser makes it bulky? Then we must discourage
|HTTPS usage, right?
|In the other side, have you really measured how much expensive SRTP
|is? it's not at all.
|
|
|> It would be better to provide a mechanism in the signaling protocol that browser supports to
|negotiate the desired security mechanism (depending on application requirement) and then use that
|mechanism (which is part of the system).
|
|The "application" is untrusted by nature, and we don't want to make
|the end-user to decide whether to trust it or not. Explained many
|times in this maillist.
|
|--
|Iñaki Baz Castillo
|<ibc@aliax.net>