RE: Hilton BA is Booked already?

Ted Lemon <Ted.Lemon@nominum.com> Wed, 16 December 2015 16:59 UTC

Return-Path: <Ted.Lemon@nominum.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 9F0891A1B30 for <ietf@ietfa.amsl.com>; Wed, 16 Dec 2015 08:59:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 QbpMQV5d_Wpb for <ietf@ietfa.amsl.com>; Wed, 16 Dec 2015 08:59:55 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 ADB4D1A1B53 for <ietf@ietf.org>; Wed, 16 Dec 2015 08:59:43 -0800 (PST)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 36230DA00A0; Wed, 16 Dec 2015 16:59:43 +0000 (UTC)
Received: from mbx-03.WIN.NOMINUM.COM ([169.254.4.19]) by CAS-04.WIN.NOMINUM.COM ([64.89.235.67]) with mapi id 14.03.0224.002; Wed, 16 Dec 2015 08:59:43 -0800
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Toerless Eckert <eckert@cisco.com>, Brian Rosen <br@salsgiver.com>
Subject: RE: Hilton BA is Booked already?
Thread-Topic: Hilton BA is Booked already?
Thread-Index: AQHROBSyswD8KU1VM0m0uFB/yIZYK57OQP2AgAACQgCAAAnqgP//fGVigAAB11eAAAm9Cg==
Date: Wed, 16 Dec 2015 16:59:42 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B630797A09BF6@mbx-03.WIN.NOMINUM.COM>
References: <723B626B-97C8-475A-BED1-EAB64C7E146F@standardstrack.com> <5671819D.4040303@tzi.org> <389D8D8B-C113-4F9F-96BB-B4E9E63B1691@ecs.soton.ac.uk> <EMEW3|21e6d02d918fb96ab4b441900d4c683brBFFUG03tjc|ecs.soton.ac.uk|389D8D8B-C113-4F9F-96BB-B4E9E63B1691@ecs.soton.ac.uk> <20151216160539.GA20112@cisco.com> <1FFA9F32-DE51-41CB-8EF1-DAD80DD508DD@salsgiver.com> <20151216161409.GB20112@cisco.com> <B709E690-321B-4119-A7C9-CF814A5E59F6@salsgiver.com>, <20151216162031.GC20112@cisco.com>
In-Reply-To: <20151216162031.GC20112@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [71.233.41.235]
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/qUY-BHnFAsgE7NCx9t56QZX8_9c>
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, Carsten Bormann <cabo@tzi.org>, Eric Burger <eburger@standardstrack.com>, IETF <ietf@ietf.org>
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: Wed, 16 Dec 2015 16:59:57 -0000

> And i am sure iwas also not 300 bookable rooms by the time the mail was sent.

I made three reservations over the course of about 20 minutes starting about ten minutes after the info went up on the IETF page.   For the first two, all the rooms were available.   For the last one, I had to take two doubles instead of a queen.   (I cancelled the first two--I was having trouble getting the reservation associated with my hhonors account, which is why I had to try multiple times.)

Given the number of dedicated attendees to the IETF, this was essentially a game of musical chairs.   It's one that happens ever IETF, and shouldn't be a surprise to anyone.   We got plenty of advance warning this time--I put an entry on my calendar.   I would have been perfectly happy if I didn't get a room at the hotel this time, as you've said you are.

So I don't really know what the problem is here.   I did a little looking around last week to see if I even _wanted_ stay in the Hilton, and there are a lot of really nice (looking) hotels in Buenos Aires.   I think this is a non-problem, but of course we will discuss it to death anyway... :)