Re: Updating BCP 10 -- NomCom ELEGIBILITY

Allison Mankin <allison.mankin@gmail.com> Sun, 11 January 2015 20:11 UTC

Return-Path: <allison.mankin@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 CBF841A1A4D for <ietf@ietfa.amsl.com>; Sun, 11 Jan 2015 12:11:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MKnLQJ-xHbty for <ietf@ietfa.amsl.com>; Sun, 11 Jan 2015 12:11:42 -0800 (PST)
Received: from mail-qc0-x22b.google.com (mail-qc0-x22b.google.com [IPv6:2607:f8b0:400d:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C70651A1A20 for <ietf@ietf.org>; Sun, 11 Jan 2015 12:11:41 -0800 (PST)
Received: by mail-qc0-f171.google.com with SMTP id r5so15729770qcx.2 for <ietf@ietf.org>; Sun, 11 Jan 2015 12:11:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=NLCiAgykmOwvOxUUPPcdJ31GA/ZzbJvZg2PKde7ZV84=; b=qH/nGzsytsHTZV56PP2H9JmeaCscFC3Sz5+iTGtZDb+V5UDLwqwNgVTCWg08K3ASk0 cF+ZyvQCXEZpv2/n4fQ+7X1vPB8ZI+jsQsxjFbhyrqIr/Wm9c3ELT3/z07QYFLisjEc9 HKmUlM44jx/5aSCwkLYxtcvPm2Jrp8FP6wC7SaKV0yRVwsZV1f5A8ErJC2C9+Y7SKZfz hZ4EeeuLpO/WZrwsLM6HC5zEEhlTy4l4a08N1p2vr1Tk8jftmwxbngkXuzDUbvh6UbzJ oCtvSqQd0y3CxmQ5AVvLL08EDcvP5mIYkoRH68618pExWttVBQa/gy3XpFl3tbdo9zQb Yr6w==
MIME-Version: 1.0
X-Received: by 10.140.38.139 with SMTP id t11mr42022378qgt.83.1421007101041; Sun, 11 Jan 2015 12:11:41 -0800 (PST)
Received: by 10.96.144.71 with HTTP; Sun, 11 Jan 2015 12:11:40 -0800 (PST)
Received: by 10.96.144.71 with HTTP; Sun, 11 Jan 2015 12:11:40 -0800 (PST)
In-Reply-To: <22671.1421006639@sandelman.ca>
References: <CAL0qLwZk=k-CWLte_ChK9f1kzLwMOTRyi7AwFa8fLjBsextBcA@mail.gmail.com> <9772.1420830216@sandelman.ca> <54B02B51.1070308@cs.tcd.ie> <5237.1420905553@sandelman.ca> <20150110183324.5CED31A6F11@ietfa.amsl.com> <54B17DDB.3080005@gmail.com> <201501102231.t0AMV21b009190@colo4.roaringpenguin.com> <22671.1421006639@sandelman.ca>
Date: Sun, 11 Jan 2015 15:11:40 -0500
Message-ID: <CAP8yD=sn-a9Y3muA8Z7Xjg+mV=qMQbmS8EEu6XmPc8RYe74cJw@mail.gmail.com>
Subject: Re: Updating BCP 10 -- NomCom ELEGIBILITY
From: Allison Mankin <allison.mankin@gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=001a11c117b87b20e1050c65ff19
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/wLSE7dFlUbQ2jDVBVtoqRtv-pr0>
Cc: IETF Discussion <ietf@ietf.org>
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: <http://www.ietf.org/mail-archive/web/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, 11 Jan 2015 20:11:44 -0000

I like Michael's original suggestion that there should be two meetings in
the last five and if there is not a third, then meeting some other
requirement, a choice of things like attended lots of past meetings, has a
defined role in a wg, ...

Others have noted this, but the two important goals of these criteria are:

Has attained a (minimal)  level of familiarity with IETF

Has a probability of attending in person for the Nomcom activities

Michael has crystallized in other posts the fact that Nomcom really needs
the in person time in order to work together, and IETF teally, critically
needs full attendance if Nomcom during the meeting(s) with interviews,
especially November, for the candidate interviews.