[rfc-dist] BCP 10, RFC 8788 on Eligibility for the 2020-2021 Nominating Committee
rfc-editor@rfc-editor.org Wed, 27 May 2020 06:31 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A10433A053F for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 26 May 2020 23:31:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 2LOHruQ3uyKL for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 26 May 2020 23:31:09 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60C923A0542 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 26 May 2020 23:31:09 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 6476DF4074D; Tue, 26 May 2020 23:30:57 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 0CDD2F4071B; Tue, 26 May 2020 23:30:57 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20200527063057.0CDD2F4071B@rfc-editor.org>
Date: Tue, 26 May 2020 23:30:57 -0700
Subject: [rfc-dist] BCP 10, RFC 8788 on Eligibility for the 2020-2021 Nominating Committee
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
BCP 10
RFC 8788
Title: Eligibility for the 2020-2021 Nominating
Committee
Author: B. Leiba
Status: Best Current Practice
Stream: IETF
Date: May 2020
Mailbox: barryleiba@computer.org
Pages: 5
See Also: BCP 10
I-D Tag: draft-iesg-nomcom-eligibility-2020-03.txt
URL: https://www.rfc-editor.org/info/rfc8788
DOI: 10.17487/RFC8788
The 2020-2021 Nominating Committee (NomCom) is to be formed between
the IETF 107 and IETF 108 meetings, and the issue of eligibility of
who can serve on that NomCom needs clarification. This document
provides a one-time interpretation of the eligibility rules that is
required for the exceptional situation of the cancellation of the
in-person IETF 107 meeting. This document only affects the seating
of the 2020-2021 NomCom and any rules or processes that relate to
NomCom eligibility before IETF 108; it does not set a precedent to be
applied in the future.
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
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org