Re: [saag] Ubiquitous Encryption: content filtering
Stephen Kent <kent@bbn.com> Tue, 23 June 2015 18:47 UTC
Return-Path: <kent@bbn.com>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D02201A8AFE for <saag@ietfa.amsl.com>; Tue, 23 Jun 2015 11:47:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JyfJRGlolcRU for <saag@ietfa.amsl.com>; Tue, 23 Jun 2015 11:47:32 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 513A11A90FD for <saag@ietf.org>; Tue, 23 Jun 2015 11:47:32 -0700 (PDT)
Received: from ssh.bbn.com ([192.1.122.15]:51355 helo=COMSEC.home) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1Z7TEI-00099m-Oy; Tue, 23 Jun 2015 14:47:30 -0400
Message-ID: <5589A9C2.40802@bbn.com>
Date: Tue, 23 Jun 2015 14:47:30 -0400
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Nico Williams <nico@cryptonector.com>
References: <99DC814A-2B7D-4802-A1C7-399E77F37BD7@gsma.com> <CABtrr-U9kLfq4GQbWSgPN=wCD=Cdi0uQ+bQqXj35j+PFtuE8Pg@mail.gmail.com> <A4BAAB326B17CE40B45830B745F70F108E070156@VOEXM17W.internal.vodafone.com> <55844743.4030300@cs.tcd.ie> <55886F38.4030906@bbn.com> <20150622211207.GM6117@localhost>
In-Reply-To: <20150622211207.GM6117@localhost>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/saag/V3LXaTMNI9g0IiJxsQXMoVhEL-Y>
Cc: saag@ietf.org
Subject: Re: [saag] Ubiquitous Encryption: content filtering
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jun 2015 18:47:34 -0000
Nico, > On Mon, Jun 22, 2015 at 04:25:28PM -0400, Stephen Kent wrote: >> On purely technical grounds, an argument for filtering in the "middle" >> is reasonable. It's much easier for a mobile operator, [...] >> >> So, from an engineering perspective, the argument about the conflict >> between end-to-end encryption and operator (including enterprise IT >> staff) access to traffic is a valid consideration, irrespective of the >> telecom-regulator argument. > But it isn't just a matter of engineering the protocol. There are > security problems involved in making this happen (like: how do you > express to the user that there is one (or more!) middle box filtering > and/or modifying their traffic? how do users get to opt out? how is > scope limited? (e.g., how do you prevent the device/operator from > MITMing the user when the user is NOT using the operator's network?)). I didn't say that there were god/easy solutions here. I just noted that, from an engineering (not regulatory) perspective, there were legitimate concerns that should be noted. > And anyways, operators already get to do this by simply forcing users to > use devices from the operators (modified to have MITM CA trust anchors). > What new technology is being requested here, regardless of whether > we'd publish it (though the current position as to that is clear: no; > but the IETF consensus can always change)? Not all "operators" have the ability to impose such constraints. In my work environment the parent company is very much a Windows shop. But, they have been persuaded that forcing Mac users to adopt their preferred OS is not a viable solution (i.e., valuable personnel would likely depart). Steve
- [saag] Ubiquitous Encryption: content filtering Natasha Rooney
- Re: [saag] Ubiquitous Encryption: content filteri… Joseph Lorenzo Hall
- Re: [saag] Ubiquitous Encryption: content filteri… Smith, Kevin, (R&D) Vodafone Group
- Re: [saag] Ubiquitous Encryption: content filteri… Joseph Lorenzo Hall
- Re: [saag] Ubiquitous Encryption: content filteri… Stephen Farrell
- Re: [saag] Ubiquitous Encryption: content filteri… Randy Bush
- Re: [saag] Ubiquitous Encryption: content filteri… Stephen Kent
- Re: [saag] Ubiquitous Encryption: content filteri… Nico Williams
- Re: [saag] Ubiquitous Encryption: content filteri… Christian Huitema
- Re: [saag] Ubiquitous Encryption: content filteri… Nico Williams
- Re: [saag] Ubiquitous Encryption: content filteri… Ted Hardie
- Re: [saag] Ubiquitous Encryption: content filteri… Nico Williams
- Re: [saag] Ubiquitous Encryption: content filteri… Randy Bush
- Re: [saag] Ubiquitous Encryption: content filteri… Tom Ritter
- Re: [saag] Ubiquitous Encryption: content filteri… Natasha Rooney
- Re: [saag] Ubiquitous Encryption: content filteri… Kathleen Moriarty
- Re: [saag] Ubiquitous Encryption: content filteri… Yoav Nir
- Re: [saag] Ubiquitous Encryption: content filteri… Kathleen Moriarty
- Re: [saag] Ubiquitous Encryption: content filteri… Natasha Rooney
- Re: [saag] Ubiquitous Encryption: content filteri… Stephen Kent
- Re: [saag] Ubiquitous Encryption: content filteri… Nico Williams
- Re: [saag] Ubiquitous Encryption: content filteri… Phillip Hallam-Baker
- Re: [saag] Ubiquitous Encryption: content filteri… Tom Ritter
- Re: [saag] Ubiquitous Encryption: content filteri… Natasha Rooney
- Re: [saag] Ubiquitous Encryption: content filteri… Kathleen Moriarty