Re: Planned changes to registration payments & deadlines

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 26 April 2018 21:02 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 8FB69128954 for <ietf@ietfa.amsl.com>; Thu, 26 Apr 2018 14:02:31 -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 Sbu7xkTKEULE for <ietf@ietfa.amsl.com>; Thu, 26 Apr 2018 14:02:30 -0700 (PDT)
Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::232]) (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 0DFB4126DCA for <ietf@ietf.org>; Thu, 26 Apr 2018 14:02:30 -0700 (PDT)
Received: by mail-pf0-x232.google.com with SMTP id p6so19311270pfn.4 for <ietf@ietf.org>; Thu, 26 Apr 2018 14:02:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=tgOg1ODdN8dWM76KWRB8gLA6m/L8Kt6hPpGK6HTLx38=; b=SYkSQl4IL2QAxMlk0FabDqTwOZg8cS95QdHLZHGH0JtU5d7KpH3E38V8O4zY/GOvit HFdirfqtmIKIb865/MGO3WEIK+NOq3+OiK5te+UaaX/0qhu+F3cpDQYsbEorgcoEHrdB 6MkCYRkzLGa8yzfcC8wEwKCupCVsjVxIAvY0ejAUBebSuVlZ3ycmVKUnWU7ljMKATmBe 63V74XTCVXN3dLrfAq0eXYWg5GbO51Ot6qbMBEHU6jT1C4nr6XyC2XHttNatDZCg1xYD dMwdEAG+fAkH4v4IM6QR/V+p6zwGyls01+cDVPbRWs0H7lHoKKQpK8K6cb5bdVzmFU05 Mipw==
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:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=tgOg1ODdN8dWM76KWRB8gLA6m/L8Kt6hPpGK6HTLx38=; b=f5NPnoBdXWUOH0ahlKaTsYkBjysznzxCuHw52XC+B859ku2NBQpahoxIfl4T5pZWV0 okNLcUqyrOm4k4yjf77ODjtlx+49FCZYbuDHbiK4clgaxQQXtwovtGgCgEtjinf+Zqb1 V+fSJb1guot5PAM8Ss7m8aJJmR0ETirE5IxRVD8hz2VSJzyL2V3th+dv4CHd2IDMbktw CqCpi+wwBq1sOtinBFPWxEAtmizfcch5UaucdONhljzT1BCGkbOQWSomzsR4APgmJi71 l9uRNzdovoH77k66jrhlPW4ekiOvfKsWCMfGo7fcicdxSxGRzBCEaXwk6k8A4EyPO2Dy EwKQ==
X-Gm-Message-State: ALQs6tApaz0pg1DYOTj9+dOgzA2ZpccZovek1HUa4xmJshzW1HEfyE33 a2pvIq7BYixNsnlWO2WswydJTw==
X-Google-Smtp-Source: AIpwx4+NXItJBMgbsWzwnRIIYfbCFSn0SPXWxE7pMYe+Wu8kn8k7gUan/7F4wTR/y5H3qBUTUOqbkQ==
X-Received: by 10.98.178.4 with SMTP id x4mr33044353pfe.21.1524776549302; Thu, 26 Apr 2018 14:02:29 -0700 (PDT)
Received: from [192.168.178.26] ([118.149.104.73]) by smtp.gmail.com with ESMTPSA id s20sm28678750pgv.14.2018.04.26.14.02.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 Apr 2018 14:02:28 -0700 (PDT)
Sender: Brian Carpenter <becarpenter46@gmail.com>
Subject: Re: Planned changes to registration payments & deadlines
To: John C Klensin <john-ietf@jck.com>
Cc: 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> <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> <F9C9AF4402D59BE5351B1BB9@PSB>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <3fe55ebf-ad93-dae8-338f-d37b08e0ad5f@gmail.com>
Date: Fri, 27 Apr 2018 09:02:33 +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: <F9C9AF4402D59BE5351B1BB9@PSB>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YMHBLM6IomzL8_X7_wpbvvsUroo>
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 21:02:31 -0000

Front posting to say I agree with John that side meetings
may (or may not) be problematic in themselves.

Regards
   Brian

On 27/04/2018 01:03, John C Klensin wrote:
> 
> 
> --On Thursday, April 26, 2018 15:57 +1200 Brian E Carpenter
> <brian.e.carpenter@gmail.com> 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."
>>
>> 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.
>> And people who don't make the 7 week deadline will then delay
>> until the 2 week deadline. So the side event organiser 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.)
>>
>> I'm not saying that's a disaster. But it is a change not
>> mentioned in your initial posting.
> 
> Remembering that we used to go to considerable lengths to
> prohibit or inhibit "side events" as a distraction from the
> IETF's work and that many of the "side events" that occur today
> cause at least some work for the Secretariat and increase the
> demands we place on facilities, let me make a counterproposal.
> This is made more to try to bring the issues that are being
> raised into focus than as a real proposal but, if the IAOC
> wanted to consider it, I wouldn't lose any sleep over the idea.
> 
> We redefine things so that there are two kinds of side events.
> Type 2 is the "old" variety: no use of IETF facilities, even
> announcements on bulletin boards, no coordination with the
> Secretariat, use of the meeting hotel (or venue if different)
> strongly discouraged or, if it occurs, forcing event organizers
> to make their own arrangements with the venue with no allowances
> for adjustments for co-location with the IETF.  What the IETF
> does about registration has no effect on this type of event
> because there just is no interaction.
> 
> Type 1 involves the kind of coordination that I infer from
> Brian's message but anyone applying to set up such a side
> meeting, asking the Secretariat for room or scheduling
> assistance, or wanting to make arrangements with a venue or
> hotel on the coattails of IETF contracts initiates those actions
> with an application to IAOC or AMS that is accompanied by a fee
> of several times the "standards" registration fee. A few "side
> event" applications at 5 or 10K USD each in addition to
> registration fees for those attending would, presumably, justify
> the costs of giving out preliminary registration numbers to
> people making notices of intent to attend.  If the IAOC wer4 to
> make a nominal charge for such notices (as a deposit to be
> credited against the registration fee when paid), it might also
> help... and, in combination with the rest, have a noticeable
> benefit to the bottom line.
> 
> Again, mostly just a thought to clarify the issues and one that
> should probably come with a disclaimer than I've never liked the
> idea of side meetings (or highly organized pseudo-BOFs or
> pseudo-bar-BOFs that require space but don't go through the
> normal review, approval, and agenda processes and the
> expectation of minutes) so I'd consider making them harder a
> benefit.  But, if we are going to complain (or even notice) that
> changes in registration models inconvenience side meetings or
> their organizers, we should also be considering the incremental
> costs of such meetings and probably discussing how to recover
> those costs (and whether it makes sense to make money on them).
> 
> best,
>    john
> 
> 
> 
> 
> .
>