Re: [Eligibility-discuss] Report on the RFC 8989 experiment
Michael Richardson <mcr+ietf@sandelman.ca> Wed, 01 September 2021 23:39 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 08E423A1E0D for <eligibility-discuss@ietfa.amsl.com>; Wed, 1 Sep 2021 16:39:26 -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 HB2ku4y5zdoH for <eligibility-discuss@ietfa.amsl.com>; Wed, 1 Sep 2021 16:39:20 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90B523A1E0B for <eligibility-discuss@ietf.org>; Wed, 1 Sep 2021 16:39:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id CB062392AA; Wed, 1 Sep 2021 19:45:16 -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 yxgn_ntDVjmv; Wed, 1 Sep 2021 19:45:11 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 94568392A9; Wed, 1 Sep 2021 19:45:11 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id DDC1B510; Wed, 1 Sep 2021 19:39:11 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, eligibility-discuss@ietf.org
In-Reply-To: <303e2994-7245-9ced-53d8-bbc9dca629ac@gmail.com>
References: <C5D2F5EC-6483-441C-90BC-1900E305D226@ietf.org> <303e2994-7245-9ced-53d8-bbc9dca629ac@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, 01 Sep 2021 19:39:11 -0400
Message-ID: <6751.1630539551@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/0-Jdz4whXfzEfsuD_jmRKWx9r2o>
Subject: Re: [Eligibility-discuss] Report on the RFC 8989 experiment
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF eligibility procedures <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, 01 Sep 2021 23:39:26 -0000
Brian E Carpenter <brian.e.carpenter@gmail.com> wrote: > As a co-author of RFC8989, I'd like to thank the IESG, Barbara, Gabriel > (and Robert Sparks behind the scenes) for this very clear report. me too! > IMHO, remote attendance counting towards NomCom eligibility has been a > success now for two years running (RFC8989 and RFC8788), so whatever > the final conclusion for the other paths in RFC8989, remote attendance > should remain as a criterion. If we move to hybrid meetings, we'd need > to define a bit more precisely what "remote attendance" means. I agree that we'd have to decide if the remote attendees for a hybrid meeting would not get counted as 8788 does not apply, and 8989 applies to entirely online meetings only (effectively extending 8788's criteria). As WGs go from ad-hoc/webex to meetecho for virtual interim meetings, we get automatic bluesheet calculations. I was in two meetecho virtual interims this week. It would be nice to know if there are people who begin to attend only virtual interims, who would likely qualify under path 2/3 (probably mostly 3) who could not qualify under path 1. If I had my way, we'd decongest plenary week and this would become even more important. But, given the huge gap between those who qualified and those who actually volunteered, we need to do gather some additional data. I'd like to suggest to the IESG and our Executive Director that we need to survey/interview some random sampling of people who were qualified, but did not volunteer. (Yes: some of them did not volunteer because they want to serve. Perhaps we can subtract them from the survey list once the list of candidates is known) -- Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide
- [Eligibility-discuss] Report on the RFC 8989 expe… IETF Chair
- Re: [Eligibility-discuss] Report on the RFC 8989 … IETF Chair
- Re: [Eligibility-discuss] Report on the RFC 8989 … Brian E Carpenter
- Re: [Eligibility-discuss] Report on the RFC 8989 … Michael Richardson
- Re: [Eligibility-discuss] Report on the RFC 8989 … Michael Richardson
- Re: [Eligibility-discuss] Report on the RFC 8989 … Gabriel Montenegro
- Re: [Eligibility-discuss] Report on the RFC 8989 … STARK, BARBARA H