IETF Logo Mail Archive

Re: Last Call: <draft-ietf-iasa2-trust-update-00.txt> (Update to the Selection of Trustees for the IETF Trust) to Best Current Practice

Jari Arkko <jari.arkko@piuha.net> Fri, 05 October 2018 16:36 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3419E130DC1; Fri, 5 Oct 2018 09:36:47 -0700 (PDT)
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] 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 Pt-ZUkVyRiPV; Fri, 5 Oct 2018 09:36:45 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id CEE96130E5C; Fri, 5 Oct 2018 09:36:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 4F583660139; Fri, 5 Oct 2018 19:36:43 +0300 (EEST)
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UowGzHsL86Ph; Fri, 5 Oct 2018 19:36:42 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTPS id 44F46660126; Fri, 5 Oct 2018 19:36:42 +0300 (EEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Last Call: <draft-ietf-iasa2-trust-update-00.txt> (Update to the Selection of Trustees for the IETF Trust) to Best Current Practice
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <093e01d452ae$ae761b70$0b625250$@olddog.co.uk>
Date: Fri, 05 Oct 2018 19:36:41 +0300
Cc: ietf@ietf.org, iasa2-chairs@ietf.org, iasa20@ietf.org, draft-ietf-iasa2-trust-update@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <470DBAE7-167C-4084-8D90-EF9566A2D86A@piuha.net>
References: <153756470188.20283.12048259576780413892.idtracker@ietfa.amsl.com> <093e01d452ae$ae761b70$0b625250$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ds7Zot3ryi1PQ7PWNZCsirQdMhU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Oct 2018 16:36:48 -0000

Adrian,

Many thanks for your perceptive review.

I have adopted your suggestions in my copy of the draft.

One follow-up below:

> Section 2
> 
>   IETF rules regarding recalls and other NomCom-related processes
>   continue to apply [RFC7437].
> 
> Pedantic, but you can't quite get away with this because the NomCom
> processes in 7437 did not apply to pure IETF Trust appointments.
> 
> How about...
> 
>   The processes regarding NomCom appointments and recalls of Trustees
>   for the IETF Trust follow those described in [RFC7437].

That’s much better, and this was an important catch.

> Does this mean this document updates 7437?

I think not, because this document uses 7437… would be happy to hear if people think otherwise.

Jari

v2.23.0 | Report a Bug | By Email