IETF Logo Mail Archive

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

Iljitsch van Beijnum <iljitsch@muada.com> Wed, 14 July 2010 16:45 UTC

Return-Path: <iljitsch@muada.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 E32F83A69B6 for <ietf@core3.amsl.com>; Wed, 14 Jul 2010 09:45:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.227
X-Spam-Level:
X-Spam-Status: No, score=-2.227 tagged_above=-999 required=5 tests=[AWL=0.372, 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 3pV3PmQ2qhwm for <ietf@core3.amsl.com>; Wed, 14 Jul 2010 09:45:54 -0700 (PDT)
Received: from sequoia.muada.com (unknown [IPv6:2001:1af8:2:5::2]) by core3.amsl.com (Postfix) with ESMTP id 09E003A659C for <ietf@ietf.org>; Wed, 14 Jul 2010 09:45:49 -0700 (PDT)
Received: from claw.it.uc3m.es ([163.117.139.233]) (authenticated bits=0) by sequoia.muada.com (8.13.3/8.13.3) with ESMTP id o6EGjRwX021971 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 14 Jul 2010 18:45:27 +0200 (CEST) (envelope-from iljitsch@muada.com)
Subject: Re: Admission Control to the IETF 78 and IETF 79 Networks
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Iljitsch van Beijnum <iljitsch@muada.com>
In-Reply-To: <AANLkTikg8QmDxh93OAXbOsXt6KTuMcDYRGeXnU91Kh35@mail.gmail.com>
Date: Wed, 14 Jul 2010 18:45:18 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <BBEA78BA-B600-4F45-8E1D-33FB35D8F75C@muada.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> <AANLkTinMFsrGyIy9bu5kzUiZqNmDbf7lpS-eht8h3hvP@mail.gmail.com> <CCD1D0AD-97DC-4CE0-9E27-CC75B5F47C54@muada.com> <AANLkTilVmeg2Tgjgllg2yT3Oc34Y4ZuwXwl9U1ELfjhc@mail.gmail.com> <20100706170631.GK25518@thunk.org> <AANLkTil357pxy8tD49Q9ds9QVlSjo9h3p3akSN9UF1XS@mail.gmail.com> <AANLkTil0YIS9H-vYxIJJS_OC7tAlcCLQQycskFcLE71V@mail.gmail.com> <AANLkTilVAn3j-iXbdytu9en-OWAjlCFQSyQy1jiY1Zq1@mail.gmail.com> <AANLkTilCRrRhYVBNKdkaBudacJDCbBx3_48D9_U2RaSM@mail.gmail.com> <AANLkTinQhd-Cn-wPsjhmGEPjjcpkVTlYkb7UfNf9-7Lc@mail.gmail.com> <AANLkTikg8QmDxh93OAXbOsXt6KTuMcDYRGeXnU91Kh35@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1081)
Cc: IETF Discussion <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: Wed, 14 Jul 2010 16:45:58 -0000

I should know better than dive back into this discussion...

On 13 jul 2010, at 18:05, Phillip Hallam-Baker wrote:

> Con: There is no cost to generating the cert, the cert can be
> generated after the device ships. Thus there is no degree of
> accountability established in the presentation of a cert. If a user
> abuses the network (e.g. to send spam) there is no bar to prevent them
> ditching the banned cert and re-applying for another.

The cost of generating the cert can be more than just generating the cert. For instance, it could be made necessary to have the cert signed by someone who is presumably trustworthy. Or they need to build up some reputation.

v2.23.0 | Report a Bug | By Email