IETF Logo Mail Archive

Re: Registration open for IETF 114

Ross Finlayson <finlayson@live555.com> Thu, 05 May 2022 19:43 UTC

Return-Path: <finlayson@live555.com>
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 A9E10C15949C for <ietf@ietfa.amsl.com>; Thu, 5 May 2022 12:43:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 HCis2cM6MEQX for <ietf@ietfa.amsl.com>; Thu, 5 May 2022 12:43:35 -0700 (PDT)
Received: from us.live555.com (us.live555.com [52.8.240.222]) (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 59F3CC14F725 for <ietf@ietf.org>; Thu, 5 May 2022 12:43:34 -0700 (PDT)
Received: from smtpclient.apple (localhost.live555.com [IPv6:0:0:0:0:0:0:0:1]) by us.live555.com (8.16.1/8.16.1) with ESMTP id 245JhXH0072990 for <ietf@ietf.org>; Thu, 5 May 2022 12:43:33 -0700 (PDT) (envelope-from finlayson@live555.com)
From: Ross Finlayson <finlayson@live555.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
Subject: Re: Registration open for IETF 114
Date: Thu, 05 May 2022 12:43:33 -0700
References: <F6744CFE-D61F-41F1-9D95-8F322EDB6E0F@ietf.org>
To: ietf@ietf.org
In-Reply-To: <F6744CFE-D61F-41F1-9D95-8F322EDB6E0F@ietf.org>
Message-Id: <F9CEB983-06B6-42E9-BAAA-D8F829CA32B3@live555.com>
X-Mailer: Apple Mail (2.3696.80.82.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OwkO56AVsG2Yf-z2g9lvrPYS0SQ>
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: Thu, 05 May 2022 19:43:35 -0000

> On May 5, 2022, at 9:57 AM, IETF Executive Director <exec-director@ietf.org> wrote:
> 
> The IETF 114 meeting venue is at the Sheraton Philadelphia Downtown.  As explained in the FAQ, you will need to register before you can reserve a guest room at the venue.

Strictly speaking, this does not appear to be correct.  The link that I was sent to me (after I registered for the IETF) to reserve a guest room was not specific to my IETF registration.  While it gave me the IETF-discounted room rate, it would have worked for anyone, even if they hadn’t registered for the IETF.

For other on-site IETF meetings (before Covid), the link to reserve a hotel guest room (at the IETF-discounted room rate) was included in the IETF “Registration open” email.  This allowed people to reserve an IETF-hotel room (often a scarce resource) early, while deferring actually registering for the IETF.

Not including the hotel room link in the “Registration open” email appears to be an (understandable) ploy to get as many paid IETF registrations as early as possible.

	Ross.

v2.23.0 | Report a Bug | By Email