Re: [Ietf108planning] Registration open for IETF 108

Colin Perkins <csp@csperkins.org> Thu, 11 June 2020 00:21 UTC

Return-Path: <csp@csperkins.org>
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 4BC4E3A0CE1; Wed, 10 Jun 2020 17:21:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=csperkins.org
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 tOVKjxBfts-C; Wed, 10 Jun 2020 17:21:26 -0700 (PDT)
Received: from balrog.mythic-beasts.com (balrog.mythic-beasts.com [IPv6:2a00:1098:0:82:1000:0:2:1]) (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 13E4B3A0CA6; Wed, 10 Jun 2020 17:21:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=csperkins.org; s=mythic-beasts-k1; h=To:Date:From:Subject; bh=/JDoenLNzRZFBWHjum/6Janiy1BKITL8VJr47TgHY2Y=; b=h66btPpECtkJyb7ZOaTmnWkkvk zMw2LZ9wBgZTMWnH70kMJJp58sCxViXmrh4KKqC4wA2JOLz+qJe+kd1pRSZgyqIOZuhFaVvQXokPs nWyNIWdREYvnOSBUBR85VPA+8BUzh+fZugP0kx0eiIitH70F0U6Ft+uRNMTmPiQAcc1t3IQ/Orpiv MzkTfwozCS6NYs5UrTLLuhmeOEIl71p3VpStZio8Cz6AlKKpxpNYTucU4TMZVWbTEPgwqvM9GC96P 7vio+rU43AkXOmlspGFoHvkkVWj5ccS8UWHdq/Ixog/V9feEOgTnMpBDt4SgWSX5Xars+OXdRxlCB mQDw/Tmw==;
Received: from [81.187.2.149] (port=33920 helo=[192.168.0.80]) by balrog.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from <csp@csperkins.org>) id 1jjAxy-0003DM-Oc; Thu, 11 Jun 2020 01:21:14 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Subject: Re: [Ietf108planning] Registration open for IETF 108
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <35fb0076-a240-096a-de7f-280d5e7ad1e3@cs.tcd.ie>
Date: Thu, 11 Jun 2020 01:20:50 +0100
Cc: Alissa Cooper <alissa@cooperw.in>, John C Klensin <john-ietf@jck.com>, "ietf108planning@ietf.org" <ietf108planning@ietf.org>, ietf <ietf@ietf.org>, "exec-director@ietf.org" <exec-director@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2F0FDD2B-03C8-4E76-9149-A2666147C66E@csperkins.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>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.3445.104.14)
X-BlackCat-Spam-Score: 4
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4nlcDlFOuEwMd8suguOap7GhOgw>
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 00:21:30 -0000

> On 10 Jun 2020, at 23:10, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> On 10/06/2020 22:09, Alissa Cooper wrote:
>> For IETF 108 we didn't have a lot of time to sort this out. Our
>> thinking was that any approach aside from random selection needs
>> substantial community consultation even if it will only apply to one
>> meeting because it implies subjective judgment about whose attendance
>> ought to be subsidized. We did not have time to do that before
>> registration details needed to be shared with the community.
> 
> I think someone pointed it out earlier, but I'm also
> puzzled how one can reach a conclusion that introducing
> a fee for remote registration didn't need community debate
> but the flavour of waiver for said fee does require such
> debate.

I tend to view the fee as a reduced rate on the in-person IETF meeting fee, since the meeting has to happen in a different format due to the pandemic. As an exceptional case, that seems reasonable to me. If it becomes the new normal, then clearly a broader community discussion will be needed around the IETF funding model. I'd guess that that discussion will take some time to conclude.

Granting fee waivers based on private application of subjective criteria, with no community guidance on what criteria to apply, seems like a much bigger process change.

Colin




> The only way I can make sense of that is if one has
> concluded that remote registration fees are happening
> for sure, regardless of what the community think, and
> that's a concern as it has all sorts of impacts that
> to me absolutely do require community debate before
> anything is done.
> 
> Again, I think the best outcome here would be to waive
> 100% and not 100 of the remote registration fees for
> IETF108 and let the community debate this before such
> decisions are taken. If we cannot afford that, then
> please say so clearly - that would be a relevant fact.
> But if we could afford that, I really don't get why
> it's ok to barge ahead like this.
> 
> S.
> 
> <0x5AB2FAF17B172BEA.asc>



-- 
Colin Perkins
https://csperkins.org/