IETF Logo Mail Archive

RE: IETF hotel selection mode and a proposal (was" Re: Hilton BA is Booked already?)

"MAISONNEUVE, JULIEN (JULIEN)" <julien.maisonneuve@alcatel-lucent.com> Fri, 18 December 2015 10:52 UTC

Return-Path: <julien.maisonneuve@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF4211B35C6 for <ietf@ietfa.amsl.com>; Fri, 18 Dec 2015 02:52:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level:
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MaMwI2YpBtq1 for <ietf@ietfa.amsl.com>; Fri, 18 Dec 2015 02:52:11 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpgre-esg-01.alcatel-lucent.com [135.245.210.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A50581B35C0 for <ietf@ietf.org>; Fri, 18 Dec 2015 02:52:11 -0800 (PST)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (unknown [135.239.2.122]) by Websense Email Security Gateway with ESMTPS id CB6106BD5380D for <ietf@ietf.org>; Fri, 18 Dec 2015 10:20:06 +0000 (GMT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id tBIAK8ZK022838 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <ietf@ietf.org>; Fri, 18 Dec 2015 11:20:08 +0100
Received: from FR712WXCHMBA12.zeu.alcatel-lucent.com ([169.254.8.230]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.03.0195.001; Fri, 18 Dec 2015 11:20:08 +0100
From: "MAISONNEUVE, JULIEN (JULIEN)" <julien.maisonneuve@alcatel-lucent.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: IETF hotel selection mode and a proposal (was" Re: Hilton BA is Booked already?)
Thread-Topic: IETF hotel selection mode and a proposal (was" Re: Hilton BA is Booked already?)
Thread-Index: AQHROQDos4jzQPzID0CHrYFOdJyld57Qg6CA
Date: Fri, 18 Dec 2015 10:20:07 +0000
Message-ID: <93A9AFC57E50B34199A715A1CA9E0EEC98D161AB@FR712WXCHMBA12.zeu.alcatel-lucent.com>
References: <076c01d138e7$0a68dba0$1f3a92e0$@olddog.co.uk> <5672E4BB.2050702@dcrocker.net> <FA905E0564B6E47B70076F92@JcK-HP8200.jck.com>
In-Reply-To: <FA905E0564B6E47B70076F92@JcK-HP8200.jck.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.39]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/s5fVdvtYYhRWcmt2oSd4aQghwIE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Fri, 18 Dec 2015 10:52:13 -0000

Another crucial aspect is clustering : the issue is completely different when the overflow hotels are across the street (as one in Yokohama) and in Buenos Aires (where the nearest overflow hotel is 1.7km away).
If selecting locations that can host everyone in one hotel is hard, surely it is easier to find places with a cluster of reasonably close (walking distance) hotels to a large-enough conference center.
I think this could take a higher priority in the selection process, for the future.
All the best,
Julien.

v2.23.0 | Report a Bug | By Email