Re: Appointment of a Transport Area Director

Margaret Wasserman <mrw@lilacglade.org> Wed, 06 March 2013 13:34 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 05B3C21F871F for <ietf@ietfa.amsl.com>; Wed, 6 Mar 2013 05:34:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.166
X-Spam-Level:
X-Spam-Status: No, score=-103.166 tagged_above=-999 required=5 tests=[AWL=-0.567, 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 m30sXfBxdRoh for <ietf@ietfa.amsl.com>; Wed, 6 Mar 2013 05:34:34 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 809A921F8718 for <ietf@ietf.org>; Wed, 6 Mar 2013 05:34:34 -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 55A932014B; Wed, 6 Mar 2013 08:34:25 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
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: <FCD86420-F051-4379-94A3-6EC95F8FF809@piuha.net>
Date: Wed, 06 Mar 2013 08:34:32 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C51C5A1D-0B0B-4404-B1DD-A775D64954A6@lilacglade.org>
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> <FCD86420-F051-4379-94A3-6EC95F8FF809@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1499)
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: Wed, 06 Mar 2013 13:34:35 -0000

Hi Jari,

On Mar 6, 2013, at 8:24 AM, Jari Arkko <jari.arkko@piuha.net> wrote:
> 
> And I think we should have a broader view about this than just updating the requirements for the seat. There are a couple of other aspects to consider as well. First, perhaps the way that we have organised TSV is contributing to the problems. Would a different organisation, say, a different grouping of the working groups to areas help businesses see a bigger value in sponsoring an AD for the area? Should the area be merged with something else, and if we did that, would that change available funding or expertise? Or do we have the right number of ADs to begin with? Second, are there more general things that we could do about the AD role, making it easier to do the job, e.g., as an academic and on the side of your other duties? This might also increase the number of available candidates in other areas.

I completely agree with this.

The shortage of candidates is not only a problem in the Transport area, even though it might be more obvious in this area, so I think we should focus on this as a general problem not a specific one.

However, I question the wisdom of choosing to work on this issue _right now_ in the middle of the nomcom selection process, rather than choosing the best candidates we can and working on this problem for next year, or for future years.  It doesn't seem likely that there are any quick fixes here.

If the IESG does decide to reorganize the TSV area(s) and/or reduce the number of seats right now, I think you need to seriously consider the possibility that all of the ADs in the affected/related areas should resign, so that the nomcom can pick the best set of ADS to cover the area(s) given the remaining seats.  So, even that sort of change isn't likely to solve the problem next week.

I'd like to receive some explanation (privately or publicly) about why we are doing this in the middle of the nomcom process that makes any sense to me...

Margaret