Re: Updating BCP 10 -- NomCom ELEGIBILITY

Ted Lemon <Ted.Lemon@nominum.com> Wed, 11 February 2015 14:35 UTC

Return-Path: <Ted.Lemon@nominum.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 133D31A0276 for <ietf@ietfa.amsl.com>; Wed, 11 Feb 2015 06:35:15 -0800 (PST)
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 F0cCIDhQ5HaZ for <ietf@ietfa.amsl.com>; Wed, 11 Feb 2015 06:35:13 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBCAB1A020B for <ietf@ietf.org>; Wed, 11 Feb 2015 06:35:12 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 8132FDA02A6 for <ietf@ietf.org>; Wed, 11 Feb 2015 14:35:12 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 4C64C53E084; Wed, 11 Feb 2015 06:35:12 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 11 Feb 2015 06:35:12 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Updating BCP 10 -- NomCom ELEGIBILITY
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <54DB66A0.1050006@pi.nu>
Date: Wed, 11 Feb 2015 09:35:09 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <BE226640-1857-4232-9D4F-78445D82776A@nominum.com>
References: <CAL0qLwZk=k-CWLte_ChK9f1kzLwMOTRyi7AwFa8fLjBsextBcA@mail.gmail.com> <9772.1420830216@sandelman.ca> <CAL0qLwZatYW2e4Wk6GXB2U26fsCn8BV2qt-07kHBugiq34zrcQ@mail.gmail.com> <04AED0595DF62A6F1013479D@JcK-HP8200.jck.com> <54DB5CBE.3070502@dcrocker.net> <54DB66A0.1050006@pi.nu>
To: Loa Andersson <loa@pi.nu>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/EC0392UVpxiVqD5yhNvVVk3pPek>
Cc: "dcrocker@bbiw.net >> Dave Crocker" <dcrocker@bbiw.net>, ietf <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: Wed, 11 Feb 2015 14:35:15 -0000

On Feb 11, 2015, at 9:26 AM, Loa Andersson <loa@pi.nu>; wrote:
> I guess I'm old-time minded here, what is wrong with 3 meetings out
> of 5, and if you want co-authored document.

The main issue with three out of five is that it discriminates against people who can't attend that often but are actively involved in the IETF.   E.g., you have kids, or you have a family member with an illness who needs care, so you stay home for a year, and suddenly you're disenfranchised, even though you were actively involved in the IETF that whole time.

>> As for Loa's question about why someone who hasn't done real IETF work
>> would want to volunteer, the answer is politics and/or ego.  They or
>> their company might want to hold sway over nomcom or the person might
>> just want to add this to their resume.
> 
> With due respect - I don't think this is how it work, do we have any
> running code? Our rules so far has not stopped anyone form paying and
> register, sit at the back of a a couple of wg meetings and three IETF
> meetings later drop his/her name into the hat. But has it happened?

The operation of each nomcom are pretty opaque to those who are not on it.   For those who have interacted with a nomcom as candidates, such an impression might exist.   It's possible that nomcom liaisons or chairs could speak to this.   However, since nomcom proceedings are supposed to be confidential, I don't know how much they could really say.   Because these properties of the nomcom are intentional and useful, it does make sense to be particularly careful about how nomcom eligibility is determined and not just trust to peoples' good natures.