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

Iñaki Baz Castillo <ibc@aliax.net> Wed, 09 November 2011 19:34 UTC

Return-Path: <ibc@aliax.net>
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 4C1E811E8099 for <rtcweb@ietfa.amsl.com>; Wed, 9 Nov 2011 11:34:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.637
X-Spam-Level:
X-Spam-Status: No, score=-2.637 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 9e1RzlI3NEpc for <rtcweb@ietfa.amsl.com>; Wed, 9 Nov 2011 11:34:18 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id B443D11E8091 for <rtcweb@ietf.org>; Wed, 9 Nov 2011 11:34:18 -0800 (PST)
Received: by vcbfk1 with SMTP id fk1so1972494vcb.31 for <rtcweb@ietf.org>; Wed, 09 Nov 2011 11:34:18 -0800 (PST)
Received: by 10.52.187.68 with SMTP id fq4mr6912007vdc.32.1320867258121; Wed, 09 Nov 2011 11:34:18 -0800 (PST)
MIME-Version: 1.0
Received: by 10.220.107.206 with HTTP; Wed, 9 Nov 2011 11:33:56 -0800 (PST)
In-Reply-To: <1D062974A4845E4D8A343C653804920206D3BAEE@XMB-BGL-414.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> <845C03B2-1975-4145-8F52-8CEC9E360AF3@edvina.net> <5454E693-5C34-4C77-BA07-2A9EE9EE4AFD@cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C01349FFE@inba-mail01.sonusnet.com> <1D062974A4845E4D8A343C653804920206D3B7FD@XMB-BGL-414.cisco.com> <387F9047F55E8C42850AD6B3A7A03C6C0134A105@inba-mail01.sonusnet.com> <1F2A2C70609D9E41844A2126145FC09804691DA2@HKGMBOXPRD22.polycom.com> <CALiegfmf59jb4asUu9LA6YY_aMtKEnM1Wy34KbuLEn3_h1xBXA@mail.gmail.com> <CALiegfkWnRT8m4S9pXTxuLsc-p_bhkG3d=PX3qgiFFt5gW5yfw@mail.gmail.com> <1D062974A4845E4D8A343C653804920206D3BA71@XMB-BGL-414.cisco.com> <CALiegfkfqjChNkGJfQQ2SZT==UkmKD4=k_A8i7U0xkqgjeEgOQ@mail.gmail.com> <1D062974A4845E4D8A343C653804920206D3BAEE@XMB-BGL-414.cisco.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Wed, 9 Nov 2011 20:33:56 +0100
Message-ID: <CALiegf=OXxRmKQu5FHBYOWrOUtV=69hnTQzU2ofMLORYbgS7Qw@mail.gmail.com>
To: "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: 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 19:34:19 -0000

2011/11/9 Muthu Arul Mozhi Perumal (mperumal) <mperumal@cisco.com>om>:
> |That's *your* problem. But you want to translate
> |*your* problem into WebRTC users by making their
> |communications non secure.
>
> Well, most often you as a WebRTC user will be the one who would want to reach someone behind legacy systems

You could consider that people in internet is not so excited with the
possibility of making a legacy PSTN from the browser. In fact, calling
a PSTN number from a web has no added value at all. Users already have
their legacy PSTN phones.



> |Implementing SRTP is really easier and cheap.
>
> Sure, in a browser. But, may not be for a provider.

Sure they can scale their systems.


> |You, telcos, have the specs and the tools to upgrade your
> |non-secure SIP devices. Do it.
>
> If you are willing to pay for it, I don't see why the tolcos won't -:)

I should not pay a telco for making my call safe. The telco should do it.


> |*My* security should NOT depend on the security
> |implemented in the peer (since I cannot trust the
> |peer, never).
>
> Good luck. You peer could be a media gateway sitting somewhere in the Internet converting SRTP to RTP and sending to the other part of the world.

Of course, but at least, I will know that the call is secure within my
local network. Imagine I open my laptop in an airport, connect to a
open WiFi (cautive portal) and make a call to another user via web,
but the server must route it (via a SIP gateway) to a SIP softswitch,
and that makes my call to use plain RTP. I'm in an airport, in an open
WiFi network. Bad.

But if my call uses SRTP until the SIP media gateway, then it could
use plain RTP in the PSTN network. That's not so dangerous.




-- 
Iñaki Baz Castillo
<ibc@aliax.net>