Re: Proposed Revisions to IETF Trust Administrative Procedures

Ray Pelletier <rpelletier@isoc.org> Mon, 07 April 2008 20:55 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 785BE3A6AC2; Mon, 7 Apr 2008 13:55:41 -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 940E13A6E0A for <ietf@core3.amsl.com>; Mon, 7 Apr 2008 13:55:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.383
X-Spam-Level:
X-Spam-Status: No, score=-2.383 tagged_above=-999 required=5 tests=[AWL=0.216, 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 JbSEd457PmBz for <ietf@core3.amsl.com>; Mon, 7 Apr 2008 13:55:36 -0700 (PDT)
Received: from smtp137.sat.emailsrvr.com (smtp137.sat.emailsrvr.com [66.216.121.137]) by core3.amsl.com (Postfix) with ESMTP id 4D39F3A6AC2 for <ietf@ietf.org>; Mon, 7 Apr 2008 13:55:36 -0700 (PDT)
Received: from relay3.relay.sat.mlsrvr.com (localhost [127.0.0.1]) by relay3.relay.sat.mlsrvr.com (SMTP Server) with ESMTP id 373F9200009; Mon, 7 Apr 2008 16:55:50 -0400 (EDT)
Received: by relay3.relay.sat.mlsrvr.com (Authenticated sender: rpelletier-AT-isoc.org) with ESMTP id E319E20002F; Mon, 7 Apr 2008 16:55:49 -0400 (EDT)
Message-ID: <47FA8A4D.5050902@isoc.org>
Date: Mon, 07 Apr 2008 16:55:41 -0400
From: Ray Pelletier <rpelletier@isoc.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en, zh, zh-cn, zh-hk, zh-sg, zh-tw, ja
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
Subject: Re: Proposed Revisions to IETF Trust Administrative Procedures
References: <47F52D51.4030501@isoc.org> <05216A653F92E3BAE8A4A244@p3.JCK.COM> <6ED3D491-F319-46BE-ADB5-539BE8E94254@cisco.com>
In-Reply-To: <6ED3D491-F319-46BE-ADB5-539BE8E94254@cisco.com>
Cc: John C Klensin <john-ietf@jck.com>, IETF Discussion <ietf@ietf.org>
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

Fred Baker wrote:

>
> On Apr 3, 2008, at 1:54 PM, John C Klensin wrote:
>
>> Probably the Trust and/or IAOC procedures or charter should be  
>> modified so that, in the event of the demise of the IAOC, the Trust  
>> falls firmly under direct IETF control (unless the IETF itself  
>> ceases to exist).
>
>
> The concept makes sense to me, but I'd be interested to understand  
> how that would be implemented. All decisions of the trust happen in  
> discussions on the IETF mailing list, and the consensus of the  
> community as determined by J i m F l e m i n g rules?

As Jorge pointed out:

This is covered by Section 6.1(c) of the Trust Agreement.  If
there are ever fewer than 3 Trustees, the IESG will appoint new
Trustees.  The existing Trustees do NOT become "permanent appointments"
if the IAOC is dissolved.  Rather, the IESG would appoint 3 Trustees
until the IAOC or some successor is constituted.

Ray


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