[Iasa20] BCP 10, RFC 8713 on IAB, IESG, IETF Trust, and IETF LLC Selection, Confirmation, and Recall Process: Operation of the IETF Nominating and Recall Committees

rfc-editor@rfc-editor.org Thu, 27 February 2020 18:17 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: iasa20@ietfa.amsl.com
Delivered-To: iasa20@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id BAC963A07AE; Thu, 27 Feb 2020 10:17:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id SAEK1901zAXL; Thu, 27 Feb 2020 10:17:18 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A4663A0794; Thu, 27 Feb 2020 10:17:18 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id EAE11F40720; Thu, 27 Feb 2020 10:17:03 -0800 (PST)
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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, iasa20@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200227181703.EAE11F40720@rfc-editor.org>
Date: Thu, 27 Feb 2020 10:17:03 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/W3PlSTc1mzNvVANs7rHYiaLTACo>
Subject: [Iasa20] =?utf-8?q?BCP_10=2C_RFC_8713_on_IAB=2C_IESG=2C_IETF_Tru?= =?utf-8?q?st=2C_and_IETF_LLC_Selection=2C_Confirmation=2C_and_Recall_Proc?= =?utf-8?q?ess=3A_Operation_of_the_IETF_Nominating_and_Recall_Committees?=
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: =?iso-8859-1?q?Discussions_relating_to_reorganising_the_IETF_administrative_structures_in_the_so_called_=93IASA_2=2E0=94_project=2E?= <iasa20.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iasa20>, <mailto:iasa20-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iasa20/>
List-Post: <mailto:iasa20@ietf.org>
List-Help: <mailto:iasa20-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iasa20>, <mailto:iasa20-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2020 18:17:26 -0000

A new Request for Comments is now available in online RFC libraries.

        BCP 10        
        RFC 8713

        Title:      IAB, IESG, IETF Trust, and IETF LLC Selection,                     
                    Confirmation, and Recall Process: Operation 
                    of the IETF Nominating and Recall Committees 
        Author:     M. Kucherawy, Ed.,
                    B. Hinden, Ed.,
                    J. Livingood, Ed.
        Status:     Best Current Practice
        Stream:     IETF
        Date:       February 2020
        Mailbox:    superuser@gmail.com, 
        Pages:      33
        Obsoletes:  RFC 7437, RFC 8318
        See Also:   BCP 10

        I-D Tag:    draft-ietf-iasa2-rfc7437bis-09.txt

        URL:        https://www.rfc-editor.org/info/rfc8713

        DOI:        10.17487/RFC8713

The process by which the members of the IAB and IESG, some Trustees
of the IETF Trust, and some Directors of the IETF Administration LLC
(IETF LLC) are selected, confirmed, and recalled is specified in this
document. This document is based on RFC 7437.  Only those updates
required to reflect the changes introduced by IETF Administrative
Support Activity (IASA) 2.0 have been included. Any other changes
will be addressed in future documents.

This document obsoletes RFC 7437 and RFC 8318.

This document is a product of the IETF Administrative Support Activity 2 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

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