Re: [saag] Ubiquitous Encryption: content filtering

Randy Bush <randy@psg.com> Tue, 23 June 2015 04:36 UTC

Return-Path: <randy@psg.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 00E2F1A012D for <saag@ietfa.amsl.com>; Mon, 22 Jun 2015 21:36:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 aLvX8KBzTaRA for <saag@ietfa.amsl.com>; Mon, 22 Jun 2015 21:36:14 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A2F31A0121 for <saag@ietf.org>; Mon, 22 Jun 2015 21:36:13 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1Z7FwP-0006ne-Ok; Tue, 23 Jun 2015 04:36:09 +0000
Date: Tue, 23 Jun 2015 13:36:08 +0900
Message-ID: <m2a8vravnr.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Stephen Kent <kent@bbn.com>
In-Reply-To: <55886F38.4030906@bbn.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>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <http://mailarchive.ietf.org/arch/msg/saag/S_lUZBpQKuyTu5At5VAr42Jj0g8>
Cc: Security Area Advisory Group <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 04:36:15 -0000

> On purely technical grounds, an argument for filtering in the "middle"
> is reasonable. It's much easier for a mobile operator, an ISP, or an
> enterprise IT organization to perform content filtering at an
> intermediate point than to try to do so in every end point device.
> That's a major reason why enterprise IT folks prefer perimeter
> firewalls over endpoint firewalls. It's very difficult and expensive
> to manage (security) software on a large number of user devices, and
> it's even worse when those devices are diverse (e.g., Windows vs. Mac
> vs. Lunix or iOS vs. Android, vs. ...).

and that is working out so well, see OPM disaster

can you say soft gooey inside?

randy