Re: Planned changes to registration payments & deadlines
Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 26 April 2018 05:12 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 D06B9124D37 for <ietf@ietfa.amsl.com>; Wed, 25 Apr 2018 22:12:41 -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 dJqZgUTT6Ycm for <ietf@ietfa.amsl.com>; Wed, 25 Apr 2018 22:12:40 -0700 (PDT)
Received: from mail-pg0-x233.google.com (mail-pg0-x233.google.com [IPv6:2607:f8b0:400e:c05::233]) (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 022A2120725 for <ietf@ietf.org>; Wed, 25 Apr 2018 22:12:40 -0700 (PDT)
Received: by mail-pg0-x233.google.com with SMTP id i29so13491050pgn.12 for <ietf@ietf.org>; Wed, 25 Apr 2018 22:12:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=pOgoPFLLKMKnC7C3HAW/aEg2SQ39VZC2kSUP3DMzsG8=; b=C7smjeg25pcH8049i1mExGoXXQPSxyslJgXDIBfwUKbbKn4NFN6k99kPU5x9yYNFMK lnuJ0koyObHKHM2WQldNYIF8nB0qBhBUZ1a2EimeM2u6oeQacAc54n3CA2+WS2QRC0S7 enU/JCazHmhUKWCYHrspeabuX9oejXb7wVz3HbOShQHu7qURUiC6weJq8KWU1gEXwllA 8McIzKHnPAHtKlSIhjqKrqi23EZ5OhxWVLdp/Obla8NEUynawAdLwfsqvm1dSReimXia OlMGW2FyGd1cdrl8DjPk59K6/uLwzW+mOYzlMjrLDbhE9JWEs+3eRoOiTxF7P3UTb0Ru FvDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=pOgoPFLLKMKnC7C3HAW/aEg2SQ39VZC2kSUP3DMzsG8=; b=DXiK7z4Ll/XyceaRv0bjVIQdwn0M4OTYazZwBGncnjwCpehuDZHfo9gtBxgO2utRTE hLBcVrPJk+GAyCA6pBfLGjfBaVNCJeJudkp0rezk+AM832OjtGgIOjNPGDP4GicCwFgH 2CEeX1yndDCpmz031KZLu4QBH8PtAuswPrp1V5+Syaq2ccnyfvqPUm3PUm1SgOFpzISR iictqptuz4nGleRcNxBK4Fmwkhe4UtS4O/7RdOvMJaBUtYU2zafw40FLJJRy5WelxnoB KOjXlRpvGRv9ohS4Fs5xsSVqHnbJiOtbm60ae//iapdkX0Qdx12Kkv/RFc/BRMrp4J3X RcjQ==
X-Gm-Message-State: ALQs6tAJAAcj7is5SjYS3fCeVVimdLRiKgr6wdiXuPiRtfkQ2dEa82w/ Q53mXczTnWDqDvyzjxiQ0lmw8w==
X-Google-Smtp-Source: AIpwx49PQbLCHtXHrF7IrhmU8OD+MDHlnymU7EkxWtTdRQwVHkYd32CU7BqrN2dyiCBWoB2BTwhw5Q==
X-Received: by 10.99.132.198 with SMTP id k189mr25259400pgd.298.1524719559233; Wed, 25 Apr 2018 22:12:39 -0700 (PDT)
Received: from [192.168.178.26] ([118.149.104.73]) by smtp.gmail.com with ESMTPSA id m185sm35880986pfm.118.2018.04.25.22.12.36 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 25 Apr 2018 22:12:38 -0700 (PDT)
Sender: Brian Carpenter <becarpenter46@gmail.com>
Subject: Re: Planned changes to registration payments & deadlines
To: ietf@ietf.org
References: <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> <dce584d0-e3ae-b369-314c-87a667679fa3@cs.tcd.ie> <20180425120624.abei3nltmpzj2hgy@mx4.yitter.info> <bb921f4d-138d-1e88-bacf-3bca2601e626@gmail.com> <20180426043508.nr6tgmosynwo7djc@mx4.yitter.info>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <d6403509-7e2f-e17f-3e8a-e4505add995f@gmail.com>
Date: Thu, 26 Apr 2018 17:12: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: <20180426043508.nr6tgmosynwo7djc@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/0-NxlyGOQeThFqxilWHTdoCYmUo>
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: Thu, 26 Apr 2018 05:12:42 -0000
On 26/04/2018 16:35, Andrew Sullivan wrote: > Hi, > > On Thu, Apr 26, 2018 at 03:57:50PM +1200, Brian E Carpenter wrote: >> Let me just adjust your text to make it more precise: >> >> "If you could register for ancillary things without having *paid* for the >> meeting, then if you never *pay* we'd need to have tracked those >> other things and be able to undo them." > > That's not "more precise"; that's just a different meaning of > "registered." > > I confess that I have never understood the IETF meaning of > "registered", in which one could be in this half-state of registered > for the meeting but not paid. I've never been to any other > paid-attendance thing where there was any way to be publicly > registered without paying first. But it is true, as I think we have > said all along in this discussion, that we are changing the meaning of > "registered" to mean "paid registration". The plan does not > anticipate any other meaning of "registration". I can't be categorical, but I feel I've been to other meetings with pre-registration prior to payment. Too many meetings over too many years to be specific :-(. >> Correct, and I fully understand that. But a side effect of the change >> is that anybody currently using the registration system as a convenience >> for arranging a side event can effectively no longer do so until the >> 7 week deadline, because people *will* pay at the last possible moment >> to minimise their credit hit. > > I guess I don't understand the complaint. To the same extent that the > IETF has a hard time predicting whether people will really show up > without knowing whether they've paid, anyone else would not know > whether the prospective attendee was really coming. One example is the WG Chairs lunch. Unless it's changed recently, you have to sign up using your reg #. Currently, that's tied to an intention to attend; in future, it will be tied to having paid. Again, I'm not saying this is a big problem. I'm saying: it's a change caused by the primary change. I think there may be other side-effects of the published list of attendees too. Such as "I see that Fred Flintstone is planning to be there, so I think I'll go too." We just don't know, of course. Brian > And presumably > the entire list of IETF attendees wouldn't be going to the side event, > so the list is too broad anyway. Finally, the list is collected for > the purposes of registration for the IETF meeting and not some other > event, so actually using the data for some other purpose might be in > contravention of EU laws (alas, I am not a lawyer, so I can't say for > certain). It seems such a side event would be better off maintaining > an independent list of prospective attendees. > >> won't get attendance mainly settled until the last 2 weeks. They will >> see two large spikes in registration corresponding to the two payment >> deadlines. (So will IASA, of course.) > > Maybe we (and it's not _IASA_, but the IETF, of course) will see that > and maybe we will not. It is hard to know without trying it. > > Best regards, > > A >
- Planned changes to registration payments & deadli… Andrew Sullivan
- Re: Planned changes to registration payments & de… Stephen Farrell
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Michael Richardson
- Re: Planned changes to registration payments & de… Brian E Carpenter
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Brian E Carpenter
- Re: Planned changes to registration payments & de… Michael Richardson
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… John C Klensin
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Ted Lemon
- Re: Planned changes to registration payments & de… Brian E Carpenter
- Re: Planned changes to registration payments & de… Ted Lemon
- Re: Planned changes to registration payments & de… Eric Rescorla
- Re: Planned changes to registration payments & de… John C Klensin
- Re: Planned changes to registration payments & de… Adam Roach
- RE: Planned changes to registration payments & de… Roni Even (A)
- Re: Planned changes to registration payments & de… Spencer Dawkins at IETF
- Re: Planned changes to registration payments & de… Stewart Bryant
- Re: Planned changes to registration payments & de… Spencer Dawkins at IETF
- Re: Planned changes to registration payments & de… Joel M. Halpern
- Re: Planned changes to registration payments & de… Joel M. Halpern
- Re: Planned changes to registration payments & de… Ted Lemon
- Re: Planned changes to registration payments & de… Ted Lemon
- Re: Planned changes to registration payments & de… Dhruv Dhody
- Re: Planned changes to registration payments & de… Nick Hilliard
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Matthew Pounsett
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Joel M. Halpern
- Re: Planned changes to registration payments & de… Dhruv Dhody
- Re: Planned changes to registration payments & de… Michael Richardson
- Re: Planned changes to registration payments & de… Jonathan Lennox
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… John Levine
- Re: Planned changes to registration payments & de… Brian E Carpenter
- Re: Planned changes to registration payments & de… Andrew Sullivan
- RE: Planned changes to registration payments & de… Roni Even (A)
- Re: Planned changes to registration payments & de… Stephen Farrell
- Re: Planned changes to registration payments & de… Stewart Bryant
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Yoav Nir
- Re: Planned changes to registration payments & de… Brian E Carpenter
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Brian E Carpenter
- Re: Planned changes to registration payments & de… John C Klensin
- Re: Planned changes to registration payments & de… John C Klensin
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Brian E Carpenter
- Re: Planned changes to registration payments & de… Bob Hinden
- Re: Planned changes to registration payments & de… Vinayak Hegde
- Re: Planned changes to registration payments & de… John R Levine
- Re: Planned changes to registration payments & de… Andrew Sullivan
- Re: Planned changes to registration payments & de… Andrew Sullivan