Re: Registration open for IETF 114

John C Klensin <john-ietf@jck.com> Tue, 10 May 2022 20:26 UTC

Return-Path: <john-ietf@jck.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 37D09C14F739 for <ietf@ietfa.amsl.com>; Tue, 10 May 2022 13:26:50 -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 HvOiXf6QgjbF for <ietf@ietfa.amsl.com>; Tue, 10 May 2022 13:26:46 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64468C14F720 for <ietf@ietf.org>; Tue, 10 May 2022 13:26:46 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1noWRO-000BRw-Vu; Tue, 10 May 2022 16:26:42 -0400
Date: Tue, 10 May 2022 16:26:36 -0400
From: John C Klensin <john-ietf@jck.com>
To: Alexa Morris <amorris@amsl.com>, Ross Finlayson <finlayson@live555.com>
cc: ietf@ietf.org
Subject: Re: Registration open for IETF 114
Message-ID: <FBBBBF3E97E093A8CA613AD5@PSB>
In-Reply-To: <E2ACB49B-FB96-4DE2-B759-039AC5779F7A@amsl.com>
References: <F6744CFE-D61F-41F1-9D95-8F322EDB6E0F@ietf.org> <F9CEB983-06B6-42E9-BAAA-D8F829CA32B3@live555.com> <E2ACB49B-FB96-4DE2-B759-039AC5779F7A@amsl.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8lq_x9UeiEn7l8ypLCt3t8232pM>
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: Tue, 10 May 2022 20:26:50 -0000


--On Friday, May 6, 2022 15:20 -0700 Alexa Morris
<amorris@amsl.com> wrote:

>> 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.
> 
> This approach, which we initiated at IETF 113, is typical of
> many conferences. It's not actually a ploy to get people to
> register early but rather a strategy to protect the IETF room
> block for those who genuinely intend to travel to
> Philadelphia.  
> 
> Unfortunately, in past years guest rooms were often snatched
> up early and hoarded until just prior to the meeting, when
> there was a rush of  cancellations. This left the IETF with an
> underutilized room block AND it left many onsite participants
> stuck at other properties they'd booked when the block was
> (temporarily) full. 

Alexa,

While I hope this works as you intend, my guess is that it won't
make much difference.  I don't know how typical I am, but don't
know whether I'll be in Philly in person and, as circumstances
change, am unlikely to be able to actually make that decision
until late June or early July.  So, with the present policies,
including the promise that, if I need to back off to remote
participation, the difference between the in-person and remote
registration fees will be refunded, my incentives are to:

 * Register now (or at least before the early bird
	cutoff) and pay up.
 * Book a hotel room now, noting that the Sheraton
	doesn't even want a deposit from me.
 * Possibly explore other options, either close by or a
	train ride away.
 * Make a decision as to whether I'm going to be in
	person or not and, if so, where I'm staying, no later
	than the first week in July and then sort thinks out.

Whether you consider that hoarding or not [1], the
symptoms/effects are no different from what you say you are
trying to avoid: I'm snatched up a room early and will sit on it
at least long enough that, if I do cancel, you get a
cancellation after many onsite attendees have made other plans.
I don't have a suggestion about how you could do better (at
least without policies that would just about guarantee I would
not attend and that would probably create far more uproar on
this list), but, other than your getting registration fees in
hand somewhat earlier, I'm not confident that this new policy
will make a big difference.

   best,
    john


[1] If you do, that description makes me uncomfortable, because
it unfairly attributes a very negative motivation to behavior
that seems to me to be not only reasonable but consistent with
the behavior you are encouraging.