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

Iñaki Baz Castillo <ibc@aliax.net> Wed, 09 November 2011 15:05 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 5525121F8B64 for <rtcweb@ietfa.amsl.com>; Wed, 9 Nov 2011 07:05:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.636
X-Spam-Level:
X-Spam-Status: No, score=-2.636 tagged_above=-999 required=5 tests=[AWL=0.041, 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 HJhDD5iKR0ZJ for <rtcweb@ietfa.amsl.com>; Wed, 9 Nov 2011 07:05:33 -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 A6C5C21F8B63 for <rtcweb@ietf.org>; Wed, 9 Nov 2011 07:05:33 -0800 (PST)
Received: by vcbfk1 with SMTP id fk1so1675274vcb.31 for <rtcweb@ietf.org>; Wed, 09 Nov 2011 07:05:33 -0800 (PST)
Received: by 10.52.187.68 with SMTP id fq4mr5235239vdc.32.1320851133157; Wed, 09 Nov 2011 07:05:33 -0800 (PST)
MIME-Version: 1.0
Received: by 10.220.107.206 with HTTP; Wed, 9 Nov 2011 07:05:12 -0800 (PST)
In-Reply-To: <1D062974A4845E4D8A343C653804920206D3BA71@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> <1D062974A4845E4D8A343C653804920206D3BA57@XMB-BGL-414.cisco.com> <CALiegfkWnRT8m4S9pXTxuLsc-p_bhkG3d=PX3qgiFFt5gW5yfw@mail.gmail.com> <1D062974A4845E4D8A343C653804920206D3BA71@XMB-BGL-414.cisco.com>
From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= <ibc@aliax.net>
Date: Wed, 9 Nov 2011 16:05:12 +0100
Message-ID: <CALiegfkfqjChNkGJfQQ2SZT==UkmKD4=k_A8i7U0xkqgjeEgOQ@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 15:05:34 -0000

2011/11/9 Muthu Arul Mozhi Perumal (mperumal) <mperumal@cisco.com>om>:
> |And what is the advantage? you still say exactly the
> |same: a WebRTC client "MUST" allow plain RTP if the
> |peer is not a WebRTC client. Why is that an argument
> |in favour of non mandating SRTP?
>
> We seem to have a group of people concerned about the cost associated with having to upgrade/replace/supplement their non-SRTP capable gears such as PSTN gateways, and I was sympathetic towards them -:)

That's *your* problem. But you want to translate *your* problem into
WebRTC users by making their communications non secure.

Implementing SRTP is really easier and cheap. There is no reason at
all not to mandate it in a new specification, even less when it's
designed to work in the open (and untrusted) Internet.

So bad luck. You, telcos, have the specs and the tools to upgrade your
non-secure SIP devices. Do it.



> |If I'm in a shared WiFi network and receive a call from
> |a non-WebRTC client not supporting SRTP, my neighbors can
> |intercept it.
>
> If the shared WiFi network hasn't employed WiFi encryption, then you would probably be more concerned with your neighbors intercepting all of your traffic than just RTP -:)

It was just an example. Think about so many open WiFi networks in
airports (captive portals with no encryption).



> |What does such "STUN extension" provides here?
>
> It would tell the browser that the peer (browser) claims WebRTC compliance and so shouldn't allow insecure calling (the STUN extension is added by the browser and the applications has no control over it).

I insist: that provides nothing. It just means that me, a WebRTC user,
could have a non-secure media session in case the remote peer is not a
WebRTC peer (or a peer implementing SRTP). It solves nothing. It makes
my communication unsafe regardless I'm a WebRTC client implementing
SRTP. *My* security should NOT depend on the security implemented in
the peer (since I cannot trust the peer, never).



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