[Icar] A modest proposal for moving forward with ICAR

"Spencer Dawkins" <spencer@mcsr-labs.org> Fri, 12 November 2004 14:20 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05019 for <icar-web-archive@ietf.org>; Fri, 12 Nov 2004 09:20:00 -0500 (EST)
Received: from megatron.ietf.org ([]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CScIq-0000yP-0c for icar-web-archive@ietf.org; Fri, 12 Nov 2004 09:21:28 -0500
Received: from localhost.localdomain ([] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSc65-0002K1-7G; Fri, 12 Nov 2004 09:08:17 -0500
Received: from odin.ietf.org ([] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CSc40-0001mU-CK for icar@megatron.ietf.org; Fri, 12 Nov 2004 09:06:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org []) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03896 for <icar@ietf.org>; Fri, 12 Nov 2004 09:06:06 -0500 (EST)
Received: from rwcrmhc11.comcast.net ([]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CSc5D-0000co-U6 for icar@ietf.org; Fri, 12 Nov 2004 09:07:34 -0500
Received: from dfnjgl21 (unknown[]) by comcast.net (rwcrmhc11) with SMTP id <2004111214052601300rmsnpe>; Fri, 12 Nov 2004 14:05:26 +0000
Message-ID: <08b301c4c8c0$c76641a0$90878182@DFNJGL21>
From: Spencer Dawkins <spencer@mcsr-labs.org>
To: ICAR Mailing List <icar@ietf.org>
Date: Fri, 12 Nov 2004 09:06:16 -0500
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7bit
Subject: [Icar] A modest proposal for moving forward with ICAR
X-BeenThere: icar@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Spencer Dawkins <spencer@mcsr-labs.org>
List-Id: Improved Cross-Area Review <icar.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/icar>, <mailto:icar-request@ietf.org?subject=unsubscribe>
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>
Sender: icar-bounces@ietf.org
Errors-To: icar-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: 7bit

My apologies in advance for reporting what seems like a coherent idea
that popped out during discussions with Pekka and Joel last night, but
I'd like to suggest a next step for ICAR that takes into account some
realities we're facing here.

- we need experience with ICAR reviews before nailing down new process
- we have some ICAR reviewers signed up, but probably not enough to do
  ICAR IETF-wide yet,
- we have a lot of reasons to do ICAR reviews, so I think we need to
  focus on one to get started
- I'm making structural suggestions during document reviews for
  Gen-ART ("late reviews"), that people agree are helpful but WAY too
  late in the process,
- we evolve our specifications from individual contributions under
  author control to working group documents under working group 
  in most cases, and
- we don't even have a BCP that talks about what it means to "adopt
  a draft as a working group".

Howzabout we

- identify an AD who is willing to commit one or more working groups
  as experiment fodder,
- assign ICAR reviewers to any individual drafts that are adopted
  as WG items
- review for document structure and completeness THEN, so
  draft-ietf-WG-mumble-00.txt is always our best effort, and
- report the reviews and experiences with this experiment in

This has the advantage of doing something now with the resources that
we have now ("contents may settle due to shipping").

Thoughts and comments?


Icar mailing list