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 17:31 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 CA00F1A1B68 for <ietf@ietfa.amsl.com>; Wed, 3 Dec 2014 09:31:19 -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 cJXYN4RueKLz for <ietf@ietfa.amsl.com>; Wed, 3 Dec 2014 09:31:18 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5FA21A1B17 for <ietf@ietf.org>; Wed, 3 Dec 2014 09:31:17 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id sB3HVEvB020215; Wed, 3 Dec 2014 17:31:14 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id sB3HVBpE020193 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 3 Dec 2014 17:31:11 GMT
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'Ralph Droms' <rdroms.ietf@gmail.com>, 'ietf' <ietf@ietf.org>
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> <FB01FE06-54EF-4935-BA8C-567C96EAAF69@gmail.com>
In-Reply-To: <FB01FE06-54EF-4935-BA8C-567C96EAAF69@gmail.com>
Subject: RE: Last Call: <draft-secretaries-good-practices-06.txt> (IETF Working Groups' Secretaries) to Best Current Practice
Date: Wed, 03 Dec 2014 17:31:06 -0000
Message-ID: <0cbe01d00f1e$ed2736b0$c775a410$@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+BS7nGKTH8AB3jI0uaBTw3wHfUf3eAfnYkx8BQ7zzegMOvf3JAw2U+pybvRhoYA==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1018-21148.001
X-TM-AS-Result: No--11.867-10.0-31-10
X-imss-scan-details: No--11.867-10.0-31-10
X-TMASE-MatchedRID: 6otD/cJAac0zx9GDMr0HvzYTypjB3iDVuikHZcC6ceA/vgFpaLdKGxtL F2kvHn0Csl/Z/K9F5YcZkOuFEoLztBo/F4wweNBub0SEnibtBBBhBfGxmdHCgvFJXtgF4GFLK5/ Vs9QmFLAtbtENyAspMTKC27mRz/poRft0j1zMO0z+9NMYfcGbZxkqnRJng/51feHPnu31iHAC8r Q71d/Yfq+FR+Nq9NNepotE4TlUkupTqTvkr4no8EK9qlwiTElf9mnDjfUPq55aW2Ktn+I8/qK6G 9Czac5IKXahC38DkFrLyJBtfObzsN/VfsVgOrak+mHRL3uzOiK36GGfwjLoZZsoi2XrUn/JyeMt MD9QOgDGlDvsLUDW2o6HM5rqDwqtyTHjW+9Dir7ywyLTPYdTqFuPiW7WBKvurg8XPT7cBAlDRNx Wsp/6Kg==
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Nd3i058HNy08SQb97waQhv7F98o
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 17:31:20 -0000

Hi Ralph,

> Here are my opinions on how to proceed...
> 
> First, it's important that RFC 2418 be updated to allow for a WG
> secretary to take on greater responsibilities, at the discretion of
> the WG chairs.  It's also important that the update include formal
> recognition that WG secretaries should be given access to WG support
> tools.  Therefore, I recommend that RFC 2418 be updated with a short
> RFC that expands the potential role for WG secretaries and that
> formally grants permission for secretaries to have access to WG tools.

I have not seen your draft revising RFC 2418. Did I miss it or are you
recommending that other people do work?

I'm sure that if you start this work others will send you their review comments.

> Second, because the [the document contains] a series of recommendations
> that may not apply to all WGs and that may change over time, I
> recommend that this very useful material be integrated into the IETF
> wiki "Working Group Chairs' Page" <http://www.ietf.org/wg/chairs-page.html>

The document even recommends doing that.

The authors, however, thought that just like the way the Tao evolved, there is
advantage in having community review and consensus of the starting text. This
can then be updated through the wiki as the situation evolves.

Does that community review and consensus need to be published through an RFC?
Probably not, but it is a convenient way to do so. 
Does publication as an Informational RFC somehow ossify the recommendations? I
don't think so.

Cheers,
Adrian