Re: NomCom procedures revision

Harald Alvestrand <harald@alvestrand.no> Sun, 30 August 2015 09:36 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B19241B3453 for <ietf@ietfa.amsl.com>; Sun, 30 Aug 2015 02:36:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aK3c0p4cCyHQ for <ietf@ietfa.amsl.com>; Sun, 30 Aug 2015 02:36:22 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) by ietfa.amsl.com (Postfix) with ESMTP id 2B8D81B344F for <ietf@ietf.org>; Sun, 30 Aug 2015 02:36:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 1E50C7C38C1 for <ietf@ietf.org>; Sun, 30 Aug 2015 11:36:20 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DvZmlWaMKW6j for <ietf@ietf.org>; Sun, 30 Aug 2015 11:36:18 +0200 (CEST)
Received: from [IPv6:2001:470:de0a:27:c547:ad93:ceb8:de8e] (unknown [IPv6:2001:470:de0a:27:c547:ad93:ceb8:de8e]) by mork.alvestrand.no (Postfix) with ESMTPSA id AC7617C3823 for <ietf@ietf.org>; Sun, 30 Aug 2015 11:36:18 +0200 (CEST)
Message-ID: <55E2CE92.5010002@alvestrand.no>
Date: Sun, 30 Aug 2015 11:36:18 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.8.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: NomCom procedures revision
References: <CAL0qLwYJzFZT=OgWqiiTw-n6mvb3PPusRtArmPs_d4_qpLfmpg@mail.gmail.com> <55E0D5E5.6030802@gmail.com> <55E1714C.6070602@pi.nu> <55E21442.3030008@gmail.com> <46DC3DDD2AB9558580D99D5B@JcK-HP8200.jck.com>
In-Reply-To: <46DC3DDD2AB9558580D99D5B@JcK-HP8200.jck.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/VEYbIa2uxIsV8fYIb9KIvjKRSAo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 30 Aug 2015 09:36:24 -0000

Den 30. aug. 2015 01:05, skrev John C Klensin:
> 
> 
> --On Sunday, August 30, 2015 08:21 +1200 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
> 
>> ...
>> I'm sympathetic to both your points, but I'm also keen to keep
>> the rule as simple as possible, for various reasons (especially
>> simplicity in verification).
>>
>> One way out is to decouple this question from RFC7437bis by
>> designing an RFC3933 Process Experiment (i.e. try out an
>> alternative qualification rule for a couple of years,
>> reverting to the current rule afterwards by default).
> 
> This may be too radical but, in the spirit of allowing people to
> apply discretion, let me success such a process experiment based
> on the principle that the reason for Nomcom-volunteer
> qualification rules is to be sure that the selecting members of
> the Nomcom have a reasonable understanding of the IETF and how
> it works.   For the purpose of this experiment, 
> 
> (1) Anyone meeting the current requirements is automatically
> qualified to volunteer, just as they are today.
> 
> (2) Anyone inclined to serve on the Nomcom and willing to meet
> whatever requirements for attendance and participation during
> the Nomcom's term apply for the Nomcom of interest may submit
> his or her name and a very brief statement of qualifications
> (or, more specifically, why they believe they are qualified) to
> the Nomcom Chair.   The Chair and previous Chair will consider
> all such applications and may, based on their personal
> discretion and the "reasonable understanding" principle may be
> added to the volunteer pool.  When the Chair publishes the list
> of volunteers, those who submitted a statement of qualifications
> will be included along with their statements and the decision of
> the Chair and prior Chair.  Egregiously silly decisions may be
> objected to following the usual procedures.
> 
> That experimental model has three important properties: it
> involves no new filtering rules, it may allow some people onto
> the Nomcom whom everyone would agree have an adequate knowledge
> of the IETF but who do not qualify on meeting counts alone, and
> it allows us to accumulate information about who actually
> volunteers and asks for an exception and what their claimed
> qualifications are.  Put differently, it may help us tell
> whether we have an actual problem or only a theoretical one.

FWIW... the last nomcom selection process had 183 qualified volunteers.

A further 14 volunteered, confirmed their volunteering, and were found
not to be qualified (I believe some were conflicted, but I think most
lost on the attendance count).

A further 120 ticked the nomcom box on an attendance form, were found to
be unqualified, and did not respond to the confirmation query. I'm
wondering about those.

I'd assume the 14 (minus the conflicts) were people who might consider
sending in an application as suggested.
So that's a minimum number - if the "application" path were known, we'd
expect more.

Harald