Re: Planned changes to registration payments & deadlines

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 24 April 2018 23:30 UTC

Return-Path: <brian.e.carpenter@gmail.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 060B4124BE8 for <ietf@ietfa.amsl.com>; Tue, 24 Apr 2018 16:30:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 LDzOUopzFxBB for <ietf@ietfa.amsl.com>; Tue, 24 Apr 2018 16:30:44 -0700 (PDT)
Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::230]) (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 6145D124319 for <ietf@ietf.org>; Tue, 24 Apr 2018 16:30:44 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id p6so13541104pfn.4 for <ietf@ietf.org>; Tue, 24 Apr 2018 16:30:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=kP6qYe4AOJhET8kwdHauYLEZFQDrv0Br8H//CSML8t8=; b=j44BbtUorv2n7IdRzTeJs698B1SrWmofvyFuBk0HpNXo4zxMH6Cf5SIQv5IDXxXU+n 875o4+7eNgq8h5cIFF6fo1nkWxisb28l6Svr9EZThkE9UuwY7Ep0JkpXfDknM+Yvmnyd 5zP4RzJ38meIP5FY4THSlLsuEsMtlws+PatnvCil3GtPSTBzGQKloI5ziLdd0Ks7YDth 5ERB9UmmCmD+PsgGXYSxqGuyH/JRgYzICIfSIdAM8b696waEV4m1MdbHEZ1styNfUf7o aJX8Iwwf97wyN00Jb9z5f5WpU2kGbzOHxJsGvfQRo3u3tWpSR36lnyWt6WPUFko+P2wl znCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=kP6qYe4AOJhET8kwdHauYLEZFQDrv0Br8H//CSML8t8=; b=PZP8DSSJtrnNyj3pPqU0V4Go75bobf3EI9Yu8mQB78+1CZPrD7DEhBX1wauRu9i0Nq MePP1uGjw3U/HJfsXN/tC/gZfMLDcGq+fJXWRt52iEAoCo/n2XCk1tsyacio2GBtPUu8 p60LCWt6ylfrjBALjDhP6zqyXrAAfIe0CkAp1342iVc+TtcYMH3tcOx9Jy79o8kQ4RXx +zq+/N0EphGkWrKmE6hFIoYbd3Vm1NMjzKlfJuznRsTf10xPR1NVaQh/CsaFqP6LgL0H 7G19d1DJCdgUknIBx1szaHJBHHCBv4v2MMK4SnUvCIm9oaFlXTuJmS1k85IIi26ELQpR K2ig==
X-Gm-Message-State: ALQs6tD3OENCWBtnMCOEsLL2EXQYQGMCuAN98wbx8p1fHfaTDgYUPKRY hnMqSly6u0o7r0llJkiKnGPSCA==
X-Google-Smtp-Source: AIpwx4/ERH7D8dH5/GpM6Pqn6iZZPPgD/Ot91uCWDibO+PzFNCCdmJCNq4C/rI7/ShWdfsxfTHf0AA==
X-Received: by 10.98.160.68 with SMTP id r65mr25073286pfe.235.1524612643324; Tue, 24 Apr 2018 16:30:43 -0700 (PDT)
Received: from [192.168.178.26] ([118.149.104.73]) by smtp.gmail.com with ESMTPSA id z16sm26849783pfn.101.2018.04.24.16.30.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Apr 2018 16:30:41 -0700 (PDT)
Subject: Re: Planned changes to registration payments & deadlines
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
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>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <453ab53b-6368-1397-db5b-7f8988a413b1@gmail.com>
Date: Wed, 25 Apr 2018 11:30:43 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <20180424165612.ecmdyay5ftfajfv3@mx4.yitter.info>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aVYKI6qQbTxQop2oKnVo8W-mRig>
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 23:30:46 -0000

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