Re: IETF areas re-organisation steps

Jari Arkko <jari.arkko@piuha.net> Sat, 27 December 2014 01:47 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C6211AD46A for <ietf@ietfa.amsl.com>; Fri, 26 Dec 2014 17:47:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dHjKmnLWSo7G for <ietf@ietfa.amsl.com>; Fri, 26 Dec 2014 17:47:18 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id D2EC71AD45F for <ietf@ietf.org>; Fri, 26 Dec 2014 17:47:17 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 760822CC5D; Sat, 27 Dec 2014 03:47:16 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gxJzN-FGG-AR; Sat, 27 Dec 2014 03:47:16 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id EA2DD2CC4D; Sat, 27 Dec 2014 03:47:15 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Content-Type: multipart/signed; boundary="Apple-Mail=_109132E8-7FBA-482B-BF52-C02C051269C5"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: IETF areas re-organisation steps
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <86571133-435B-48D5-A6B2-6050AC67E133@ofcourseimright.com>
Date: Sat, 27 Dec 2014 03:47:13 +0200
Message-Id: <63744448-11B3-4294-A184-B923D0DC686E@piuha.net>
References: <5614C286-0CD2-4DAD-A846-510EE38D1B9A@ietf.org> <86571133-435B-48D5-A6B2-6050AC67E133@ofcourseimright.com>
To: Eliot Lear <lear@ofcourseimright.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/-w9joTZd40d8zwqMNIrUk3eLjWo
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 27 Dec 2014 01:47:19 -0000

Eliot,

> I'd like to understand how you expect the various job descriptions to change. In particular, with regard to NAPP (or  it ends up being called), do you intend to simply combine the three? I ask because if a goal is to encourage people to be ADs, if the description reads as though nobody would be qualified to do All of That, then nobody will apply.  Knowing this I'm sure you already have lots of thoughts on how to guide NOMCOM. Could you share?

Good question.

The descriptions have to change. In the case of NAPP, that’s a description that we need by summer 2015.

As you point out, it would be a bad idea to require people that can do everything. I think the answer is that among the set of ADs covering the area, they should be able to cover the technical topics in that area. Preferably with some overlap. This isn’t all that different from what has happened in the past with big areas such as INT; no AD usually has the breadth to cover everything alone, but together they can do a reasonable job. Putting the puzzle together means some more work for the nomcom, however.

Jari