RE: Planned changes to registration payments & deadlines

"Roni Even (A)" <roni.even@huawei.com> Wed, 25 April 2018 05:39 UTC

Return-Path: <roni.even@huawei.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 DE703126FB3 for <ietf@ietfa.amsl.com>; Tue, 24 Apr 2018 22:39:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 Fo94xgzByusy for <ietf@ietfa.amsl.com>; Tue, 24 Apr 2018 22:39:08 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 254D3126B7E for <ietf@ietf.org>; Tue, 24 Apr 2018 22:39:08 -0700 (PDT)
Received: from lhreml703-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 74722E7F87907 for <ietf@ietf.org>; Wed, 25 Apr 2018 06:39:04 +0100 (IST)
Received: from DGGEMM403-HUB.china.huawei.com (10.3.20.211) by lhreml703-cah.china.huawei.com (10.201.108.44) with Microsoft SMTP Server (TLS) id 14.3.382.0; Wed, 25 Apr 2018 06:39:06 +0100
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.214]) by DGGEMM403-HUB.china.huawei.com ([10.3.20.211]) with mapi id 14.03.0361.001; Wed, 25 Apr 2018 13:38:58 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Planned changes to registration payments & deadlines
Thread-Topic: Planned changes to registration payments & deadlines
Thread-Index: AQHT2x8cJnCUgKm7jkqIBwGYfNMAPqQPauxAgACy4lT//4AkAIAAbjqAgAAjpoCAAMie4A==
Date: Wed, 25 Apr 2018 05:38:58 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD877D6A@DGGEMM506-MBX.china.huawei.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> <162fa738af8.2772.55b9c0b96417b0a70c4dcaded0d2e1c6@anvilwalrusden.com>
In-Reply-To: <162fa738af8.2772.55b9c0b96417b0a70c4dcaded0d2e1c6@anvilwalrusden.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.200.202.72]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/P7UCK8D16wu3DIMDjA_375ezv9k>
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 05:39:10 -0000

Hi,
I asked this question and got no answer.
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

Roni Even

-----Original Message-----
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Andrew Sullivan
Sent: Wednesday, April 25, 2018 4:38 AM
To: Brian E Carpenter; ietf@ietf.org
Subject: Re: Planned changes to registration payments & deadlines

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