Re: Updating BCP 10 -- NomCom ELEGIBILITY

Loa Andersson <loa@pi.nu> Wed, 11 February 2015 14:26 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 276C11A01AE for <ietf@ietfa.amsl.com>; Wed, 11 Feb 2015 06:26:56 -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 TY-bOQkOaet5 for <ietf@ietfa.amsl.com>; Wed, 11 Feb 2015 06:26:52 -0800 (PST)
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 751A01A0358 for <ietf@ietf.org>; Wed, 11 Feb 2015 06:26:52 -0800 (PST)
Received: from [192.168.1.12] (unknown [49.149.201.205]) (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 4A67818013E4; Wed, 11 Feb 2015 15:26:49 +0100 (CET)
Message-ID: <54DB66A0.1050006@pi.nu>
Date: Wed, 11 Feb 2015 22:26:40 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "dcrocker@bbiw.net >> Dave Crocker" <dcrocker@bbiw.net>, ietf <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> <04AED0595DF62A6F1013479D@JcK-HP8200.jck.com> <54DB5CBE.3070502@dcrocker.net>
In-Reply-To: <54DB5CBE.3070502@dcrocker.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/rHUabXNrwLwTowGqReksj7yZHQw>
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:26:56 -0000

Dave,

On 2015-02-11 21:44, Dave Crocker wrote:
> Swap the focus.  Rather than seeking to characterize the clueless, let's
> characterize folk who are much more likely to be clueful:

Would be a blessing :)
>
>       Ensure that at least a portion of the Nomcom has contributed in
> formal, documented way.  AD, Chair, author.. whatever set of activities
> we feel makes it likely they will have clue.

I guess I'm old-time minded here, what is wrong with 3 meetings out
of 5, and if you want co-authored document.
>
>
> 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?

/Loa

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64