Re: [datatracker-rqmts] Last Call: <draft-ietf-genarea-charter-tool-07.txt> (Requirements for a Working Group Charter Tool) to Informational RFC

Robert Sparks <rjsparks@nostrum.com> Tue, 15 March 2011 22:19 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: datatracker-rqmts@core3.amsl.com
Delivered-To: datatracker-rqmts@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC2C43A6EA1; Tue, 15 Mar 2011 15:19:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.597
X-Spam-Level:
X-Spam-Status: No, score=-102.597 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jCq7XYV5DJjq; Tue, 15 Mar 2011 15:19:28 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 486963A6BC6; Tue, 15 Mar 2011 15:19:26 -0700 (PDT)
Received: from [192.168.2.105] (pool-173-57-91-217.dllstx.fios.verizon.net [173.57.91.217]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p2FMKpwN086034 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 15 Mar 2011 17:20:51 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <20110311221124.17584.25925.idtracker@localhost>
Date: Tue, 15 Mar 2011 17:20:51 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <AE893EF9-04B7-4B8B-95FD-EF54F0BA8ABC@nostrum.com>
References: <20110311221124.17584.25925.idtracker@localhost>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1082)
Received-SPF: pass (nostrum.com: 173.57.91.217 is authenticated by a trusted mechanism)
Cc: datatracker-rqmts@ietf.org
Subject: Re: [datatracker-rqmts] Last Call: <draft-ietf-genarea-charter-tool-07.txt> (Requirements for a Working Group Charter Tool) to Informational RFC
X-BeenThere: datatracker-rqmts@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <datatracker-rqmts.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/datatracker-rqmts>, <mailto:datatracker-rqmts-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/datatracker-rqmts>
List-Post: <mailto:datatracker-rqmts@ietf.org>
List-Help: <mailto:datatracker-rqmts-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/datatracker-rqmts>, <mailto:datatracker-rqmts-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 22:19:29 -0000

Hi Paul -

In section 2.2, I would prefer either using the names the tracker currently uses for IESG evaluation:
"Discuss" and "Comment", or some set of words that do not intersect those, perhaps "Blocking" and
"Not-Blocking". The current set ("discuss" and "regular") will lead to confusion.

In section 2.7, you don't specifically capture WGs that currently exist, but are not rechartering at the moment.
I think you meant to as part of the second paragraph, but the last phrase could be read to be exclusive.

(As an aside - do you intend that for existing working groups, this history will go all the way back to when
the group was formed? Will we be able to count on <foo-charter-00> being the charter that the working group
formed with for all foo?)

In section 3.1 - It would be better to have the ability to override the tool's rejection of a name because some
previous effort (particularly abandoned ones) had the same name. If someone thought about using a name
5 years ago, but never took it even to the point of Internal Review, why should the tool force it not be be used now?
This is a place that human judgement should be allowed to be exercised.

Also, we should make sure the tool doesn't unintentionally make reopening a closed WG harder than intended.

It would help to clarify in the first bullet in 3.1 that the tool should prompt the AD, but not prevent them from
completing the move if that's the right thing to do. (The tool is providing a reminder, not enforcing a rule).

In the 4th bullet of that list, you ask the tool to send a note to the scretariat to schedule discussion on a telechat.
In practice today, this happens as part of the transition into External Review. I suggest moving the sentence into
the 3rd bullet.

In section 3.2's second bullet, it is possible, I believe, to directly approve a recharter from internal review. The tool
should allow that transition.

I'm a little concerned about taking working groups for which a recharter is being considered out of the state named
"WG Exists". Semantically, if you aren't in that state, it implies the WG doesn't exist, and I could see someone
drawing the wrong conclusion from a search. The best way to avoid this might be to rename the "WG Exists" state
to something like "WG Chartered - no rechartering effort currently in progress" (which I realize is too wordy).


RjS








On Mar 11, 2011, at 4:11 PM, The IESG wrote:

> 
> The IESG has received a request from the General Area Open Meeting WG
> (genarea) to consider the following document:
> - 'Requirements for a Working Group Charter Tool'
>  <draft-ietf-genarea-charter-tool-07.txt> as an Informational RFC
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2011-03-25. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-genarea-charter-tool/
> 
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-genarea-charter-tool/
> 
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce