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

Joel Jaeggli <joelja@bogus.com> Thu, 01 July 2010 16:42 UTC

Return-Path: <joelja@bogus.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 9C9A73A684A for <ietf@core3.amsl.com>; Thu, 1 Jul 2010 09:42:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.321
X-Spam-Level:
X-Spam-Status: No, score=-1.321 tagged_above=-999 required=5 tests=[AWL=-0.211, BAYES_05=-1.11]
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 F7WGP-PkQE9D for <ietf@core3.amsl.com>; Thu, 1 Jul 2010 09:42:35 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 55D2A3A6824 for <ietf@ietf.org>; Thu, 1 Jul 2010 09:42:31 -0700 (PDT)
Received: from [192.168.2.100] (m3c0536d0.tmodns.net [208.54.5.60]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id o61GgaNr055493 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 1 Jul 2010 16:42:41 GMT (envelope-from joelja@bogus.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>
Message-Id: <92C447BB-792E-4EF7-ACAC-C91A4D27DC51@bogus.com>
From: Joel Jaeggli <joelja@bogus.com>
To: Andrew Sullivan <ajs@shinkuro.com>
In-Reply-To: <20100701154421.GB43159@shinkuro.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPad Mail (7B367)
Mime-Version: 1.0 (iPad Mail 7B367)
Subject: Re: Admission Control to the IETF 78 and IETF 79 Networks
Date: Thu, 01 Jul 2010 09:42:16 -0700
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.2 (nagasaki.bogus.com [147.28.0.81]); Thu, 01 Jul 2010 16:42:43 +0000 (UTC)
Cc: "ietf@ietf.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: Thu, 01 Jul 2010 16:42:38 -0000

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.

One can refer to the RFID experiment and discussion for another example of pii data handling in ietf experiments.

Joel's iPad

On Jul 1, 2010, at 8:44 AM, Andrew Sullivan <ajs@shinkuro.com> wrote:

> On Thu, Jul 01, 2010 at 08:26:35AM -0700, Fred Baker wrote:
> 
>> While it is new in IETF meetings, it is far from unusual in WiFi
>> networks to find some form of authentication. This happens at coffee
>> shops, college campuses, corporate campuses, and people's
>> apartments. 
> 
> I'd hate to think that the IETF is modelling its networks on dodgy
> semi-opaque NAT boxes with bad DNS habits and poor performance.  
> 
> That aside, I have some questions.  What are the plans for logging of
> the authentication requests, failures, and successes, and who could
> legally have access to those logs?  In particular, are the governments
> of the countries where the (respective) events are to be held able to
> require that the logs be turned over?  How long will the logs be kept,
> and by whom?  (Obviously, these are not new issues, but given the
> increased ability under this approach to associate a particular human
> with one or more MAC addresses, it would seem that the status of such
> logging might be more important.)
> 
> A
> 
> -- 
> Andrew Sullivan
> ajs@shinkuro.com
> Shinkuro, Inc.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>