Re: Registration open for IETF 114

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 09 May 2022 17:25 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 D0071C14F72A for <ietf@ietfa.amsl.com>; Mon, 9 May 2022 10:25:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=sandelman.ca
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a-kn-R4QECV8 for <ietf@ietfa.amsl.com>; Mon, 9 May 2022 10:25:45 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5F23C14F729 for <ietf@ietf.org>; Mon, 9 May 2022 10:25:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 2506B38C80 for <ietf@ietf.org>; Mon, 9 May 2022 13:39:11 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id m52xSfLa8mpG for <ietf@ietf.org>; Mon, 9 May 2022 13:39:09 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 647FD38C7F for <ietf@ietf.org>; Mon, 9 May 2022 13:39:09 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sandelman.ca; s=mail; t=1652117949; bh=ln6C3z89TjRaCcFgBO/+IyCEQtbxsUHjA5FZ2fipOqQ=; h=From:To:Subject:In-Reply-To:References:Date:From; b=quBBvm/G7luroywS6VtM50dm01pBQbbAVA0+rhpZekEXKfq4PIrNNJ88IEn2G7TFT KyiTMrWiFyhAEVBL6V4y2G2DRTTFxxwHzA5Bzh+4xfnAuhNm5GD4CUcohbHKSDYouR c7dTZIOrX+cyZKVoFzXEJqZcxzhLG4B46fAbHchYl749I2Fd3Y++WKovxG01SceyBM NqWKA+22RCFR/g0tipSysH/IwrMNE/mJR5tu6Qq3CCZ+kzUrp9dcRUtimVXCx9qeAX qAxJ9ELB/TpOnEHLvA/pgchHh8c4Li6FbLqhP1sDHV5K48lW2ZinVyPQkjJcBmSs9Y 3ziQk44SRYr0Q==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 14EE611A for <ietf@ietf.org>; Mon, 9 May 2022 13:25:42 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: IETF <ietf@ietf.org>
Subject: Re: Registration open for IETF 114
In-Reply-To: <DC8A79944855148CBDA8A40E@PSB>
References: <F6744CFE-D61F-41F1-9D95-8F322EDB6E0F@ietf.org> <F9CEB983-06B6-42E9-BAAA-D8F829CA32B3@live555.com> <CAC8QAccwyROv188W_GqBVpU4TgwZ9ESSg96P_HMc50Wva6LOsg@mail.gmail.com> <DC8A79944855148CBDA8A40E@PSB>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Mon, 09 May 2022 13:25:42 -0400
Message-ID: <15162.1652117142@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eb6MsnNUn_frCbvGYdXV5f1GuAs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.34
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: Mon, 09 May 2022 17:25:49 -0000

John C Klensin <john-ietf@jck.com> wrote:
    >> Last time early registration carried a much bigger  discount
    >> than this time. That is my only real concern.

    > I'd add one.  With online meetings prior to the pandemic, the
    > meeting page(s) listed alternate hotels and similar facilities
    > in the vicinity of the venue, ones that had been at least
    > minimally checked out in venue site visits.

Yes.  That had value to me as well.
At this point, I don't think that we actually have the numbers for overflow hotels.

    > Apparently, this
    > time, not only is the main hotel not heavily discounted, but
    > people looking for other options are apparently completely on
    > their own.  I can guess at some of the reasons for the former,
    > starting with lower and more uncertain attendee numbers but less
    > so for the latter.

The price of the main hotel hasn't been low, and often the IETF rate wasn't
discounted in any way.  This has been true for many years.
But, we fill out the promised block, we get available rooms which we might
now get, and we get way better network.
One advantage of the listed overflow hotels is that they was a much better
chance (90%+...) that all of the staff spoke english.  While some random
hotel you find through a web site, that chance is much lower.

In general, I have used airbnb's pre-pandemic, and I expect to use them again
in the future.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide