Re: Planned changes to registration payments & deadlines

Matthew Pounsett <matt@conundrum.com> Tue, 24 April 2018 14:28 UTC

Return-Path: <matt@conundrum.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 2DD67128D2E for <ietf@ietfa.amsl.com>; Tue, 24 Apr 2018 07:28:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=conundrum-com.20150623.gappssmtp.com
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 HTRAk3U8UZtu for <ietf@ietfa.amsl.com>; Tue, 24 Apr 2018 07:28:02 -0700 (PDT)
Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1AB012895E for <ietf@ietf.org>; Tue, 24 Apr 2018 07:28:01 -0700 (PDT)
Received: by mail-it0-x22d.google.com with SMTP id c3-v6so1234839itj.4 for <ietf@ietf.org>; Tue, 24 Apr 2018 07:28:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=conundrum-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=k+xYYBbpKiUt5VOd4f4pbdh13Tam/ZwhBlRovVBlr4Y=; b=uldAFwBI2t8JTm0mM5Q3ySmWSysSVTlRKG8/x0VhK54jFQa+zafJX4bG0ttXlbmXGo EFYbSXChV4wdIUgkWgj49ELJJZUmDrVDq9I/W36eXVA9SH0nDV+xbk2LS5o3yjG4x6YM rpmwCV8xQJWyy7bPH6LuC07vtJafSEUXVrHmwJYo9GNW+uH+c8s8ecPLmAaV5arwNdUy fXpHpBzwBfnFrwNc0rvFOE2WHLIvLbCxXivu0J8FycAKycKJ7fq+C9unSjes1OyaBOMR WoG1pCy/kUwvH314nGPKN+i2goULOny7MUuG0V/PG7ZfIWYUA/K8/oWkIk/hzp7wum34 dlbQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=k+xYYBbpKiUt5VOd4f4pbdh13Tam/ZwhBlRovVBlr4Y=; b=aOJ09os8hsAJ+QjnLktAeOAYg4hk8oYDH/w94d7RvoX6MbJbK83gefgtSfwoXWUw+V nF+4LIOJrHmlI0vmGK2W4x4TUsZPcvzU5Pn//u0+U4gNUx1h2EehBNtC8lfMjFzjqxZ7 c0FHKlxPS1yoGFo/Y9J6rlDFbBR8Gs78XCnthVHTWw/e7gkRRcqM7KjbuGMI/KVe+rP9 Gj8Fmz4o7fiZykvDzHTozq+BK/NIPe94YFcRx/4+DE5oNoB5qZ21NbrcM37C7IC/kIql Ezioc7XGdmm1qdjRFqFnzcJmYrtoYUrRddN1iGSC+8qdB7ykNhD2lhcz74CVkYxvIOsV 3bAQ==
X-Gm-Message-State: ALQs6tAldUlQ7UjziMIgKYTftUOe2jRP4zeF4ok6isVsRL/tP2hgUwAs Lc46I/+T8fk7CRUC8jwEmEC5MFJT5ZHZDfdM+NqE23ex
X-Google-Smtp-Source: AIpwx4/qncJY+6YSPP/i6tvYggmV6LlUoqFVb0cjsfA83KdMMVpTfW8r2xuCGx2zXTmvtn/HzIhjCnv0RCfutOPI2W8=
X-Received: by 2002:a24:468e:: with SMTP id j136-v6mr19692055itb.151.1524580081067; Tue, 24 Apr 2018 07:28:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a02:942e:0:0:0:0:0 with HTTP; Tue, 24 Apr 2018 07:28:00 -0700 (PDT)
In-Reply-To: <20180423220651.t5f6emixyoo3sp6c@mx4.yitter.info>
References: <20180419174627.2krzjbxgx25s5wxz@mx4.yitter.info> <20180423162016.elmju5r6qcb6xcbt@anvilwalrusden.com> <49c1c20d-000c-9664-d998-cace737704d8@gmail.com> <20180423220651.t5f6emixyoo3sp6c@mx4.yitter.info>
From: Matthew Pounsett <matt@conundrum.com>
Date: Tue, 24 Apr 2018 10:28:00 -0400
Message-ID: <CAAiTEH8Gzt=pBuz0fiB3zAJ18VYQZdz8ytoobpSU0XhPu-sh7g@mail.gmail.com>
Subject: Re: Planned changes to registration payments & deadlines
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Cc: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002a48a0056a98f6db"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eT-HZ1trVRZDQ6z4GKDE7C62Lns>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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, 24 Apr 2018 14:28:04 -0000

On 23 April 2018 at 18:06, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:

> > I can understand that in general, but there are cases where
> > somebody wants to register without being quite sure whether they
> > will attend remotely or in person. So since registration for
> > remote participation presumably remains free, there needs to be
> > a clear option for upgrading from remote to on-site registration,
> > which would then require payment as part of the upgrade.
>
> I don't think I understand what you're saying.  If remote
> participation remains free (there is no current plan about rules for
> remote participation), then if someone decides later in the planning
> cycle to go to the meeting, they pay the meeting fee on that date.
> Are you suggesting that someone who registered early for remote
> participation and later decides to go to the venue should qualify for
> the rate applicable at the time they registered for remote
> participation?
>

I think the suggestion was more about process than payment.  In the past,
it hasn't been clear how to go about changing attendance types, or even if
it was possible.  I had to switch from in-person to remote for a recent
meeting and ended up emailing the secretariat to get someone to do it
manually.  That worked because payment and registration were separate.

I'd like to echo a related idea from the thread:  perhaps we could maintain
the current separate registration and payment processes, but impose the
deadlines on payment?  In other words, it doesn't matter when I register...
whether I'm early-bird or not depends on when I pay.  I think that would
satisfy your requirements as well as keep the status quo process-wise for
anyone who has someone else (an employer, assistant, or whoever) paying on
their behalf.


>  But I don't see how it is even remotely possible to describe "4 weeks in
> advance of something" as "early".
>
> I agree.  I think the proposed schedule is quite reasonable.