Re: Appointment of a Transport Area Director

David Kessens <david.kessens@nsn.com> Thu, 07 March 2013 18:24 UTC

Return-Path: <david.kessens@nsn.com>
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 9845E21F89E5 for <ietf@ietfa.amsl.com>; Thu, 7 Mar 2013 10:24:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 5v5SFCf+pgEC for <ietf@ietfa.amsl.com>; Thu, 7 Mar 2013 10:24:16 -0800 (PST)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 5FAF521F89C7 for <ietf@ietf.org>; Thu, 7 Mar 2013 10:24:15 -0800 (PST)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id r27IOBMg010301 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 7 Mar 2013 19:24:11 +0100
Received: from localhost.localdomain ([10.138.48.137]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id r27IO90V029123; Thu, 7 Mar 2013 19:24:10 +0100
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.14.5/8.14.5) with ESMTP id r27IO8V0028142; Thu, 7 Mar 2013 10:24:08 -0800
Received: (from david@localhost) by localhost.localdomain (8.14.5/8.14.5/Submit) id r27IO63O028140; Thu, 7 Mar 2013 10:24:06 -0800
Date: Thu, 07 Mar 2013 10:24:06 -0800
From: David Kessens <david.kessens@nsn.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Subject: Re: Appointment of a Transport Area Director
Message-ID: <20130307182406.GR2854@nsn.com>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <tsl6213p67w.fsf@mit.edu>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 2890
X-purgate-ID: 151667::1362680651-0000547A-B432195A/0-0/0-0
Cc: 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: Thu, 07 Mar 2013 18:24:16 -0000

Sam,

Can we please stop the hairsplitting ?

It is not the IESG's fault if you feel that the nomcom is taking the IESG
input as absolute software style 'requirements' as opposed to often more
lightly interpreted 'job requirements' as desirable from the IESG's
perspective. Please take that message to the nomcom if you wish.

The grander picture here is that there will be a session where the community
can discuss the topic of what to do with the TSV area director position. You
are part of that community and I have no doubt that you will be given a
chance to speak up. This session is clearly not about the finer details of
the nomcom process.

David Kessens
---

On Thu, Mar 07, 2013 at 10:41:55AM -0500, Sam Hartman wrote:
> >>>>> "Martin" == Martin Stiemerling <martin.stiemerling@neclab.eu> writes:
> 
>     Martin> Hi Margaret, I will answer as the agenda below is out of the
>     Martin> TSVAREA session.
> 
>     Martin> On 03/07/2013 03:21 PM, Margaret Wasserman wrote:
>     >> 
> > Hi Russ,
>     >> 
>     >> On Mar 5, 2013, at 11:18 AM, Russ Housley <housley@vigilsec.com>
>     >> wrote:
>     >>> The rest of your question ought to be discussed at the TSVAREA
>     >>> meeting in Orlando.
>     >> 
>     >> I have looked at the agenda of the TSV Area Open Meeting (on
>     >> Wednesday from 9:00am to 11:30am), and it includes the following
>     >> item:
>     >> 
>     >> "- Open Mic about "Area Expectations for the TSV ADs" -- 60
>     >> minutes The questions we will ask the community: - what is the
>     >> existing description we gave to NomCom. - does the community
>     >> agree with it? - is it reasonable, or are we asking too much?"
>     >> 
>     >> By "description we gave to the NomCom" do you mean the IESG's
>     >> list of desired criteria?  Is the NomCom also going to report on
>     >> the criteria that they came up with, after considering the IESG's
>     >> input and whatever input they received from the community?
> 
>     Martin> The IESG has sent these requirements [1] to the nomcom, as
>     Martin> stated on that site. That's what is meant with "what is the
>     Martin> existing description we gave to NomCom".
> 
> Hi, after reading your message I still don't understand the answer to
> Margaret's question.
> 
> Also, I'd like to remind you that the IESg does not send requirements to
> the nomcom.  According to RFC 3777 the IESG sends a set of desired
> expertise.  The nomcom develops a set of required qualifications based
> on these and community input.
> 
> It's not just a semantic point.  I think over the years the IESG has
> started to believe that the IESG rather the community sets the job
> requirements for ADs.  I'd like to ask IESG members especially to be
> very careful about the terminology and to respect the process.

David Kessens
---