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

Ravindran Parthasarathi <pravindran@sonusnet.com> Wed, 09 November 2011 02:58 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 16BFA11E8073 for <rtcweb@ietfa.amsl.com>; Tue, 8 Nov 2011 18:58:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.63
X-Spam-Level:
X-Spam-Status: No, score=-2.63 tagged_above=-999 required=5 tests=[AWL=-0.031, 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 kHyLkoiAWxve for <rtcweb@ietfa.amsl.com>; Tue, 8 Nov 2011 18:58:07 -0800 (PST)
Received: from mail-ma01.sonusnet.com (sonussf2.sonusnet.com [208.45.178.27]) by ietfa.amsl.com (Postfix) with ESMTP id 229A51F0C47 for <rtcweb@ietf.org>; Tue, 8 Nov 2011 18:58:07 -0800 (PST)
Received: from sonusmail06.sonusnet.com (sonusmail06.sonusnet.com [10.128.32.156]) by sonuspps2.sonusnet.com (8.14.3/8.14.3) with ESMTP id pA92wdQ2019199; Tue, 8 Nov 2011 21:58:39 -0500
Received: from sonusinmail02.sonusnet.com ([10.70.51.30]) by sonusmail06.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 8 Nov 2011 21:58:02 -0500
Received: from INBA-HUB01.sonusnet.com ([10.70.51.86]) by sonusinmail02.sonusnet.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 9 Nov 2011 08:28:11 +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; Wed, 9 Nov 2011 08:28:11 +0530
From: Ravindran Parthasarathi <pravindran@sonusnet.com>
To: Cullen Jennings <fluffy@cisco.com>, "Olle E. Johansson" <oej@edvina.net>
Thread-Topic: [rtcweb] Let's define the purpose of WebRTC
Thread-Index: AQHMm7/XxS9yQix74UmCewMPtvNQWZWe2WiAgABcZwCAAFnsgIAA1PQAgACv/gCAAAVogIAAGdwAgAHTzND//7JMAIAAEPMAgAESTSA=
Date: Wed, 9 Nov 2011 02:58:10 +0000
Message-ID: <387F9047F55E8C42850AD6B3A7A03C6C01349FFE@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> <845C03B2-1975-4145-8F52-8CEC9E360AF3@edvina.net> <5454E693-5C34-4C77-BA07-2A9EE9EE4AFD@cisco.com>
In-Reply-To: <5454E693-5C34-4C77-BA07-2A9EE9EE4AFD@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: 09 Nov 2011 02:58:11.0483 (UTC) FILETIME=[6AB596B0:01CC9E8B]
Cc: "<rtcweb@ietf.org>" <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 02:58:08 -0000

Cullen,

As I mentioned in http://www.ietf.org/mail-archive/web/rtcweb/current/msg02674.html, below comment #2 is not valid in IETF. 

But I'm interested in your opinion as Enterprise UC expert on my 1st comment:

"1) Security could be in the lower layer itself (IPsec, VPN, private MPLS cloud). For Enterprise-only-WebRTC application (no federation & no interop), there is no need of security for specific application like WebRTC as it is ensured in the infrastructure. WebRTC security will be duplicated for these infrastructure and may lead to double encryption unnecessarily."

Thanks
Partha

>-----Original Message-----
>From: Cullen Jennings [mailto:fluffy@cisco.com]
>Sent: Tuesday, November 08, 2011 9:29 PM
>To: Olle E. Johansson
>Cc: Ravindran Parthasarathi; <rtcweb@ietf.org>
>Subject: Re: [rtcweb] Let's define the purpose of WebRTC
>
>
>On Nov 8, 2011, at 7:58 AM, Olle E. Johansson wrote:
>
>>>
>>> 2) Being in India, I'm interested in avoiding Government restriction
>on WebRTC proposal (Thanks to Tim for pointing this). I may not surprise
>to see that WebRTC mechanism is banned in India because intelligent
>agency struggles to break the key in each terrorist WebRTC site.
>(http://www.pcworld.com/businesscenter/article/235639/india_wants_to_int
>ercept_skype_google_communications.html)
>> That is an interesting objection. I don't think SRTP by default is the
>problem here. In the case where you need lawful interception in the
>application,
>> the server needs to route the calls through an RTCweb b2b media
>server.
>
>I think the situation in India is a taxiation not encryption issue.
>Partha and I can do VoIP between Canada and India fully encrypted no
>problem - in fact we have a dial plan set up specifically so I can do
>that with him. The issue is a taxation issue. If we want to be able to
>connect that voip server to the PSTN in a way that it becomes what the
>regulators in India consider a telephone service, then we need
>permission to effectively be an indian telco. Right now I can make a
>full SRTP encrypted conversation with between my IP phones and Partha's
>but I don't think Partha can use his IP phone to access one the the PSTN
>GWs outside India.
>
>Anyways, I will remind people of RAVEN http://www.rfc-
>editor.org/rfc/rfc2804.txt
>