[Iasa20] BCP 101, RFC 8717 on IETF Administrative Support Activity 2.0: Consolidated Updates to IETF Administrative Terminology

rfc-editor@rfc-editor.org Thu, 27 February 2020 18:24 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 A7E213A07C9; Thu, 27 Feb 2020 10:24:16 -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=unavailable autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id s8wBr5fxSmF5; Thu, 27 Feb 2020 10:24:14 -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 0A9A53A046E; Thu, 27 Feb 2020 10:18:34 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id CB499F4073E; Thu, 27 Feb 2020 10:18:19 -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: <20200227181819.CB499F4073E@rfc-editor.org>
Date: Thu, 27 Feb 2020 10:18:19 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/taRzNe8qWyV4KMJ6Qy9C0La1Ubc>
Subject: [Iasa20] =?utf-8?q?BCP_101=2C_RFC_8717_on_IETF_Administrative_Su?= =?utf-8?q?pport_Activity_2=2E0=3A_Consolidated_Updates_to_IETF_Administra?= =?utf-8?q?tive_Terminology?=
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:24:24 -0000

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

        BCP 101        
        RFC 8717

        Title:      IETF Administrative Support Activity 2.0: 
                    Consolidated Updates to IETF Administrative 
        Author:     J. Klensin, Ed.
        Status:     Best Current Practice
        Stream:     IETF
        Date:       February 2020
        Mailbox:    john-ietf@jck.com
        Pages:      7
        Updates:    RFC 2028, RFC 2418, RFC 3005, RFC 3710, 
                    RFC 3929, RFC 4633, RFC 6702
        See Also:   BCP 101

        I-D Tag:    draft-ietf-iasa2-consolidated-upd-07.txt

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

        DOI:        10.17487/RFC8717

In 2018, the IETF began the transition to a new administrative
structure and updated its IETF Administrative Support Activity (IASA)
to a new "IASA 2.0" structure. In addition to more substantive
changes that are described in other documents, the transition to the
2018 IETF Administrative Support structure changes several position
titles and organizational relationships that are referenced
elsewhere.  Rather than reissue those referencing documents
individually, this specification provides updates to them and
deprecates some now-obsolete documents to ensure that there is no
confusion due to these changes.

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