Re: Proposed Revisions to IETF Trust Administrative Procedures

Marshall Eubanks <tme@multicasttech.com> Wed, 09 April 2008 14:24 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 C2B063A6DB2; Wed, 9 Apr 2008 07:24:40 -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 BF3133A6DB2 for <ietf@core3.amsl.com>; Wed, 9 Apr 2008 07:24:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.849
X-Spam-Level:
X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5 tests=[AWL=0.750, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 o7UzykQ54ykr for <ietf@core3.amsl.com>; Wed, 9 Apr 2008 07:24:38 -0700 (PDT)
Received: from multicasttech.com (lennon.multicasttech.com [63.105.122.7]) by core3.amsl.com (Postfix) with ESMTP id 9FE433A6D15 for <ietf@ietf.org>; Wed, 9 Apr 2008 07:24:38 -0700 (PDT)
Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP-TLS id 10970498; Wed, 09 Apr 2008 10:24:56 -0400
Message-Id: <405E5ABA-C7C2-4A2A-8840-84A3860443AA@multicasttech.com>
From: Marshall Eubanks <tme@multicasttech.com>
To: John C Klensin <john-ietf@jck.com>
In-Reply-To: <33EDFDB1A6BB5C5B68362C2C@p3.JCK.COM>
Mime-Version: 1.0 (Apple Message framework v919.2)
Subject: Re: Proposed Revisions to IETF Trust Administrative Procedures
Date: Wed, 09 Apr 2008 10:24:53 -0400
References: <20080407194507.44B6028C21E@core3.amsl.com> <CAB795A3F7B5B1851E831FBB@beethoven.local> <0BDFFF51DC89434FA33F8B37FCE363D511F94E2B@zcarhxm2.corp.nortel.com> <E974AC59312981BA5F1A1364@p3.JCK.COM> <47FC2355.9030505@gmail.com> <33EDFDB1A6BB5C5B68362C2C@p3.JCK.COM>
X-Mailer: Apple Mail (2.919.2)
Cc: Leslie Daigle <leslie@thinkingcat.com>, Harald Alvestrand <harald@alvestrand.no>, 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


On Apr 9, 2008, at 8:21 AM, John C Klensin wrote:

>
>
> --On Wednesday, 09 April, 2008 14:00 +1200 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>
>> Let's expand the quotation from the current, unamended Trust
>> procedures slightly:
>>
>> "If at any time the IAOC ceases to
>> exist, the Trustees then in office shall remain in office
>> and determine the future of
>> the Trust in accordance with the Trust Agreement."
>>
>> I agree there's a drafting error - it should say
>>
>> ""If at any time the IAOC ceases to
>> exist, the Trustees then in office shall remain in office
>> SOLELY IN ORDER TO determine the future of
>> the Trust in accordance with the Trust Agreement.""
>>

How, precisely, would the IAOC cease to exist ?

If they all resign or die, the IETF (IESG, IAB, ISOC) would appoint  
more.

If BCP 101 was changed, the new document would undoubtedly cover the  
treatment of the Trust
by the IAOC replacement, or allow for direct appointments, or  
whatever. At any rate, that should be worried about
then, not now.

This wording is, in my opinion, purely to account for the case of the  
IETF ceasing to exist, in which
case I think Brian's wording is appropriate. (And, of course, if there  
is no IETF, there would presumably also be
no IESG, so they could not appoint more.)

One of the parties of the Trust agreement was worried about this. I am  
not.

Regards
Marshall


>> That was certainly the intent.
>
> But that is still inconsistent with the way I (and others) have
> read the Trust Agreement itself.   If that reading is correct
> then, if the IAOC ceases to exist, the then-current batch of
> Trustees, or at least those who are Trustees as the result of
> IETF appointments or positions, all go "poof" in that role.  The
> IESG then appoints three Trustees and _they_, not the prior
> incumbents, get to determine the future of the Trust.
>
> This distinction is important because it means that the people
> doing the "determining of the future" are potentially different
> people and definitely in different roles.  Precisely the one
> thing those lame-duck Trustees should not be doing is
> "determining the future of the Trust".   The language that would
> be consistent with that reading of the Trust Agreement would be
> something more like...
>
> 	"If at any time the IAOC ceases to exist, the Trustees
> 	then in office shall remain in office only until the
> 	IESG can appoint new Trustees in accordance with the
> 	Trust Agreement.  During that period, their sole role
> 	and authority will be to conduct day to day business;
> 	they are prohibited from making any decisions with
> 	long-term or broad implications that cannot be reversed
> 	by their IESG-appointed successors."
>
> If one is going to plan for an unlikely, and potentially
> catastrophic, contingency at all, it is worth getting it right.
> Even independent of what the Trust Agreement says, if the IETF
> decides to get rid of the IAOC, the decisions about what happens
> next to IETF Administration should be firmly and exclusively in
> IETF hands.
>
> Then one needs to worry about what happens if the IETF goes away
> :-(
>
>      john
>
> _______________________________________________
> IETF mailing list
> IETF@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

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