Re: [Icar] ICAR draft charter rev 2

David Meyer <dmm@1-4-5.net> Mon, 12 January 2004 22:28 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25895 for <icar-archive@odin.ietf.org>; Mon, 12 Jan 2004 17:28:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgAXd-0008K0-DA for icar-archive@odin.ietf.org; Mon, 12 Jan 2004 17:28:13 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0CMSCJM031972 for icar-archive@odin.ietf.org; Mon, 12 Jan 2004 17:28:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgAXa-0008JX-NO for icar-web-archive@optimus.ietf.org; Mon, 12 Jan 2004 17:28:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25873 for <icar-web-archive@ietf.org>; Mon, 12 Jan 2004 17:28:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AgAXY-00067h-00 for icar-web-archive@ietf.org; Mon, 12 Jan 2004 17:28:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AgAVh-000647-00 for icar-web-archive@ietf.org; Mon, 12 Jan 2004 17:26:14 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AgAUX-000613-00 for icar-web-archive@ietf.org; Mon, 12 Jan 2004 17:25:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgAUZ-0008Fb-36; Mon, 12 Jan 2004 17:25:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgATg-0008EH-Tg for icar@optimus.ietf.org; Mon, 12 Jan 2004 17:24:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25798 for <icar@ietf.org>; Mon, 12 Jan 2004 17:24:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AgATe-0005xw-00 for icar@ietf.org; Mon, 12 Jan 2004 17:24:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AgARs-0005uW-00 for icar@ietf.org; Mon, 12 Jan 2004 17:22:16 -0500
Received: from m106.maoz.com ([205.167.76.9]) by ietf-mx with esmtp (Exim 4.12) id 1AgAQl-0005or-00 for icar@ietf.org; Mon, 12 Jan 2004 17:21:08 -0500
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1]) by m106.maoz.com (8.12.10/8.12.10) with ESMTP id i0CMKb6f018299; Mon, 12 Jan 2004 14:20:37 -0800
Received: (from dmm@localhost) by m106.maoz.com (8.12.10/8.12.10/Submit) id i0CMKbEx018298; Mon, 12 Jan 2004 14:20:37 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Mon, 12 Jan 2004 14:20:37 -0800
From: David Meyer <dmm@1-4-5.net>
To: icar@ietf.org
Subject: Re: [Icar] ICAR draft charter rev 2
Message-ID: <20040112222037.GA18177@1-4-5.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-philosophy: "I just had to let it go" -- John Lennon
Sender: icar-admin@ietf.org
Errors-To: icar-admin@ietf.org
X-BeenThere: icar@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/icar>, <mailto:icar-request@ietf.org?subject=unsubscribe>
List-Id: Improved Cross-Area Review <icar.ietf.org>
List-Post: <mailto:icar@ietf.org>
List-Help: <mailto:icar-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/icar>, <mailto:icar-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

	This looks good. Just a few nits:

	(i).	What does "submit drafts" mean? I assume (again)
		that we mean "produce WG document" (which in turn
		means that the document name is of the form
		draft-ietf-icar-xxxx, was adopted by WG
		consensus, and it can be found on  
		ftp://ftp.ietf.org/internet-drafts); this is in
		contrast to "submit draft ... to IESG..." (all of
		this is really a nit an belongs in a discussion
		of how one writes a charter, I suppose),

	(ii).	Can we be more precise about what "earlier" means
		in "It is an explicit goal of the WG to come up
		with mechanisms encouraging earlier review of the
		documents"? My first question when I read this
		was "earlier than what"? 

	(iii).	SEP 2005: Evaluate WG progress and potential;
		close or recharter 

		What does it mean (what is meant) by evaluating
		the WG "potential" (i.e., we could be talking
		about a kind of potential s/a potential energy,
		but I'm pretty sure that isn't what is entended).

	Other than that, the charter defines some reasonable
	goals within a (importantly) constrained scope, and time
	frames. 

	Dave


>> Revision 2 below, please.
>> 
>> -- 
>> Alex
>> 
>>    WG name: improved cross-area review (icar)
>> 
>>    Chairs: <TBD>
>> 
>>    General Area Director(s):
>>     Harald Alvestrand <harald@alvestrand.no>
>> 
>>    General Area Advisor:
>>     Harald Alvestrand <harald@alvestrand.no>
>>    
>>    Mailing list: icar@ietf.org
>>    Subscription: icar-request@ietf.org
>>    Archives : https://www1.ietf.org/mail-archive/working-groups/icar/current/maillist.html
>> 
>>    WG Description:
>> 
>>      The WG will work out mechanisms for improved cross-functional
>>      review within the IETF, addressing the issues identified by the
>>      PROBLEM WG. This includes a better community review, as well as
>>      more structured pre-IESG review that may be used to improve
>>      scalability of the IESG review function.
>> 
>>      Definitions:
>> 
>>       o Cross-functional review: document review covering different
>>       aspects of Internet technology, including those represented by
>>       WGs within different IETF areas.
>> 
>>       o Community review: document review performed by individual IETF
>>       participants and not caused by their responsibilities within
>>       the IETF management structure.
>> 
>>       o Structured review: more formal and role-based document review
>>       performed by individuals assuming certain responsibilities (such
>>       as by WG chairs, directorate and IESG members.)
>> 
>>      It is an explicit goal of the WG to come up with mechanisms
>>      encouraging earlier review of the documents. An early review is
>>      best for catching architectural problems while they're still
>>      relatively easy to solve. In particular, many cross-functional
>>      interactions can be spotted and dealt with, thus avoiding many
>>      "late surprises". A final review (currently done by the IESG) can
>>      catch remaining cross-functional interactions, as well as deal
>>      with overall quality issues.
>>      
>>      The WG will cooperate with others in starting and evaluating
>>      experiments with early community and structured reviews. The
>>      evaluation of such experiments may be published as Informational
>>      RFCs if the group so desires.
>> 
>>      The WG will also coordinate with other WGs involved in the IETF
>>      reform process on proposed changes to the IETF Working Group
>>      operations and Standards process if those are considered
>>      necessary.
>> 
>>    WG milestones:
>> 
>>      FEB 2004: Submit drafts on improved community and structured reviews
>>      SEP 2004: Submit draft on improved community review to
>>                the IESG for publication as BCP
>>      SEP 2004: Submit draft on improved structured community review to
>>                the IESG for publication as BCP
>>      SEP 2005: Evaluate WG progress and potential; close or recharter
>> 
>> 
>> _______________________________________________
>> Icar mailing list
>> Icar@ietf.org
>> https://www1.ietf.org/mailman/listinfo/icar
>> 
>> ===8<===========End of original message text===========

_______________________________________________
Icar mailing list
Icar@ietf.org
https://www1.ietf.org/mailman/listinfo/icar