Re: draft-klensin-nomcom-term-00.txt

Ralph Droms <rdroms@cisco.com> Wed, 27 July 2005 15:12 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dxna0-0004lq-PW; Wed, 27 Jul 2005 11:12:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DxnZy-0004kz-Ek for ietf@megatron.ietf.org; Wed, 27 Jul 2005 11:12:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06065 for <ietf@ietf.org>; Wed, 27 Jul 2005 11:12:15 -0400 (EDT)
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dxo5C-000071-Sg for ietf@ietf.org; Wed, 27 Jul 2005 11:44:38 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-2.cisco.com with ESMTP; 27 Jul 2005 11:12:06 -0400
X-IronPort-AV: i="3.95,146,1120449600"; d="scan'208"; a="64148471:sNHT31837468"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j6RFC6Vu017010; Wed, 27 Jul 2005 11:12:06 -0400 (EDT)
Received: from xmb-rtp-211.amer.cisco.com ([64.102.31.118]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 27 Jul 2005 11:12:06 -0400
Received: from 161.44.65.128 ([161.44.65.128]) by xmb-rtp-211.amer.cisco.com ([64.102.31.118]) via Exchange Front-End Server email.cisco.com ([64.102.31.38]) with Microsoft Exchange Server HTTP-DAV ; Wed, 27 Jul 2005 15:12:06 +0000
Received: from localhost.localdomain by email.cisco.com; 27 Jul 2005 11:12:48 -0400
From: Ralph Droms <rdroms@cisco.com>
To: Brian E Carpenter <brc@zurich.ibm.com>
In-Reply-To: <42E78869.5020106@zurich.ibm.com>
References: <12ab01c5922f$e6f5bdf0$4b087c0a@DFNJGL21> <42E78869.5020106@zurich.ibm.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: Wed, 27 Jul 2005 11:12:47 -0400
Message-Id: <1122477168.27735.13.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.4 (2.0.4-2)
X-OriginalArrivalTime: 27 Jul 2005 15:12:06.0398 (UTC) FILETIME=[8D1E61E0:01C592BD]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88
Content-Transfer-Encoding: 7bit
Cc: IETF General Discussion Mailing List <ietf@ietf.org>
Subject: Re: draft-klensin-nomcom-term-00.txt
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

Brian - while I haven't thought through all of the implications of the
process in draft-klensin-nomcom-term-00.txt, I don't think the two-stage
process will necessarily significantly length then process.  The
proposed process would require re-shuffling of of specific tasks, but I
don't think it fundamentally adds any new work to the work in the
current process.  There are serialization and dependency timing issues,
but I think there is also some work that might be eliminated from the
current process.

The proposed process might also provide some time saving by
compartmentalizing the decision process - my intuition from recent
experience on nomcom is that some of the deliberation might have gone
more quickly if we had teased apart retention from nomination.

And some of the decision process would go away in the case of ADs who
have reached their term limits.

- Ralph

On Wed, 2005-07-27 at 15:13 +0200, Brian E Carpenter wrote:
> Spencer,
> 
> I haven't fully analyzed the proposal yet, so I will refrain from
> substantive comment.
> 
> However, in answer to your question, I'm sure the answer is no,
> because the two-stage process suggested in the draft will add a
> significant number of weeks to the process, and we would almost
> certainly have to start about two months earlier. I haven't done
> a detailed analysis of the timeline, but I'm pretty sure we
> couldn't make it this year. And that's assuming we reached consensus
> very rapidly.
> 
>      Brian
> 
> Spencer Dawkins wrote:
> > This draft (available at
> > http://www.ietf.org/internet-drafts/draft-klensin-nomcom-term-00.txt)
> > does a reasonable job of balancing between current-generation leadership 
> > continuity and next-generation leadership development.
> > 
> > I have previously expressed the opinion that an absolute prohibition on 
> > four terms of continuous service would be preferable, but the 
> > flexibility granted to NOMCOM in this proposal is acceptable (and I 
> > could be wrong).
> > 
> > The current IETF is a better place because of several I* members who 
> > have returned to the community - they are providing strong technical 
> > leadership, without dots on badges. Honorable retirement after honorable 
> > service on IESG or IAB is not a bad thing.
> > 
> > If I read RFC 3777 correctly, we will be assembling the next NOMCOM very 
> > soon ("at least two months before the Third IETF"). So, I'm wondering...
> > 
> > If there is community consensus that this draft proposes something 
> > reasonable, would we give the draft to the incoming NOMCOM as part of 
> > their instructions and perform a BCP 93 process experiment?
> > 
> > Spencer
> > 
> > 
> > _______________________________________________
> > Ietf mailing list
> > Ietf@ietf.org
> > https://www1.ietf.org/mailman/listinfo/ietf
> > 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf

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