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

Joel Jaeggli <joelja@bogus.com> Thu, 01 July 2010 19:59 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 714BF3A6A49 for <ietf@core3.amsl.com>; Thu, 1 Jul 2010 12:59:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.013
X-Spam-Level:
X-Spam-Status: No, score=-2.013 tagged_above=-999 required=5 tests=[AWL=0.586, BAYES_00=-2.599]
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 U1AU7RVvJaji for <ietf@core3.amsl.com>; Thu, 1 Jul 2010 12:59:09 -0700 (PDT)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by core3.amsl.com (Postfix) with ESMTP id 5F0533A6A47 for <ietf@ietf.org>; Thu, 1 Jul 2010 12:59:09 -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 o61JxCLa066465 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 1 Jul 2010 19:59:18 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> <92C447BB-792E-4EF7-ACAC-C91A4D27DC51@bogus.com> <20100701170744.GD43159@shinkuro.com> <4D37C04B-711B-4B1E-8299-3B0CD85D2DC4@muada.com> <4C2CEA82.8010904@vigilsec.com> <5482D813-80EE-4128-959B-B0DDD8BD22C7@muada.com>
Message-Id: <1A1366AD-EBAB-469B-86EF-DACB9FF85FF9@bogus.com>
From: Joel Jaeggli <joelja@bogus.com>
To: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <5482D813-80EE-4128-959B-B0DDD8BD22C7@muada.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 12:58:51 -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 19:59:20 +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 19:59:10 -0000

It not necessary to log but it is necessary to create either a firewall ACL or an L2 fib entry at the time of authentication...

Joel's iPad

On Jul 1, 2010, at 12:32 PM, Iljitsch van Beijnum <iljitsch@muada.com> wrote:

> On 1 jul 2010, at 21:20, Russ Housley wrote:
> 
>> Again, the use of anonymous registration IDs is available to you and
>> anyone that wants one.  If you are concerned about the logs, then you
>> should use one.
> 
> I'm concerned about the correlation between my MAC address and the hosts I communicate with. Anonymous IDs don't help against that, but not logging does, because then the only way for a government to obtain this correlation is on an individual basis rather than casting a wide net that catches large amounts of previously logged information.
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>