Re: What to incorporate (Re: Options for IETF administrative restructuring)

avri@psg.com Fri, 03 September 2004 16:00 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07820; Fri, 3 Sep 2004 12:00:50 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C3GXG-0002tM-Ug; Fri, 03 Sep 2004 12:03:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C3GRt-0001mW-CZ; Fri, 03 Sep 2004 11:58:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C3GOz-00014F-8X for ietf@megatron.ietf.org; Fri, 03 Sep 2004 11:55:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07572 for <ietf@ietf.org>; Fri, 3 Sep 2004 11:54:59 -0400 (EDT)
From: avri@psg.com
Received: from tla.crepundia.net ([194.71.127.149] helo=report.tla-group.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C3GRb-0002l0-F6 for ietf@ietf.org; Fri, 03 Sep 2004 11:57:44 -0400
Received: from [127.0.0.1] (report.tla-group.com [194.71.127.149]) by report.tla-group.com (8.12.4/8.12.4) with ESMTP id i83Fb0eq016720 for <ietf@ietf.org>; Fri, 3 Sep 2004 17:37:48 +0200
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <4136FFFB.4000300@zurich.ibm.com>
References: <OLEPILDGDKGAPONGCBEOCEKOCHAA.cdel@firsthand.net> <4136FFFB.4000300@zurich.ibm.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <9A945FCA-FDC1-11D8-B019-000393CC2112@psg.com>
Content-Transfer-Encoding: 7bit
Date: Fri, 03 Sep 2004 11:54:57 -0400
To: ietf@ietf.org
X-Mailer: Apple Mail (2.619)
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit
Subject: Re: What to incorporate (Re: Options for IETF administrative restructuring)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: 7bit

On 2 sep 2004, at 07.11, Brian E Carpenter wrote:

>> Yes that would be helpful.
>
> Well, I don't agree. I think it would defocus the discussion (which
> is about putting the IETF's administration onto a business-like
> basis). IMHO the only case in which we should discuss the wider
> option is if the newtrk WG proposes changes in the standards process
> that would make such a thing necessary.

I guess I don't understand this comment.

As I see it, one reason for another option would have to do with the 
independence of the IETF to change its processes, should it want to.  
Not necessarily because it has a plan today to do so.

One of the concerns I have over the ISOC dependent mechanisms, which I 
guess is all of the presented options, is the link between budgeting 
and process.  If a process change requires a different form of 
budgeting support, would the IETF need the approval of ISOC to make 
that change?  Often what seems like a purely technical decision has 
policy and budgetary implications.  Assuming that we don't want to have 
reconsider the organizational relationship again in the near future, I 
believe we need to take such possibilities into account.

I think another consideration in making these administrative decisions 
has to do with the IETF's voice in the general standards and Internet 
governance arena.  Will ISOC, as a 'parent' organization - my 
interpretation of the options that are offered, be the responsible 
party for such activities?  E.g. currently for a liaison to the ITU, it 
is ISOC that is the liaison association.  Should ISOC disagree with the 
IETF position on a liaison matter who has the final say?  Likewise with 
the ongoing governance debate in the international arena, will ISOC or 
the IETF be the negotiating body?  And before we decide that this is 
just policy and does not relate to protocol issues, we should not 
ignore the intimate link between policy and technical - while it is not 
always direct, there generally is a technical implication in policy 
decisions and, generally,  also a policy impact in technical decisions. 
Basically I am concerned about the real independence of the IETF as a 
technical standards body when ISOC, which the IETF does not control, 
has the governing policy and financial voice.

I would be interested in seeing an analysis of an option which has the 
IETF as a independent nonprofit corporate entity.  This could be either 
as a wholly owned subsidiary of ISOC, thus keeping the fiduciary 
relationship, or as completely independent organization.

a.



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf