IETF Logo Mail Archive

RE: Appointment of a Transport Area Director

"Romascanu, Dan (Dan)" <dromasca@avaya.com> Tue, 05 March 2013 10:21 UTC

Return-Path: <dromasca@avaya.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 0431B21F86A1 for <ietf@ietfa.amsl.com>; Tue, 5 Mar 2013 02:21:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.099
X-Spam-Level:
X-Spam-Status: No, score=-103.099 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 SNNSJwlYHIeQ for <ietf@ietfa.amsl.com>; Tue, 5 Mar 2013 02:21:13 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by ietfa.amsl.com (Postfix) with ESMTP id 3101121F8651 for <ietf@ietf.org>; Tue, 5 Mar 2013 02:21:09 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAFupNVHGmAcF/2dsb2JhbABEgma/boEEFnOCHwEBAQEDEigxDgwEAgEIDQEDBAEBAQoUCQcyFAkIAgQBDQUIARmHcQELoUqMa5A1jUsRfyYLAgUGgllhA5xkilSDCIFyNQ
X-IronPort-AV: E=Sophos;i="4.84,786,1355115600"; d="scan'208";a="1764"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 05 Mar 2013 05:21:06 -0500
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 05 Mar 2013 05:20:21 -0500
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.02.0328.009; Tue, 5 Mar 2013 05:21:04 -0500
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: Alia Atlas <akatlas@gmail.com>, Benoit Claise <bclaise@cisco.com>
Subject: RE: Appointment of a Transport Area Director
Thread-Topic: Appointment of a Transport Area Director
Thread-Index: AQHOF8wEjFxAbpkk/UKydEte4N67h5iT7JyAgAAXC4CAADhygIAAA2uAgAAB3gCAADcogIABNlMAgAAaAACAAA23gIAAHvWAgACIHYCAAAHqAIAAZecg
Date: Tue, 05 Mar 2013 10:21:04 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA09E8BC@AZ-FFEXMB04.global.avaya.com>
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> <513528A3.4090006@cisco.com> <CAG4d1rfCAukFHqwXRQ4D5Rz8RGriMxPi_CZjOav3MFbR+FTsMg@mail.gmail.com>
In-Reply-To: <CAG4d1rfCAukFHqwXRQ4D5Rz8RGriMxPi_CZjOav3MFbR+FTsMg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.46]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: John Leslie <john@jlc.net>, 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: Tue, 05 Mar 2013 10:21:14 -0000

We had such a WG-Chairs session dedicated exactly to this topic (document shepherding) at IETF-82 - including a panel of document shepherds and ADs sharing experience and discussing ways to improve the process and make the shepherds role more efficient. 

Dan




> -----Original Message-----
> From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of
> Alia Atlas
> Sent: Tuesday, March 05, 2013 1:12 AM
> To: Benoit Claise
> Cc: John Leslie; IETF IETF
> Subject: Re: Appointment of a Transport Area Director
> 
> Perhaps even dedicate a WG-Chairs lunch meeting to it?  I think the role
> has grown over the years.
> 
> Alia
> 
> On Mon, Mar 4, 2013 at 6:05 PM, Benoit Claise <bclaise@cisco.com> wrote:
> > 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
> >
> >

v2.23.0 | Report a Bug | By Email