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

Cullen Jennings <fluffy@cisco.com> Mon, 28 November 2011 20:23 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 5B9A621F8558 for <rtcweb@ietfa.amsl.com>; Mon, 28 Nov 2011 12:23:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 AA20Q8Tf6Nbq for <rtcweb@ietfa.amsl.com>; Mon, 28 Nov 2011 12:23:03 -0800 (PST)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 77D8221F856F for <rtcweb@ietf.org>; Mon, 28 Nov 2011 12:23:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fluffy@cisco.com; l=1370; q=dns/txt; s=iport; t=1322511783; x=1323721383; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=X55ZdTvM0YYAgNTMW8NVUH8k3/CWzzPwg0Vn3BuBDaA=; b=VpK+3k2ZDGrJTRMFlaPvReba87txV7eFIE6LjYUX1YRqbrcrtAKI454G YyETpwg2RFrEcukNLxkEmV2fTcEozN1c2+ouDbN++r9deKK4wxRX4gMNn OFiEkCZ+ynvU1tKULuZwAbBUbNnMv7XjdNfNzkj5fDmFE5pv+hg5L167Y g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAFDs006rRDoG/2dsb2JhbABDqnKBBYFyAQEBAwESASc/DAQLFQMnB0YRBhMih2MImFcBkXSMZYl/YwSIIYwphUCMaw
X-IronPort-AV: E=Sophos;i="4.69,586,1315180800"; d="scan'208";a="16579549"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 28 Nov 2011 20:23:01 +0000
Received: from [192.168.4.100] (sjc-fluffy-8914.cisco.com [10.20.249.165]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pASKN1wX027314; Mon, 28 Nov 2011 20:23:01 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Cullen Jennings <fluffy@cisco.com>
In-Reply-To: <387F9047F55E8C42850AD6B3A7A03C6C01CE76D3@inba-mail01.sonusnet.com>
Date: Mon, 28 Nov 2011 13:23:00 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <AD407C13-9AFE-4EFF-98BE-4B45198D353E@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> <4368BF50-2B50-4C9A-9CF4-E7D87705E4BF@cisco.com> <387F9047F55E8C4285 0AD6B3A7A03C6C01CE76D3@inba-mail01.sonusnet.com>
To: "Ravindran, Parthasarathi" <pravindran@sonusnet.com>
X-Mailer: Apple Mail (2.1084)
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: Mon, 28 Nov 2011 20:23:04 -0000

On Nov 13, 2011, at 6:59 AM, Ravindran, Parthasarathi wrote:

> 
> 
>> -----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>

right - each screen is 1 video stream in RTP so I think we are saying the same numbers - makes sense

> 
> 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>

Might want to go poke on that requirement a bit and see what you get