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

"Pete Resnick" <resnick@episteme.net> Thu, 25 October 2018 18:18 UTC

Return-Path: <resnick@episteme.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 A60FE126F72; Thu, 25 Oct 2018 11:18:45 -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 RgajCMfN3Fxh; Thu, 25 Oct 2018 11:18:44 -0700 (PDT)
Received: from episteme.net (episteme.net [216.169.5.102]) by ietfa.amsl.com (Postfix) with ESMTP id A2EBB130E01; Thu, 25 Oct 2018 11:18:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by episteme.net (Postfix) with ESMTP id 5052B6BB580D; Thu, 25 Oct 2018 13:18:44 -0500 (CDT)
Received: from episteme.net ([127.0.0.1]) by localhost (episteme.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RQMPoy-CCRNx; Thu, 25 Oct 2018 13:18:43 -0500 (CDT)
Received: from [172.16.1.18] (episteme.net [216.169.5.102]) by episteme.net (Postfix) with ESMTPSA id 75AB16BB5804; Thu, 25 Oct 2018 13:18:42 -0500 (CDT)
From: Pete Resnick <resnick@episteme.net>
To: ietf@ietf.org
Cc: iasa20@ietf.org
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
Date: Thu, 25 Oct 2018 13:18:42 -0500
X-Mailer: MailMate (1.12r5523)
Message-ID: <A10AF232-65A1-4795-ACEF-D5B2073C35E7@episteme.net>
In-Reply-To: <7A17228D-7B76-4A63-B318-7761617647A9@episteme.net>
References: <153756470188.20283.12048259576780413892.idtracker@ietfa.amsl.com> <7A17228D-7B76-4A63-B318-7761617647A9@episteme.net>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; markup="markdown"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5ir_yW3ro5GYc4llb-qwM-9nRj0>
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: Thu, 25 Oct 2018 18:18:46 -0000

On 25 Oct 2018, at 13:15, Pete Resnick wrote:

> Section 2 says that NomCom-appointed Trustees can be recalled 
> according to 7437 (presumably bis). Can the IESG-appointed and 
> ISOC-BoT-appointed Trustees be recalled or otherwise removed as 
> Trustees? If so, by what mechanism? I don't have any opinion on what 
> the mechanism should be (e.g., the appointing body can simply say, 
> "You're fired", or the 7437 process could be used, or ...), but I do 
> think there needs to be some mechanism specified for removing them if 
> necessary.

My apologies; I see this has already been resolved.

pr

v2.23.0 | Report a Bug | By Email