[Iasa20] BCP 101, RFC 8714 on Update to the Process for Selection of Trustees for the IETF Trust
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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81AE03A0772; Thu, 27 Feb 2020 10:17:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2zA4MAwvZFB8; Thu, 27 Feb 2020 10:17:26 -0800 (PST)
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 32CEA3A07AF; Thu, 27 Feb 2020 10:17:26 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id E3CEDF40727; Thu, 27 Feb 2020 10:17:11 -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: <20200227181711.E3CEDF40727@rfc-editor.org>
Date: Thu, 27 Feb 2020 10:17:11 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/8-LJ2UHpOJn4jI7AmBL8MEE6jxI>
Subject: [Iasa20] BCP 101, RFC 8714 on Update to the Process for Selection of Trustees for the IETF Trust
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions relating to reorganising the IETF administrative structures in the so called IASA 2.0 project. <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:34 -0000
A new Request for Comments is now available in online RFC libraries.
BCP 101
RFC 8714
Title: Update to the Process for Selection
of Trustees for the IETF Trust
Author: J. Arkko,
T. Hardie
Status: Best Current Practice
Stream: IETF
Date: February 2020
Mailbox: jari.arkko@piuha.net,
ted.ietf@gmail.com
Pages: 6
Obsoletes: RFC 4371
See Also: BCP 101
I-D Tag: draft-ietf-iasa2-trust-update-03.txt
URL: https://www.rfc-editor.org/info/rfc8714
DOI: 10.17487/RFC8714
This memo updates the process for selection of Trustees for the IETF
Trust. Previously, the IETF Administrative Oversight Committee (IAOC)
members also acted as Trustees, but the IAOC has been eliminated as
part of an update to the structure of the IETF Administrative Support
Activity (IASA). This memo specifies that the Trustees shall be
selected separately.
This memo obsoletes RFC 4371. The changes relate only to the
selection of Trustees. All other aspects of the IETF Trust remain as
they are today.
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
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