Re: IETF Administrative Reorganization: What was that problem anyway?
Aaron Falk <falk@ISI.EDU> Wed, 15 September 2004 01:16 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 VAA13848; Tue, 14 Sep 2004 21:16:17 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C7OUE-0006c6-8q; Tue, 14 Sep 2004 21:21:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C7OCu-0004Av-Jz; Tue, 14 Sep 2004 21:03:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C7NtK-0004mY-Ko for ietf@megatron.ietf.org; Tue, 14 Sep 2004 20:43:22 -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 UAA09060 for <ietf@ietf.org>; Tue, 14 Sep 2004 20:43:21 -0400 (EDT)
Received: from vapor.isi.edu ([128.9.64.64]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C7NyL-0005F5-9w for ietf@ietf.org; Tue, 14 Sep 2004 20:48:33 -0400
Received: from [128.9.168.79] (nak.isi.edu [128.9.168.79]) by vapor.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i8F0gVQ09709; Tue, 14 Sep 2004 17:42:31 -0700 (PDT)
In-Reply-To: <1BAA2A8E7E650C991C575C8D@scan.jck.com>
References: <1BAA2A8E7E650C991C575C8D@scan.jck.com>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <1FCC9142-06B0-11D9-BEF0-000A95DBDB84@isi.edu>
Content-Transfer-Encoding: 7bit
From: Aaron Falk <falk@ISI.EDU>
Date: Tue, 14 Sep 2004 17:42:30 -0700
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.619)
X-ISI-4-32-5-MailScanner: Found to be clean
X-MailScanner-From: falk@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: Re: IETF Administrative Reorganization: What was that problem anyway?
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.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Content-Transfer-Encoding: 7bit
John- Thanks for your note. A good reset of the discussion, IMO. Some chiming in and a question below... On Sep 14, 2004, at 2:12 PM, John C Klensin wrote: We have > exactly two problems: > > (1) For a number of policy and budgetary reasons, having two > revenue sources that have to be kept isolated from each > other lies on a scale between "suboptimal" and "nuts". > > (2) The IESG perceives that they are not getting adequate > support for their work, and the standards process more > generally, from the Secretariat and that, despite > considerable effort, there has been little progress on > solving that problem. Yes, my understanding as well. > And the guarantee of responsiveness, in _any_ organizational > structure in which administrative/financial management are > separated from standards management, lies in mutual trust and > mutual understanding of goals and objectives, not in > discussions of, e.g., who can blow whose bolts. strongly agree. > The question, then, is whether we can devise a scenario that > addresses the critical path questions without inventing any > more administrative structure than needed, without depending on > unreasonable expectations of the skills of the IETF _technical_ > leadership, and without compromising the apparent and actual > independence and ability of the IETF to develop good technical > standards without undue influence from funding sources. Agreed. > To reprise, the criteria for that alternative administrative > organizational structure should include: > > (i) The IETF volunteer (standards process) leadership and, > for that matter, anyone with responsibility for steering > the standards process, is at arms-length from financial > dealings with particular donors who might be assumed to be > influencing the IETF's standards process. > > (ii) Nomcom appointments to IETF volunteer technical/ > standards process leadership positions are not expected to > require that candidates have significant administrative > or financial skills, nor are candidates expected to acquire > those skills on appointment. > > (iii) We put as much IETF energy into organization-creation > as is actually needed to solve identifiable and real > problems, and no more. In particular, we don't try to > create elaborate structures to handle hypothesized problems > that have not occurred and probably will never occur, nor > do we try to use IETF Administration as a way to develop > and carry out unnecessary social experiments. > > john > So, from this I guess you don't like scenarios C & D? :) Does this mean you do like scenarios A & B? Or are you suggesting that some other as-yet-unspecified solution will meet criteria (i) - (iii) above and solve problems (1) & (2)? --aaron _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- IETF Administrative Reorganization: What was that… John C Klensin
- Re: IETF Administrative Reorganization: What was … Aaron Falk
- Re: IETF Administrative Reorganization: What was … Carl Malamud
- Re: IETF Administrative Reorganization: What was … John C Klensin
- Re: IETF Administrative Reorganization: What was … Carl Malamud
- Re: IETF Administrative Reorganization: What was … John C Klensin
- Re: IETF Administrative Reorganization: What was … avri