Re: Last Call: <draft-leiba-3777upd-eligibility-04.txt> (Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership) to Best Current Practice

Dave Crocker <dcrocker@bbiw.net> Thu, 27 September 2012 18:21 UTC

Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6254821F866A for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 11:21:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.44
X-Spam-Level:
X-Spam-Status: No, score=-6.44 tagged_above=-999 required=5 tests=[AWL=0.159, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dutMulGs9S4J for <ietf@ietfa.amsl.com>; Thu, 27 Sep 2012 11:21:57 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7FC9321F85AF for <ietf@ietf.org>; Thu, 27 Sep 2012 11:21:57 -0700 (PDT)
Received: from [192.168.1.7] (ppp-67-124-89-127.dsl.pltn13.pacbell.net [67.124.89.127]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id q8RILufS012103 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 27 Sep 2012 11:21:57 -0700
Message-ID: <50649932.6050801@bbiw.net>
Date: Thu, 27 Sep 2012 11:21:38 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Last Call: <draft-leiba-3777upd-eligibility-04.txt> (Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership) to Best Current Practice
References: <20120927150522.9680.50930.idtracker@ietfa.amsl.com> <8098D3F7-A030-49F0-ADBC-EE2F2F360D15@vigilsec.com> <50647C77.5070805@dcrocker.net> <E2D914B6-C0CD-4228-A7CA-5EA72CFF67E0@vigilsec.com>
In-Reply-To: <E2D914B6-C0CD-4228-A7CA-5EA72CFF67E0@vigilsec.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Thu, 27 Sep 2012 11:21:57 -0700 (PDT)
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 27 Sep 2012 18:21:58 -0000

On 9/27/2012 10:57 AM, Russ Housley wrote:
>> As for the earlier discussion seeking to exclude paid staff, I
>> think it odd to have criteria that would permit /any/ paid staff to
>> sit on Nomcom.  We pay for a number of folk 'staff' folk to show up
>> and IETF meetings and none of them should qualify for Nomcom, IMO.
...
> (2) Looking at the history
> (https://www.ietf.org/nomcom/committee.html), it does not seem that
> there has been an issue of 'staff' seeking NomCom spots.  Prior to
> IETF Last Call, a previous version of this document was discussed on
> this mail list and on the ietf-nomcom mailing list. It was also
> discussed by a design team made up of ex-NomCom Chairs,  My sense of
> those discussions is to exclude as few people as necessary to avoid a
> self-selecting leadership, and the current document reflects that
> perspective.


So, to provide a specific example, you would be OK with having someone 
from AMS on Nomcom?

d/

-- 
  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net