Re: Registration details for IETF 108

Melinda Shore <melinda.shore@gmail.com> Sun, 31 May 2020 21:44 UTC

Return-Path: <melinda.shore@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 51BB03A0DEE for <ietf@ietfa.amsl.com>; Sun, 31 May 2020 14:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, 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 4__7Y-9H3M62 for <ietf@ietfa.amsl.com>; Sun, 31 May 2020 14:44:46 -0700 (PDT)
Received: from mail-pf1-x431.google.com (mail-pf1-x431.google.com [IPv6:2607:f8b0:4864:20::431]) (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 420E53A0DEC for <ietf@ietf.org>; Sun, 31 May 2020 14:44:46 -0700 (PDT)
Received: by mail-pf1-x431.google.com with SMTP id 64so2508987pfg.8 for <ietf@ietf.org>; Sun, 31 May 2020 14:44:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=DE7KdZW7+rN9V6KgACo76PmhygrPdiUEj0QqgG1WtIs=; b=M85V5ffCJITRIRiMXBLCjbiu1/8ZFWNwFYpt5HjLc/ZT29ehtrE0caabWVM8r+KXft Yr0eCIreA+sjT57Cgc8mPw60zUXOX+cmXNYu8FOOFXtmjzXkXcBHXSWaSxe19179f53n WgGBF8I28yyFbh9D6Zu/wHcFsN0jo8Qb29Ydqc819bGw/9zRB48nyemrcFe/ieDdzxhA 8TYZ0NJtQKryxTJfQNRlFsk7JEZEvfaSrmB1cm2UK7U6RTPH1qgDE5+x28iiHGN0UuNt k46K9rLyAuGZdO6tQkK8SbT2bsbL6HJJV0HZd4rh097zoKSADs4ikBnN12tObfeIXDVF NSDw==
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:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=DE7KdZW7+rN9V6KgACo76PmhygrPdiUEj0QqgG1WtIs=; b=i32/2AxgySNEEbq5185Mn+l/QghqjEDGqPyVk4c9MxVuoe6QpOG8DbBP6UZx2pKApK hR8Nh4TtvVecJlQ4ak7VJBLVpfaWk4xIa1OclZaWBhqv6WSdaLdaFj/Y6pEeUNj8GLqE JZTMQ+MjT9t87NUMXgc+gJNgw14Dxw6AE9jfv0uSxkgrjw1lVTsThZDFFqFVW4o5dqIh 3R/LFjgiq+Xo+O7fn6vk1lHTMipz+OdI1mfNeg8R4foN12w//nBhexXn+i/CPqdXfMwE XlW+oJLsVMpd4AIhr/72NVoPJadQs3wRfjqj4EK/m19hECdtcLTb9W0jjBTRrObVeF2y bDvA==
X-Gm-Message-State: AOAM532oeLtgLJB2XdZ59NLrb66be626+sX2vDd68mDTUTyOoZNJr1sS HSi+PS6rJZeR5Vg9po618pNaGUel
X-Google-Smtp-Source: ABdhPJyIJKRkWRtru8jPdoL9kGPafATQgFfVmmCQ7fiTmQHI31Stx3GuLhm9ya9wDxWT09dNThrgrQ==
X-Received: by 2002:a63:6d86:: with SMTP id i128mr16188861pgc.432.1590961483887; Sun, 31 May 2020 14:44:43 -0700 (PDT)
Received: from aspen.local ([63.140.71.170]) by smtp.gmail.com with ESMTPSA id ep10sm5186975pjb.25.2020.05.31.14.44.42 for <ietf@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 31 May 2020 14:44:42 -0700 (PDT)
Subject: Re: Registration details for IETF 108
To: ietf@ietf.org
References: <159062833754.6110.5826748635235943562@ietfa.amsl.com> <6.2.5.6.2.20200531121457.0b249858@elandnews.com> <CABcZeBOzVHaSZa0A3eDz12RwNuCiHtiJL8wqvAhhLPN6YEQOkQ@mail.gmail.com>
From: Melinda Shore <melinda.shore@gmail.com>
Message-ID: <afa11959-3348-4054-409c-803824a2f332@gmail.com>
Date: Sun, 31 May 2020 13:44:41 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.8.0
MIME-Version: 1.0
In-Reply-To: <CABcZeBOzVHaSZa0A3eDz12RwNuCiHtiJL8wqvAhhLPN6YEQOkQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mZVumhhiUgiSUuGqxAl5Bzft_GY>
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: Sun, 31 May 2020 21:44:47 -0000

On 5/31/20 1:13 PM, Eric Rescorla wrote:
> I don't think the characterization of this as "pay-to-play" is accurate. You
> are certainly free to participate in mailing lists, github, etc.

I'm somewhat troubled by this, as well, tbh.  To the extent that
the IETF has gradually and effectively moved to having decisions
made in meetings it would be unfortunate indeed to exclude
people based on financial circumstances.  I'd like to see the
decision-making situation fixed but given the history of that
discussion I think we are where we are, and free remote participation
provides at least some mitigation.  I also tend to think that
saying that meeting participation isn't necessary because {mailing
lists,Github,whatever} is incompatible with the insistence that
the IETF continue to meet because it's not really possible to
progress work without real-time discussion.  I'll also note that
for as long as there's been a remote participation option available
it's been free.  We're now in the odd position of having all-remote
meetings absorb what used to be "remote participants" into the
group of "participants," with some consequential side-effects
(although arguably there are no such things as side-effects, just
effects).

I do think this decision has some unintended consequences.
Scholarships or other subsidy might provide some mitigation
but would potentially be messy/awkward.  The organization
is long overdue for some navel-gazing about working methods.
It's unreasonable to expect perfect consistency but I think
things have gotten a little more incoherent than they should
be.

Melinda

-- 
Melinda Shore
melinda.shore@gmail.com

Software longa, hardware brevis