Re: Appointment of a Transport Area Director

Hector Santos <hsantos@isdg.net> Mon, 04 March 2013 14:13 UTC

Return-Path: <hsantos@isdg.net>
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 4268521F8A3F for <ietf@ietfa.amsl.com>; Mon, 4 Mar 2013 06:13:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 lM43kiF+jguu for <ietf@ietfa.amsl.com>; Mon, 4 Mar 2013 06:13:07 -0800 (PST)
Received: from secure.winserver.com (news.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 3FD0F21F89CC for <ietf@ietf.org>; Mon, 4 Mar 2013 06:13:06 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2793; t=1362406377; h=Received:Received: Message-ID:Date:From:To:Subject:Organization:List-ID; bh=HiuvqpE R0EhOBgRTqaBF4EqJzkA=; b=qBVYNfKX37AvxiwDOdjg47NH26Dn9SA0IISGrHH 9eSl8LNxcN8CNuhDt4Fuq3i0J4raKQOJK7sJeomZ3kpdgSLP1nwn+EwGoSBZx73P /8yputw4rmqUS2CUKiONZzPXKFgwKe0AR5bLzOwxLWlq+XJ22+YCaIPkNyTsnQjZ 4/fU=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 04 Mar 2013 09:12:57 -0500
Received: from [208.247.131.8] ([208.247.131.8]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1200117391.9983.4748; Mon, 04 Mar 2013 09:12:56 -0500
Message-ID: <5134AB6C.3090004@isdg.net>
Date: Mon, 04 Mar 2013 09:10:52 -0500
From: Hector Santos <hsantos@isdg.net>
User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>
Subject: Re: Appointment of a Transport Area Director
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>
In-Reply-To: <D4D47BCFFE5A004F95D707546AC0D7E91F780D2F@SACEXCMBX01-PRD.hq.netapp.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: IETF IETF <ietf@ietf.org>, Eric Burger <eburger@standardstrack.com>
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: Mon, 04 Mar 2013 14:13:08 -0000

One item to consider is to lower the work load of the AD, in particular 
in reviewing docs towards of the end of projects.  Issues and dilemmas 
are piled on.   I think one approach to lowering appeals, for example, 
is  to address unresolved delicate WG issues much faster, in particular 
the tough ones that reach an impasse and no normal "Rough" WG 
consensus.  This is where the AD may and has helped but I also suggest 
we have a group of peers that can quickly resolve (make decisions) the 
more  delicate WG issues that tends to hold back progress and piled more 
work on people to do which runs the risk of lower quality result and 
also apathy (give up on the work). It may better to ignore it to avoid 
endorsing a controversial direction.   I have had two ADs in the past 
both apologize for not dealing with issues (reading the I-D) a lot sooner.

Perhaps, we should look at some of the IETF activities that makes it 
less appealing to even "apply" for the "job."



On 3/4/2013 8:07 AM, Eggert, Lars wrote:
> Hi,
>
> On Mar 4, 2013, at 13:18, Eric Burger<eburger@standardstrack.com>  wrote:
>> I will say it again - the IETF is organized by us.  Therefore, this situation is created by us.  We have the power to fix it.  We have to want to fix it.  Saying there is nothing we can do because this is the way it is is the same as saying we do not WANT to fix it.
> what is "the fix"?
>
> The IETF is set up so that the top level leadership requires technical expertise. It is not only a management job. This is a key differentiator to other SDOs, and IMO it shows in the quality of the output we produce. The reason the RFCs are typically of very good quality is that the same eyeballs go over all documents before they go out. This creates a level of uniformity that is otherwise difficult to achieve. But it requires technical expertise on the top, and it requires a significant investment of time.
>
> I don't see how we can maintain the quality of our output if we turn the AD position into a management job. Especially when technical expertise is delegated to bodies that rely on volunteers. Don't get me wrong, the work done in the various directorates is awesome, but it's often difficult to get them to apply a uniform measure when reviewing, and it's also difficult to get them to stick to deadlines. They're volunteers, after all.
>
> And, as Joel said earlier, unless we delegate the right to raise and clear discusses to the directorates as well, the AD still needs to be able to understand and defend a technical argument on behalf of a reviewer. If there is a controversy, the time for that involvement dwarfs the time needed for the initial review.
>
> There is no easy fix. Well, maybe the WGs could stop wanting to publish so many documents...
>
> Lars
>