Re: [rtcweb] SRTP requirement - wiretapping (Re: Let's define the purpose of WebRTC)

Cullen Jennings <fluffy@cisco.com> Fri, 11 November 2011 14:59 UTC

Return-Path: <fluffy@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 00D8C21F8A64 for <rtcweb@ietfa.amsl.com>; Fri, 11 Nov 2011 06:59:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.974
X-Spam-Level:
X-Spam-Status: No, score=-105.974 tagged_above=-999 required=5 tests=[AWL=-0.367, BAYES_00=-2.599, DATE_IN_PAST_12_24=0.992, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 VybpjgOI9HAc for <rtcweb@ietfa.amsl.com>; Fri, 11 Nov 2011 06:59:02 -0800 (PST)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 734B121F863E for <rtcweb@ietf.org>; Fri, 11 Nov 2011 06:59:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=457; q=dns/txt; s=iport; t=1321023542; x=1322233142; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=MWfHR3GxFiCElOcaW8CideKqfQTUR0YQKrOF8BBrPa8=; b=jBfkMB9FqYcsiArXA7x8QzxtUa05qs6B8eOmcVATg6sQLcS4R7qdcQ5V i7z/WV9m24n1H25/6kcPgFfSAeU0WfMjtkr8h1D5jIprGtgPCaf8joQsF 6Ey9Y/wS0o+MC7Kz6Lt1BWJspD9Rq5r1Box/i1EdhwXSzsn/BT4Cth7X5 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAB43vU6rRDoJ/2dsb2JhbABDqh2BBYFyAQEBAwESASc/BQsLRlcGNYdgm0IBnkOJG2MEiA6MH5IF
X-IronPort-AV: E=Sophos;i="4.69,495,1315180800"; d="scan'208";a="13661743"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 11 Nov 2011 14:59:02 +0000
Received: from tky-vpn-client-230-146.cisco.com (tky-vpn-client-230-146.cisco.com [10.70.230.146]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pABEwvun030161; Fri, 11 Nov 2011 14:59:01 GMT
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <387F9047F55E8C42850AD6B3A7A03C6C0134A6B5@inba-mail01.sonusnet.com>
Date: Fri, 11 Nov 2011 07:14:40 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <4368BF50-2B50-4C9A-9CF4-E7D87705E4BF@cisco.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> <4EB9ACF5.80805@alvestrand.no> <387F9047F55E8C42850AD6B3A7A03C6C01349F60@inba-mail01.sonusnet.com> <CAD6AjGTn2WPaVQh01y-PVYZtpVYKopocqzQBSEMQadozjEd-Tw@mail.gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C01349FE6@inba-mail01.sonusnet.com> <CABcZeBNvGVWgNiLcP9=n+hnfvV1P4_uF1+Q2oC6dwgya80BwGQ@mail.gmail.com> <387F9047F55E8C42850AD6B3A7A03C6C0134A6B5@inba-mail01.sonusnet.com>
To: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] SRTP requirement - wiretapping (Re: 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: Fri, 11 Nov 2011 14:59:03 -0000

On Nov 10, 2011, at 13:19 , Ravindran, Parthasarathi wrote:

> AFAIK in case of telepresence or equivalent endpoint, it requires the special hardware to encrypt/decrypt the whole bunch of media from it. 

Really? For a fairly high end 3 screenTP systems, it's like a 6 mbps stream. I seem to recall a linksys router with VPN could do crypto at that rate. Been awhile since I looked at the numbers so perhaps I have this all wrong.