Re: Planned changes to registration payments & deadlines

Jonathan Lennox <jonathan@vidyo.com> Tue, 24 April 2018 16:33 UTC

Return-Path: <jonathan@vidyo.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 6932412E8DD for <ietf@ietfa.amsl.com>; Tue, 24 Apr 2018 09:33:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=vidyo-com.20150623.gappssmtp.com
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 YNonHtbNtT3P for <ietf@ietfa.amsl.com>; Tue, 24 Apr 2018 09:33:21 -0700 (PDT)
Received: from mail-qt0-x22a.google.com (mail-qt0-x22a.google.com [IPv6:2607:f8b0:400d:c0d::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8774112702E for <ietf@ietf.org>; Tue, 24 Apr 2018 09:33:21 -0700 (PDT)
Received: by mail-qt0-x22a.google.com with SMTP id w12-v6so22908004qti.4 for <ietf@ietf.org>; Tue, 24 Apr 2018 09:33:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vidyo-com.20150623.gappssmtp.com; s=20150623; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=rTSCZIaxBiiF6vKCfpR7H86cZI91p2aTO3XkZXWKdr8=; b=RS76aq1p8CH8ao+uBhLG0HOAtozQ31LPsi0eNnQ4FZjfXX3625tH/IIQJRXMC7PQDg sjVYVA8MrXd6soUrn8AAnr1rRq3OouClvn68RlB6FWDZTjuTY2EiCKG7mO1vZjkjFwfU apXel8xJVatjl11lvpbt+64V59VmVo7wPnLdDsDRHwCw4jQF05oRIuFR/JJ7tUg/1rN3 EzIj82hrrcaldnjg1aw3c9jChURmUCKEc0sa4bNkWwP+Vb4jDusCLUPqRKgHnhLjrFUk auCOtET+62+h8ksD7U0IlFZh/i9EoHI9ZqJbK+r4JHX4RHuAxGPrnp4G6ADr+gKzxpyo cdRg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=rTSCZIaxBiiF6vKCfpR7H86cZI91p2aTO3XkZXWKdr8=; b=n52fg4khf5ntczTJwzqnemffN8qcMLHJbwLX/962jAjmBoHK+QnLmj5BTy+gbiYoSv V2m62pY6+xfkGhk97QFfcA7qMeX+thWfjPsaVZCNlnhWXqNhBAe/nLOWZJ/DQqBn1FA3 mJ453VPWi4NPQWdr5PMR709yORmmar31f4rhjWS878+CNS30T8vBjxWrZlXU1hj5+Pie +8TpzGuAviparrMF2GJ0P2GziToDn2+ELnfjoBPXGxu+0kU6iRDQtKXwb8dFhgByCr+z W8qYpyA9T/CDmaxST9kM5O9gxNy5ukcFWR+hEuAxRPcx0/x9UOFrB1wLtTfzdc1YT4k+ Cy+Q==
X-Gm-Message-State: ALQs6tAnUlytI1pS3NuTJgTu9T1zT4UqQJ1CIJa72/JryOajhPPUnIBF K3fm/rZZ9yewjnDRrYT3KgFFp8RO2TU=
X-Google-Smtp-Source: AIpwx49xY8sjtZB6GibIg9I9Ui66cKHGIIZIVwSjBI0x4bDqhbwMvE/8O+lU5m4NN9vjU9UoeKFKUg==
X-Received: by 2002:ac8:35b0:: with SMTP id k45-v6mr27221731qtb.81.1524587600051; Tue, 24 Apr 2018 09:33:20 -0700 (PDT)
Received: from [172.16.2.142] ([160.79.219.114]) by smtp.gmail.com with ESMTPSA id m59-v6sm2402398qte.8.2018.04.24.09.33.18 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Apr 2018 09:33:19 -0700 (PDT)
From: Jonathan Lennox <jonathan@vidyo.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Subject: Re: Planned changes to registration payments & deadlines
Date: Tue, 24 Apr 2018 12:33:18 -0400
References: <20180419174627.2krzjbxgx25s5wxz@mx4.yitter.info> <20180423162016.elmju5r6qcb6xcbt@anvilwalrusden.com> <6E58094ECC8D8344914996DAD28F1CCD8779EC@DGGEMM506-MBX.china.huawei.com> <20180424141306.zb5kefcac3b633az@mx4.yitter.info>
To: ietf@ietf.org
In-Reply-To: <20180424141306.zb5kefcac3b633az@mx4.yitter.info>
Message-Id: <074F424E-F757-41CA-83E1-54BAF741E24C@vidyo.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FuB4koAns-EF8Y5zmRJCc7y-VLk>
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 16:33:23 -0000

> On Apr 24, 2018, at 10:13 AM, Andrew Sullivan <ajs@anvilwalrusden.com> wrote:
> 
> 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?

At what point will it be possible to buy tickets for the social event?  Because the social sells out so quickly, I regularly register as soon as the social is announced, so I can buy a ticket; but I delay paying the registration fee until a later credit card cycle, so I can get my travel reimbursement before my credit card bill is due.