[Iasa20] Secdir last call review of draft-ietf-iasa2-rfc7776bis-02

Melinda Shore via Datatracker <noreply@ietf.org> Thu, 08 August 2019 23:53 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: iasa20@ietf.org
Delivered-To: iasa20@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7524E120154; Thu, 8 Aug 2019 16:53:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Melinda Shore via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: draft-ietf-iasa2-rfc7776bis.all@ietf.org, ietf@ietf.org, iasa20@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.100.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Melinda Shore <melinda.shore@nomountain.net>
Message-ID: <156530839229.7502.10596578919129972914@ietfa.amsl.com>
Date: Thu, 08 Aug 2019 16:53:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/iasa20/0KYHqX8RAUVVCQ1Z_cBqtXObiTE>
Subject: [Iasa20] Secdir last call review of draft-ietf-iasa2-rfc7776bis-02
X-BeenThere: iasa20@ietf.org
X-Mailman-Version: 2.1.29
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, 08 Aug 2019 23:53:25 -0000

Reviewer: Melinda Shore
Review result: Ready

This document updates IETF anti-harassment procedures to reflect organizational
changes to the IETF (specifically, the replacement of the IAOC with the IETF
LLC, and the replacement of the IETF Administrative Director with the IETF LLC
Executive Director).  Additionally, it updates the text with respect to
ombudsteam-initiated recall processes, but it does not change make changes to
the processes themselves.  The document is clearly written and unambiguous, and
there are no new security considerations.  The document is ready for
publication.