Re: IETF Meeting Venue Selection Criteria

Stephane Bortzmeyer <bortzmeyer@nic.fr> Fri, 14 October 2005 08:15 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQKim-0003fY-42; Fri, 14 Oct 2005 04:15:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQKik-0003fO-72 for ietf@megatron.ietf.org; Fri, 14 Oct 2005 04:15:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA25085 for <ietf@ietf.org>; Fri, 14 Oct 2005 04:15:12 -0400 (EDT)
Received: from mx2.nic.fr ([192.134.4.11]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EQKtP-0003nt-K6 for ietf@ietf.org; Fri, 14 Oct 2005 04:26:20 -0400
Received: from localhost (localhost.localdomain [127.0.0.1]) by mx2.nic.fr (Postfix) with ESMTP id 1A6E426C0CF; Fri, 14 Oct 2005 10:15:16 +0200 (CEST)
Received: from maya40.nic.fr (maya40.nic.fr [192.134.4.151]) by mx2.nic.fr (Postfix) with ESMTP id 0110726C085; Fri, 14 Oct 2005 10:15:15 +0200 (CEST)
Received: from batilda.nic.fr (postfix@batilda.nic.fr [192.134.4.69]) by maya40.nic.fr (8.12.4/8.12.4) with ESMTP id j9E8FEYa598384; Fri, 14 Oct 2005 10:15:14 +0200 (CEST)
Received: by batilda.nic.fr (Postfix, from userid 1000) id D9B2A16A9A4; Fri, 14 Oct 2005 10:15:14 +0200 (CEST)
Date: Fri, 14 Oct 2005 10:15:14 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Message-ID: <20051014081514.GA23583@nic.fr>
References: <BF74AC74.1338C6%jordi.palet@consulintel.es>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <BF74AC74.1338C6%jordi.palet@consulintel.es>
X-Operating-System: Debian GNU/Linux 3.1
X-Kernel: Linux 2.6.8-2-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.9i
X-Virus-Scanned: by amavisd-new at mx2.nic.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: IETF Meeting Venue Selection Criteria
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

On Fri, Oct 14, 2005 at 12:29:40AM +0200,
 JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote 
 a message of 37 lines which said:

> http://www.ietf.org/internet-drafts/draft-palet-ietf-meeting-venue-selection-criteria-00.txt

(Now -01)

Next drafts : "How to select appropriate dining room for a Meeting",
"IETF bathroom requirements", ...

> The airport should be of such capacity to accommodate 60% of the
> attendees arriving and departing on the same day, in addition to the
> usual number of passengers.

IETF MUST NOT hold a meeting in a location where the international
airport is not IETF-compliant and open-standards-based.

> The traveling to the venue location should be possible with a
> maximum of one flight hop from a major hub.  The airport must have a
> diversity of international carriers.

The location MUST be accessible to IETF members with a TTL of 1.

> If there is already a WLAN in the building can be turned off

The IETF MUST NOT accept competing WLAN access.

> Appropriate warnings (e.g. about local crime risks) must be given.

The IETF MUST NOT hold meetings in Baghdad or New Orleans for the
foreseeable future.

Appropriate warnings about local risks of hurricanes, flooding,
tsunami or earthquakes must be given.

[Good bye, California.]




_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf