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

"Ravindran, Parthasarathi" <pravindran@sonusnet.com> Sun, 13 November 2011 13:59 UTC

Return-Path: <pravindran@sonusnet.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 B9A4921F8B61 for <rtcweb@ietfa.amsl.com>; Sun, 13 Nov 2011 05:59:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.614
X-Spam-Level:
X-Spam-Status: No, score=-2.614 tagged_above=-999 required=5 tests=[AWL=-0.015, BAYES_00=-2.599]
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 8eYvV28ybGBO for <rtcweb@ietfa.amsl.com>; Sun, 13 Nov 2011 05:59:04 -0800 (PST)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id E565421F8B40 for <rtcweb@ietf.org>; Sun, 13 Nov 2011 05:59:03 -0800 (PST)
Received: from sonusmail07.sonusnet.com (sonusmail07.sonusnet.com [10.128.32.157]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id pADDxdd8001712; Sun, 13 Nov 2011 08:59:39 -0500
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail07.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 13 Nov 2011 08:59:01 -0500
Received: from INBA-HUB01.sonusnet.com ([10.70.51.86]) by sonusinmail02.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675); Sun, 13 Nov 2011 19:29:13 +0530
Received: from INBA-MAIL01.sonusnet.com ([fe80::8d0f:e4f9:a74f:3daf]) by inba-hub01.sonusnet.com ([fe80::5cbc:2823:f6cc:9ce7%11]) with mapi id 14.01.0339.001; Sun, 13 Nov 2011 19:29:12 +0530
From: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
To: Cullen Jennings <fluffy@cisco.com>
Thread-Topic: [rtcweb] SRTP requirement - wiretapping (Re: Let's define the purpose of WebRTC)
Thread-Index: AQHMnoiMLXoobGtfx0Kkx8oSZTnrRJWj1oYwgABiqoCAAVQz4IAA1mMAgAScmgA=
Date: Sun, 13 Nov 2011 13:59:12 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6C01CE76D3@inba-mail01.sonusnet.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> <4368BF50-2B50-4C9A-9CF4-E7D87705E4BF@cisco.com>
In-Reply-To: <4368BF50-2B50-4C9A-9CF4-E7D87705E4BF@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.70.53.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 13 Nov 2011 13:59:13.0651 (UTC) FILETIME=[6CDB2430:01CCA20C]
Cc: "rtcweb@ietf.org" <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: Sun, 13 Nov 2011 13:59:04 -0000

>-----Original Message-----
>From: Cullen Jennings [mailto:fluffy@cisco.com]
>
>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.

<partha> AFAIK, ~15Mbps is very much possible for 3 screen TP and one of 
the related link is http://www.nojitter.com/blog/225400682. I come to
know about these numbers during SBC development to interop with 
telepresence. May be multiple variant of TP exists </partha>

 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.

<partha> In fact, I started thinking in this line based on your 
point on SIPREC requirement not to mandate separate SRTP keys for 
telepresence recording & communication session and it was accepted in
SIPREC. </partha>