Re: Updating BCP 10 -- NomCom ELEGIBILITY

Melinda Shore <melinda.shore@gmail.com> Sat, 14 February 2015 04:27 UTC

Return-Path: <melinda.shore@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 0D87B1A012D for <ietf@ietfa.amsl.com>; Fri, 13 Feb 2015 20:27:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, 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 AQXyHw_BS0eU for <ietf@ietfa.amsl.com>; Fri, 13 Feb 2015 20:27:33 -0800 (PST)
Received: from mail-pd0-f179.google.com (mail-pd0-f179.google.com [209.85.192.179]) (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 9A4AB1A0125 for <ietf@ietf.org>; Fri, 13 Feb 2015 20:27:33 -0800 (PST)
Received: by pdjz10 with SMTP id z10so23480044pdj.0 for <ietf@ietf.org>; Fri, 13 Feb 2015 20:27:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=LkvoJGJoJ2Pbpt55N0ZPmf99HgistqK3UU31pjOM6oc=; b=ikgbz2OSUFVZ/8/e37EU3Y3/x05obUtVBni2qmqLLRZx8w82rrZzDfqYeTtRb0j5Za 0GKuJgzv3ph1cvSFuWWiEawEj+EJP9548CkQQEplrxpxWDCQmyVki9ZV5rZgiY+HnImY qifoIrVdKYRiCa9WYgniLIMN1NhnDcH7VrffZ+qoIHZqfk/Rnj4pTfxt6A3gDLn7JH4r 9WNeflZVBbxXngLz2HkHZgAzEuvsdlZajBH8JXk5DVxhn/aoPQxXlIWwVMs6VUkGzznB 6uOI1fddlY8dTXnfEr53E/qSFjBb+Rl2mZY119LlYpHubII5TxeZcfqPrJh07+hdtMHG 2Yqw==
X-Received: by 10.66.224.164 with SMTP id rd4mr20684783pac.12.1423888053376; Fri, 13 Feb 2015 20:27:33 -0800 (PST)
Received: from spandex.local (216-67-79-246-rb1.sol.dsl.dynamic.acsalaska.net. [216.67.79.246]) by mx.google.com with ESMTPSA id t10sm8102785pdr.75.2015.02.13.20.27.31 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 13 Feb 2015 20:27:32 -0800 (PST)
Message-ID: <54DECEB2.1030004@gmail.com>
Date: Fri, 13 Feb 2015 19:27:30 -0900
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Updating BCP 10 -- NomCom ELEGIBILITY
References: <CAL0qLwZk=k-CWLte_ChK9f1kzLwMOTRyi7AwFa8fLjBsextBcA@mail.gmail.com> <9772.1420830216@sandelman.ca> <CAL0qLwZatYW2e4Wk6GXB2U26fsCn8BV2qt-07kHBugiq34zrcQ@mail.gmail.com> <6025.1423672358@sandelman.ca> <CAL0qLwYtE618sA99hgXP-5wk+BYdcXLbiZqd_36OreYQ1LB7hQ@mail.gmail.com> <54DBD71C.20101@joelhalpern.com> <26803.1423772214@sandelman.ca> <DF32ACD2-FC76-4856-96CE-26423D7F313F@cs.ucla.edu>
In-Reply-To: <DF32ACD2-FC76-4856-96CE-26423D7F313F@cs.ucla.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/KJjCRoDd-YwfJh7P-b8B934D8Ak>
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: Sat, 14 Feb 2015 04:27:35 -0000

On 2/13/15 7:04 PM, Lixia Zhang wrote:
> I noticed this subject line has been a long running thread and I have
> not read it all, but I'd really like to repeat Michael's comment
> here: the nomcom can't produce diversity; it only filter the input
> for the best people.  Thus the solution of getting diversity is not
> at nomcom, but the overall IETF process.

I think that's largely true but I don't think it's the entire story.
I do think the nomcom could be weighting criteria differently or
changing parameters in ways that might get make things easier to
get candidates who don't fit the current mold.

Melinda