Re: IETF Meeting Venue Selection Criteria

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Sat, 22 October 2005 17:23 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ETN5E-0002xP-9i; Sat, 22 Oct 2005 13:23:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1ETN51-0002u1-QZ for ietf@megatron.ietf.org; Sat, 22 Oct 2005 13:22:51 -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 NAA21881 for <ietf@ietf.org>; Sat, 22 Oct 2005 13:22:39 -0400 (EDT)
Received: from mail.consulintel.es ([213.172.48.142] helo=consulintel.es) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ETNH1-0006gi-L1 for ietf@ietf.org; Sat, 22 Oct 2005 13:35:38 -0400
Received: from [192.35.164.42] by consulintel.es (MDaemon.PRO.v7.2.5.R) with ESMTP id md50001358121.msg for <ietf@ietf.org>; Sat, 22 Oct 2005 19:21:32 +0200
User-Agent: Microsoft-Entourage/11.2.0.050811
Date: Fri, 21 Oct 2005 17:28:18 -0700
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <BF7ED5B2.136C9D%jordi.palet@consulintel.es>
Thread-Topic: IETF Meeting Venue Selection Criteria
Thread-Index: AcXWn3+rvg/mQEKSEdqVIwAKldLC/g==
In-Reply-To: <434F7697.1000001@dial.pipex.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-Authenticated-Sender: jordi.palet@consulintel.es
X-MDRemoteIP: 192.35.164.42
X-Return-Path: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on mail.consulintel.es
X-Spam-Status: No, hits=-3.4 required=5.0 tests=BAYES_00,DATE_IN_PAST_12_24, TO_ADDRESS_EQ_REAL autolearn=no version=2.64
X-Spam-Processed: consulintel.es, Sat, 22 Oct 2005 19:22:06 +0200
X-MDAV-Processed: consulintel.es, Sat, 22 Oct 2005 19:22:06 +0200
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 2ed806e2f53ff1a061ad4f97e00345ac
Content-Transfer-Encoding: 7bit
Subject: Re: IETF Meeting Venue Selection Criteria
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jordi.palet@consulintel.es
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

Hi Elwyn,

Thanks a lot for all your inputs (and same for the rest of contributors).
I'm not sure to catch a couple of them:

> There is also the matter of break time refreshment provision..
> succouring 1300 thirsty, half-starved nerds (sorry, IETFers) two or
> three times a day at a reasonable cost can be a challenge.

You mean the break time is short ? I'm not sure that belongs to this
document, but more to a question of the meeting scheduling.

Regarding the cost, this is of course also considered during the
negotiation, so not sure if anything else need to be added into the document
about this.

> 
> You need to differentiate the technical requirements of the venue from
> what the network providers need to do.... there are some fuzzy edges
> here e.g., the WAN links

Yes, the idea is to have two documents. In theory there is one somewhere
about the technical issues, but as I've not been able to get a copy, I
prefer to keep the text here mean while. At the end I can take it out and
contribute to a 2nd document with all that, or even start it from scratch
(if it doesn't becomes available from other authors) with all the comments.

> 
> Editorial note: You should flag up that continental European conventions
> are in use for numbers.

What do you mean exactly ?


Regards,
Jordi




> De: Elwyn Davies <elwynd@dial.pipex.com>
> Responder a: <ietf-bounces@ietf.org>
> Fecha: Fri, 14 Oct 2005 10:12:55 +0100
> Para: "ietf@ietf.org" <ietf@ietf.org>
> CC: <jordi.palet@consulintel.es>
> Asunto: Re: IETF Meeting Venue Selection Criteria
> 
> 
> 
> Ole Jacobsen wrote:
> 
>> On Thu, 13 Oct 2005, Hallam-Baker, Phillip wrote:
>> 
>>  
>> 
>>> How about adding that the mean outdoor temperature at the time of the
>>> year the meeting is being held should be above 0 degrees Centigrade?
>>> 
>>>    
>>> 
>> 
>> Why?
>> 
> There is some logic in this.. Participants need to be able to get from
> airport to hotel to venue on foot/public transport without needing to
> bring excessive personal protection gear that they might not otherwise
> own, or experiencing heat stroke because they aren't used to the
> temperature/humidity (oh, and touristing before/after isn't much fun
> either).
> 
> Another related criterion is that the expected weather is not going to
> produce a high risk of transport disruption.. southern USA in the
> hurricane season???  continental Canada in December???  Asia in the
> monsoon season??? whereever in the peak holiday influx season for that
> region???
> 
> More importantly, the venue must be able to maintain a sensible
> temperature/humidity in the conference rooms (20-23 deg  C, 50% Relative
> Humidity).  Remember that the side effect of allowing 80% of people to
> plug in their laptops is that each of them may be dissipating an extra
> 150-200 watts of heat into the room over and above what the human body
> does.  This is actually more than doubling the heat load into the room,
> and cooling systems may not be able to cope - the IETF is an unusual
> body and it imposes cruel and unusual punishment on cooling systems.
> Sitting for a week in excessively warm and humid rooms is not pleasant
> (working efficiency falls off even at 26C).  For example, the Paris
> meeting turned out ok because the outside temperature dropped right
> about when the actual conference began, but I was at an Interop event in
> the same building the previous week when the temperatures were much
> higher, and being in one of the smaller rooms with lots of bodies and
> more computers was unpleasant.. the cooling just wasn't coping.   My
> mind has blanked out the location, but we had a very unpleasant week in
> a US venue two or three years ago when the cooling couldn't cope.
> Reference:
> http://ergo.human.cornell.edu/studentdownloads/DEA350notes/Thermal/thcomnotes1
> .html
> http://ergo.human.cornell.edu/studentdownloads/DEA350notes/Thermal/thcomnotes2
> .html
> http://ergo.human.cornell.edu/studentdownloads/DEA350notes/Thermal/thcondnotes
> .html
> 
> Other health risks: Would participants need vaccinations before
> attending?  Is it in a malaria risk area?  Are there other infectious
> disease hazards or nuisances - e.g., West Nile fever, Lyme disease,
> Scottish Highland midges.  Even if visas are not required are there any
> health checks at immigration?
> 
> The airport (and/or other wide area transport links) need to have
> adequate capacity and decent connections.. probably not an issue if the
> venue is sufficiently large but worth checking.
> 
> The criteria say nothing about accessibility for the differently able.
> 
> There is also the matter of break time refreshment provision..
> succouring 1300 thirsty, half-starved nerds (sorry, IETFers) two or
> three times a day at a reasonable cost can be a challenge.
> 
> You need to differentiate the technical requirements of the venue from
> what the network providers need to do.... there are some fuzzy edges
> here e.g., the WAN links
> 
> Editorial note: You should flag up that continental European conventions
> are in use for numbers.
> 
> Regards,
> Elwyn
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf




************************************
The IPv6 Portal: http://www.ipv6tf.org

Barcelona 2005 Global IPv6 Summit
Information available at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




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