Re: Appointment of a Transport Area Director

Martin Stiemerling <martin.stiemerling@neclab.eu> Tue, 05 March 2013 11:04 UTC

Return-Path: <Martin.Stiemerling@neclab.eu>
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 912FC21F8625 for <ietf@ietfa.amsl.com>; Tue, 5 Mar 2013 03:04:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.849
X-Spam-Level:
X-Spam-Status: No, score=-103.849 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 azXEOnwKkLjz for <ietf@ietfa.amsl.com>; Tue, 5 Mar 2013 03:04:05 -0800 (PST)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 5699921F8623 for <ietf@ietf.org>; Tue, 5 Mar 2013 03:04:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id B9F7C10355D; Tue, 5 Mar 2013 12:04:04 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de)
Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id utJGZJx-2vO3; Tue, 5 Mar 2013 12:04:04 +0100 (CET)
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) by mailer1.neclab.eu (Postfix) with ESMTP id A16DA10355C; Tue, 5 Mar 2013 12:03:54 +0100 (CET)
Received: from [10.7.0.105] (10.7.0.105) by skoll.office.hd (192.168.125.11) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 5 Mar 2013 12:03:24 +0100
Message-ID: <5135D119.5050400@neclab.eu>
Date: Tue, 05 Mar 2013 12:03:53 +0100
From: Martin Stiemerling <martin.stiemerling@neclab.eu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130221 Thunderbird/17.0.3
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Appointment of a Transport Area Director
References: <21B86E13-B8DA-4119-BBB1-B5EE6D2B5C1D@ietf.org> <51330179.3040500@gmail.com> <919840EE-BEC8-4F82-8D3C-B116698A4262@gmx.net> <1D88E6E9-33DE-4C4D-89F4-B0B762155D6F@standardstrack.com> <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> <51351E0B.5050901@dcrocker.net>
In-Reply-To: <51351E0B.5050901@dcrocker.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.7.0.105]
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: Tue, 05 Mar 2013 11:04:07 -0000

Hi Dave,

On 03/04/2013 11:19 PM, Dave Crocker wrote:
>
> On 3/4/2013 1:48 PM, Margaret Wasserman wrote:
>> The problem with this argument is that it appears that we have a
>> choice between "limited knowledge of congestion control" and "an
>> empty seat".  Which one is more likely to be able to learn about
>> it?
>
>
> Carefully considering the tradeoffs and requirements seems to be the
>  corre challenge here.
>
> To extend this point further:
>
> We've defined job requirements that produce an extremely small pool
> of candidates.  In the case of TSV, the pool is zero, but in others
> it is also problematic.  This is a long-standing problem, but we keep
>  ignoring it.
>
> Rather than carefully consider the essential job requirements -- in
> terms of the core work that must be done by an AD -- we seem to think
>  that we can continue with unchanged job requirements.

Not fully true:
There will be a discussion in the TSVAREA session at the IETF-86 meeting 
in Orlando, exactly discussing the job requirements for the TSV AD position:
https://datatracker.ietf.org/meeting/86/agenda/tsvarea/

   Martin

>
> ADs do not 'lead' the work of their area.  They do not initiate the
> work, produce the charters or write the specifications.  Work that
> fails or succeeds does so because it has community consensus and
> demand, not because an AD was diligent or clever.  The job of an AD
> is to facilitate community efforts, not to direct them.
>
> Technical expertise in a technical manager is essential as an adjunct
> to the management.  We keep confusing this essential requirement with
> the kind of work that an individual contributor does.
>
> As long as we maintain that confusion, we will define a job that is
> too demanding, and demands too many of the wrong skills.
>
> d/
>

-- 
martin.stiemerling@neclab.eu

NEC Laboratories Europe
NEC Europe Limited
Registered Office:
Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB
Registered in England 2832014