Re: Updating BCP 10 -- NomCom ELEGIBILITY

"Murray S. Kucherawy" <> Thu, 12 February 2015 06:23 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id A28A81A904F for <>; Wed, 11 Feb 2015 22:23:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 N6Z6Q12tZJBO for <>; Wed, 11 Feb 2015 22:23:33 -0800 (PST)
Received: from ( [IPv6:2a00:1450:400c:c03::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4E2141A9067 for <>; Wed, 11 Feb 2015 22:23:33 -0800 (PST)
Received: by with SMTP id m14so2047831wev.8 for <>; Wed, 11 Feb 2015 22:23:32 -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=+n6gRWaFZ0iAvy+xR4thU645EcstNrcTx2Z2pZjlCL8=; b=V/WF38KyI3lQR64xP2B33wMo2bJJuToF6f569Y2vrbxkodfaRZUWUw+NkUK7tHjl9i b6KalJwJh4XEXYCSF2sU5bmj4UhLJ09mu1DbvqBeg8Xow/3pDTxnZ0heAxAjJP27T9mH RfLAbU6ufgBaVIS0SmJh3ik2Mtd/Z3Tfsnu3/9HTOrJXPqMRBArF/04L0OfINAhs2mCa A5BrsmsocVDqUxyTeG8bCntDmF0ksK09eZiyOuDfuPpHZB2JxkaTm7dAAXHJH4JEQz5y cD+IlThuOnGZr0250SYqliOT+3WOKxHZnLsgTSjUykUw48lg14Oenaf+fs4evokmK/vn F9Kg==
MIME-Version: 1.0
X-Received: by with SMTP id lu19mr3084939wic.52.1423722212046; Wed, 11 Feb 2015 22:23:32 -0800 (PST)
Received: by with HTTP; Wed, 11 Feb 2015 22:23:31 -0800 (PST)
In-Reply-To: <>
References: <> <> <> <> <> <>
Date: Wed, 11 Feb 2015 22:23:31 -0800
Message-ID: <>
Subject: Re: Updating BCP 10 -- NomCom ELEGIBILITY
From: "Murray S. Kucherawy" <>
To: Michael Richardson <>
Content-Type: multipart/alternative; boundary=001a11c3a6b8b53cb4050ede28a8
Archived-At: <>
Cc: 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 06:23:35 -0000

On Wed, Feb 11, 2015 at 7:10 PM, Michael Richardson <>

> I'm confused how you came up with four years.

You said:

Once eligible, the rules for remaining eligible would be different.
I would propose something like having *contributed* to at least two
meetings in the past four

...and I remembered "years" instead of "meetings" for some reason.  Still,
the things you suggested as qualifying contributions don't account for some
other things that I would argue should qualify.  For instance:  Requiring
that I be the submitting author on a document that got WG time disregards
valuable documents that never needed in-person WG time.  The same goes for
the point about opening a ticket against a document that got WG time.

Even better, contributing to the IETF in meaningful ways is not always tied
to meetings.  Some working group chairs and editors do great work for WGs
that never even meet.  Nothing ever gets agenda time in those.

The speed with which something gets to AUTH48 isn't always reliable.  I'm
not sure making that a gating factor would work so well; I could lose my
eligibility just because some directorate review took way too long to come

To repeat: I recognize that we like the general idea here, and I agree.
I'm just having trouble coming up with ways to qualify that aren't
difficult to describe precisely and completely and don't needlessly exclude
people that probably should qualify.