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

Nico Williams <nico@cryptonector.com> Sun, 28 December 2014 23:13 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 AE5A31A90C8 for <ietf@ietfa.amsl.com>; Sun, 28 Dec 2014 15:13:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.266
X-Spam-Level:
X-Spam-Status: No, score=-0.266 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 SOlyRXgaKrv7 for <ietf@ietfa.amsl.com>; Sun, 28 Dec 2014 15:13:03 -0800 (PST)
Received: from homiemail-a30.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 4D7F51AC43D for <ietf@ietf.org>; Sun, 28 Dec 2014 15:13:03 -0800 (PST)
Received: from homiemail-a30.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a30.g.dreamhost.com (Postfix) with ESMTP id AF65D21DE6F; Sun, 28 Dec 2014 15:13:02 -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=ZWn3y2jrKdB4Zb W27eZdExMsEwo=; b=A7IfdGPp8vGS8pMxIjFklYmh2K/rAY+OXq4O6JnK9ilb7f 7GbIM0Vuf+2k7oBPLBf9BDkkcJc10l24FEoIJOKTH8W2EpQLBMjm3ocWvmiW8XkA kKjKfckBIbYcRsoV/YcLpZ+BM7TuXh2tRxdJfw7Amx9OIzPYiw6fa252FUVRc=
Received: from localhost (108-207-244-174.lightspeed.austtx.sbcglobal.net [108.207.244.174]) (Authenticated sender: nico@cryptonector.com) by homiemail-a30.g.dreamhost.com (Postfix) with ESMTPA id 4D70121DE65; Sun, 28 Dec 2014 15:13:02 -0800 (PST)
Date: Sun, 28 Dec 2014 17:13:01 -0600
From: Nico Williams <nico@cryptonector.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Out-of-area ADs [Re: IETF areas re-organisation steps]
Message-ID: <20141228231257.GC24442@localhost>
References: <5614C286-0CD2-4DAD-A846-510EE38D1B9A@ietf.org> <549DAE1C.5080400@gmail.com> <54A02C8A.3020707@qti.qualcomm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <54A02C8A.3020707@qti.qualcomm.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7y7jGqXUou78hfcZblu5dk6Bemw
Cc: 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 23:13:04 -0000

On Sun, Dec 28, 2014 at 11:15:06AM -0500, Pete Resnick wrote:
> On 12/26/14 1:51 PM, Brian E Carpenter wrote:
> 
> Do note the explanation for this in our original message, as I think
> you have an embedded assumption that's at least non-obvious:
> 
> >There are numerous instances where the constituency of a WG exists
> >in a particular IETF area, but the most appropriate AD for that work happens
> >to be in a different area, or where the ADs in the area are simply overloaded
> >and an AD outside of the area is perfectly capable of managing the work.
> 
> To expand a bit: We do think having WGs in particular Areas is
> useful, and we think generally we're getting our assignment of WGs
> to particular Areas correct: At the scale of an Area, it is
> generally quite obvious and natural that the kind of work we want
> done in a WG falls to a particular IETF constituency, and those
> folks are normally in a particular Area.
> 
> However, we have not found that ADs are so specialized that there is
> a "correct" AD for every WG, or that the AD whose main area (or
> Area) of expertise is always the best person to manage any
> particular WG. [...]
> 
> We think the current way we've been doing assignments are a bit too
> rigid. It *should* be normal for us to assign specific WGs to the
> best AD for that WG, even if the best AD for the Area happens to be
> a different AD. That flexibility should let us redistribute the load
> as needed, and hopefully make it easier for the NomCom to fill
> slots.

This.

For me then this comes down to: once-in-a-while "restructurings" that
consist of one-but-more-likely-many WG/AD reassignments, versus more
frequent one-or-two WG/AD reassignments.

For me "flexibility" as to WG/AD assigments, among other things, means
that each such assignment can't be allowed to require IETF consensus
with 100+-post threads on ietf@ietf.org.  To me WG/AD assigments should
be a matter strictly for the IESG and WG chairs; WG participant and IETF
input should be welcomed, but their consensus should not be formally
required.

The alternatives are once-a-year restructurings yielding long
ietf@ietf.org threads (OK), less frequent restructurings (not OK), or
death by a thousand 100-post threads.

I think[*] I much prefer frequent one-off WG/AD reassignments, _without_
the overhead of IETF consensus in each case.  Someone is bound to see a
conspiracy in that view, which is probably why this isn't on the table :(

Nico

[*] Eh, I can't be too certain about it; I've no idea how that might
    work out IRL.  Maybe we'll hate the result, but we can always go
    back to the alternatives later.