Re: [rtcweb] Resolving RTP/SDES question in Paris

"Ejzak, Richard P (Richard)" <richard.ejzak@alcatel-lucent.com> Mon, 19 March 2012 16:01 UTC

Return-Path: <richard.ejzak@alcatel-lucent.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 0B12C21F8873 for <rtcweb@ietfa.amsl.com>; Mon, 19 Mar 2012 09:01:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.585
X-Spam-Level:
X-Spam-Status: No, score=-8.585 tagged_above=-999 required=5 tests=[AWL=2.014, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 AqWsVPQ2Wxbm for <rtcweb@ietfa.amsl.com>; Mon, 19 Mar 2012 09:01:03 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id C7EE421F8871 for <rtcweb@ietf.org>; Mon, 19 Mar 2012 09:01:02 -0700 (PDT)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id q2JG11i5017168 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 19 Mar 2012 11:01:01 -0500 (CDT)
Received: from USNAVSXCHHUB03.ndc.alcatel-lucent.com (usnavsxchhub03.ndc.alcatel-lucent.com [135.3.39.112]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id q2JG11FN030909 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 19 Mar 2012 11:01:01 -0500
Received: from USNAVSXCHMBSA1.ndc.alcatel-lucent.com ([135.3.39.127]) by USNAVSXCHHUB03.ndc.alcatel-lucent.com ([135.3.39.112]) with mapi; Mon, 19 Mar 2012 11:01:01 -0500
From: "Ejzak, Richard P (Richard)" <richard.ejzak@alcatel-lucent.com>
To: Ted Hardie <ted.ietf@gmail.com>
Date: Mon, 19 Mar 2012 11:00:59 -0500
Thread-Topic: [rtcweb] Resolving RTP/SDES question in Paris
Thread-Index: Ac0F364fe64p7aRdSYq96cxzxGN1KQAB9j4A
Message-ID: <6F428EFD2B8C2F49A2FB1317291A76C113564482A1@USNAVSXCHMBSA1.ndc.alcatel-lucent.com>
References: <4F4759DC.7060303@ericsson.com> <387F9047F55E8C42850AD6B3A7A03C6C0E1FEB69@inba-mail01.sonusnet.com> <CALiegfnkYVEpmPV-zSL_4wOY-HiFZN-qJCQCiioaS=5NaqhLZw@mail.gmail.com> <CAD5OKxvtOAxMBx6xDnyfTnEq76oDEm6uj1xL6wGjjrtKUAHy3g@mail.gmail.com> <CABcZeBNZiotPmCfT53uEo+O0xw4xv6tXW1M_G-3A5BHuncsduA@mail.gmail.com> <CAD5OKxvYOY5JZ2mYNGiH1poUBQkyOOycePFijH5H+SxtcdqujQ@mail.gmail.com> <CABkgnnVe-b6Sv=R67bMJk_NQqQwdrRUn6rBm7Gu_CMcfPQwtEg@mail.gmail.com> <CAD5OKxvZbEJ7sV4WPAYoQapzMR_QwAftj-oKg=ioMKHNT792wQ@mail.gmail.com> <6F428EFD2B8C2F49A2FB1317291A76C113563C5A92@USNAVSXCHMBSA1.ndc.alcatel-lucent.com> <CA+9kkMDxZ-HW+C285d==5fVQaukxc8gPVTp-5oaGxstbk1RfqA@mail.gmail.com>
In-Reply-To: <CA+9kkMDxZ-HW+C285d==5fVQaukxc8gPVTp-5oaGxstbk1RfqA@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="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] Resolving RTP/SDES question in Paris
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, 19 Mar 2012 16:01:04 -0000

Ted,
I simply do not buy your argument.

It doesn't matter what security scheme is used if you download a dedicated communications client that you don't trust.  It can play whatever games it wants with the UI and the security configuration and you are none the better off.  You have to trust the application.

It is only within the context of a trusted browser (and its UI) that any of this security work makes sense.  As long as you can trust the browser to tell you what's going on, you don't have to trust the application.

You might also have a trusted dedicated application but it better follow the same guidelines if it expects to remain trusted.

Richard

-----Original Message-----
From: Ted Hardie [mailto:ted.ietf@gmail.com] 
Sent: Monday, March 19, 2012 9:51 AM
To: Ejzak, Richard P (Richard)
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] Resolving RTP/SDES question in Paris

On Sun, Mar 18, 2012 at 9:10 PM, Ejzak, Richard P (Richard)
<richard.ejzak@alcatel-lucent.com> wrote:
> I would like to argue two points: 1) DTLS-SRTP with IdP is the only media
> security scheme that rtcweb should support; and 2) rtcweb should also
> support RTP (no media security) with a clear requirement on the browser UI
> to warn the user of the complete lack of media security.
>

I'd like to comment on the "browser UI" issue here.  As we have
discussed in the past, the users of this technology may very well
include applications which are not browsers.  In the "pokerstars"
example, a mobile device may very well be using a purpose-built
application instead of the mobile browser in order to reach the site.
These mobile apps may interact with web-browser based clients during
the same hand of poker.   If the web-browser based client wants to use
an insecure media channel and can get consent, there is still no
guarantee that other clients can do the same using the same UI
feature.

Web technology != browser.  Let's be careful not to build the security
story at the protocol level on UI features we can neither predict nor
control.  We can choose not to have certain levels of security, but
hand-waving that decision away because we believe it can be managed at
some other layer is a very risky proposition.

regards,

Ted