RE: IETF privacy policy - update

"Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com> Tue, 20 July 2010 09:16 UTC

Return-Path: <Chris.Dearlove@baesystems.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 937003A6452 for <ietf@core3.amsl.com>; Tue, 20 Jul 2010 02:16:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.094
X-Spam-Level:
X-Spam-Status: No, score=-6.094 tagged_above=-999 required=5 tests=[AWL=0.505, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l6jQt0V83SBJ for <ietf@core3.amsl.com>; Tue, 20 Jul 2010 02:16:27 -0700 (PDT)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by core3.amsl.com (Postfix) with ESMTP id 819913A67A4 for <ietf@ietf.org>; Tue, 20 Jul 2010 02:16:27 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.55,231,1278284400"; d="scan'208";a="77317321"
Received: from unknown (HELO baemasodc004.greenlnk.net) ([10.108.36.11]) by Baemasodc001ir.sharelnk.net with ESMTP; 20 Jul 2010 10:16:42 +0100
Received: from glkms1102.GREENLNK.NET (glkms1102.greenlnk.net [10.108.36.193]) by baemasodc004.greenlnk.net (Switch-3.4.3/Switch-3.4.3) with ESMTP id o6K9Gf5N015418; Tue, 20 Jul 2010 10:16:42 +0100
Received: from GLKMS2100.GREENLNK.NET ([10.15.184.93]) by glkms1102.GREENLNK.NET with Microsoft SMTPSVC(6.0.3790.3959); Tue, 20 Jul 2010 10:16:41 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: RE: IETF privacy policy - update
Date: Tue, 20 Jul 2010 10:16:40 +0100
Message-ID: <ABE739C5ADAC9A41ACCC72DF366B719D0340DBB2@GLKMS2100.GREENLNK.NET>
In-Reply-To: <201007152359.o6FNxAi7006088@fs4113.wdf.sap.corp>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
thread-topic: IETF privacy policy - update
thread-index: Acskec3AoVHks+7bSjCt8lGx5X41uQDcaWmQ
References: <23A0C2B7-9EAC-4C84-8D4F-C18FB2590991@cdt.org> from "John Morris"at Jul 15, 10 11:50:58 pm <201007152359.o6FNxAi7006088@fs4113.wdf.sap.corp>
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
To: mrex@sap.com, John Morris <jmorris-lists@cdt.org>
X-OriginalArrivalTime: 20 Jul 2010 09:16:41.0761 (UTC) FILETIME=[440C4110:01CB27EC]
Cc: paul.hoffman@vpnc.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jul 2010 09:16:28 -0000

>>                                                              I think

>> is very likely (if not certain) that right now the IETF is operating

>> in violation of the European Union's Data Protection Directive,

> nope, never while they're in the U.S.  National data protection laws
do
> not apply for someone operating entirely in a different country.

I have no idea about to what extent the EU directive applies. But I
would
have thought it would be tricky to argue that the IETF is operating
entirely in the US when it's about to meet and collect data in
Maastricht.

********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************