Re: Out-of-area ADs [Re: IETF areas re-organisation steps]

Nico Williams <nico@cryptonector.com> Sun, 28 December 2014 20:14 UTC

Return-Path: <nico@cryptonector.com>
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 898E81A896A for <ietf@ietfa.amsl.com>; Sun, 28 Dec 2014 12:14:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.233
X-Spam-Level:
X-Spam-Status: No, score=0.233 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
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 iVclY6ntfqBd for <ietf@ietfa.amsl.com>; Sun, 28 Dec 2014 12:14:07 -0800 (PST)
Received: from homiemail-a77.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 8C8641A907F for <ietf@ietf.org>; Sun, 28 Dec 2014 12:14:07 -0800 (PST)
Received: from homiemail-a77.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a77.g.dreamhost.com (Postfix) with ESMTP id 26D889405C; Sun, 28 Dec 2014 12:14:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=KP1HzAYrW03Sqa JKTWUdgZ5s7IQ=; b=lpIL5x1pkgJgfJd+u8IRsCJccS5NX76zkUcw9gQIXLXjXH Sbac/7j/YVWR69FXU0uJKmgliSjh0r00PT2aX2a6DVx8jezZ9OEFagEqtKmVM4fE cOtCDCjZwrUTJZri0K9JxT9Kf7OKOXNmuDqUj63IlTTDUiClDxynHu36BkKRk=
Received: from localhost (108-207-244-174.lightspeed.austtx.sbcglobal.net [108.207.244.174]) (Authenticated sender: nico@cryptonector.com) by homiemail-a77.g.dreamhost.com (Postfix) with ESMTPA id B8F0D94059; Sun, 28 Dec 2014 12:14:06 -0800 (PST)
Date: Sun, 28 Dec 2014 14:14:06 -0600
From: Nico Williams <nico@cryptonector.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Out-of-area ADs [Re: IETF areas re-organisation steps]
Message-ID: <20141228201401.GB24442@localhost>
References: <5614C286-0CD2-4DAD-A846-510EE38D1B9A@ietf.org> <549DAE1C.5080400@gmail.com> <54A02C8A.3020707@qti.qualcomm.com> <54A04CDC.8020009@dcrocker.net> <54A05568.705@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <54A05568.705@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/1AHWL1fXXPA9yp1OpUVfza4QkQ8
Cc: Pete Resnick <presnick@qti.qualcomm.com>, dcrocker@bbiw.net, 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: Sun, 28 Dec 2014 20:14:08 -0000

On Mon, Dec 29, 2014 at 08:09:28AM +1300, Brian E Carpenter wrote:
> On 29/12/2014 07:33, Dave Crocker wrote:
> ...
> >> However, we have not found that ADs are so specialized that there
> >> is a "correct" AD for every WG,
> > 
> > raises the possibility that AD job descriptions ought to make
> > explicit reference to cross-area skills?  This, of course, leads to
> > the challenge of figuring out what that means, in pragmatic terms.
> 
> This ties back into Nico's point about maybe flattening the hierarchy (*)
> and essentially abolishing areas as such. I have much sympathy with that,
> although it's a bit scary. [...]

I get the fear.  But I think the risks are manageable with a simple
prescription:

>                     [...]. But it means that we would indeed change the
> criteria for picking ADs. [...]

Here's my high-level proposal:

   We need an IESG mostly populated by generalists who can specialize,
   and a few specialists who can generalize.

It's a compromise, of course.  You've all heard the about the jack of
all trades, master of none...  And having a specialist for every
possible, relevant specialization is expensive (which I think is why
we're discussing this _at all_).

But here's the thing: it is actually expected and required of most
people, over their lengthy (nowadays) lives, that they will adapt and
change all sorts of things, changing careers, and becoming experts in
new fields.  At least smart people anyways, which the IESG had better be
chock-full of.

It's fair to say that some IESG members will be more expert in
"security", and others in "transport", but damn it, it ought to be the
case that the neither is completely ignorant of the principles and even
details that the other deals with.

How the IESG members spread the workload amongst each other is not that
interesting to me, really -- I have better things to concern myself with
(since I'm not on the IESG).  That they do it effectively is, and that
they don't consequently drop important things by the wayside is too.  We
already have directorate reviews to assist IESG reviews, and IESG review
already provides an opportunity for the full power of all the IESG's
members to be applied to every document crossing its path.  What more
can we ask for?

>                    [...]. We wouldn't be looking for, say, a Transport AD
> who is a widely recognised expert on congestion control, or a Security AD
> who is competent to verify a crypto algorithm. In fact, over-specialisation
> would be a *disqualification* for serving on the IESG.

Yes-ish.  I don't mind having a few specialists whose job is to prevent
the sorts of gross mistakes that... the IESG is there to prevent.  I
think the specializations needed would be few, maybe just three,
roughly:

 - security (the sorts of people who can tell that your protocol has
   security problems; not necessarily cryptographers),
 - networking (the sorts of people who can tell you that your protocol
   will cause harm to the Internet, or will fail to scale),
 - and operations (the sorts of people who can tell you that you're
   using DNS incorrectly).

All other specializations should be selected for (or against) on the
basis of what is needed more of at the time.

> Serving as a Gen-ART reviewer has been a great experience for me, but has
> often forced me out of my technical comfort zone. It would be the same
> for the IESG in such a new order. They would have to depend more than
> today on expert reviewers.

Yes, and they've already been doing that anyways.

Nico
--