RE: Proposed Revisions to IETF Trust Administrative Procedures
"Ed Juskevicius" <edj@nortel.com> Wed, 09 April 2008 17:50 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 1226E3A6A35;
Wed, 9 Apr 2008 10:50:33 -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 711993A687B
for <ietf@core3.amsl.com>; Wed, 9 Apr 2008 10:50:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.541
X-Spam-Level:
X-Spam-Status: No, score=-6.541 tagged_above=-999 required=5 tests=[AWL=0.058,
BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 q8tY4n-hwcIJ for <ietf@core3.amsl.com>;
Wed, 9 Apr 2008 10:50:27 -0700 (PDT)
Received: from zcars04e.nortel.com (zcars04e.nortel.com [47.129.242.56])
by core3.amsl.com (Postfix) with ESMTP id 27F0028C2BD
for <ietf@ietf.org>; Wed, 9 Apr 2008 10:50:23 -0700 (PDT)
Received: from zcarhxm2.corp.nortel.com (zcarhxm2.corp.nortel.com
[47.129.230.99])
by zcars04e.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id
m39Hnuq14734; Wed, 9 Apr 2008 17:49:56 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: Proposed Revisions to IETF Trust Administrative Procedures
Date: Wed, 9 Apr 2008 13:50:35 -0400
Message-ID: <0BDFFF51DC89434FA33F8B37FCE363D511F94E4E@zcarhxm2.corp.nortel.com>
In-Reply-To: <BE553BCE544B8A70231137C9@p3.JCK.COM>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Proposed Revisions to IETF Trust Administrative Procedures
Thread-Index: AciaaK8iuhAFdM6fRjCxQBX8eAOIogAACTBg
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>
<405E5ABA-C7C2-4A2A-8840-84A3860443AA@multicasttech.com>
<BE553BCE544B8A70231137C9@p3.JCK.COM>
From: "Ed Juskevicius" <edj@nortel.com>
To: "John C Klensin" <john-ietf@jck.com>
Cc: Leslie Daigle <leslie@thinkingcat.com>, IETF Discussion <ietf@ietf.org>,
Harald Alvestrand <harald@alvestrand.no>
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, you wrote: > Then recommend to the community that the Trust Agreement be changed. The Trustees are not talking about changing the terms of the Trust Agreement, so this should not be necessary. > I am worried about the IAOC and/or Trustees adopting procedures that > are inconsistent with the Trust Agreement. Me too! It is not the intention of the Trustees to adopt procedures that are inconsistent with the Trust Agreement. > if anything is going to be said, it needs to be consistent with the > Trust Agreement _and_ reflect the desires and intent of the community. I agree. Regards, Ed Juskevicius -----Original Message----- From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of John C Klensin Sent: Wednesday, April 09, 2008 1:39 PM To: Marshall Eubanks Cc: Leslie Daigle; Harald Alvestrand; IETF Discussion Subject: Re: Proposed Revisions to IETF Trust Administrative Procedures --On Wednesday, 09 April, 2008 10:24 -0400 Marshall Eubanks <tme@multicasttech.com> wrote: > How, precisely, would the IAOC cease to exist ? Marshall, this is nearly irrelevant. The point is that there is language covering that case in the Trust Agreement and there is language in the procedures developed by the Trustees, and they are not consistent. > 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. Then recommend to the community that the Trust Agreement be changed. If the ability to make this sort of change somehow got negotiated away... well, I guess we live with that, but it is still no reason to have a procedural document inconsistent with the Trust agreement. > > 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. My imagination is paranoid enough to think of at least one more case, but I would suggest that the principle remains and that, were the IETF to abruptly go out of business, the former members of the former IAOC might not be the best people to act as receivers of the Trust and controllers of its remaining assets. Note that, with the way the new IPR documents are drawn, the Trust has some long-term responsibilities to the Internet community whether the IETF exists or not. > (And, of course, > if there is no IETF, there would presumably also be no IESG, so they > could not appoint more.) The Trust Agreement, IIR, says "IESG or its successor". Whether the various arrangements now in place are adequate to designate a successor to the IESG if they and IETF go out of business, I don't know. But I do know that isn't the problem of the Trust or IAOC (although either could make a proposal about what to do about it). > One of the parties of the Trust agreement was worried about this. I am > not. I'm not particularly worried about the conditions that would trigger any of these provisions occurring. I am worried about the IAOC and/or Trustees adopting procedures that are inconsistent with the Trust Agreement. Given what the Trust Agreement says, I don't believe the procedures actually need to say a word on this topic. Not saying a word would be, I believe, consistent with your "worried about then, not now" suggestion. But, if anything is going to be said, it needs to be consistent with the Trust Agreement _and_ reflect the desires and intent of the community. 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
- Proposed Revisions to IETF Trust Administrative P… Ray Pelletier
- Re: Proposed Revisions to IETF Trust Administrati… John C Klensin
- Re: Proposed Revisions to IETF Trust Administrati… Russ Housley
- Re: Proposed Revisions to IETF Trust Administrati… Brian E Carpenter
- Re: Proposed Revisions to IETF Trust Administrati… John C Klensin
- Re: Proposed Revisions to IETF Trust Administrati… Harald Alvestrand
- Re: Proposed Revisions to IETF Trust Administrati… Harald Alvestrand
- Re: Proposed Revisions to IETF Trust Administrati… Brian E Carpenter
- Re: Proposed Revisions to IETF Trust Administrati… Brian E Carpenter
- Re: Proposed Revisions to IETF Trust Administrati… Leslie Daigle
- Re: Proposed Revisions to IETF Trust Administrati… Russ Housley
- Re: Proposed Revisions to IETF Trust Administrati… Fred Baker
- Re: Proposed Revisions to IETF Trust Administrati… Ray Pelletier
- Re: Proposed Revisions to IETF Trust Administrati… John C Klensin
- Re: Proposed Revisions to IETF Trust Administrati… Ray Pelletier
- Re: Proposed Revisions to IETF Trust Administrati… Soininen Jonne (NSN FI/Espoo)
- Re: Proposed Revisions to IETF Trust Administrati… Leslie Daigle
- RE: Proposed Revisions to IETF Trust Administrati… Ed Juskevicius
- Re: Proposed Revisions to IETF Trust Administrati… Russ Housley
- Re: Proposed Revisions to IETF Trust Administrati… Fred Baker
- RE: Proposed Revisions to IETF Trust Administrati… John C Klensin
- Re: Proposed Revisions to IETF Trust Administrati… John C Klensin
- Re: Proposed Revisions to IETF Trust Administrati… Brian E Carpenter
- Re: Proposed Revisions to IETF Trust Administrati… John C Klensin
- Re: Proposed Revisions to IETF Trust Administrati… Marshall Eubanks
- Re: Proposed Revisions to IETF Trust Administrati… John C Klensin
- RE: Proposed Revisions to IETF Trust Administrati… Ed Juskevicius
- RE: Proposed Revisions to IETF Trust Administrati… John C Klensin
- Re: Proposed Revisions to IETF Trust Administrati… Brian E Carpenter
- Re: Proposed Revisions to IETF Trust Administrati… Ray Pelletier
- Re: Proposed Revisions to IETF Trust Administrati… Ted Hardie
- Re: Proposed Revisions to IETF Trust Administrati… John C Klensin
- Re: Proposed Revisions to IETF Trust Administrati… Harald Alvestrand
- Re: Proposed Revisions to IETF Trust Administrati… Marshall Eubanks
- Re: Proposed Revisions to IETF Trust Administrati… Stephan Wenger
- Re: Proposed Revisions to IETF Trust Administrati… Fred Baker
- Re: Proposed Revisions to IETF Trust Administrati… Brian E Carpenter
- Re: Proposed Revisions to IETF Trust Administrati… Ray Pelletier
- Re: Proposed Revisions to IETF Trust Administrati… TS Glassey