Re: Planned changes to registration payments & deadlines

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 24 April 2018 14:13 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 16CB1124235 for <ietf@ietfa.amsl.com>; Tue, 24 Apr 2018 07:13:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=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=IC1jvggo; dkim=pass (1024-bit key) header.d=yitter.info header.b=YxTSS9xh
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 T2npE3HQXXeK for <ietf@ietfa.amsl.com>; Tue, 24 Apr 2018 07:13:13 -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 B1B53124C27 for <ietf@ietf.org>; Tue, 24 Apr 2018 07:13:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 1079ABF23E for <ietf@ietf.org>; Tue, 24 Apr 2018 14:13:13 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1524579193; bh=VooS23NxNkSGP/VIZPmTZ0FH/jEGYXRMTRl37408Gxg=; h=Date:From:To:Subject:References:In-Reply-To:From; b=IC1jvggo//FulE6jIG/sLJk5isqH29WSL2OpeSk5mYRRixYEj2lzQ4t+UCSV4lwXT wCPebr1UZ+tTXNaYEB7P4Oe6QHm4M+KTVMkPRs1kkIm3ZGWHd8H0eqDIawEvrAGhKH Y6sn/cYVgL7J5RZX9tOeg3e/FNxv7BGmSmRsgaRE=
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 1sbcTx15gMbA for <ietf@ietf.org>; Tue, 24 Apr 2018 14:13:07 +0000 (UTC)
Date: Tue, 24 Apr 2018 10:13:06 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1524579187; bh=VooS23NxNkSGP/VIZPmTZ0FH/jEGYXRMTRl37408Gxg=; h=Date:From:To:Subject:References:In-Reply-To:From; b=YxTSS9xhMQfSFiun2GvAA3D/XmCVO4xumr2ZIkh/WKlmhN+yThp/W52P+aM9gN6/B Ffo3R5oi/OiC2UHIMARXedj+zCjoVqaQT8plFUi9lIxITauLrbEN9b5OlkXyvAfUoD mzl7kTHcJki/1Ks6PWxtIdVspmv3jYtfKLvEbFcM=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Planned changes to registration payments & deadlines
Message-ID: <20180424141306.zb5kefcac3b633az@mx4.yitter.info>
References: <20180419174627.2krzjbxgx25s5wxz@mx4.yitter.info> <20180423162016.elmju5r6qcb6xcbt@anvilwalrusden.com> <6E58094ECC8D8344914996DAD28F1CCD8779EC@DGGEMM506-MBX.china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD8779EC@DGGEMM506-MBX.china.huawei.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FkY0aC7GGDmHnp4_VwS6s28Rjt0>
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: Tue, 24 Apr 2018 14:13:20 -0000

Hi,

On Tue, Apr 24, 2018 at 06:00:47AM +0000, Roni Even (A) wrote:
> 
> I do not understand why you need to pay when you register. The fee toady depends on when you pay and not when you register.
> 

This is an issue that Stephen also raised, and I want to make this a
little clearer: we are not going to lose all the information people
enter if the payment step happens later.  The work flow may be a
little different than today, but it will be possible to enter all the
registration data and then come back later to complete registration by
paying.

What is different is in how we count this.  Today, we have "unpaid
registrations" and "paid registrations", and when you have filled in
your registration data you are "registered" (and listed as registered,
on the public list of attendees if you so wish).  That will stop.
>From the point of view of the meeting system, anyone who is not paid
is just not registered.

Does that make this clearer?

Thanks for the comment,

A
-- 
Andrew Sullivan
ajs@anvilwalrusden.com