Re: Admission Control to the IETF 78 and IETF 79 Networks

Andrew Sullivan <ajs@shinkuro.com> Thu, 01 July 2010 17:07 UTC

Return-Path: <ajs@shinkuro.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 92D6F3A68F5 for <ietf@core3.amsl.com>; Thu, 1 Jul 2010 10:07:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.845
X-Spam-Level:
X-Spam-Status: No, score=0.845 tagged_above=-999 required=5 tests=[AWL=0.844, BAYES_50=0.001]
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 DS-UcruTvQzL for <ietf@core3.amsl.com>; Thu, 1 Jul 2010 10:07:37 -0700 (PDT)
Received: from mail.yitter.info (mail.yitter.info [208.86.224.201]) by core3.amsl.com (Postfix) with ESMTP id 66AD33A68C7 for <ietf@ietf.org>; Thu, 1 Jul 2010 10:07:36 -0700 (PDT)
Received: from crankycanuck.ca (69-196-144-230.dsl.teksavvy.com [69.196.144.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.yitter.info (Postfix) with ESMTPSA id F01F21ECB41D for <ietf@ietf.org>; Thu, 1 Jul 2010 17:07:46 +0000 (UTC)
Date: Thu, 01 Jul 2010 13:07:45 -0400
From: Andrew Sullivan <ajs@shinkuro.com>
To: ietf@ietf.org
Subject: Re: Admission Control to the IETF 78 and IETF 79 Networks
Message-ID: <20100701170744.GD43159@shinkuro.com>
References: <CFB08C07-DE90-47BE-ADFF-FC72162BBFA1@daedelus.com> <4C2BBD51.2060605@ietf.org> <6.2.5.6.2.20100701070804.0c26b8a0@resistor.net> <6D6E25E2-057B-4591-9288-1283036D0374@cisco.com> <20100701154421.GB43159@shinkuro.com> <92C447BB-792E-4EF7-ACAC-C91A4D27DC51@bogus.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <92C447BB-792E-4EF7-ACAC-C91A4D27DC51@bogus.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
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: Thu, 01 Jul 2010 17:07:45 -0000

On Thu, Jul 01, 2010 at 09:42:16AM -0700, Joel Jaeggli wrote:
> It has been the documented practice of the ietf meeting network
> operations to limit the amount of pii data collected in operation or
> experimentation and to destroy logs containing pii data if they
> exist (example data collected by the IDS or formerly http proxy back
> when we ran one) after the meeting.

This is useful, but not quite what I was asking.  Clearly, the above
means that the logs exist during the meeting, while we are at the host
venue.  I think it is safe to say that under some legal regimes, a
government could require the delivery of such existing logs to them.
Once such logs have been delivered, then even if the meeting netops
people destroy the logs, the logs can persist.  Right?

What I'm trying to find out is what assurances, if any, we have about
the ability of the IETF to remain in sole control of the data.  I'm
not really a paranoid type, but perhaps the recent experience of
Toronto police simply lying (with government collusion) about what
powers they had to detain people during the recent G20 meeting has
made me a little sensitive to this kind of (surprise, new)
requirement.  I would also likely care less, except the whole point of
this effort is plainly to support one government's policy -- a policy
that I find odious, and one that appears at least once to have had
technical side effects on the global DNS.  I'll leave aside the optics
of announcing the new policy less than a month before it is to be
implemented, and after people have already made travel plans, paid
meeting fees, and so on.

A

-- 
Andrew Sullivan
ajs@shinkuro.com
Shinkuro, Inc.