RE: Last Call: <draft-secretaries-good-practices-06.txt> (IETF Working Groups' Secretaries) to Best Current Practice

"Adrian Farrel" <adrian@olddog.co.uk> Wed, 03 December 2014 16:05 UTC

Return-Path: <adrian@olddog.co.uk>
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 A921A1A1B8D for <ietf@ietfa.amsl.com>; Wed, 3 Dec 2014 08:05:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] 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 CMOmqhmNg_LX for <ietf@ietfa.amsl.com>; Wed, 3 Dec 2014 08:05:39 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6887C1A1BAC for <ietf@ietf.org>; Wed, 3 Dec 2014 08:05:39 -0800 (PST)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id sB3G5Zvt009602; Wed, 3 Dec 2014 16:05:35 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id sB3G5WXF009588 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 3 Dec 2014 16:05:33 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'John C Klensin' <john-ietf@jck.com>, 'Melinda Shore' <melinda.shore@gmail.com>
References: <20140612132656.8100.57197.idtracker@ietfa.amsl.com> <CAL0qLwZEo-AN4Er0gmbCyWJwTqOKBUKKMHEMQ_YqhK+oB+pcgg@mail.gmail.com> <547E9DBA.9040703@pi.nu> <0c1001d00ee9$36598670$a30c9350$@olddog.co.uk> <D51141636F7AC8CBFE11FA93@JcK-HP8200.jck.com> <547F23AD.90206@gmail.com> <F1301BDF5BA91E9561C6654C@JcK-HP8200.jck.com>
In-Reply-To: <F1301BDF5BA91E9561C6654C@JcK-HP8200.jck.com>
Subject: RE: Last Call: <draft-secretaries-good-practices-06.txt> (IETF Working Groups' Secretaries) to Best Current Practice
Date: Wed, 03 Dec 2014 16:05:28 -0000
Message-ID: <0c7901d00f12$f6790a60$e36b1f20$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQIDrSy+BS7nGKTH8AB3jI0uaBTw3wHfUf3eAfnYkx8BQ7zzegMOvf3JAOAcIbsCIb7gPpu9Vpww
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1018-21146.007
X-TM-AS-Result: No--35.451-10.0-31-10
X-imss-scan-details: No--35.451-10.0-31-10
X-TMASE-MatchedRID: u6ojmU07PKwzx9GDMr0HvzYTypjB3iDVuikHZcC6ceA/vgFpaLdKG1PZ g0NGsaNHDXL4sY4eXeZ1hldizFWvgDYAIpFXvjkBdiLDwvWethgOp2w/jxkSlL/XvPLNcin3SiQ Px3glce8NaogSex9N1QMF7Ja5rb3xYiS5IMZgPcOzI1v7J4hECoUxu0XmBQlT0mAM2eipqlq/bJ MjxVLZKSM4UmL8+gA/LAqbfdmj50R2Rany8ZWn3pYsKSXWWrsHwFK4YRN3aYd4X2t7q5DnFf0nu a2BBlFeIy5PgOde9KJrTOvKB1axc4coPy7Xk6in/O70vD0Lt8C3dp6DuD+6wCIWzbRXGr/CVNEb /igMznDv7KQvOHjFKJVI+00Z1dsods1VAj9mPJ0mtTGirqG/D34yToAKzDgmHRspwjeLvSUs5ii SbV7/wU1ANork0E8UHDtbfLIirUkVq2ox1dkUGWzBijri5+RV2aYdnwn7qHdF+YXPIqAdvnZruQ G5/1P7lO/Gtv45h7lQ2ydzFfJQt6GYxp7PhTUAMIiU395I8H0fXzVgO0hVqjhZSwDkDbch9pjZd gwQjPlMGZpWuTNwqkzxJ+s43oG7WONZnYJ3/08VQ1GjM4M/GCDPOgHqOrGCInzOyTDR1utNNlDh 2H9pCHpBq6CZodE51g4a32PkotDlRxm3A2wKujl/1fD/GopdyJ1gFgOMhOn6APa9i04WGCq2rl3 dzGQ1A/3R8k/14e0=
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/DI12K1qK2-8XKC0Ix1lxF4RZ5dY
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
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: Wed, 03 Dec 2014 16:05:42 -0000

John,

I placed the document on the IESG telechat after a period of silence that
followed the publication of the -07 version of the document and an email
summarising the changes from the editor.

At the same time I sent an additional note to this list. I don't know (or care)
whether that is what triggered renewed conversations, but I welcome them. I
don't think you should take such a negative tone and assume that the no-one
wants to listen to your concerns. Let's see whether we can address them before
the telechat in just over two weeks' time.

I believe I see two issues raised by you and Melinda in this thread which I may
summarise as:
- This I-D needs to be clearer that it is not normative, not defining process, 
   and not directing WG chairs to use secretaries.
- The use of a WG secretary somewhat reflects an abdication of
  responsibility by a WG chair who was appointed to carry out these tasks.

Now, I think the first of these might be something we can address with some
careful text in the Abstract and Introduction. Would you agree? If so, I' m sure
we can work something out.

The second is more of a philosophical question. The chair is "contracted" to
deliver and given certain powers to achieve delivery. Can the chair delegate the
actions while supervising their implementation and carrying responsibility for
their correctness? This is maybe an issue we can address by making it clear who
carries responsibility  for actions carried out by a WG secretary and what the
complaint/appeals path is. 

But I would note for the second of these points that the WG secretary role
exists and there is also the concept of a "delegate". These ways of handling
IETF work are not introduced or made concrete by this document. We can't,
therefore, hold this document to account for the existence of things we don't
like. We can only ensure that the document accurately describes what exists.

Regards,
Adrian

> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of John C Klensin
> Sent: 03 December 2014 15:26
> To: Melinda Shore; ietf@ietf.org
> Subject: Re: Last Call: <draft-secretaries-good-practices-06.txt> (IETF
Working
> Groups' Secretaries) to Best Current Practice
> 
> 
> 
> --On Wednesday, December 03, 2014 05:52 -0900 Melinda Shore
> <melinda.shore@gmail.com> wrote:
> 
> > I'd like to echo what John said.  I'm somewhat concerned that
> > the growth of the wg secretary role has something to do with
> > an inability (or unwillingness) to deal directly with poor
> > chair performance.  Individual chairs may prefer to have the
> > assistance but I am truly sorry to see this becoming typical
> > working group practice.  "All problems can be solved by
> > introducing a layer of indirection" may be a slightly
> > entertaining joke about programming practice but it seems a
> > woeful approach to organizational problems.
> 
> Melinda,
> 
> Well put and thanks for getting to the core of the problem.   I
> actually like having WG Secretaries for a few reasons that are
> separate from the above (and largely separate from the
> discussion in the document).  Used well, under the right
> circumstances, and with appropriate care, the WG Secretary role
> may be a good leadership development activity -- under some
> circumstances, far more appropriate than appointing a junior or
> inexperienced person as a co-chair who really shouldn't be
> considered accountable for WG performance.
> 
> For those who like structure and titles, perhaps we should
> formally create an "Assistant Chair" or "Apprentice Chair" role,
> give it a fancy title that would look good on CVs and to
> corporate folks working on travel budgets, and downplay
> "Secretary".  I hope I'm joking.
> 
> But, again, use of "WG Secretary" for leadership development is
> an argument for flexibility with the title and role, not a
> document that appears to suggest that all good WGs should have
> secretaries and that good secretaries should do some particular
> list of things.
> 
> That is the last from me on this topic, especially since the
> tracker says "(Has enough positions to pass.)".   If true, that
> leaves the appeals process (on the grounds that these issues
> have been raised before, going back at least to August, and
> never seriously addressed) and/or a discussion with the Nomcom
> (on the grounds that the IESG is exercising bad judgment by
> regularly putting these "more rules and more structure"
> proposals in front of the community and the Nomcom is the only
> realistic remedy for collective IESG bad judgment).
> 
>    john