[Iasa20] BCP 25, RFC 8716 on Update to the IETF Anti-Harassment Procedures for the Replacement of the IETF Administrative Oversight Committee (IAOC) with the IETF Administration LLC

rfc-editor@rfc-editor.org Thu, 27 February 2020 18:18 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 9871C3A076F; Thu, 27 Feb 2020 10:18: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 d5oQ8K8mfsyB; Thu, 27 Feb 2020 10:18:13 -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 1DAE03A07DE; Thu, 27 Feb 2020 10:18:13 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id DECE5F4071D; Thu, 27 Feb 2020 10:17:58 -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: <20200227181758.DECE5F4071D@rfc-editor.org>
Date: Thu, 27 Feb 2020 10:17:58 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/reWTyaKJOrDCGIKWY5qE123Rxqo>
Subject: [Iasa20] =?utf-8?q?BCP_25=2C_RFC_8716_on_Update_to_the_IETF_Anti?= =?utf-8?q?-Harassment_Procedures_for_the_Replacement_of_the_IETF_Administ?= =?utf-8?q?rative_Oversight_Committee_=28IAOC=29_with_the_IETF_Administrat?= =?utf-8?q?ion_LLC?=
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:18:23 -0000

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

        BCP 25        
        RFC 8716

        Title:      Update to the IETF Anti-Harassment 
                    Procedures for the Replacement of the 
                    IETF Administrative Oversight Committee (IAOC) 
                    with the IETF Administration LLC 
        Author:     P. Resnick,
                    A. Farrel
        Status:     Best Current Practice
        Stream:     IETF
        Date:       February 2020
        Mailbox:    resnick@episteme.net, 
        Pages:      7
        Updates:    RFC 7776
        See Also:   BCP 25

        I-D Tag:    draft-ietf-iasa2-rfc7776bis-03.txt

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

        DOI:        10.17487/RFC8716

The IETF Anti-Harassment Procedures are described in RFC 7776.

The IETF Administrative Oversight Committee (IAOC) has been replaced
by the IETF Administration LLC, and the IETF Administrative Director
has been replaced by the IETF LLC Executive Director.  This document
updates RFC 7776 to amend these terms.

RFC 7776 contained updates to RFC 7437.  RFC 8713 has incorporated
those updates, so this document also updates RFC 7776 to remove those

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