Re: Appointment of a Transport Area Director

Margaret Wasserman <mrw@lilacglade.org> Fri, 08 March 2013 14:43 UTC

Return-Path: <mrw@lilacglade.org>
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 E6C3821F85BD for <ietf@ietfa.amsl.com>; Fri, 8 Mar 2013 06:43:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.325
X-Spam-Level:
X-Spam-Status: No, score=-103.325 tagged_above=-999 required=5 tests=[AWL=-0.726, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IIAe7uEAL1Vf for <ietf@ietfa.amsl.com>; Fri, 8 Mar 2013 06:43:03 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 566EE21F85B4 for <ietf@ietf.org>; Fri, 8 Mar 2013 06:43:03 -0800 (PST)
Received: from new-host-2.home (pool-71-184-79-25.bstnma.fios.verizon.net [71.184.79.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.painless-security.com (Postfix) with ESMTPSA id 2375C2016B; Fri, 8 Mar 2013 09:42:49 -0500 (EST)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Appointment of a Transport Area Director
From: Margaret Wasserman <mrw@lilacglade.org>
In-Reply-To: <5138F22D.5040206@dcrocker.net>
Date: Fri, 08 Mar 2013 09:43:01 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <BFD6EF98-8001-41D2-950F-AD55C0C3C0F6@lilacglade.org>
References: <5134F720.5010507@cisco.com> <tsl1ubvlywt.fsf@mit.edu> <CAHBDyN6AM-_b2HMrmmQQVuhxFc-_Rfpfg0=r38mkcJ4zqoJeTw@mail.gmail.com> <tslr4julxmh.fsf@mit.edu> <1C1C0842-BF6A-4A3F-A312-35CF0A994793@lilacglade.org> <BDCCFB12-1F2C-44BD-867A-92E5745F3D39@vigilsec.com> <7B6FDB89-F360-45B6-8240-F2F9F81ABAA7@vigilsec.com> <9292FB65-9842-4C95-9284-15F1E9ECEE1D@lilacglade.org> <5138AE1F.5080602@neclab.eu> <tsl6213p67w.fsf@mit.edu> <20130307182406.GR2854@nsn.com> <tslk3pjm55w.fsf@mit.edu> <5138F22D.5040206@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1499)
Cc: Sam Hartman <hartmans-ietf@mit.edu>, IETF <ietf@ietf.org>, Martin Stiemerling <martin.stiemerling@neclab.eu>
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: Fri, 08 Mar 2013 14:43:04 -0000

On Mar 7, 2013, at 3:01 PM, Dave Crocker <dhc@dcrocker.net> wrote:
> Unfortunately, Sam, your model is simply wrong.
> 
> The IESG defines the job requirements.  The Nomcom selects according to those criteria.
> 
> I'm been in a number of Nomcom's that wished for some flexibility concerning job requirements, but each of these Nomcoms was very clear that it did not have a mandate to make changes in job criteria.

Dave, this isn't what  RFC 3777 says…

RFC 3777 says that the IESG submits the IESG's desired criteria, that the nomcom gets input from the community on what the criteria should be, and that the nomcom decides (based on both inputs) what criteria the nomcom will use to select candidates.

This is why I do support the nomcom asking the community for further input if it is unclear what the requirements should be.

IMO, nomcoms don't do a very good job of asking the community about what the criteria should be.  The entire input-gathering process is focused on the individual candidates, and the community can't really offer feedback on candidates they don't know.  

Based on your message and other things that have been said about this year's process, I think the community has lost track of the nomcom's job in setting the criteria.  For years, I have been choosing to give the nomcom free-form feedback on the criteria via e-mail or during interviews, and now I understand why I've been getting blank stares or silence in return.

Margaret