Re: [Recentattendees] Registration open for IETF 113
Alexa Morris <amorris@amsl.com> Thu, 27 January 2022 22:51 UTC
Return-Path: <amorris@amsl.com>
X-Original-To: recentattendees@ietfa.amsl.com
Delivered-To: recentattendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33C313A0884; Thu, 27 Jan 2022 14:51:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.898
X-Spam-Level:
X-Spam-Status: No, score=-6.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 HhyXxgXc3ckS; Thu, 27 Jan 2022 14:51:32 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 101673A0888; Thu, 27 Jan 2022 14:51:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id D9779425A344; Thu, 27 Jan 2022 14:51:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30cq5d8vFH9l; Thu, 27 Jan 2022 14:51:31 -0800 (PST)
Received: from smtpclient.apple (unknown [IPv6:2601:647:4200:c8e0:f99f:11cd:8e13:8a30]) by c8a.amsl.com (Postfix) with ESMTPSA id BB98A424B435; Thu, 27 Jan 2022 14:51:31 -0800 (PST)
From: Alexa Morris <amorris@amsl.com>
Message-Id: <428F2733-2ED3-4EB9-B434-B7FCAF643954@amsl.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E01F0A18-C36B-4D60-847E-5F9C2E90543B"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Thu, 27 Jan 2022 14:51:30 -0800
In-Reply-To: <B1697701-00AD-4521-8A5A-9255A15AE0C1@tzi.org>
Cc: recentattendees@ietf.org, IETF discussion list <ietf@ietf.org>
To: Carsten Bormann <cabo@tzi.org>
References: <164331318866.22065.18215516813962572590@ietfa.amsl.com> <B1697701-00AD-4521-8A5A-9255A15AE0C1@tzi.org>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/recentattendees/zc5p0CYRQBgQALD2L6JtbtQyepY>
Subject: Re: [Recentattendees] Registration open for IETF 113
X-BeenThere: recentattendees@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Recent IETF Attendees <recentattendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/recentattendees>, <mailto:recentattendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/recentattendees/>
List-Post: <mailto:recentattendees@ietf.org>
List-Help: <mailto:recentattendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/recentattendees>, <mailto:recentattendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jan 2022 22:51:36 -0000
Hi Carsten, > On Jan 27, 2022, at 2:37 PM, Carsten Bormann <cabo@tzi.org> wrote: > > I see that this was designed to allow converting onsite to remote at the early-bird tariff even after Feb 7. Good, so for those on the brink a decision isn’t forced on Feb 7 already. > > Given that the hotel link only comes with onsite registration, I’m distilling the following procedure: > > > * Register for onsite now > * Wait for the hotel link in the registration confirmation > * Read the cancellation conditions, which don’t seem to be available otherwise The hotel cancellation terms are published at https://www.ietf.org/how/meetings/113/hotel/ <https://www.ietf.org/how/meetings/113/hotel/>. Only the IETF-specific reservation URL is sent after you register. Best, Alexa > > Case 1: Unfavorable onsite hotel cancellation conditions > > * Convert the onsite registration to remote by mailing support@ > * expect differential refund > * all set for remote. > > Case 2: Favorable onsite hotel cancellation conditions > > * Book the onsite hotel > * Wait until mid-March or so > > Case 2a: Travel still seems possible > > * all set for onsite (maybe book flight or train if not done yet). > > Case 2b: Travel conditions unfavorable, need to revert to onsite > > * Cancel hotel > * Convert the onsite registration to remote by mailing support@ > * expect differential refund > * all set for remote. > > > > Any flaws (unnecessary steps, wrong steps, cancellation fees, increased registration costs) in my reasoning? > > Grüße, Carsten >