Re: Planned changes to registration payments & deadlines

Andrew Sullivan <ajs@anvilwalrusden.com> Wed, 25 April 2018 11:57 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 4DBFC127522 for <ietf@ietfa.amsl.com>; Wed, 25 Apr 2018 04:57:46 -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=IFqRNi/I; dkim=pass (1024-bit key) header.d=yitter.info header.b=mggy95Ex
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 BpyzgKdjTRyw for <ietf@ietfa.amsl.com>; Wed, 25 Apr 2018 04:57:44 -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 570B51243F6 for <ietf@ietf.org>; Wed, 25 Apr 2018 04:57:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id EA0A3BF23E; Wed, 25 Apr 2018 11:57:12 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1524657432; bh=sYgrvwefPnkwSBPrNS+cqyqYd5BclvQfkTJKX0j65rU=; h=Date:From:To:Subject:References:In-Reply-To:From; b=IFqRNi/IRlzBYJmyhDPOACnXc6zVQQHQIDk7cUIx58RGzi0NRSEN5WrunAJEEP+K5 9iZz5m9ZyPD9WR+mO+d0YKxuoVb7FJZezaObDbKESRpjMHizK1cgpGkz7Uz+YOfyNW 7vUZzpm1Nww0JSm39+/L8Dej7kHPMazU7iexNU1I=
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 SHqHsZgSUIWo; Wed, 25 Apr 2018 11:57:11 +0000 (UTC)
Date: Wed, 25 Apr 2018 07:57:10 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1524657431; bh=sYgrvwefPnkwSBPrNS+cqyqYd5BclvQfkTJKX0j65rU=; h=Date:From:To:Subject:References:In-Reply-To:From; b=mggy95ExlBFkdgMoV3Y/OKMtdzNJc44aB3l0DN+RfPeZFRKFoFT06/8jqS06ZoHR7 0Q3HXnWmVDe9/S4+3em5+X7bc/M8HVf6OfsbVp3l+vuF8bknB1NgPLJWQbMLsb7P2J er7nTZX5tSk74OSXqGgVw4DR/zqLTVOjO+bvOP2k=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: "Roni Even (A)" <roni.even@huawei.com>, ietf@ietf.org
Subject: Re: Planned changes to registration payments & deadlines
Message-ID: <20180425115709.o35zxawqqxpxgwqi@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> <6E58094ECC8D8344914996DAD28F1CCD877D6A@DGGEMM506-MBX.china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD877D6A@DGGEMM506-MBX.china.huawei.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AWUoHbLchm8n4Mds2CM5pSTJg1I>
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 11:57:46 -0000

Hi Roni,

On Wed, Apr 25, 2018 at 05:38:58AM +0000, Roni Even (A) wrote:
> Hi,
> I asked this question and got no answer.

My apologies; I thought I answered your question in
https://mailarchive.ietf.org/arch/msg/ietf/FkY0aC7GGDmHnp4_VwS6s28Rjt0/?qid=2b1021a715767b75d6ff36f5db2f96bb.
Let me try again.

> Is there a reason why you need to pay when registering since the fee is based on when you pay not when you register in the current policy.
>
> It complicate the process when the registration which requires your personal information and the payment done by the company are done by two separate persons
> 

We will not require that registration happens in a single step; it
will still be possible to pay separtely from filling in the personal
information required for registration.  But registration is only
complete upon payment.

The reason we need this is not just perversity.  Part of the goal, as
I mentioned in another message yesterday, is predictability.  In the
case of a registration that is not yet paid, we have little in the way
of signal as to whether the person will show up.  Paid registrations
are a stronger indication of who is actually coming to the meeting.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com