Re: Registration open for IETF 114

Behcet Sarikaya <sarikaya2012@gmail.com> Mon, 09 May 2022 14:59 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 E8244C159A1D for <ietf@ietfa.amsl.com>; Mon, 9 May 2022 07:59:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level:
X-Spam-Status: No, score=-1.847 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=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 iJgrL16T1wNN for <ietf@ietfa.amsl.com>; Mon, 9 May 2022 07:59:44 -0700 (PDT)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (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 BE4DAC15E6C2 for <ietf@ietf.org>; Mon, 9 May 2022 07:59:44 -0700 (PDT)
Received: by mail-lj1-x22c.google.com with SMTP id q130so17374120ljb.5 for <ietf@ietf.org>; Mon, 09 May 2022 07:59:44 -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=NDbg6zETIeJhpwuEOC1sY4LEFQhbyANutVfE4aY2imc=; b=dRZiVHk1IECKRECVZGtHgChXuBjCV2XizpvC7JELzmY9tEtdTkCKlm9MGyfVkbjQLE gUUqSL9D+y34OTv/vzyLEx/+3d/+mlwLffuAdmtCwRS+RTfAfqnn2yHI0HD9nLP+nw3F E5viboMfH6yebLR4BbDtCD5pQ9BeJGhcF7wvAsP2YNR366ptINOZkfLJd5ki4/zmCG3Z 4fcmPydkAOwj06XpKNUhcrZ1NtfUVGz8vH/qQVerxXPDqtmP2yaHLsyZq80ktDKyNwgY e/bT4r+qAEgg1SqQm9oXiZVrYYqKtPDl/59xAG3Si1YJHNtXk9kjyETnc5U057WxrlDp YgAQ==
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=NDbg6zETIeJhpwuEOC1sY4LEFQhbyANutVfE4aY2imc=; b=0hJ/HrDCPvqSU8/bWXaSvAKIRg4RBTiop2VCNHl/s83LvwepCb7Fxqjm98lThHF+Hf UuYevTrH7cPGVMYUgzUZp67n0mNr+YrWkaqJQTYyrhA45feHIQenwmLhGQJMW5sABNCE 4ddUrqKJHqvXkSYtJ/qWm1SLiW+NoKckNcTJFfGo41yFKJMse+IVby9HUlLIMMVPsRco B2kmPgF/IDbh+jSeNzWWh5YmdfH3uPjTtcKJnhbVaj4kKobcyF+ZLVbIXKvtjuJLH5A1 i5Im1QHqkVles7FS4VNN3iHy+VG8IgjmrUdfQPlwhC25hpg4gR9gTW6OuaMAl5joKyVI dcPQ==
X-Gm-Message-State: AOAM530Tf/BbH7Ye1DpVv6N1W7Zvf5SypVixo71ZakUvMB1kkc93a/hj cEb+mHJ24Oca5DgxlfzghbzqoGZgpxsvExU4UY4sinPTGPU=
X-Google-Smtp-Source: ABdhPJziscPFpnn5VqurDRpQ1+HNwXnIYBBn/l+fwHl2PGJEckwI6URHVxyD9kZxPVcWQueGzlI0KOKkdKZZjKXmTvE=
X-Received: by 2002:a05:651c:1792:b0:235:1df3:7b8e with SMTP id bn18-20020a05651c179200b002351df37b8emr10808619ljb.464.1652108382496; Mon, 09 May 2022 07:59:42 -0700 (PDT)
MIME-Version: 1.0
References: <F6744CFE-D61F-41F1-9D95-8F322EDB6E0F@ietf.org> <F9CEB983-06B6-42E9-BAAA-D8F829CA32B3@live555.com>
In-Reply-To: <F9CEB983-06B6-42E9-BAAA-D8F829CA32B3@live555.com>
Reply-To: sarikaya@ieee.org
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Mon, 09 May 2022 09:59:31 -0500
Message-ID: <CAC8QAccwyROv188W_GqBVpU4TgwZ9ESSg96P_HMc50Wva6LOsg@mail.gmail.com>
Subject: Re: Registration open for IETF 114
To: Ross Finlayson <finlayson@live555.com>
Cc: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000044eac105de95758e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9LkVQqNVsFPJM2zAr9ROQ4bBxMM>
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 14:59:47 -0000

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.

Behcet

>         Ross.
>
>