Re: Appointment of a Transport Area Director

Sam Hartman <hartmans-ietf@mit.edu> Thu, 07 March 2013 15:42 UTC

Return-Path: <hartmans@mit.edu>
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 450A321F8D63 for <ietf@ietfa.amsl.com>; Thu, 7 Mar 2013 07:42:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.544
X-Spam-Level:
X-Spam-Status: No, score=-102.544 tagged_above=-999 required=5 tests=[AWL=0.055, 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 YsPTD1gpETrL for <ietf@ietfa.amsl.com>; Thu, 7 Mar 2013 07:42: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 67BC221F8D62 for <ietf@ietf.org>; Thu, 7 Mar 2013 07:42:03 -0800 (PST)
Received: from carter-zimmerman.suchdamage.org (c-98-216-0-82.hsd1.ma.comcast.net [98.216.0.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS id AC72E20183; Thu, 7 Mar 2013 10:41:46 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 6411541CE; Thu, 7 Mar 2013 10:41:55 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Martin Stiemerling <martin.stiemerling@neclab.eu>
Subject: Re: Appointment of a Transport Area Director
References: <21B86E13-B8DA-4119-BBB1-B5EE6D2B5C1D@ietf.org> <D4D47BCFFE5A004F95D707546AC0D7E91F77BA46@SACEXCMBX01-PRD.hq.netapp.com> <3CB8992B-212A-4776-95FE-71CA1E382FFF@standardstrack.com> <513376DB.7000200@dcrocker.net> <E22ACC99-B465-4769-8B59-BB98A7BA93DF@gmx.net> <79E77523-3D92-4CE9-8689-483D416794EF@standardstrack.com> <D4D47BCFFE5A004F95D707546AC0D7E91F780D2F@SACEXCMBX01-PRD.hq.netapp.com> <071C6ED7-352C-4E74-A483-F5E7A3270FA5@gmail.com> <C726E531-57DC-4C42-9053-1394983126D6@vigilsec.com> <5134D5A0.4050209@gmail.com> <tsllia3m5lh.fsf@mit.edu> <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>
Date: Thu, 07 Mar 2013 10:41:55 -0500
In-Reply-To: <5138AE1F.5080602@neclab.eu> (Martin Stiemerling's message of "Thu, 7 Mar 2013 16:11:27 +0100")
Message-ID: <tsl6213p67w.fsf@mit.edu>
User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: IETF <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, 07 Mar 2013 15:42:04 -0000

>>>>> "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.