IETF Logo Mail Archive

Re: Planned changes to registration payments & deadlines

Andrew Sullivan <ajs@anvilwalrusden.com> Wed, 25 April 2018 01:38 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 344EC12DA04 for <ietf@ietfa.amsl.com>; Tue, 24 Apr 2018 18:38:55 -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=eIYdT5Ta; dkim=pass (1024-bit key) header.d=yitter.info header.b=bFSGWXgC
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 eUtRbNZxKCBD for <ietf@ietfa.amsl.com>; Tue, 24 Apr 2018 18:38:53 -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 AF7EA126D85 for <ietf@ietf.org>; Tue, 24 Apr 2018 18:38:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id EB9AFBF23F; Wed, 25 Apr 2018 01:38:22 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1524620302; bh=tIxZJM+JN8rRr9JPXb3zamW0VeyrOIfrSGBruHExDb8=; h=From:To:Date:In-Reply-To:References:Subject:From; b=eIYdT5TadFZmRAtL3ZSNb25uzTUJ9jz7GzDc9U3xi7vDGmZ8EuIfEBuW80xm9wrZs IuP0qBDZO7/R7P6wleAnOVFeAZH0QvvFOxHDaETeyEmT/iIYKFkObynyQj07Uqu46m 4/Pl57d1ar4luo3bMFJoP/msoB6Qkh7au6pAnCxA=
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 Netj_z38NPTT; Wed, 25 Apr 2018 01:38:21 +0000 (UTC)
From: Andrew Sullivan <ajs@anvilwalrusden.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1524620301; bh=tIxZJM+JN8rRr9JPXb3zamW0VeyrOIfrSGBruHExDb8=; h=From:To:Date:In-Reply-To:References:Subject:From; b=bFSGWXgCzPxshQhotqYnZGyzmppIsuGYQwCDGqoo25yDzHyv3KGFwy2Q6UfeRKhWQ bAIoYG+9BirNeSpCxyAj6LuQ+xyybBQnD+gWval9x/jp1mux+33AtN0CDOzhf1Lln5 EiDtWCU8WUZhCFEByTlo6vJ+hFhculTYuk+aIc8E=
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, <ietf@ietf.org>
Date: Tue, 24 Apr 2018 21:38:19 -0400
Message-ID: <162fa738af8.2772.55b9c0b96417b0a70c4dcaded0d2e1c6@anvilwalrusden.com>
In-Reply-To: <453ab53b-6368-1397-db5b-7f8988a413b1@gmail.com>
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>
Subject: Re: Planned changes to registration payments & deadlines
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4-H-A0RZTlxR_x_FE3U3IaW5ogc>
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 01:38:55 -0000

Hi,

No, a registration number will not be available under the plan, because the 
prospective registrant won't actually be registered before payment. Payment 
will be a necessary condition for registration. Without paying, one won't 
be registered.

I hope that's clearer.

Best regards,

A

--
Please excuse my clumbsy thums
----------
On April 24, 2018 19:30:52 Brian E Carpenter <brian.e.carpenter@gmail.com> 
wrote:

On 25/04/2018 04:56, Andrew Sullivan wrote:
...
There is one assumption in your question, however, that is worth
emphasising: you can't get a social ticket until you're registered,
and under our plan "registration" means "paid registration".  This
also applies to companion registrations to the meeting, &c &c.  There
will simply be no such status as "registered but not paid", even if
registration may take many weeks so that payment can be processed
separately from sign-up.

Digging a bit deeper into that, there are other cases where you need
a registration number well before the meeting - registering for
certain types of side-meeting, for example. So will the registration
*number* be available while payment is pending? (An implementation
detail, I know, but probably better debugged in advance.)

Brian

v2.8.7 | Report a Bug | By Email