Re: Appointment of a Transport Area Director

Benoit Claise <bclaise@cisco.com> Mon, 04 March 2013 23:05 UTC

Return-Path: <bclaise@cisco.com>
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 7FA3B21F88E2 for <ietf@ietfa.amsl.com>; Mon, 4 Mar 2013 15:05:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.195
X-Spam-Level:
X-Spam-Status: No, score=-10.195 tagged_above=-999 required=5 tests=[AWL=0.404, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
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 EGlu+ZuAtvE9 for <ietf@ietfa.amsl.com>; Mon, 4 Mar 2013 15:05:51 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id B1A8E21F87FF for <ietf@ietf.org>; Mon, 4 Mar 2013 15:05:50 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r24N5lVn009890; Tue, 5 Mar 2013 00:05:47 +0100 (CET)
Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r24N57hU028438; Tue, 5 Mar 2013 00:05:24 +0100 (CET)
Message-ID: <513528A3.4090006@cisco.com>
Date: Tue, 05 Mar 2013 00:05:07 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3
MIME-Version: 1.0
To: John Leslie <john@jlc.net>
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> <20130304145757.GJ84856@verdi>
In-Reply-To: <20130304145757.GJ84856@verdi>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: IETF IETF <ietf@ietf.org>
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 23:05:51 -0000

On 4/03/2013 15:57, John Leslie wrote:
> Eggert, Lars <lars@netapp.com> wrote:
>> 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"?
>     There is an obvious place to look for ideas: the directorates. See:
>
> http://www.ietf.org/iesg/directorate.html
That would help if the AD job would not be a full time job. Sure.
And I see some suggestions in this email thread to rely more on the 
directorates. That makes sense (but reviews vary greatly, however)
One track not mentioned in this thread is the document shepherd.
The document shepherd job, when done according to RFC 4858 (see 
specifically section 3.2 and 3.3) would save a huge amount of time to 
the AD.
Recently, for a single draft, I spent hoouuurrrssss trying to track all 
the open issues from the directorates and the IESG, and chasing the 
authors. On top of taking some time, I had to be become expert for every 
single aspect of the specification to evaluate whether the answer was 
right... while the document shepherd has already the expertise.
We should probably stress (again) the importance of document shepherd 
function...

Regards, Benoit