Re: Planned changes to registration payments & deadlines

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 26 April 2018 03:57 UTC

Return-Path: <brian.e.carpenter@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 523BE12DA04 for <ietf@ietfa.amsl.com>; Wed, 25 Apr 2018 20:57:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UGqwoDZlEAcb for <ietf@ietfa.amsl.com>; Wed, 25 Apr 2018 20:57:47 -0700 (PDT)
Received: from mail-pg0-x229.google.com (mail-pg0-x229.google.com [IPv6:2607:f8b0:400e:c05::229]) (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 7E1DC1241F3 for <ietf@ietf.org>; Wed, 25 Apr 2018 20:57:47 -0700 (PDT)
Received: by mail-pg0-x229.google.com with SMTP id i194so14876730pgd.0 for <ietf@ietf.org>; Wed, 25 Apr 2018 20:57:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=fqbsSmHM/NPB4DiM7JX2po81r1h69p1lb3K+t02SOQc=; b=a8ymL9cULvttMaR8UaNtT4ZW8daQBfhHHB0LCdGS/AzbLOe1Z8BvNbVjXo5uEPMkMr dxZ1CwrLiLesw7mIrXo/bAu222QtEU+1o1p0/xbC4EKMZVrtMQuT3Dr0br/ClMo9uTaz ohj84X1fA5rN7lhTCNwmlcghJTXFLQq1+kQ9qDTs2G6MKdn1t1mEqL3XyqqKR6PA9OGY A3KB3dEUs6yZQ+Rg2gmpTTmFCMbaZ3ceCkFZu5MLFBA+yqY6wtIxvzr+Bsd2ACwJarCd kK55MLfGpMHabyExDEKta6+pfRQVVdtOFfHNhgOwcSC6ttiUGrFqZ4Bbc7EY9gr54oBm gerQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=fqbsSmHM/NPB4DiM7JX2po81r1h69p1lb3K+t02SOQc=; b=kStPwB/JiSw27PY928Uqtct0zndJSVE852EMOizbdb1dz9ophoy7u1ZRgHVuZTP340 49/Tpbw+flC+k2B6nzXmeXD0AntGwIETNJbvL/cP7ZHak48TV6xe4cYRVE0i8hrxUvwY Vy8PKYxeCBFgapKbyc8jq2W80kcrqkDPDM2gCWGsiosHItZdCJlAmTUDNTov7i8u5blA ema5BQHuxHVBrpBSHiEX097K463q0OmrBKati37S+2KMvGqytIWqpDceHDDETJpNaikj 3VFgCgYDk6mV4lprsu73Eh9dCwZdrYIiiZg1261+iQ1tUx900eqkiGQtecvq6CpZrQNA m1jw==
X-Gm-Message-State: ALQs6tCdYXIYriEruPF5L5yDfF1ySjBVXnT/q4Zdfc5C7FYPdB8w5eCb VvqFpDr28axHEIJaB+8ppMxFPw==
X-Google-Smtp-Source: AIpwx4+KsQLVMJZjEz3C+cp5dmOoZvHuHGkDKRFhCmceWd7oMaMbqb0gKkUMIpCW23Q7p5LCb9pEGg==
X-Received: by 10.101.82.194 with SMTP id z2mr26306640pgp.69.1524715066683; Wed, 25 Apr 2018 20:57:46 -0700 (PDT)
Received: from [192.168.178.26] ([118.149.104.73]) by smtp.gmail.com with ESMTPSA id g21sm31001725pfi.143.2018.04.25.20.57.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 25 Apr 2018 20:57:46 -0700 (PDT)
Sender: Brian Carpenter <becarpenter46@gmail.com>
Subject: Re: Planned changes to registration payments & deadlines
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
References: <20180419174627.2krzjbxgx25s5wxz@mx4.yitter.info> <20180423162016.elmju5r6qcb6xcbt@anvilwalrusden.com> <6E58094ECC8D8344914996DAD28F1CCD8779EC@DGGEMM506-MBX.china.huawei.com> <20180424141306.zb5kefcac3b633az@mx4.yitter.info> <074F424E-F757-41CA-83E1-54BAF741E24C@vidyo.com> <20180424165612.ecmdyay5ftfajfv3@mx4.yitter.info> <453ab53b-6368-1397-db5b-7f8988a413b1@gmail.com> <162fa738af8.2772.55b9c0b96417b0a70c4dcaded0d2e1c6@anvilwalrusden.com> <dce584d0-e3ae-b369-314c-87a667679fa3@cs.tcd.ie> <20180425120624.abei3nltmpzj2hgy@mx4.yitter.info>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <bb921f4d-138d-1e88-bacf-3bca2601e626@gmail.com>
Date: Thu, 26 Apr 2018 15:57:50 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <20180425120624.abei3nltmpzj2hgy@mx4.yitter.info>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zDpxr0oWzAwIJkZhY6UEjKKApmc>
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: Thu, 26 Apr 2018 03:57:49 -0000

Andrew,

On 26/04/2018 00:06, Andrew Sullivan wrote:
> Hi,
> 
> On Wed, Apr 25, 2018 at 08:25:15AM +0100, Stephen Farrell wrote:
> 
>> FWIW, I think that's another bit of a bad plan - I see no reason why
>> the ability to buy a social ticket or not, or the ability to register
>> a companion or not, would affect meeting income.
> 
> It affects expenses.  If you are not registered (i.e. if you didn't
> pay yet) then we have no evidence you're going to come.  If you could
> register for ancillary things without having registered for the
> meeting, then if you never register we'd need to have tracked those
> other things and be able to undo them.  

Let me just adjust your text to make it more precise:

"If you could register for ancillary things without having *paid* for the
meeting, then if you never *pay* we'd need to have tracked those
other things and be able to undo them."

Correct, and I fully understand that. But a side effect of the change
is that anybody currently using the registration system as a convenience
for arranging a side event can effectively no longer do so until the
7 week deadline, because people *will* pay at the last possible moment
to minimise their credit hit. And people who don't make the 7 week deadline
will then delay until the 2 week deadline. So the side event organiser
won't get attendance mainly settled until the last 2 weeks. They will
see two large spikes in registration corresponding to the two payment
deadlines. (So will IASA, of course.)

I'm not saying that's a disaster. But it is a change not mentioned in
your initial posting.

    Brian

> The way that is handled now
> is, "Not well," so the existing tooling and processes are not really a
> consideration.
> 
>>
>> PS: I realise my workflow may be a bit of a corner-case, but I'm
>> starting to regret that the IAOC didn't just bump the meeting fee
>> and leave it at that - another US$100 or something on the fee could
>> even work out cheaper for me compared to the time spent dealing more
>> with my local bureaucrats... and for them having to deal more with me
>> too of course;-)
>>
> 
> If that's the case, why don't you stick with your current workflow
> using the later rate?  It seems to me that you could achieve your goal
> simply by paying more money, no?
> 
> Best regards,
> 
> A
>