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

John C Klensin <john-ietf@jck.com> Mon, 08 December 2014 17:50 UTC

Return-Path: <john-ietf@jck.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 6FB131ACD3B for <ietf@ietfa.amsl.com>; Mon, 8 Dec 2014 09:50:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] 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 2RrkKZzgW7gh for <ietf@ietfa.amsl.com>; Mon, 8 Dec 2014 09:50:28 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E29D11A1BEF for <ietf@ietf.org>; Mon, 8 Dec 2014 09:50:27 -0800 (PST)
Received: from h8.int.jck.com ([198.252.137.35] helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Xy2S0-000FNu-MJ; Mon, 08 Dec 2014 12:50:24 -0500
Date: Mon, 08 Dec 2014 12:50:19 -0500
From: John C Klensin <john-ietf@jck.com>
To: Benoit Claise <bclaise@cisco.com>
Subject: Re: Last Call: <draft-secretaries-good-practices-06.txt> (IETF Working Groups' Secretaries) to Best Current Practice
Message-ID: <9720740610ED46E29131F87C@JcK-HP8200.jck.com>
In-Reply-To: <5485AA97.1080804@cisco.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> <0c7901d00f12$f6790a60$e36b1f20$@olddog.co.uk> <547F37C7.6030207@gmail.com> <0cbf01d00f1f$853f10d0$8fbd3270$@olddog.co.uk> <547F4CF2.9020707@gmail.com> <m261dnje1v.wl%randy@psg.com> <9DD12708-7020-4F59-9A58-40A74E9E96FA@gmail.com> <5485AA97.1080804@cisco.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.35
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/LyVCbSpNIMONkhbTIvlqnBpXqvY
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF Disgust <ietf@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: Mon, 08 Dec 2014 17:50:29 -0000


--On Monday, December 08, 2014 14:41 +0100 Benoit Claise
<bclaise@cisco.com> wrote:

>...
> If not, what's left for the chairs? Just a title?
> Exactly like having 3 WG chairs leads to dilution of
> responsibility, I fear that that same dilution of
> responsibility will apply here. At least with the way it's
> specified in this document, i.e, like a formal role.

yep.

> Maybe it boils down to the fact that I have not seen a
> successful secretary in action.

I have and I've seen them be good for leadership development
too.  But the successful ones actually should be pretty
invisible from outside the WG -- helping with the Chair workload
but with no independently-specified responsibility or authority.

I like the idea of allowing secretaries.  I just don't think
that formalizing the role or creating IETF-wide role
descriptions is likely to be helpful.  Indeed, I think it could
cause significant harm.

    john