Re: Planned changes to registration payments & deadlines

Andrew Sullivan <ajs@anvilwalrusden.com> Mon, 23 April 2018 22:07 UTC

Return-Path: <ajs@anvilwalrusden.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 72D8712DA04 for <ietf@ietfa.amsl.com>; Mon, 23 Apr 2018 15:07:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=kIKS8jFb; dkim=pass (1024-bit key) header.d=yitter.info header.b=WKr8gxn8
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 LUZyL_El0rnK for <ietf@ietfa.amsl.com>; Mon, 23 Apr 2018 15:07:33 -0700 (PDT)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26AB212E89B for <ietf@ietf.org>; Mon, 23 Apr 2018 15:07:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 72293BECAC for <ietf@ietf.org>; Mon, 23 Apr 2018 22:06:55 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1524521215; bh=s/pvb4AQH+Ad4clXWt1L85tggENVJZzARVk1DtXqHGw=; h=Date:From:To:Subject:References:In-Reply-To:From; b=kIKS8jFbGRl2cyZUxpe+3LOlmyStGMVdydpTPUD7oXuT3LjasDxz2cVObBqdbkt8J HFkMudtuAh2UWU1qTEttiOsXrEjZB7fXqtjrYIlnGdvBzur1EtWu/24F13mi19+a1/ 8y1Gz+o6O25ZX/SYQMbadFqSTFWgoehut9L09OmM=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LD2Q_PqSCtWn for <ietf@ietf.org>; Mon, 23 Apr 2018 22:06:54 +0000 (UTC)
Date: Mon, 23 Apr 2018 18:06:51 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1524521214; bh=s/pvb4AQH+Ad4clXWt1L85tggENVJZzARVk1DtXqHGw=; h=Date:From:To:Subject:References:In-Reply-To:From; b=WKr8gxn8WAdTQ9qHeiXITU/QdT2w1Jo44op5Zt4G+gP1RpjLgefuSuzKT25BlR8Mt aHCQxxhAvSHmHJFRg7zgsgmkLPSxJTTLrkTBzmDgAmXL8i+JTplrG8vs41ps2v7Wqx wbndU5ou/aYUocyd/jkw+dZjNDsm3pp/x9ZsIw7o=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Planned changes to registration payments & deadlines
Message-ID: <20180423220651.t5f6emixyoo3sp6c@mx4.yitter.info>
References: <20180419174627.2krzjbxgx25s5wxz@mx4.yitter.info> <20180423162016.elmju5r6qcb6xcbt@anvilwalrusden.com> <49c1c20d-000c-9664-d998-cace737704d8@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <49c1c20d-000c-9664-d998-cace737704d8@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TbwZM4Qrd2jE5_1wqh7b8deS2EE>
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: Mon, 23 Apr 2018 22:07:38 -0000

Hi Brian,

Thanks for the comments.

On Tue, Apr 24, 2018 at 08:59:28AM +1200, Brian E Carpenter wrote:

> 1. "Payment is due at registration."
> 
> 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? 

> 2. "Early Bird 700 7 weeks before"
> 
> Given lead times many people experience for travel approvals,
> 7 weeks *really* seems like a lot, however normal it may be for
> other events. In fact, for travel planning the current IETF
> policy is very user-friendly. Could we compromise at 4 weeks?

I don't see how.  "Early" ought to mean, well, "early".  7 weeks is
early.  4 weeks is not; that's standard, and should pay the standard
fee.  We are warning people about this plan well in advance, so people
who need to get travel approval to get the early bird rate for IETF
103 may start their approvals process now (or, in a couple weeks, if
they really want to wait until the final details are worked out).  But
I don't see how it is even remotely possible to describe "4 weeks in
advance of something" as "early".

Best regards,

A


-- 
Andrew Sullivan
ajs@anvilwalrusden.com