Re: Updating BCP 10 -- NomCom ELEGIBILITY

Michael Richardson <> Wed, 18 February 2015 01:35 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 16D661A87C8 for <>; Tue, 17 Feb 2015 17:35:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id iwuU0pd0DHZ2 for <>; Tue, 17 Feb 2015 17:35:38 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B66111A87BE for <>; Tue, 17 Feb 2015 17:35:38 -0800 (PST)
Received: from ( [IPv6:2607:f0b0:f:2::247]) by (Postfix) with ESMTP id 32F73203C9 for <>; Tue, 17 Feb 2015 20:43:26 -0500 (EST)
Received: by (Postfix, from userid 179) id 2F45A63A21; Tue, 17 Feb 2015 20:35:37 -0500 (EST)
Received: from (localhost []) by (Postfix) with ESMTP id 18019637F5 for <>; Tue, 17 Feb 2015 20:35:37 -0500 (EST)
From: Michael Richardson <>
To: ietf <>
Subject: Re: Updating BCP 10 -- NomCom ELEGIBILITY
In-Reply-To: <>
References: <> <> <> <> <> <> <> <> <> <> <> <> <>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 17 Feb 2015 20:35:37 -0500
Message-ID: <>
Archived-At: <>
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: Wed, 18 Feb 2015 01:35:41 -0000

Murray S. Kucherawy <> wrote:
    > On Fri, Feb 13, 2015 at 10:10 AM, Melinda Shore
    > <> wrote:

    >> On 2/13/15 8:44 AM, Dave Cridland wrote: > Moreover, if you accept
    >> that the word "culture" is effectively > indistinguishable to
    >> outsiders from the term "status quo" (though the > intent is obviously
    >> different), it's really quite revealing. All this > "preserving the
    >> culture" talk comes out in an entirely different light.
    >> I think this is a really important comment.  I mean, *really*
    >> important comment.

    > Bringing us back to the draft under discussion:

    > It sounds to me like our policies and tools around remote participation
    > haven't evolved yet to the point where we can set down some serious
    > NomCom eligibility criteria different from what's there now.  By that
    > I'm not in any way saying that these aren't important things to sort
    > out, just that it's not possible at the moment to come to consensus on
    > what exact changes we should make.

    > I suppose another way to look at that is: I have no idea what to write
    > in terms of replacement text for the current Section 4.14 of BCP 10
    > that reflects a consensus here.  Does anyone else want to take a stab
    > at it?

I've been super-busy on a dozen fronts, but I've been reading every message
on this thread.  I don't know if it is urgent get this text done this week.

I might propose that we ask for a BOF; but an in-person discussion would be
self-selecting.  It might be that having a virtual interim meeting after
Dallas would make more sense.   What if we had some kind of remote attendee summit?

I don't think that the quality of the tools or the question of fee or not
should prevent us from considering if there is a way to change the manner in
which ones remains eligible.  As written, I don't think that Dave Cridland
would ever become eligible again (since that would still be 3/5), nor, I
think were he already eligible, that he'd remain so, because you still have
to attend 1 meeting/year to remain eligible.

{It has become clear to me in thinking about this, that we need to make sure
we figure out when we measure properly}

Michael Richardson <>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-