Re: Proposed Revisions to IETF Trust Administrative Procedures

Russ Housley <housley@vigilsec.com> Thu, 03 April 2008 21:26 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6B09D3A6DCE; Thu, 3 Apr 2008 14:26:45 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 41C473A6CEF for <ietf@core3.amsl.com>; Thu, 3 Apr 2008 14:26:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.04
X-Spam-Level:
X-Spam-Status: No, score=-2.04 tagged_above=-999 required=5 tests=[AWL=0.559, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iNK-GL4ZESKU for <ietf@core3.amsl.com>; Thu, 3 Apr 2008 14:26:43 -0700 (PDT)
Received: from woodstock.binhost.com (woodstock.binhost.com [8.8.40.152]) by core3.amsl.com (Postfix) with SMTP id DF6ED3A6AB0 for <ietf@ietf.org>; Thu, 3 Apr 2008 14:26:01 -0700 (PDT)
Received: (qmail 4324 invoked by uid 0); 3 Apr 2008 21:25:59 -0000
Received: from unknown (HELO THINKPADR52.vigilsec.com) (72.83.129.167) by woodstock.binhost.com with SMTP; 3 Apr 2008 21:25:59 -0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 03 Apr 2008 17:25:59 -0400
To: John C Klensin <john-ietf@jck.com>,Ray Pelletier <rpelletier@isoc.org>, <ietf@ietf.org>
From: Russ Housley <housley@vigilsec.com>
Subject: Re: Proposed Revisions to IETF Trust Administrative Procedures
In-Reply-To: <05216A653F92E3BAE8A4A244@p3.JCK.COM>
References: <47F52D51.4030501@isoc.org> <05216A653F92E3BAE8A4A244@p3.JCK.COM>
Mime-Version: 1.0
Message-Id: <20080403212601.DF6ED3A6AB0@core3.amsl.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

John:

>(2) Because some members of the IAOC are appointed by (or
>ex-officio from) other bodies, I would prefer that, if there is
>going to be a separate Trust Chair, that person be required to
>be an IETF appointee and subject to recall.  No matter how many
>"the Chair is nothing special" rules one has, we all know from
>experience that long-term (as distinct from rotating) chairs of
>long-lived bodies tend to be treated, externally at least, as
>spokespeople, etc.

We already have recall procedures for IAOC members.  They are 
documented in RFC 4071.  Since the first requirement to be a Trustee 
is to be an IAOC member, nothing further seems to be needed.

Russ 

_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf