[Eligibility-discuss] BCP 10, RFC 9389 on Nominating Committee Eligibility
rfc-editor@rfc-editor.org Fri, 28 April 2023 23:21 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
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 B877BC152B03; Fri, 28 Apr 2023 16:21:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.948
X-Spam-Level:
X-Spam-Status: No, score=-3.948 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZKBXYNIcE4Ag; Fri, 28 Apr 2023 16:21:42 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84FA3C1522C4; Fri, 28 Apr 2023 16:21:31 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 68FFE55F69; Fri, 28 Apr 2023 16:21:31 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, eligibility-discuss@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230428232131.68FFE55F69@rfcpa.amsl.com>
Date: Fri, 28 Apr 2023 16:21:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/3RLHvwfFyPIcfk4STlovui7gDX8>
Subject: [Eligibility-discuss] BCP 10, RFC 9389 on Nominating Committee Eligibility
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 28 Apr 2023 23:21:45 -0000
A new Request for Comments is now available in online RFC libraries.
BCP 10
RFC 9389
Title: Nominating Committee Eligibility
Author: M. Duke
Status: Best Current Practice
Stream: IETF
Date: April 2023
Mailbox: martin.h.duke@gmail.com
Pages: 9
Obsoletes: RFC 8788, RFC 8989
Updates: RFC 8713
See Also: BCP 10
I-D Tag: draft-ietf-elegy-rfc8989bis-05.txt
URL: https://www.rfc-editor.org/info/rfc9389
DOI: 10.17487/RFC9389
The IETF Nominating Committee (NomCom) appoints candidates to several
IETF leadership committees. RFC 8713 provides criteria for NomCom
membership that attempt to ensure NomCom volunteers are members of
the loosely defined IETF community, by requiring in-person attendance
in three of the past five in-person meetings. In 2020 and 2021, the
IETF had six consecutive fully online plenary meetings that drove
rapid advancement in remote meeting technologies and procedures,
including an experiment that included remote attendance for NomCom
eligibility. This document updates RFC 8713 by defining a new set of
eligibility criteria from first principles, with consideration to the
increased salience of remote attendance. This document obsoletes RFCs
8788 and 8989.
This document is a product of the NomCom Eligibility Update Working Group of the IETF.
BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC