Re: [Ietf108planning] Registration open for IETF 108

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 11 June 2020 19:09 UTC

Return-Path: <jmh@joelhalpern.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 C7B713A0061 for <ietf@ietfa.amsl.com>; Thu, 11 Jun 2020 12:09:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 7_62DHCzQHde for <ietf@ietfa.amsl.com>; Thu, 11 Jun 2020 12:09:46 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 480BA3A005B for <ietf@ietf.org>; Thu, 11 Jun 2020 12:09:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 49jYMF6WPpz6G9BB; Thu, 11 Jun 2020 12:09:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1591902585; bh=OZ9zOc4ET+wvYd7NJPSQL9JHRPvDx7qze/b+/YTxs6c=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=Z0YgRsM/zbgGwxw4VJpriIYMRUcP8j9EpimhFBtmuHG34MMkDk7dX3BQ5U1Wsx2ql rQ6jmS7EkYog7R3vfu2TB1SITJaptd3a/qUQSw38gKea6PIhpoKNe5hikqXHM3wT4M AG0OnIm0TqYaSYYwCvArPiYIGnwosmIRiajaNyTk=
X-Quarantine-ID: <xDp1HMH1o9qJ>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 49jYMF2vwKz6GHfW; Thu, 11 Jun 2020 12:09:45 -0700 (PDT)
Subject: Re: [Ietf108planning] Registration open for IETF 108
To: Ole Jacobsen <olejacobsen=40me.com@dmarc.ietf.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>
References: <159166311543.4506.736406779378278905@ietfa.amsl.com> <CAFgnS4WOjmNOf_MRfms1RD0e15xYP-xcfNiyqS7p5ofYBEQPdw@mail.gmail.com> <d65a8aeffc61b6d069afa87f3c91b10496c4d5b2.camel@lsl.digital> <5FCC8656386268B41681E1DE@PSB> <B4293B17-6F83-4B9E-89BF-C0B1388F346F@cable.comcast.com> <CABmDk8=gxXiQ60hpdCNB6jK0EG_ssAQnzjgJp=c9yXNKabHKeA@mail.gmail.com> <CABmDk8mwVfWZQmBwZ9c4xaoStwv7CeRRceihTR846iq_LYPFFw@mail.gmail.com> <F6BFB099-2526-4EEB-A267-F2A1D0A7DDFB@cooperw.in> <35fb0076-a240-096a-de7f-280d5e7ad1e3@cs.tcd.ie> <2F0FDD2B-03C8-4E76-9149-A2666147C66E@csperkins.org> <27875646-243d-8d03-b588-866b883fea7c@cs.tcd.ie> <8C935847-70C8-439B-8F4C-83DB9A43E4DF@ietf.org> <46159495-3bef-be6d-31f7-1b83737359ad@gmail.com> <B6DFDB6D-7A97-4EE3-8554-6AF005C73EC3@ietf.org> <2a36750841d34cb99695077d60760ceb@att.com> <F73A75FF-5521-4B07-9905-D621FA3C3E28@me.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <1c9099e4-c0b2-480a-793d-bc674b8449a8@joelhalpern.com>
Date: Thu, 11 Jun 2020 15:09:44 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <F73A75FF-5521-4B07-9905-D621FA3C3E28@me.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0I-IV2wA3dbny43WsDBGY16aZ9o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Jun 2020 19:09:49 -0000

Actually, my guess is that the notion of annual fees per person would be 
a complication for many organizations.  For example, while there are a 
core set of Ericsson participants who come to every meeting, there are 
also folks who come to about one in three. Sure, they do not get to 
offer to be on nomcom.  But they do participate when they are present. 
(And they do pay registration when they attend.)  Even many of the 
regular participants attend only two out of three.  So it would get very 
messy.

Yours,
Joel

On 6/11/2020 2:58 PM, Ole Jacobsen wrote:
> Hi Barbara,
> 
> I was going to suggest something very similar, recognizing that we have more or
> less 2 classes of attendees; those who “always” attend in person and those who
> never do so for whatever reasons. Since it is reasonable to assume that the “always”
> crowd already had Madrid in their budget (private or corporate), it would seem
> to follow that Virtual Madrid is indeed going to represent significant savings over
> a normal meeting.
> 
> If we were to add a box with something like:
> 
> [x] I’d like to contribute an additional amount to support remote participants (etc)
> 
> … which lets you add an to the “shopping cart” during registration.
> 
> This would indeed be a very nice experiment!
> 
> Ole
> 
> 
>> On 11 Jun 2020, at 11:42, STARK, BARBARA H <bs7652@att.com> wrote:
>>
>>> If the fee waiver programme were uncapped then would you still regard that as a bandaid?
>>> Jay
>>
>> I'm going to reply at this point in the thread with some thoughts I haven't seen expressed yet.
>> Much of the commentary against registration fees has come from or on behalf of people who struggle to pay the fees.
>> Much of the commentary for registration fees has come from people who do not struggle to pay the fees.
>>
>> As someone who doesn't struggle to pay the fee (because my employer finds it a significant savings over what would have been paid), but who recognizes that others do struggle, what I would have preferred would be:
>>
>> Put a statement on the registration page:
>>
>> IETF needs to raise $515,145 to pay for costs that would normally have been covered by in-person registration fees. See https://www.ietf.org/blog/ietf108-registration-fees/ for more details. We request that those who are able to pay the fees do so. Any who are not able, please simply check the "waiver request" box. You will then be able to register for free. If your company would like to help sponsor our experiment with unlimited waivers (to enable IETF to continue allowing all to contribute, regardless of situation) , please contact us at <email>.
>>
>> And then have unlimited and automatic waiver.
>>
>> IETF likes to experiment. So we should experiment with a trust model. Trust that only those who need the waiver will request it, and see what happens.
>> Barbara
> 
> Ole J. Jacobsen
> Editor and Publisher
> The Internet Protocol Journal
> Office: +1 415-550-9433
> Cell:   +1 415-370-4628
> Web: protocoljournal.org
> E-mail: olejacobsen@me.com
> E-mail: ole@protocoljournal.org
> Skype: organdemo
>