Re: Admission Control to the IETF 78 and IETF 79 Networks
SM <sm@resistor.net> Thu, 01 July 2010 15:09 UTC
Return-Path: <sm@resistor.net>
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 D5BF93A6452 for <ietf@core3.amsl.com>; Thu, 1 Jul 2010 08:09:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.91
X-Spam-Level:
X-Spam-Status: No, score=-0.91 tagged_above=-999 required=5 tests=[AWL=-0.911, 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 zlTJon4VMXyO for <ietf@core3.amsl.com>; Thu, 1 Jul 2010 08:09:05 -0700 (PDT)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id 6ED3B3A685C for <ietf@ietf.org>; Thu, 1 Jul 2010 08:09:05 -0700 (PDT)
Received: from SUBMAN.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.5.Alpha0/8.14.5.Alpha0) with ESMTP id o61F8LEH005828 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Thu, 1 Jul 2010 08:09:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1277996954; x=1278083354; bh=n7Yf/jo1J/DDMteYvmuMqdI5sQkB+TIcbSqyM5SavlI=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=4svfXesVBi91fMIGdJ4IrfVq2kbrraDiG4mmEf1IZq8rgMjiOqUwLiGlo5AsG0KT+ z91dyyUGz8Rp7LiahBG5OAMHgMn1YrP+U4DsWkEP0Fx1aUttL5YgnYRy3IPWRn1KXp COTGKWweSGrALL0MULKC6CCwea996ybG7iTH6wlA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1277996954; x=1278083354; bh=n7Yf/jo1J/DDMteYvmuMqdI5sQkB+TIcbSqyM5SavlI=; h=Message-Id:Date:To:From:Subject:In-Reply-To:References: Mime-Version:Content-Type:Cc; b=CsZcmGrPIL6e23EKHzhe3nFgE4JlFpC+C5oNNpeoTj3iYtQ5ATQv9SXB+vvJNrxTL Z9bW5RQKLKvaWUtYeLe95hvujwnayhZC40bE6z6nBRCahnuBsMLMNIBe55zyKOVuqS k8JDTkmw1As/TdOPCJfgsLOiRG2q2msqSSAlXqi0=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=rE2bKnhiKYc4zEnJs9y39XCjMBc6Uz3wlk4M6a0xosVp0puEWpviQ5QMk1+mdxgIn TFrHM1D7yx5tc7anR58qsRosRTWkdiUXh6gwi34As2ubOnrMUqsxUSTmoNW3rmIO2ED hxJNo8evew6r8FCtrV6vwlxZb76VpCcK/7HzQNY=
Message-Id: <6.2.5.6.2.20100701070804.0c26b8a0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 01 Jul 2010 08:08:09 -0700
To: IETF <ietf@ietf.org>
From: SM <sm@resistor.net>
Subject: Re: Admission Control to the IETF 78 and IETF 79 Networks
In-Reply-To: <4C2BBD51.2060605@ietf.org>
References: <CFB08C07-DE90-47BE-ADFF-FC72162BBFA1@daedelus.com> <4C2BBD51.2060605@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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 15:09:07 -0000
Hello, At 14:55 30-06-10, IETF Chair wrote: >I am writing to let you know about a change in the IETF meeting network. >At IETF 79 in Beijing, the IETF network will be connected to the open >Internet with absolutely no filtering. However, we have agreed with our >hosts that only IETF meeting participants will have access to the >network. Following sound engineering practices, we will deploy >admission control mechanisms as part of the IETF 78 meeting network in >Maastricht to ensure that they are working properly before they are >mission critical. Most IETF participants probably know that the consensus of the IETF is documented through BCPs and other Standards Track RFCs. If the text in the RFC isn't clear, there is room for disagreement. If it is ill-defined, someone will go and find the loophole. If the above text was in a BCP, we could nit on the definition of IETF meeting participants. It is clear to people unfamiliar with the IETF that IETF meeting participants means people who have registered for the IETF meeting. I have been told that an IETF meeting does not have security guards at the door to verify who has a badge to determine whether the person is registered for the meeting. If someone walks into an IETF meeting, the person can enjoy the cookie for free and even provide a contribution at the mic. The person enjoys the same privileges as people who have paid for meeting attendance fee. I'll take the opportunity to thank Karen O'Donoghue for keeping the IAOC minutes up to date. The IAB could do with some help in that area. Some of you may recall that the Beijing venue contract was discussed on this mailing list last year. It resulted in some resolutions as follows: "Whereas the Host has assured the IAOC that 'a normal IETF meeting can be legally held in China and that no pre-screening of material or monitoring of session content is required or will be done,' Whereas the IAOC, based on the assurances of the Host and a history of the venue successfully hosting major international conferences that relate to our industry, believes a normal IETF meeting can be held at the venue, Whereas the IAOC heard all arguments made on the list, and made its determination on the ability to hold a successful meeting i.e. run it in a fashion as we always have, using the tools that we always have, with a critical mass of the traditional participants, discussing the usual topics." The fashion in the IETF is to have an open network. There isn't any admission control and credentials are not required to enjoy the benefit of free and full Internet access. The IETF may run out of cookies; it never runs out of bandwidth. >I am writing to let you know what to expect in both Maastricht and Beijing. And it is expected that the comments on this thread will follow sound IETF practices when it comes to mailing list discussions. :-) Regards, -sm
- Re: Admission Control to the IETF 78 and IETF 79 … Martin Rex
- Admission Control to the IETF 78 and IETF 79 Netw… IETF Chair
- Re: Admission Control to the IETF 78 and IETF 79 … SM
- Re: Admission Control to the IETF 78 and IETF 79 … Fred Baker
- Re: Admission Control to the IETF 78 and IETF 79 … Olivier MJ Crepin-Leblond
- Re: Admission Control to the IETF 78 and IETF 79 … Dave CROCKER
- Re: Admission Control to the IETF 78 and IETF 79 … Andrew Sullivan
- Re: Admission Control to the IETF 78 and IETF 79 … Richard L. Barnes
- Re: Admission Control to the IETF 78 and IETF 79 … Ole Jacobsen
- Re: Admission Control to the IETF 78 and IETF 79 … Joel Jaeggli
- Re: Admission Control to the IETF 78 and IETF 79 … Marshall Eubanks
- Re: Admission Control to the IETF 78 and IETF 79 … Andrew Sullivan
- Re: Admission Control to the IETF 78 and IETF 79 … Iljitsch van Beijnum
- Re: Admission Control to the IETF 78 and IETF 79 … Ted Hardie
- Re: Admission Control to the IETF 78 and IETF 79 … Russ Housley
- Re: Admission Control to the IETF 78 and IETF 79 … Richard L. Barnes
- Re: Admission Control to the IETF 78 and IETF 79 … Russ Housley
- Re: Admission Control to the IETF 78 and IETF 79 … Russ Housley
- Re: Admission Control to the IETF 78 and IETF 79 … Russ Housley
- Re: Admission Control to the IETF 78 and IETF 79 … Richard L. Barnes
- Re: Admission Control to the IETF 78 and IETF 79 … Iljitsch van Beijnum
- Re: Admission Control to the IETF 78 and IETF 79 … Russ Housley
- Re: Admission Control to the IETF 78 and IETF 79 … David Conrad
- Re: Admission Control to the IETF 78 and IETF 79 … Joel Jaeggli
- Re: Admission Control to the IETF 78 and IETF 79 … Randy Bush
- Re: Admission Control to the IETF 78 and IETF 79 … Randy Bush
- Re: Admission Control to the IETF 78 and IETF 79 … Randy Bush
- Re: Admission Control to the IETF 78 and IETF 79 … Martin Rex
- Re: Admission Control to the IETF 78 and IETF 79 … Randy Bush
- Re: Admission Control to the IETF 78 and IETF 79 … John C Klensin
- Re: Admission Control to the IETF 78 and IETF 79 … Ole Jacobsen
- Re: Admission Control to the IETF 78 and IETF 79 … Russ Housley
- Re: Admission Control to the IETF 78 and IETF 79 … Michael StJohns
- Re: Admission Control to the IETF 78 and IETF 79 … Randy Bush
- Re: Admission Control to the IETF 78 and IETF 79 … Russ Housley
- Re: Admission Control to the IETF 78 and IETF 79 … Russ Housley
- free internet for ieters only Health
- Re: Admission Control to the IETF 78 and IETF 79 … Robert Moskowitz
- Re: Admission Control to the IETF 78 and IETF 79 … Douglas Otis
- Re: Admission Control to the IETF 78 and IETF 79 … SM
- Re: Admission Control to the IETF 78 and IETF 79 … Ole Jacobsen
- Re: Admission Control to the IETF 78 and IETF 79 … Bob Hinden
- Re: Admission Control to the IETF 78 and IETF 79 … Phillip Hallam-Baker
- Re: Admission Control to the IETF 78 and IETF 79 … SM
- Re: Admission Control to the IETF 78 and IETF 79 … Iljitsch van Beijnum
- Re: Admission Control to the IETF 78 and IETF 79 … Andrew G. Malis
- Re: Admission Control to the IETF 78 and IETF 79 … Marocco Enrico
- Re: Admission Control to the IETF 78 and IETF 79 … Ole Jacobsen
- Re: Admission Control to the IETF 78 and IETF 79 … Marocco Enrico
- Re: Admission Control to the IETF 78 and IETF 79 … Joel Jaeggli
- Re: Admission Control to the IETF 78 and IETF 79 … Phillip Hallam-Baker
- Re: Admission Control to the IETF 78 and IETF 79 … Chris Elliott
- Re: Admission Control to the IETF 78 and IETF 79 … tytso
- Re: Admission Control to the IETF 78 and IETF 79 … Mark Atwood
- Re: Admission Control to the IETF 78 and IETF 79 … Chris Elliott
- Re: Admission Control to the IETF 78 and IETF 79 … joel jaeggli
- Re: Admission Control to the IETF 78 and IETF 79 … Phillip Hallam-Baker
- Re: Admission Control to the IETF 78 and IETF 79 … Chris Elliott
- Re: Admission Control to the IETF 78 and IETF 79 … Chris Elliott
- Re: Admission Control to the IETF 78 and IETF 79 … Martin Rex
- Re: Admission Control to the IETF 78 and IETF 79 … Chris Elliott
- Re: Admission Control to the IETF 78 and IETF 79 … Douglas Otis
- Re: Admission Control to the IETF 78 and IETF 79 … Donald Eastlake
- Re: Admission Control to the IETF 78 and IETF 79 … Phillip Hallam-Baker
- Re: Admission Control to the IETF 78 and IETF 79 … Phillip Hallam-Baker
- Re: Admission Control to the IETF 78 and IETF 79 … Phillip Hallam-Baker
- Re: Admission Control to the IETF 78 and IETF 79 … Phillip Hallam-Baker
- Re: Admission Control to the IETF 78 and IETF 79 … Iljitsch van Beijnum
- Re: Admission Control to the IETF 78 and IETF 79 … Iljitsch van Beijnum
- Re: Admission Control to the IETF 78 and IETF 79 … IETF Chair
- RE: Admission Control to the IETF 78 and IETF 79 … Josh Howlett
- Re: Admission Control to the IETF 78 and IETF 79 … Phillip Hallam-Baker