Re: Planned changes to registration payments & deadlines

Andrew Sullivan <ajs@anvilwalrusden.com> Tue, 24 April 2018 16:56 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 7888612D88C for <ietf@ietfa.amsl.com>; Tue, 24 Apr 2018 09:56:49 -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=eybmwN3g; dkim=pass (1024-bit key) header.d=yitter.info header.b=DavBR7Uy
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 e_I30WiX6ziS for <ietf@ietfa.amsl.com>; Tue, 24 Apr 2018 09:56:47 -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 7676412D7EA for <ietf@ietf.org>; Tue, 24 Apr 2018 09:56:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id 72631BF23E for <ietf@ietf.org>; Tue, 24 Apr 2018 16:56:16 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1524588976; bh=XspVC0P+YIwiiLh+1qwc93IflimgxQXcFxAdb/o4nCA=; h=Date:From:To:Subject:References:In-Reply-To:From; b=eybmwN3gH5WsweBwVzzWzv4H4b+rJne8rHH5YmHw5XgGj2O9aomyA8geiKrmJOP8I u0g2cXERSHwSbd8SJP7/6ARXkISSFL7EY1yPD7r2e35fzFcSTHVZidb4Co12voW1sB FN99jDEGYPYyJddmywndS4FVDxU3h+etpDz0j/pw=
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 YNsqG5ycoq3a for <ietf@ietf.org>; Tue, 24 Apr 2018 16:56:14 +0000 (UTC)
Date: Tue, 24 Apr 2018 12:56:12 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1524588974; bh=XspVC0P+YIwiiLh+1qwc93IflimgxQXcFxAdb/o4nCA=; h=Date:From:To:Subject:References:In-Reply-To:From; b=DavBR7Uy0+uYL0XlSq/RYSS+k7ZgA7s84OOzRCqwhjV/IJmGs+VpNmDTjozkJc0sz WP99qg0zp9zKSPl0Xvxx4yPApCGJHyCj8Y7ZE3zx9PGjDmNRjfT/62Xw19paFhLyYF niHU83zN5HK1lRoaWC6WMqmkT6xtf0kHpMOR/77A=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Planned changes to registration payments & deadlines
Message-ID: <20180424165612.ecmdyay5ftfajfv3@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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <074F424E-F757-41CA-83E1-54BAF741E24C@vidyo.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Y9dABZd8Kjev_OJ1p4JDOx1sC2g>
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:56:49 -0000

Hi,

On Tue, Apr 24, 2018 at 12:33:18PM -0400, Jonathan Lennox wrote:
> 
> 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.
> 

Thanks for this question.  The answer is not perfectly clear, because
there are a few possibilities.  Keep in mind that the social is not
actually operated by the IETF, so some of these details are up to the
host sponsoring the social.  Nevertheless, I can think of three
obvious alternatives:

    1.  The social usually has between 500 and 800 tickets.  It would
    be wildly outside our expectations that 500-800 people registered
    (including payment) for the meeting so far in advance that only
    the early birds could get social tickets.  So maybe do nothing,
    and social tickets are first come, first served.

    2.  Perhaps the social tickets could be released about a month
    before the meeting, meaning that people undertaking standard
    registration would have the same shot as early birds.

    3.  Perhaps some % of the tickets could be available as soon as
    the social is announced, with the (smaller) remainder being
    released close to the meeting, to guarantee that even late
    registrants could have a shot at a social ticket.

We may experiment with different approaches to see what works best.

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.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com