Re: NomCom procedures revision

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 29 August 2015 20:21 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 18D201B40CB for <ietf@ietfa.amsl.com>; Sat, 29 Aug 2015 13:21:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] 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 t_hv73rQfElN for <ietf@ietfa.amsl.com>; Sat, 29 Aug 2015 13:21:34 -0700 (PDT)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F8DD1B40C8 for <ietf@ietf.org>; Sat, 29 Aug 2015 13:21:34 -0700 (PDT)
Received: by pacdd16 with SMTP id dd16so96333553pac.2 for <ietf@ietf.org>; Sat, 29 Aug 2015 13:21:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=5oQG8zWRffklCbguCsOG84wuyoyLhGjD4Y8uIWe+89Y=; b=wHSBwbL+vXZyN9Fzp9P1yLcc7WMffAOmBvTeAlnBxMwX2UK3raSjApRQO+Yhc/XJUn joYd5UkYdNCcjlebCGlsb2skIZFlvz10bmRtK5ZIecJrH62pVlhQTCPm48NPiFUFfQon KSqdRQw+K39YQa5f8R3sQ+DqAUiBaY7sfk08uvZsVQqxqN6aDIY78ySloKcFGZe0Wu5+ /uJfhCBrOEn4tFNTBupN/cCHCel4Je5oP/MQttrnVq08iLyO3y6rG+iaN+9AQQcXLqAU eo05DAKuDJaLF76TYsa442IjhuRSyJscOqwmTjDpVJ1cPoyGysFx8zJtG1t5vk2KFgeE Ng1Q==
X-Received: by 10.67.15.66 with SMTP id fm2mr568496pad.82.1440879692664; Sat, 29 Aug 2015 13:21:32 -0700 (PDT)
Received: from [172.27.6.155] ([131.203.238.122]) by smtp.gmail.com with ESMTPSA id em1sm9481521pbd.42.2015.08.29.13.21.30 for <ietf@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 29 Aug 2015 13:21:31 -0700 (PDT)
Subject: Re: NomCom procedures revision
To: ietf <ietf@ietf.org>
References: <CAL0qLwYJzFZT=OgWqiiTw-n6mvb3PPusRtArmPs_d4_qpLfmpg@mail.gmail.com> <55E0D5E5.6030802@gmail.com> <55E1714C.6070602@pi.nu>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <55E21442.3030008@gmail.com>
Date: Sun, 30 Aug 2015 08:21:22 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <55E1714C.6070602@pi.nu>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/q3OehRIzyrEnZpGCBS_nKGPz9QI>
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: Sat, 29 Aug 2015 20:21:36 -0000

On 29/08/2015 20:46, Loa Andersson wrote:
> Brian,
> 
> 
> On 2015-08-28 23:43, Brian E Carpenter wrote:
>> On 25/08/2015 16:01, Murray S. Kucherawy wrote:
>>> Some months ago I started the work of editing a revision to the NomCom
>>> procedures (RFC7437bis).  We made progress on some points, but seem to have
>>> stalled on revising the requirements for qualifying to serve on NomCom.
>>>
>>> The draft I have recently expired.  Is there any interest in taking another
>>> run at this now?  Alternatively, is it worth publishing what we did
>>> accomplish, and leaving that one point for a later attempt?
>>
>> Since you ask, I continue to feel that the 3/5 rule is restrictive for people
>> who have limited travel possibilities but have significant IETF experience.
>> Maybe we could have another week on that question, and then go with what we
>> have (with Harald's tweaks)?
>>
>> So...
>>
>> "  Members of the IETF community must have attended at least three of
>>     the last five IETF meetings in order to volunteer."
>>
>> One quick fix is to change it to "three of the last six" which would
>> allow for a whole year of no travel and would not be hard to administer.
>> Another would be to add an alternative qualification "or five of the last
>> ten" to allow for longer-term regular participants. Either way, I think
>> that attending 50% of meetings should be enough.
> 
> I don't have a real problem with "3 out of 6" or "5 out of 10" or even 50% of our meetings, but I at least one of those 3, 5 or
> 50% needs to
> be recent (let us say 1 or the last two, and 3 out of 6.
> 
> What I'm saying is that, and yes it is an extreme case, someone that
> attended the first 48 meetings would not be qualified when we establish
> the next NomCom after IETF 96. Nor would someone attending 5 meetings
> and then did not attend for almost 2 years be qualified.
> 

On another sub-thread, John Klensin said:

> The kind of adjustments Brian and others
> have suggested may help, but I think the real issue is that we
> need not just to allow for fewer recent f2f meetings but to
> consider remote participation experience a real asset (while,
> ideally, pushing back on Nomcom membership by what Marshall Rose
> referred to a Go-ers, rather than Do-ers, no matter how many f2f
> (or remote) meetings they attend.

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).

    Brian