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

"Richard Draves" <richdr@microsoft.com> Thu, 28 July 2005 20:36 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DyF6q-0004Ux-9F; Thu, 28 Jul 2005 16:36:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DyF6n-0004Uh-Ty for ietf@megatron.ietf.org; Thu, 28 Jul 2005 16:36:01 -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 QAA27341 for <ietf@ietf.org>; Thu, 28 Jul 2005 16:35:59 -0400 (EDT)
Received: from mail2.microsoft.com ([131.107.3.124]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DyFcH-00013p-Ui for ietf@ietf.org; Thu, 28 Jul 2005 17:08:37 -0400
Received: from mailout2.microsoft.com ([157.54.1.120]) by mail2.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 28 Jul 2005 13:35:46 -0700
Received: from RED-MSG-31.redmond.corp.microsoft.com ([157.54.47.231]) by mailout2.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 28 Jul 2005 13:35:46 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 28 Jul 2005 13:36:06 -0700
Message-ID: <5C611EA73500FE4C908733811F670B4508353E9B@RED-MSG-31.redmond.corp.microsoft.com>
Thread-Topic: draft-klensin-nomcom-term-00.txt
Thread-Index: AcWTnThp2lu9XHqpShuAABjxQ/WPSQAFH7GQ
From: Richard Draves <richdr@microsoft.com>
To: ietf@ietf.org
X-OriginalArrivalTime: 28 Jul 2005 20:35:46.0903 (UTC) FILETIME=[EF0E0670:01C593B3]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: quoted-printable
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

[I'm sorry to be joining this discussion late.]

I see several different goals in John's draft:
1. Setting guidelines for length of service.
2. Early notification to incumbents.
3. Reducing the nomcom's workload.

I think giving the nomcom more guidance about appropriate length of
service is a fine thing. (And I tend to agree that service beyond three
terms should be unusual.) Having a generally-recognized length of
service would help generate candidates to replace a well-regarded AD who
has served several terms.

I think announcing early decisions regarding incumbents is not good. I
think there's great value in looking at the slate of candidates as a
whole. I don't like the idea of making a decision about an incumbent
without seeing the pool of potential replacements.

The goal of simplifying life for the nomcom is laudable, but in fact if
an AD incumbent is doing a good job, there are generally very few
credible & willing alternatives for the job so it doesn't take many
cycles to sort out the situation. So I don't think this proposal would
reduce the nomcom's workload.

Rich

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