[Iasa20] BCP 101, RFC 8711 on Structure of the IETF Administrative Support Activity, Version 2.0

rfc-editor@rfc-editor.org Thu, 27 February 2020 18:15 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 98B273A03F4; Thu, 27 Feb 2020 10:15:40 -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 6xN7AjGNeAJx; Thu, 27 Feb 2020 10:15:39 -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 41A433A03EA; Thu, 27 Feb 2020 10:15:39 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 0A030F40711; Thu, 27 Feb 2020 10:15:25 -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: <20200227181525.0A030F40711@rfc-editor.org>
Date: Thu, 27 Feb 2020 10:15:25 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/OQsPA3_SBUEZ0j9PUDL6G7-MExc>
Subject: [Iasa20] =?utf-8?q?BCP_101=2C_RFC_8711_on_Structure_of_the_IETF_?= =?utf-8?q?Administrative_Support_Activity=2C_Version_2=2E0?=
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:15:41 -0000

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

        BCP 101        
        RFC 8711

        Title:      Structure of the IETF Administrative 
                    Support Activity, Version 2.0 
        Author:     B. Haberman,
                    J. Hall,
                    J. Livingood
        Status:     Best Current Practice
        Stream:     IETF
        Date:       February 2020
        Mailbox:    brian@innovationslab.net, 
        Pages:      22
        Obsoletes:  RFC 4071, RFC 4333, RFC 7691
        See Also:   BCP 101

        I-D Tag:    draft-ietf-iasa2-rfc4071bis-11.txt

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

        DOI:        10.17487/RFC8711

The IETF Administrative Support Activity (IASA) was originally
established in 2005. In the years since then, the needs of the IETF
evolved in ways that required changes to its administrative
structure. The purpose of this RFC is to document and describe the
IETF Administrative Support Activity, version 2.0 (IASA 2.0). It
defines the roles and responsibilities of the IETF Administration LLC
Board (IETF LLC Board), the IETF Executive Director, and the Internet
Society in the fiscal and administrative support of the IETF
standards process.  It also defines the membership and selection
rules for the IETF LLC Board.

This document obsoletes RFC 4071, RFC 4333, and RFC 7691.

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