Re: [Eligibility-discuss] Seeking reviews for draft-carpenter-eligibility-expand-05
Michael Richardson <mcr+ietf@sandelman.ca> Wed, 09 September 2020 17:01 UTC
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: eligibility-discuss@ietfa.amsl.com
Delivered-To: eligibility-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 805113A0B34 for <eligibility-discuss@ietfa.amsl.com>; Wed, 9 Sep 2020 10:01:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 jIf6urDo4O0t for <eligibility-discuss@ietfa.amsl.com>; Wed, 9 Sep 2020 10:01:16 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA4433A0B32 for <eligibility-discuss@ietf.org>; Wed, 9 Sep 2020 10:01:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 6CEAF389CA for <eligibility-discuss@ietf.org>; Wed, 9 Sep 2020 12:40:04 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Fn6lhEdHYwwN for <eligibility-discuss@ietf.org>; Wed, 9 Sep 2020 12:39:57 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 7535D389B2 for <eligibility-discuss@ietf.org>; Wed, 9 Sep 2020 12:39:57 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 21A69553 for <eligibility-discuss@ietf.org>; Wed, 9 Sep 2020 13:01:07 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: eligibility-discuss@ietf.org
In-Reply-To: <CAKKJt-eSYSPtCKeusZLjEG9j35owGS4m5V2OwxPmgnicJMAs+A@mail.gmail.com>
References: <edda9433-c95e-4605-b985-a6b8e4c38438@dogfood.fastmail.com> <4905.1599657136@localhost> <CAKKJt-eSYSPtCKeusZLjEG9j35owGS4m5V2OwxPmgnicJMAs+A@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 09 Sep 2020 13:01:07 -0400
Message-ID: <23522.1599670867@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/Yv2u8EodfgEGFs_a6-kuNgxvAtQ>
Subject: Re: [Eligibility-discuss] Seeking reviews for draft-carpenter-eligibility-expand-05
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <eligibility-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eligibility-discuss/>
List-Post: <mailto:eligibility-discuss@ietf.org>
List-Help: <mailto:eligibility-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Sep 2020 17:01:19 -0000
Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote: > Collecting "what we've also discussed" into another document, so that > people don't have to chase fairly obscure email threads (which are rarely > short, when Nomcom topics are discussed), would be valuable. Agreed. >> 1) These are the things we plan to implement for 2021. >> >> 2) These are the things that we are considering for the future. >> There are either unresolved (but solvable) issues with them and/or >> We didn't want to change too much at once. >> > I'd offer a slightly different framing for 2 and for 3: 2> - "We think we could get IETF Consensus for this change in the future 2> based on discussion to date, but it's not part of the current 2> experiment" 3> - "We don't think we could get IETF Consensus for this change in the 3> future based on discussion to date" Your wording is better. The reason I think that we need to tell people about <2> is that I think it is reasonable to say what might get "measured", so they can adopt earlier. > ISTM that if we'd tried to get IETF Consensus for eligibility of remote > attendees at any point, pre-CoViD-19, we would have concluded that it was a > "bad idea", for reasons that have already been raised about gaming and sock > puppets, but things really did change ("literally no one has attended the > last three IETF meetings in person, so literally no one will be eligible to > serve on Nomcom"). A previously "bad idea" may be the best idea we can come > up with, in a given situation. +1 -- Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide
- Re: [Eligibility-discuss] Seeking reviews for dra… Michael Richardson
- Re: [Eligibility-discuss] Seeking reviews for dra… Spencer Dawkins at IETF
- Re: [Eligibility-discuss] Seeking reviews for dra… Michael Richardson
- Re: [Eligibility-discuss] Seeking reviews for dra… Salz, Rich
- Re: [Eligibility-discuss] Seeking reviews for dra… Brian E Carpenter
- Re: [Eligibility-discuss] Seeking reviews for dra… Brian E Carpenter
- Re: [Eligibility-discuss] Seeking reviews for dra… Salz, Rich