Re: NomCom procedures revision
Loa Andersson <loa@pi.nu> Sat, 29 August 2015 08:46 UTC
Return-Path: <loa@pi.nu>
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 C4A7D1B3138 for <ietf@ietfa.amsl.com>; Sat, 29 Aug 2015 01:46:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 WEDdJP_joEKj for <ietf@ietfa.amsl.com>; Sat, 29 Aug 2015 01:46:08 -0700 (PDT)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71B291B312C for <ietf@ietf.org>; Sat, 29 Aug 2015 01:46:08 -0700 (PDT)
Received: from [192.168.0.101] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id DD4D21802AB1; Sat, 29 Aug 2015 10:46:06 +0200 (CEST)
Subject: Re: NomCom procedures revision
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Murray S. Kucherawy" <superuser@gmail.com>, ietf <ietf@ietf.org>
References: <CAL0qLwYJzFZT=OgWqiiTw-n6mvb3PPusRtArmPs_d4_qpLfmpg@mail.gmail.com> <55E0D5E5.6030802@gmail.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <55E1714C.6070602@pi.nu>
Date: Sat, 29 Aug 2015 10:46:04 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <55E0D5E5.6030802@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/XBTIp-6LuGFei9NlwmYeiXe3dAw>
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 08:46:10 -0000
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. /Loa > > Brian > >> >> http://datatracker.ietf.org/doc/draft-kucherawy-rfc7437bis/ >> >> -MSK >> >
- NomCom procedures revision Murray S. Kucherawy
- Re: NomCom procedures revision Joe Hildebrand
- Re: NomCom procedures revision Murray S. Kucherawy
- Re: NomCom procedures revision Randy Bush
- Re: NomCom procedures revision Abdussalam Baryun
- Re: NomCom procedures revision Murray S. Kucherawy
- Re: NomCom procedures revision Harald Alvestrand
- Re: NomCom procedures revision Dave Crocker
- Re: NomCom procedures revision Tony Hansen
- Re: NomCom procedures revision Brian E Carpenter
- RE: NomCom procedures revision Adrian Farrel
- Re: NomCom procedures revision Joel Halpern
- Re: NomCom procedures revision Mary Barnes
- Re: NomCom procedures revision Loa Andersson
- Re: NomCom procedures revision John C Klensin
- Re: NomCom procedures revision Brian E Carpenter
- Re: NomCom procedures revision Lixia Zhang
- Re: NomCom procedures revision John C Klensin
- Re: NomCom procedures revision Harald Alvestrand
- Re: NomCom procedures revision Brian E Carpenter
- Re: NomCom procedures revision John C Klensin
- Re: NomCom procedures revision Brian E Carpenter
- Re: NomCom procedures revision Murray S. Kucherawy
- Re: NomCom procedures revision Brian E Carpenter
- Re: NomCom procedures revision Melinda Shore
- Re: NomCom procedures revision Samuel Weiler