Re: Appointment of a Transport Area Director

Scott Brim <swb@internet2.edu> Sun, 03 March 2013 17:37 UTC

Return-Path: <swb@internet2.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 7DE5B21F873D; Sun, 3 Mar 2013 09:37:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.049
X-Spam-Level:
X-Spam-Status: No, score=-6.049 tagged_above=-999 required=5 tests=[AWL=0.550, 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 gHqMIKROF2XP; Sun, 3 Mar 2013 09:37:48 -0800 (PST)
Received: from tx2outboundpool.messaging.microsoft.com (tx2ehsobe004.messaging.microsoft.com [65.55.88.14]) by ietfa.amsl.com (Postfix) with ESMTP id CAE5121F86E1; Sun, 3 Mar 2013 09:37:47 -0800 (PST)
Received: from mail200-tx2-R.bigfish.com (10.9.14.230) by TX2EHSOBE004.bigfish.com (10.9.40.24) with Microsoft SMTP Server id 14.1.225.23; Sun, 3 Mar 2013 17:37:47 +0000
Received: from mail200-tx2 (localhost [127.0.0.1]) by mail200-tx2-R.bigfish.com (Postfix) with ESMTP id 23B814022C; Sun, 3 Mar 2013 17:37:47 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.245.149; KIP:(null); UIP:(null); IPV:NLI; H:CH1PRD0810HT003.namprd08.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 3
X-BigFish: S3(zzzz1f42h1d77h1ee6h1de0h1202h1e76h1d1ah1d2ah1082kzzz2dh2a8h668h839h93fhe5bhf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h1ad9h1155h)
Received: from mail200-tx2 (localhost.localdomain [127.0.0.1]) by mail200-tx2 (MessageSwitch) id 1362332264409172_29674; Sun, 3 Mar 2013 17:37:44 +0000 (UTC)
Received: from TX2EHSMHS033.bigfish.com (unknown [10.9.14.248]) by mail200-tx2.bigfish.com (Postfix) with ESMTP id 60C0A98004A; Sun, 3 Mar 2013 17:37:44 +0000 (UTC)
Received: from CH1PRD0810HT003.namprd08.prod.outlook.com (157.56.245.149) by TX2EHSMHS033.bigfish.com (10.9.99.133) with Microsoft SMTP Server (TLS) id 14.1.225.23; Sun, 3 Mar 2013 17:37:44 +0000
Received: from CH1PRD0810MB395.namprd08.prod.outlook.com ([169.254.11.35]) by CH1PRD0810HT003.namprd08.prod.outlook.com ([10.255.145.166]) with mapi id 14.16.0275.006; Sun, 3 Mar 2013 17:37:43 +0000
From: Scott Brim <swb@internet2.edu>
To: Mary Barnes <mary.ietf.barnes@gmail.com>, "Eggert, Lars" <lars@netapp.com>
Subject: Re: Appointment of a Transport Area Director
Thread-Topic: Appointment of a Transport Area Director
Thread-Index: AQHOGBxXoNiGhQvvNkCxXAbjr24QxpiUHuGAgAAKT4D//75hgA==
Date: Sun, 03 Mar 2013 17:37:43 +0000
Message-ID: <CD58EFB7.80E3%swb@internet2.edu>
In-Reply-To: <CAHBDyN6dcBjL8FG0+Omz0UVQ2qCxo8LnUXet2B1tWM68yRXKYA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.255.145.132]
Content-Type: text/plain; charset="utf-8"
Content-ID: <E82E2367EAAEE5429BBEDB72D8403B2C@namprd08.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: internet2.edu
Cc: IETF Chair <chair@ietf.org>, 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: Sun, 03 Mar 2013 17:37:48 -0000

I see three different factors being discussed together.

  - whether an AD needs technical expertise across the area

  - whether an AD's work hours can be decreased

  - what is TSV's problem anyway

The size of the job is mostly orthogonal from the level of technical
expertise required.  Most of the work is done by a directorate.  However,
even if that's true, it would be a mistake to have an AD overseeing a
directorate without understanding the issues the directorate deliberates.
I really disagree with some who believe the job should be reduced to
something more administrative and less technical, as a way to make it more
"appealing".  Someone has to set priorities, expedite, and make decisions
(lots of them - do not depend on directorates for your decisions).  That
requires technical competence.  Not deep knowledge of every protocol
field, but certainly an understanding of the issues each WG is grappling
with, and enough to ask difficult questions and understand the answers.

Is that too much for one AD?  Is the area too complex?  Then split the
area.  We must have leaders, and we must have them comprehend what they
are leading, so size the work for that while also keeping up the quality
of the leadership.

Scott