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

Christer Holmberg <christer.holmberg@ericsson.com> Wed, 09 November 2011 19:54 UTC

Return-Path: <christer.holmberg@ericsson.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 0121021F84AF for <rtcweb@ietfa.amsl.com>; Wed, 9 Nov 2011 11:54:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.204
X-Spam-Level:
X-Spam-Status: No, score=-6.204 tagged_above=-999 required=5 tests=[AWL=0.095, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
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 k-i67os9tQ9f for <rtcweb@ietfa.amsl.com>; Wed, 9 Nov 2011 11:54:51 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by ietfa.amsl.com (Postfix) with ESMTP id 34D9611E808B for <rtcweb@ietf.org>; Wed, 9 Nov 2011 11:54:51 -0800 (PST)
X-AuditID: c1b4fb39-b7b3eae00000252a-bb-4ebada8a1caa
Received: from esessmw0237.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw9.se.ericsson.net (Symantec Mail Security) with SMTP id BC.20.09514.A8ADABE4; Wed, 9 Nov 2011 20:54:50 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.57]) by esessmw0237.eemea.ericsson.se ([153.88.115.90]) with mapi; Wed, 9 Nov 2011 20:54:49 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: =?iso-8859-1?Q?I=F1aki_Baz_Castillo?= <ibc@aliax.net>, "Muthu Arul Mozhi Perumal (mperumal)" <mperumal@cisco.com>
Date: Wed, 9 Nov 2011 20:54:50 +0100
Thread-Topic: [rtcweb] Let's define the purpose of WebRTC
Thread-Index: AcyfFpZDvdoy5yfaQ66OoD4ViYDyoQAAM7Fr
Message-ID: <7F2072F1E0DE894DA4B517B93C6A058522357173CA@ESESSCMS0356.eemea.ericsson.se>
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>, <CALiegf=OXxRmKQu5FHBYOWrOUtV=69hnTQzU2ofMLORYbgS7Qw@mail.gmail.com>
In-Reply-To: <CALiegf=OXxRmKQu5FHBYOWrOUtV=69hnTQzU2ofMLORYbgS7Qw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
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 19:54:52 -0000

Hi,

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

I don't think we shall speculate in how people will use, and to whom the will call, using their browser apps.

AFAIK, most SIP calls today end up in PSTN, and the browser technology will allow people to access "SIP phones" from more or less any computer connected to the internet.


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

So, in your example you are basically talking about "access network security", because you don't really care what happens (with regards to media security) after the WiFi access leg?

Regards,

Christer