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

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

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 505E621F8C14 for <>; Wed, 9 Nov 2011 02:57:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.911
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id bSRX3IHx896o for <>; Wed, 9 Nov 2011 02:57:34 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 68BC821F8C13 for <>; Wed, 9 Nov 2011 02:57:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; 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-AV: E=Sophos;i="4.69,483,1315180800"; d="scan'208";a="2712216"
Received: from ([]) by with ESMTP; 09 Nov 2011 10:57:32 +0000
Received: from ( []) by (8.14.3/8.14.3) with ESMTP id pA9AvV9j011723; Wed, 9 Nov 2011 10:57:31 GMT
Received: from ([]) by 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: <>
In-Reply-To: <>
Thread-Topic: [rtcweb] Let's define the purpose of WebRTC
Thread-Index: AcyewttF81xR6ZeeT5K2GLper1nh6AABIbBA
References: <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <>
From: "Muthu Arul Mozhi Perumal (mperumal)" <>
To: =?utf-8?B?ScOxYWtpIEJheiBDYXN0aWxsbw==?= <>, "Avasarala, Ranjit" <>
X-OriginalArrivalTime: 09 Nov 2011 10:57:31.0431 (UTC) FILETIME=[60F96370:01CC9ECE]
Subject: Re: [rtcweb] Let's define the purpose of WebRTC
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-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.


|-----Original Message-----
|From: Iñaki Baz Castillo []
|Sent: Wednesday, November 09, 2011 3:05 PM
|To: Avasarala, Ranjit
|Cc: Ravindran Parthasarathi; Muthu Arul Mozhi Perumal (mperumal); Cullen Jennings (fluffy); Olle E.
|Subject: Re: [rtcweb] Let's define the purpose of WebRTC
|2011/11/9 Avasarala, Ranjit <>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