Re: Registration open for IETF 114

Behcet Sarikaya <sarikaya2012@gmail.com> Tue, 10 May 2022 14:33 UTC

Return-Path: <sarikaya2012@gmail.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 BEEA4C14F725 for <ietf@ietfa.amsl.com>; Tue, 10 May 2022 07:33:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level:
X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 cXM_hlCBeUct for <ietf@ietfa.amsl.com>; Tue, 10 May 2022 07:33:05 -0700 (PDT)
Received: from mail-lf1-x132.google.com (mail-lf1-x132.google.com [IPv6:2a00:1450:4864:20::132]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 34C4BC14F722 for <ietf@ietf.org>; Tue, 10 May 2022 07:33:05 -0700 (PDT)
Received: by mail-lf1-x132.google.com with SMTP id d19so8062806lfj.4 for <ietf@ietf.org>; Tue, 10 May 2022 07:33:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=tr/oGiAXb8uyeRfPQZQ+FUTbyV4csdDto4UE78Wgdwg=; b=Sl9oyAgh8kFQAB0r0oVuuGY7+ECn9CxymHoGaZVQnEVwbtxPQ6aGObY3BuVxajkSxA 3JzkVNxBREQtuM7Tl8biPljJi77VGQsG3qPlLSLvGZZmRRb6kaZaNYkHotb2Ca1IRZGX IYQNMtev/NevDcZGwmdBcTBTxEXqd1MeMxj5axVRN5sfaWWcIulzZPbA3rzjDSJxxv0P rZo00XNbBRs/aMDhhAWehlNszaQ8J03JMCIC8UXI7Qcz1lJaaRPgC+wXTJvDNWdF1HSi YTiz6zsgly/s28hOpFRunp0D4bVEFl8VaaUvggRkmmetapY2wV9chekhmaDhY5/M7D9O Bjvg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=tr/oGiAXb8uyeRfPQZQ+FUTbyV4csdDto4UE78Wgdwg=; b=T6GNNLiP2zGqm2j/Vb/wkCfalPSTA8C7myJ9ImqXDKG3FX5guEEsquZMGb6VGQSA95 xDF3XBVw5/Wn6dEZjBri97JvMtAzXxUhRPErG4T1tT6lleQ93mnf7wBK3PbJuKR4Mu9c D+H2Svig2+GId+bvPtMukk/KDf+tEj+4KNOXqyaK9w2XEgfkQGi4DMh1tbzk7LiwIbDw A3rVz3uXU6rmuZ/i/TOloB/GfsgmUB2rt+fSeowMyuPSaKiLyOpZ44OWCJMXm7yNtt/P u4V91tVLTXGoa1cHhfMgDBdTlmPSL5IWq7k/iJzk5r22pfVUe/qPgYosHvgKkSq5KkdY nsGg==
X-Gm-Message-State: AOAM533oKGRPR5xTpm5O2doETzzWFeZroI3hc0lrVjxtVdDkhU5oa8Vq R+Uwp7F27hB8zhQ41SotpvIWT9GbDPliV/BkmYs=
X-Google-Smtp-Source: ABdhPJyJkv84PXf1XH91JxQZglChiYssuR7W7AaiUC/ea4eOF5EmBdPdSYQ/nkBf/gCiiTkub2BnwXR2eoRyj0jLm0w=
X-Received: by 2002:a05:6512:3484:b0:472:13f9:4aee with SMTP id v4-20020a056512348400b0047213f94aeemr16721888lfr.288.1652193182962; Tue, 10 May 2022 07:33:02 -0700 (PDT)
MIME-Version: 1.0
References: <F6744CFE-D61F-41F1-9D95-8F322EDB6E0F@ietf.org> <F9CEB983-06B6-42E9-BAAA-D8F829CA32B3@live555.com> <CAC8QAccwyROv188W_GqBVpU4TgwZ9ESSg96P_HMc50Wva6LOsg@mail.gmail.com> <DC8A79944855148CBDA8A40E@PSB> <7F8FD4B5-6B9D-439F-9969-D92D18E7DFB7@amsl.com> <326A2099999A3C4E4B1AD433@PSB>
In-Reply-To: <326A2099999A3C4E4B1AD433@PSB>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Tue, 10 May 2022 09:32:51 -0500
Message-ID: <CAC8QAcc37sUf+=_ovPTpHXXZE0wwz7zamx-NVLaQgi+UJnYWrA@mail.gmail.com>
Subject: Re: Registration open for IETF 114
To: John C Klensin <john-ietf@jck.com>
Cc: Alexa Morris <amorris@amsl.com>, Behcet Sarikaya <sarikaya@ieee.org>, Ross Finlayson <finlayson@live555.com>, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c556ca05dea933ab"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TET93xOYz2-5wSgCcyAADcafico>
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 14:33:05 -0000

On Mon, May 9, 2022 at 1:52 PM John C Klensin <john-ietf@jck.com> wrote:

> Alexa,
>
> Understood.
> Thanks
>    john
>
>
> --On Monday, May 9, 2022 10:31 -0700 Alexa Morris
> <amorris@amsl.com> wrote:
>
> > Hi John,
> >
> >> On May 9, 2022, at 8:19 AM, John C Klensin
> >> <john-ietf@jck.com> wrote:
> >>
> >>
> >>
> >> --On Monday, May 9, 2022 09:59 -0500 Behcet Sarikaya
> >> <sarikaya2012@gmail.com <mailto:sarikaya2012@gmail.com>>
> >> wrote:
> >>
> >>> On Thu, May 5, 2022 at 2:43 PM Ross Finlayson
> >>> <finlayson@live555.com> wrote:
> >>>
> >>>>
> >>>>> 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.
> >>
> >>> 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.  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.
> >
> >
> > You're correct that pre-pandemic the IETF usually contracted
> > with one or two additional local properties. Typically this
> > was done to provide a less expensive alternative to the main
> > IETF venue. However in more recent years we observed that
> > these alternative venues were poorly-utilized and it was
> > decided that the very minimal number of bookings did not
> > justify the substantial amount of administrative effort
> > required, except in those cases where the main room block was
> > either very expensive, or insufficient in size.
> >
> > Happily, the IETF 114 meeting venue (Sheraton Philadelphia
> > Downtown) has offered the IETF a very reasonable rate ($190
> > USD) so we expect that most people will opt to stay there, and
> > accordingly we have a sizable room block.
> >
> > Finally, the hotel room discount that Behcet referred to was
> > unique to Vienna, where the first 400 guest room reservations
> > were at a highly discounted rate. It's highly unlikely that we
> > will see something like that again.
> >
>


Thanks Alexa :).

Behcet

> > Best,
> > Alexa
> >
> >>
> >>   john
> >
>
>
>