Re: Planned changes to registration payments & deadlines

Andrew Sullivan <ajs@anvilwalrusden.com> Wed, 25 April 2018 12:06 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 A3A991243F6 for <ietf@ietfa.amsl.com>; Wed, 25 Apr 2018 05:06:29 -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=XVU2fHLR; dkim=pass (1024-bit key) header.d=yitter.info header.b=eIWfcd/K
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 6jx_Zc-vud9o for <ietf@ietfa.amsl.com>; Wed, 25 Apr 2018 05:06:27 -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 DA311120454 for <ietf@ietf.org>; Wed, 25 Apr 2018 05:06:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 4AEB6BF23E for <ietf@ietf.org>; Wed, 25 Apr 2018 12:06:27 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1524657987; bh=lCGBr/r43fJ52ctmfDg2Yq0iRC8uBvPSM80GErd2noA=; h=Date:From:To:Subject:References:In-Reply-To:From; b=XVU2fHLRdJv6VaBa4Egr2IzRQfFWguxCmJ257yRtve/8p8TznPRB0s2mSOKpGo6F2 peHz3tsq+DmLJwVrvzuz7n6ebAsQmpNxEEycOhp5LUct37uoDJMzDDb5qG8YLg/bA2 oV4k77qer5SDH3Zv06QXJjM1vjxyrF3G5nm7fSNs=
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 QFf12U9W3OaQ for <ietf@ietf.org>; Wed, 25 Apr 2018 12:06:25 +0000 (UTC)
Date: Wed, 25 Apr 2018 08:06:24 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1524657985; bh=lCGBr/r43fJ52ctmfDg2Yq0iRC8uBvPSM80GErd2noA=; h=Date:From:To:Subject:References:In-Reply-To:From; b=eIWfcd/KO+HF+7213Gm3UXwHni5i3yY/WtGgYVgfsv1ZlCluWM1XYNyrWNfuGDev/ yuA71yeR3UpDzpEhw3A43QYFywJpqQD/MTlkdHgEtHpNtTblxSkoAOqqcJWSXjwcQt 8ZUq20PvYfuaJnSELkhkeebIeGkd1J+jnjZ24L60=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Planned changes to registration payments & deadlines
Message-ID: <20180425120624.abei3nltmpzj2hgy@mx4.yitter.info>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <dce584d0-e3ae-b369-314c-87a667679fa3@cs.tcd.ie>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jQjpvzFCp0BkqDF6d8-Mvvt5Qno>
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: Wed, 25 Apr 2018 12:06:30 -0000

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.  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

-- 
Andrew Sullivan
ajs@anvilwalrusden.com