Re: IETF areas re-organisation steps

Ted Hardie <ted.ietf@gmail.com> Fri, 09 January 2015 19:54 UTC

Return-Path: <ted.ietf@gmail.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 D6CD61A8F44; Fri, 9 Jan 2015 11:54:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 8ubFL37NQQAw; Fri, 9 Jan 2015 11:54:08 -0800 (PST)
Received: from mail-ie0-x229.google.com (mail-ie0-x229.google.com [IPv6:2607:f8b0:4001:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A1CE1A87CB; Fri, 9 Jan 2015 11:54:08 -0800 (PST)
Received: by mail-ie0-f169.google.com with SMTP id y20so16882668ier.0; Fri, 09 Jan 2015 11:54:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=696HWpYgiZERYNMu7wfYUTt/dwX8n0NQQBVqFKWDIYY=; b=kRmNKF+2NfA8gM3S/ivDRJRoTajn6C9patdyJEoK9AC90ucK51lsQacYPKoJnoGNhw pG1HjfREDTWUEvxtywcB3ePkYc5Twdg2VsTG8XJo9ddseyhI0aQgHflFey5ut440gZNu 5lim9PVTl2+kvFMWFaAX4KswCdgj26M2HklV4NNWb/c28NzNYLFEodw0IVe2g76NmMQ9 MJk4ynuEg1t49bRHAutyrjq+5QDOOB4aUupzkHDQxG9+8Dki+Qu5M9kYM1WkGD0Qidc+ jN7mCQoI+LtXyd5Y0TMLMD1y4HuO7flBZy72Y116yAPOSN2bTT3VftiFWi7WddwOg/Y7 RmiA==
MIME-Version: 1.0
X-Received: by 10.107.138.131 with SMTP id c3mr16993111ioj.0.1420833247522; Fri, 09 Jan 2015 11:54:07 -0800 (PST)
Received: by 10.42.107.145 with HTTP; Fri, 9 Jan 2015 11:54:07 -0800 (PST)
In-Reply-To: <D68B9223-0A90-4FCD-B1B1-0CBD6B82F054@ietf.org>
References: <5614C286-0CD2-4DAD-A846-510EE38D1B9A@ietf.org> <D68B9223-0A90-4FCD-B1B1-0CBD6B82F054@ietf.org>
Date: Fri, 9 Jan 2015 11:54:07 -0800
Message-ID: <CA+9kkMB+c7rSn7WmCwndNmux4h9ujBqNmQC6XRNOJax7qPyCqQ@mail.gmail.com>
Subject: Re: IETF areas re-organisation steps
From: Ted Hardie <ted.ietf@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a113e986400f756050c3d850d
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/HcRouhaWp2Ta71P4d5oYjGYrOmE>
Cc: IETF WG Chairs <wgchairs@ietf.org>, IETF Announcement List <ietf-announce@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: Fri, 09 Jan 2015 19:54:14 -0000

Jari,

Thanks for re-posting this and for the community engagement on the topic.
Some comments below.

On Thu, Jan 8, 2015 at 3:00 AM, IETF Chair <chair@ietf.org> wrote:

>
> This message was originally sent during holidays, but I was asked to
> re-send it now that most of us are back in the office.
>
> Dear Community:
>
> In October, we let you know that we would be coming up with some proposals
> and consulting with you on the topic of re-organizing the IESG and the IETF
> areas with the intent to increase flexibility as IETF work evolves, to
> ensure that
> all IETF work is covered by an AD, and to balance and reduce the workload
> across the ADs [1]. We committed to developing a re-organization proposal
> by
> May 2015 (thus including ADs that will be newly seated in March 2015). We
> have taken several steps since then toward that goal: we recommended that
> the
> nomcom not to fill the APP AD vacancy in the current nomcom cycle [2], and
> we
> are taking steps to redistribute workload in order to allow for more
> resources
> to be focused on YANG model coordination [3].
>
> This message provides an outline of further steps we propose to take in
> 2015
> as part of the re-organization and invites community feedback on those
> steps.
> Step I below is already in progress. Step II in particular requires timely
> action, and therefore we are requesting community feedback by January 15,
> 2015 on that step in particular and on the overall proposal.
>
> None of the steps below should be viewed as permanent or overly
> constraining
> how the IESG and the areas might be organized in future years. In general
> we’d
> like to increase the ability for the IESG to be flexible going forward. We
> are
> suggesting the steps below as measures to experiment with as a means to
> determine their effectiveness. The IESG intends to continue to re-evaluate
> all
> of the steps on a regular basis.
>
>
> PRINCIPLES
>
> The IESG believes the re-organization should proceed according to the
> following principles:
>
>
​Are these roughly in order of importance to the IESG?  If so, I think
the order is wrong.  As relevance here means "doing good work people use"
and maybe even "doing the work only this organization can do", it has
to come first.  After that, I'd put sustainability, since the ability to
continue to do that work is supported by it.  ​


> 1) Agility: The IESG should be able to adapt as Internet engineering
> evolves.
> When work focus shifts and new technologies emerge, it is critical that the
> the IESG can follow the shift and effectively manage the new work.
>
> 2) Relevance: The organization of the technical work must facilitate the
> IETF's continued relevance to the industry. As we change how we develop
> technology throughout the Internet, the IETF must be able to change how our
> standards development works with the technology development.
>
> 3) Flexibility: The organization of the IESG and of the technical areas
> should
> accommodate variations in workloads, time commitments, and AD skillsets, as
> well as changes in those over time. It is important to make it possible for
> more IETF participants to be able to serve as Area Directors and to make
> the
> work co-exist with their normal jobs.
>
> 4) Sustainability: The Area Director role should be a position that
> accomplished engineers aspire to and that employers want to support. We
> should
> emphasize the "steering" and "director" aspects, supporting and guiding the
> technical work in the working groups.
>
>
> THREE STEPS
>
> We suggest taking the three steps described below to fulfill these
> principles.
>
>
> I.  FURTHER SHIFTING OF WG RESPONSIBILITY TO OUT-OF-AREA ADS
>
> The ability to react to changes in the industry, for example the IESG YANG
> Model Work Redistribution [3], requires flexibility within the IETF
> leadership
> positions. 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
> address these possibilities, the IESG is moving towards a model where a WG
> can
> exist in one area, but its shepherding AD comes from another area. This
> flexibility will allow the IESG to apply its skills where they can be of
> most
> use while still keeping related WGs together within an area. The IESG
> proposes
> to experiment with this approach initially by shifting to out-of-area ADs
> for
> RADEXT, DIME, LMAP, and ANIMA, perhaps with another few WGs to follow.
>
>
​So, I think this increasing your flexibility, but does nothing much for
sustainability.
You still are having the same pool of bodies do the work, simply taking AD
capacity
from one area and using it another.  That may be nice, but it increases the
level of cooperation needed between the area management and the visiting
ADs, so it is really only a marginal gain even for the area getting the
outside talent.

To make a dent in this, you actually have to increase the number of bodies
available to do the work.  And to do that, you have to reformulate some of
the
work so that bodies who do it don't have to have the tag AD.  (The document
shepherd opening up to non WG chairs is a good example here).​

​I'm really hesitant to support tool development work here until the bang
for
the buck here is larger.  Formalizing a method for robbing Peter to pay Paul
isn't much ​to get excited spending money on.

In order to achieve the above, there is some tools development work needed.
> Many components of the IETF tool set (e.g., the datatracker) make
> assumptions
> about WG/AD relationships based on the WG's assigned area. That issue is
> currently being worked on by the tools team, but will take a few months'
> time.
> During this intermediate period (prior to the tools work completing), the
> cross-area shepherding effort will be done informally by the IESG. This
> informal approach will address:
>
> a. Shepherding AD - Each WG will still have an AD assigned to it from its
> area, referred to as the Home Area AD. The actual shepherding AD will be
> temporarily listed as the Technical Advisor. The shepherding AD will be in
> charge of all WG management issues. The IESG will develop a way to
> explicitly
> indicate the shepherding AD on the WG's charter page.
>
> b. E-mail aliases - WG chairs and participants who wish to reach the ADs
> for a
> WG via the <foo>-ads tools aliases should explicitly include the AD listed
> as
> Technical Advisor for the WG.
>
> c. Document shepherding - When a WG chair submits a publication request,
> that
> request will flow to the Home Area AD. The Home Area AD should then
> delegate
> shepherding responsibilities to the shepherding AD for handling.
>
> d. Appeals - IETF participants should be directed to send any appeals
> related
> to the WG to the shepherding AD rather than the Home Area AD.
>
>
> II.  ADDING A THIRD RTG AD
>
> The IESG is considering requesting that the currently seated nomcom select
> an
> additional routing AD, such that two new routing ADs, rather than one,
> would
> be seated for two-year terms in spring 2015. The reasoning behind this
> request
> is that the load in the RTG area is currently unsustainably high. The
> placement of a third AD will have the effect of spreading that load such
> that
> the time requirement may now be more consistent with the work loads of ADs
> in
> other areas. The total number of ADs on the IESG would not change if the
> APP
> seat remains vacant.
>
> This request is further justified by the considerable increase in
> management-related work in the RTG area. Specifically, there are a lot of
> new
> YANG models being written. Although the coordination of YANG across the
> IETF
> falls as the responsibility of the OPS ADs (specifically the Management
> AD) it
> is expected that the RTG ADs will need to work on an increasing number of
> YANG
> documents as well.
>
> If an additional RTG AD were to be seated, the IESG would propose to move
> three working groups from the INT area to the RTG area to balance AD loads:
> L2TPEXT, LISP, and TRILL.
>
> As with all of the proposed organizational changes, the IESG would expect
> to
> re-evaluate the need for this third RTG AD in future years and balance that
> need against the need to have other skill sets or more generalist roles
> represented on the IESG.
>
>
​This justification seems to hint at a "Model Language AD" who
can serve the whole IETF as a shepherd of YANG work across areas.
Why is that not a better answer here?

Noting that you are short of routing AD attention and shifting other
work into the area after fixing that problem also seems to ignore the
"out of area" AD mechanism introduced above--why is that not
sufficient?  I also note that the proposed shift changes the useful
skillsets for both routing and INT, and that doing so at this point in
the nomcom cycle isn't exactly optimal.


> Work is underway to create support for this model in our process
> documentation:
> http://tools.ietf.org/html/draft-dawkins-iesg-one-or-more-04.
>
>
> III.  MERGING OF UPPER LAYER PROTOCOL AREAS
>
> As previously noted [1], a significant amount of the work that is going on
> in
> the APP area pertains to the web protocols, but that has a good deal of
> crossover with work in RAI. There is also some crossover work between the
> APP
> and TSV areas. To accommodate these overlaps and provide better WG
> management
> across these three areas, the IESG is proposing to merge the APP, RAI, and
> TSV
> areas into one combined Network Applications (NAPP) area. From March
> 2015-March 2016, this combined area would be overseen by the five remaining
> ADs from APP, RAI, and TSV, with some redistribution of WG shepherding
> responsibilities among them to balance workloads. DISPATCH, TSVWG, and
> APPSAWG
> would continue to function much as they currently do.
>
> The NAPP ADs would continue to encourage progress towards closure of the
> many
> WGs in the area that are close to completing their chartered work. As such,
> the IESG would expect to request in the 2015-16 nomcom cycle a reduction in
> NAPP AD headcount, yielding four seated NAPP ADs starting in March 2016. If
> possible, we could reduce down to 4 NAPP ADs prior to that time and
> re-assign
> the fifth AD’s duties to further help balance IESG load.
>
>
​So, I thoroughly agree that the name here is distractingly bad, but I
also believe that you're building the wrong bike shed.  As it stands,
coordinating
four or five people's schedules to have calls and agree on document
processing either
means a fairly large investment in time spent on Doodle polls or allowing
the area to have "mini-Areas" whose coordination remains loose. As
Robert Sparks pointed out, the failure to use common methods (like DISPATCH)
is going to run into trouble and exacerbate that.  ​

​There are a lot organizational principles possible here. RAI was organized
more or
less as a topic area with "all those things relating to Internet Telephony
(plus a few)"​
as the topic.  This meta-area doesn't seem to have such an organizational
principle,
and the "there are overlaps" argument doesn't seem that strong given the
large number
of _other_ overlaps.  I understand that folks are tempted by the "select a
bunch of generalists"
and let them work it out as a free-form approach to the AD job, and that
this could be
a mini version of that.   Personally, though,  I think having set areas
remains valuable, in
part because it shows how the overall organization understands the way the
work interconnects.
Putting too much in a single bucket muddies the interconnection into
incomprehnsibility,
at least to me.

To return a moment to the question of sustainability, I think the key
element is always offload.
When all the site selection and contract work left the IESG and was taken
up by the IAOC,
the IESG gained cycles over all.  That might have been hard to see at the
time because of
the overall transition, but it is obvious now.  I think the IESG might get
more bang for its
re-organizational buck if it focused on areas where its tasks could be
handed over to new
bodies.  As a very small example, if the conflict review work were done by
a different group,
with each area sending a delegate, would that hurt anything much?  Would it
gain any real
time?  This may be a small example, but I think the principle is
general--please focus on
areas where the IESG can differentiate its workload and then delegate the
bits that
can be done elsewhere.

My thanks again for the opportunity to comment,

Ted Hardie



> Jari Arkko for the IESG
>
>
> REFERENCES
>
> [1]
> http://www.ietf.org/mail-archive/web/ietf-announce/current/msg13314.html
> [2]
> http://www.ietf.org/mail-archive/web/ietf-announce/current/msg13364.html
> [3]
> http://www.ietf.org/mail-archive/web/ietf-announce/current/msg13576.html
>
>