Re: Updating BCP 10 -- NomCom ELEGIBILITY

"Murray S. Kucherawy" <> Thu, 12 February 2015 00:05 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 9EDB01A1BDF for <>; Wed, 11 Feb 2015 16:05:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id bR7wQV3YkGDF for <>; Wed, 11 Feb 2015 16:05:23 -0800 (PST)
Received: from ( [IPv6:2a00:1450:400c:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 46D201A1BDE for <>; Wed, 11 Feb 2015 16:05:23 -0800 (PST)
Received: by with SMTP id h11so424677wiw.1 for <>; Wed, 11 Feb 2015 16:05:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=W8b5J2g73zhIFGonKGOuxXWGE0GgjhKjZg6748PtN1Y=; b=LKKgAYl+rshn5o6A39QrrEajsCEygAL/UD3t3um8gorUZbQ83Bx5jvsk2S1DL4AOhN 6MTCCfWAcByNWj358mPd2l19hS8WJ2jUactx6Oubi+lh1nXeSuVVQo8Ic7SfPrthWuMs duBNTjR0ykiK1BznEclAVXQIuQfYdrIWBzvIlIa3WV0Yxk5vp4HjRzFVWVlMHa0vUUTm R6yL95aOwTyO2FZSQvZP5DliLeCP9HnOatJID6PCnjNJYaXjo3hiWCF0lP4OeFOrFeXZ 7daKSPUTKuvUf3ZycAbXqJlgk1A5t2nxn9mZUK9/kBj0zLIA9uuY/N9p4UhvTLl77z3H WRBQ==
MIME-Version: 1.0
X-Received: by with SMTP id ja10mr935529wic.52.1423699521905; Wed, 11 Feb 2015 16:05:21 -0800 (PST)
Received: by with HTTP; Wed, 11 Feb 2015 16:05:21 -0800 (PST)
In-Reply-To: <>
References: <> <> <> <> <> <>
Date: Wed, 11 Feb 2015 16:05:21 -0800
Message-ID: <>
Subject: Re: Updating BCP 10 -- NomCom ELEGIBILITY
From: "Murray S. Kucherawy" <>
To: Joel Halpern <>
Content-Type: multipart/alternative; boundary=047d7b62498c4529ac050ed8e0aa
Archived-At: <>
Cc: Michael Richardson <>, ietf <>
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 12 Feb 2015 00:05:28 -0000

On Wed, Feb 11, 2015 at 2:26 PM, Joel Halpern <> wrote:

> I am starting to sympathize with Mike.  What is our goal here.
> Expanding the nomcom pool with folks who may be contributing but do not
> have visibility to how things are working does not seem to help us.
> [...]

There was plenty of support for, and no objection to, the idea of relaxing
how one remains eligible after becoming eligible.  It's the mechanics of
this that seem to be the problem.  It's exacerbated by the fact that it's
hard to evaluate programmatically one's contributions other than purely by
counting them.

I could be WG chair of a WG that exists for five years, but never meets and
rarely produces anything.  The datatracker shows me as a co-chair all that

I could be a WG co-chair for ten years where my co-chair does all the work
and I am but a well-liked slacker.  The datatracker still shows me as a
co-chair all that time.

I could be editor of a major RFC along with others, one that takes years to
get to publication, and my only contribution was to write one major
paragraph that's unchanged since the -00 version years ago.  Still, my name
is front page on a standards track RFC.

I could scribe for the IAOC every time and do absolutely nothing else.
This gives me depth on one topic, but no breadth on any other, yet I can
still claim scribe credits.

I could have the same count of WG chairships, documents, scribings, etc.,
as someone else, but still have a frighteningly poor understanding of how
the IETF operates compared to that other person because I skate by in terms
of my contribution while the other person is fully involved.  However,
numerically, we are equivalent.

etc. etc.

As has been observed, any rule we define here can be gamed.  If we want to
solve for this, the problem then is that evaluating each case claiming
qualification now puts a burden on the Chair, or the Secretariat, or
someone else, to decide which claims "count" and which don't, and be able
to support that evaluation.  If I may invoke some grade school rhetoric:
"Not it!"

On the other hand, maybe we should remember that these are merely the
criteria to get into the pool of potential volunteers.  It doesn't land you
a NomCom slot; you still have to get randomly selected.  So maybe the
percentage of people that skate by as described above will generally be low
enough that we shouldn't let perfect be the enemy of the good.

And if it seriously doesn't work, we can always change it again.  I'll bet
it would be at most one NomCom cycle before a terrible selection process
gets replaced.