Re: Proposed Revisions to IETF Trust Administrative Procedures

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 05 April 2008 03:34 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 DBD243A6953; Fri, 4 Apr 2008 20:34:15 -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 EA7733A6B0F for <ietf@core3.amsl.com>; Fri, 4 Apr 2008 20:34:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.653
X-Spam-Level:
X-Spam-Status: No, score=-1.653 tagged_above=-999 required=5 tests=[AWL=0.946, 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 jm2V5M7v1RId for <ietf@core3.amsl.com>; Fri, 4 Apr 2008 20:34:13 -0700 (PDT)
Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.225]) by core3.amsl.com (Postfix) with ESMTP id 0E6063A6940 for <ietf@ietf.org>; Fri, 4 Apr 2008 20:34:12 -0700 (PDT)
Received: by wx-out-0506.google.com with SMTP id i26so359504wxd.31 for <ietf@ietf.org>; Fri, 04 Apr 2008 20:34:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:organization:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=d4IljdAVz30DZ/rSXA7Q2W+hsrmvvK54yJlm1vMWnw8=; b=YJkaaLtC1dp2HKlj7yMMBwdBRpwxi9ipiLR3YzWh8Bf9+ggLCOAe+YZfW7j4AKWjNZwCpHqWp7AsXYGOWcgOIh6CMx8g/lva7G1MVFzswQOTk9uczuHBb/c7jMqMO8XLPWCFZAblWJectzrp8VNNxrjpFyz7MosW1IGpIzsybNI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=cWGuo3yejSD0E2rLw48IrjmkqHKBx14ci47fja66Hl+Xin2CleChUz1Qh0JMuN6S0FAJ/oje0doW9U4ykIqArTzfE5mIewyAb+CSa2n+qlouqmBYSLl4OqQBBETAKLDAz3f6ysPMT0e5rxZgR+BFE69F1uMnnamqY9+OdHHNk1o=
Received: by 10.114.59.1 with SMTP id h1mr3261928waa.39.1207366459727; Fri, 04 Apr 2008 20:34:19 -0700 (PDT)
Received: from ?10.1.1.4? ( [118.92.144.223]) by mx.google.com with ESMTPS id n20sm8719045pof.12.2008.04.04.20.34.15 (version=SSLv3 cipher=RC4-MD5); Fri, 04 Apr 2008 20:34:17 -0700 (PDT)
Message-ID: <47F6F333.4070203@gmail.com>
Date: Sat, 05 Apr 2008 16:34:11 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Harald Alvestrand <harald@alvestrand.no>
Subject: Re: Proposed Revisions to IETF Trust Administrative Procedures
References: <47F52D51.4030501@isoc.org> <47F5FBA4.6080403@alvestrand.no>
In-Reply-To: <47F5FBA4.6080403@alvestrand.no>
Cc: 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 2008-04-04 22:57, Harald Alvestrand wrote:
> Ray Pelletier wrote:
>> 12. The Trustees are the current members of the IAOC. When a member 
>> leaves the IAOC for whatever reason, he or she ceases to be a Trustee. 
>> When a new member joins the IAOC, he or she becomes a Trustee [ADD - 
>> upon their acceptance in writing].
> This is already covered in the Trust agreement section 6.1, which states 
> that the IAOC are "Eligible Persons", and they become Trustees when they 
> agree to that in writing. The addition makes the administrative 
> procedures consistent with the trust agreement - but why say it twice?

I agree with that - which is why it *is* a no-op as far as the adminstrative
procedures document is concerned. I also agree with John Klensin that the
process of inducting IAOC members must include this signature, but I'm
not sure that we need to modify any documents, since RFC 4371
updates RFC 4071 and contains a normative reference to the Trust
Agreement. I think the paper trail is already complete.

>> 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.
> This is already covered in the Trust Agreement section 6.1 (c) - the 
> expiration of the IAOC would reduce the number of Eligible Persons to 
> zero, making the IESG, or the IESG's successor as the leadership of the 
> IETF, repsonsible for picking at least 3 people to serve as temporary 
> Trustees.
> 
> So this proposed change would be in breach of the trust agreement - not 
> good.

I believe that is correct. No IAOC means that all Trustees vanish
instantly and the IESG has to take action. Good catch.

   Brian

> 
> The administrative procedures need to refer to section 6.1 of the trust 
> agreement; creativity is bad.
> 
>                   Harald
> _______________________________________________
> 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