Re: IETF 97 - Registration and Hotel Reservations Open Now!

Jari Arkko <jari.arkko@piuha.net> Fri, 12 August 2016 20:00 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDF5012D7D3 for <ietf@ietfa.amsl.com>; Fri, 12 Aug 2016 13:00:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.147
X-Spam-Level:
X-Spam-Status: No, score=-3.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.247] autolearn=ham autolearn_force=no
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 cX76TRR-XhBb for <ietf@ietfa.amsl.com>; Fri, 12 Aug 2016 13:00:45 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 2BFAC12D0EA for <ietf@ietf.org>; Fri, 12 Aug 2016 13:00:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 733792CCB3; Fri, 12 Aug 2016 23:00:43 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wvIsdAXIVOUo; Fri, 12 Aug 2016 23:00:42 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 8B9902CC45; Fri, 12 Aug 2016 23:00:42 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Subject: Re: IETF 97 - Registration and Hotel Reservations Open Now!
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_7CBEA628-F2D5-40FC-A5FD-45746051AB82"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <82A17B2FC06D1F8BD216D229@JcK-HP8200>
Date: Fri, 12 Aug 2016 22:00:41 +0200
Message-Id: <55DBF8B3-CB33-4E3F-9989-3B468FD53C72@piuha.net>
References: <147094744424.21281.7915555432277043072.idtracker@ietfa.amsl.com> <57AD2730.8050602@swin.edu.au> <9916BCD4DBD65FB7D44A6F88@JcK-HP8200>, <953016d5-6f64-bd94-c221-95d96f693c2c@dcrocker.net> <7594FB04B1934943A5C02806D1A2204B4BBDEDF4@ESESSMB208.ericsson.se> <036801d1f464$aaf1df20$00d59d60$@gmail.com> <42234065-1C6E-4224-A48C-1186F536E02F@piuha.net> <82A17B2FC06D1F8BD216D229@JcK-HP8200>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Svloz36-7RZ7xqsJR3qlXDHe-Jc>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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, 12 Aug 2016 20:00:48 -0000

John,

For what it is worth, I also consider it troubling that we are constantly in this situation. Now, I don’t actually know yet why we are in this situation this time. It could be about IT or policy issues on hotel’s side (e.g., why the reservations are available but only if you do them in several pieces). It could be about hotel not living up to its promise or us failing to hold them to their promise. It could be us not asking big enough block. Or that we simply can’t get big enough block and satisfy our other requirements. Or some combination thereof — and it is my perception that it is likely a combination. I do know that it is often very difficult for us to get bigger blocks than what we have.

I’ll note that we’ve promised a broader review of how well the IASA system works, and this is one topic among several to look at. We’ve said that the IAOC will get to this review later this year, given other ongoing efforts that are taking a lot of time.

As for the other issue that you mentioned, I can confirm that we should not demand you or any else explain why staying at a particular facility is important. I can imagine several reasons, some of which are true for various subsets of the community. Maybe a better question might be whether we’re having a sufficiently broad and satisfactory selection of official and unofficial alternatives (incl. airbnb) in our selected meeting locations. I don’t believe that IETF can cope with just the main hotel in almost any location.

Jari