Re: [ietf-privacy] Research Note on NSA/Snowden for EuroParl PRISM inquiry

Stephen Farrell <stephen.farrell@cs.tcd.ie> Sun, 29 September 2013 14:33 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf-privacy@ietfa.amsl.com
Delivered-To: ietf-privacy@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAA3A21F9FBA for <ietf-privacy@ietfa.amsl.com>; Sun, 29 Sep 2013 07:33:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 ElDnfZq15ACr for <ietf-privacy@ietfa.amsl.com>; Sun, 29 Sep 2013 07:33:37 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 5458321F9F3A for <ietf-privacy@ietf.org>; Sun, 29 Sep 2013 07:33:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 8E282BE75; Sun, 29 Sep 2013 15:33:36 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hEcv83bWCbX3; Sun, 29 Sep 2013 15:33:33 +0100 (IST)
Received: from [10.87.48.11] (unknown [86.42.27.255]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 786A7BE49; Sun, 29 Sep 2013 15:33:33 +0100 (IST)
Message-ID: <52483A3D.5060104@cs.tcd.ie>
Date: Sun, 29 Sep 2013 15:33:33 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0
MIME-Version: 1.0
To: Caspar Bowden <caspar@PrivacyStrategy.eu>, ietf-privacy@ietf.org
References: <52457A8E.9090105@casparbowden.net> <524830AA.8080409@PrivacyStrategy.eu>
In-Reply-To: <524830AA.8080409@PrivacyStrategy.eu>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [ietf-privacy] Research Note on NSA/Snowden for EuroParl PRISM inquiry
X-BeenThere: ietf-privacy@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Internet Privacy Discussion List <ietf-privacy.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-privacy>, <mailto:ietf-privacy-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-privacy>
List-Post: <mailto:ietf-privacy@ietf.org>
List-Help: <mailto:ietf-privacy-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-privacy>, <mailto:ietf-privacy-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 29 Sep 2013 14:33:41 -0000

Hi Caspar,

On 09/29/2013 02:52 PM, Caspar Bowden wrote:
> Although partly EU-specific, this <http://t.co/X4j9iCE6Ox> research Note
> on FISA/NSA for European Parliament PRISM inquiry might interest list
> members (35 pages, interdisciplinary). It was presented on 24th Sep and
> has now been accepted, so please redistribute if you wish
> 
> grateful for any feedback

I've only skimmed the recommnedations/conclusions so far but have
two comments. (I'll read the rest later, honest:-)

- I don't see why a "euro cloud" (section 3.1) would be any less
surveilled, e.g. by .eu governments on their own behalf of on behalf
of their partners. There could be jusrisdictional reasons for that
maybe (not that I'd understand those) but I don't think such a
recommendation really touches on pervasive monitoring at all unless
you're under the misaprehension that .eu governments are all far too
nice for that kind of thing or something. Can you explain that one?

- I think you could add a recommendation to work with the Internet
community on better technical solutions that can perhaps dramatically
increase the costs for pervasive monitoring. That's not a purely
cryptographic thing, and is something on which work is being done
e.g. here in the IETF. Note, nobody's claiming that changes made in
the IETF can fully "fix" this problem, but there are things we can
do that can help if they get deployed.

BTW, I think it'd be useful for us as well if the IETF had a way
to learn more about the non-technical reactions to all this stuff,
any ideas there welcome.

Cheers,
S.


> 
> Caspar
> @CasparBowden
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> ietf-privacy mailing list
> ietf-privacy@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-privacy
>