Re: Options for IETF administrative restructuring
John C Klensin <john-ietf@jck.com> Thu, 26 August 2004 19:27 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 PAA00082; Thu, 26 Aug 2004 15:27:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0PvV-00041v-Ih; Thu, 26 Aug 2004 15:28:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C0Pnd-0000vm-AC; Thu, 26 Aug 2004 15:20:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C0Pmt-0000P7-WF for ietf@megatron.ietf.org; Thu, 26 Aug 2004 15:19:56 -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 PAA29669 for <ietf@ietf.org>; Thu, 26 Aug 2004 15:19:53 -0400 (EDT)
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C0Pno-0003ut-Vz for ietf@ietf.org; Thu, 26 Aug 2004 15:20:56 -0400
Received: from [127.0.0.1] (helo=localhost) by bs.jck.com with esmtp (Exim 4.34) id 1C0Pmj-000BnU-OV; Thu, 26 Aug 2004 15:19:46 -0400
Date: Thu, 26 Aug 2004 15:19:43 -0400
From: John C Klensin <john-ietf@jck.com>
To: Leslie Daigle <leslie@thinkingcat.com>, Harald Tveit Alvestrand <harald@alvestrand.no>
Message-ID: <98F73353B4C48AD0B7026AB7@as-s2n.inter-touch.net>
In-Reply-To: <412DFEE9.80003@thinkingcat.com>
References: <412DFEE9.80003@thinkingcat.com>
X-Mailer: Mulberry/3.1.6 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
Subject: 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.0 (/)
X-Scan-Signature: 92df29fa99cf13e554b84c8374345c17
Content-Transfer-Encoding: 7bit
Leslie and Harald, I would like to make one suggestion about this process. For suggestions about substance, I will, of course, wait for the final -00 version of the draft. This note is deliberately being sent before I have done so because I don't want my remarks to be biased by how I feel about its specific content. There was considerable confusion in San Diego, and earlier, induced by large numbers of sub-discussions, with different, sometimes designated, groups of people holding discussions and not having access to each other's comments. Harald responded to comments about this during the plenary by indicating that, once the draft was posted, everything would be public. So I would like to suggest that any discussions within or among the IAB and IESG, or subsets of them, or between them and other groups, take place on mailing lists whose archives are public and/or which can be subscribed to (even if only on a read-only basis) by interested members of the community. The key strategic decisions here (as distinct from the fine details) have to be made with the informed consent of the IETF community. To me, that implies that all of the options and their pros and cons have to be on the table: after the fact, there should not be even a suspicion that the choice was influenced by discussions of only a reduced set of options. I note in particular that your first "next step" reads "Have a public discussion on the IETF list on the options presented in the draft". I think that is exactly correct iff the community is reasonably assured that _all_ of the plausible options have been identified, and fairly described, in the draft. I hope and trust that is the case, but any suspicions, engendered by private discussion, that some options have been excluded from discussion by excluding them from the draft, would be extremely harmful and should be avoided. As you said, we need to take the time to get this right. We also need to be sure that the community emerges from the process confident that all of the options have been fairly considered in the process of selecting the right one. thanks, john --On Thursday, August 26, 2004 11:16 AM -0400 Leslie Daigle <leslie@thinkingcat.com> wrote: > [This is a re-send of a message I sent last night; that > message is >... > Hello, IETF community. > > Attached is the document we promised you in San Diego - a > report from > our consultant, Carl Malamud, which lays out a series of > options and > recommendations for moving forward with the IETF administrative > restructuring process, according to the recommendations laid > out in RFC3716 (the Advisory Committee report). It has been > submitted to the Internet Drafts repository and should be >... _______________________________________________ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
- Options for IETF administrative restructuring Leslie Daigle
- Re: Options for IETF administrative restructuring John C Klensin
- Options for IETF administrative restructuring Leslie Daigle
- Re: Options for IETF administrative restructuring Leslie Daigle
- Re: Options for IETF administrative restructuring Paul Vixie
- Re: Options for IETF administrative restructuring JORDI PALET MARTINEZ
- Venue selection (Re: Options for IETF administrat… Harald Tveit Alvestrand
- Re: Venue selection (Re: Options for IETF adminis… Iljitsch van Beijnum
- Re: Venue selection (Re: Options for IETF adminis… JORDI PALET MARTINEZ
- RE: Options for IETF administrative restructuring Christian de Larrinaga
- Re: Venue selection (Re: Options for IETF adminis… Michael Richardson
- RE: Options for IETF administrative restructuring Harald Tveit Alvestrand
- Re: Options for IETF administrative restructuring Brian E Carpenter
- What to incorporate (Re: Options for IETF adminis… Harald Tveit Alvestrand
- RE: What to incorporate (Re: Options for IETF adm… Christian de Larrinaga
- Re: What to incorporate (Re: Options for IETF adm… Brian E Carpenter
- Re: What to incorporate (Re: Options for IETF adm… Susan Harris
- Re: What to incorporate (Re: Options for IETF adm… Carl Malamud
- Re: What to incorporate (Re: Options for IETF adm… Susan Harris
- Re: What to incorporate (Re: Options for IETF adm… Leslie Daigle
- Re: What to incorporate (Re: Options for IETF adm… Dean Anderson
- Re: What to incorporate (Re: Options for IETF adm… Dean Anderson
- Re: What to incorporate (Re: Options for IETF adm… Harald Tveit Alvestrand
- Re: What to incorporate (Re: Options for IETF adm… scott bradner
- Re: What to incorporate (Re: Options for IETF adm… Adrian Farrel
- Re: Options for IETF administrative restructuring scott bradner
- Re: What to incorporate (Re: Options for IETF adm… avri
- RE: Options for IETF administrative restructuring Wijnen, Bert (Bert)
- RE: Options for IETF administrative restructuring Steve Crocker
- Budget numbers (Re: What to incorporate) Harald Tveit Alvestrand
- Legal umbrella etc (Re: What to incorporate) Harald Tveit Alvestrand
- Re: Legal umbrella etc (Re: What to incorporate) Dean Anderson
- Re: What to incorporate (Re: Options for IETF adm… Brian E Carpenter
- Re: Options for IETF administrative restructuring Aaron Falk
- RE: Options for IETF administrative restructuring Wijnen, Bert (Bert)
- RE: Options for IETF administrative restructuring graham.travers
- RE: Options for IETF administrative restructuring Margaret Wasserman
- Re: Options for IETF administrative restructuring Eliot Lear
- RE: Options for IETF administrative restructuring graham.travers
- Re: Options for IETF administrative restructuring Brian E Carpenter
- Re: Options for IETF administrative restructuring avri
- RE: Options for IETF administrative restructuring John C Klensin
- Re: Options for IETF administrative restructuring Pete Resnick
- Explosive bolts [Re: Options for IETF administrat… Brian E Carpenter
- Re: Options for IETF administrative restructuring Brian E Carpenter
- Re: Options for IETF administrative restructuring avri
- Re: Options for IETF administrative restructuring Margaret Wasserman
- Re: Explosive bolts [Re: Options for IETF adminis… Pete Resnick
- Re: Explosive bolts [Re: Options for IETF adminis… scott bradner
- Re: Options for IETF administrative restructuring Sam Hartman
- Re: Explosive bolts [Re: Options for IETF adminis… Paul Vixie
- Re: Explosive bolts [Re: Options for IETF adminis… Carl Malamud
- Re: Options for IETF administrative restructuring Aaron Falk
- Re: Options for IETF administrative restructuring Sam Hartman
- Re: Options for IETF administrative restructuring Leslie Daigle
- RE: Options for IETF administrative restructuring Steve Crocker
- RE: Options for IETF administrative restructuring Fred Baker
- Re: Explosive bolts [Re: Options for IETF adminis… Brian E Carpenter
- Re: Explosive bolts [Re: Options for IETF adminis… John C Klensin
- Re: Explosive bolts [Re: Options for IETF adminis… Harald Tveit Alvestrand
- Re: Explosive bolts [Re: Options for IETF adminis… Lynn St.Amour
- There is no proposal on the table for *IETF* inco… Pete Resnick
- Re: There is no proposal on the table for *IETF* … Margaret Wasserman
- Re: There is no proposal on the table for *IETF* … Lynn St.Amour
- Re: Options for IETF administrative restructuring John C Klensin
- ISOC board meeting comes AFTER IETF meeting this … Steve Crocker