Re: Planned changes to registration payments & deadlines

Andrew Sullivan <ajs@anvilwalrusden.com> Mon, 23 April 2018 17:08 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 E2A7C12D886 for <ietf@ietfa.amsl.com>; Mon, 23 Apr 2018 10:08:06 -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=iS5vpybx; dkim=pass (1024-bit key) header.d=yitter.info header.b=KUI1Iu2d
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 3gOhs6QNIYj5 for <ietf@ietfa.amsl.com>; Mon, 23 Apr 2018 10:08:05 -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 0E5CE12D87A for <ietf@ietf.org>; Mon, 23 Apr 2018 10:08:05 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 429E7BECAC for <ietf@ietf.org>; Mon, 23 Apr 2018 17:08:04 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1524503284; bh=MvYc7tMknF7BGw8RmyzWQHY8MqGyPLt2tgPSXG6cVrk=; h=Date:From:To:Subject:References:In-Reply-To:From; b=iS5vpybxDYhsHoJ7zAraoEsPyh3heF04LNOJS2jaLeSgPnvz5fawyoHQoTrxIvP/t U6euizz+uEc4z8KA4QUmljwcDKyxZFBEIg2TlmLvm3zkooH+aIylF/+ZLwI/vevAIO yocmNfFgKJLhfsgos8ugvnTHV+6tQ25P6nPMpK2o=
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 nknDrUiLgU3d for <ietf@ietf.org>; Mon, 23 Apr 2018 17:08:03 +0000 (UTC)
Date: Mon, 23 Apr 2018 13:08:01 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1524503282; bh=MvYc7tMknF7BGw8RmyzWQHY8MqGyPLt2tgPSXG6cVrk=; h=Date:From:To:Subject:References:In-Reply-To:From; b=KUI1Iu2dLf6gmAPd7CTe6KMGhOzyCT+UGIw8szl9GtRvsXHlORiO1LdJ+6A0LHcq5 9tyfgjjgLTmA3XsucrGHtJWfscZFokh4+IxP8ZzMMF3HX5HFn+lzNzFSvTO4rTLf2y qw8v2LHcQTwJsPUj2VtX6hRRTHTvsv75UgklQZz0=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Planned changes to registration payments & deadlines
Message-ID: <20180423170800.r4g76mfeoxrlvv44@mx4.yitter.info>
References: <20180419174627.2krzjbxgx25s5wxz@mx4.yitter.info> <20180423162016.elmju5r6qcb6xcbt@anvilwalrusden.com> <f85e3003-4742-57ff-be5f-638d88a7ff89@cs.tcd.ie>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <f85e3003-4742-57ff-be5f-638d88a7ff89@cs.tcd.ie>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5ZVdINNILarEUTqZOQhHU3j2fsk>
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 17:08:07 -0000

Hi,

Thanks for the comments.

On Mon, Apr 23, 2018 at 05:42:03PM +0100, Stephen Farrell wrote:

> That makes my life a bit harder. Not sure if it also
> affects others hence cc'ing the list.

We appreciate that it will indeed make certain things harder.

> I usually register early, and make some hotel reservation
> at about the same time. Later, I arrange flights via our
> travel agent, and then generate one purchase order for
> the meeting fee, flights and hotel (I get them to pre-pay
> the room cost). They then do the meeting fee payment etc.
> 
> The above change will force me to do two purchase orders
> which is a pain.

Or else, it will require you to commit to your flight dates earlier,
or else pay a higher fee later, yes.

> I'd ask that the IAOC reconsider requiring payment at
> registration time.

If we do not make this change, then I expect we'll see an
across-the-board fee increase, and I don't think we're keen on that.
 
> I'm also not that keen on the earlier early-bird. It's
> fairly common that I won't know if I want to be present
> for the weekend when the hackathon happens until close
> to the meeting time. If you do move to requiring payment
> at registration time, then that'd make no difference,
> but with the current setup, I usually know enough before
> the current cutoff to book flights at the same time as
> we pay. I'd normally not know that seven weeks before
> the meeting though so that change is also a bit of a pain.

That sounds like you're not actually planning to be an "Early Bird"
registration, then, but a "Standard Bird" or a "Late Bird".  I think
what you're really arguing is that it would be bad to face an increase
in registration fees if you decide late about your registration.  But
that increase is indeed exactly what is contemplated here.  "Early
registration" to the meeting is a commitment that you're coming to it,
no matter what.  Otherwise, use a standard registration.

> bunch of others who do similar things, then I hope that
> you take that into account and don't make many lives a
> bit harder:-)

Some lives have to get harder: we can't afford to run the meeting the
way we do now, so something needs to change.  One way to change is to
make "early" mean, well, "early".  So that's what we are proposing.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com