Re: [Icar] Thoughts on ICAR direction

"Joel M. Halpern" <joel@stevecrocker.com> Mon, 08 November 2004 15:21 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18431 for <icar-web-archive@ietf.org>; Mon, 8 Nov 2004 10:21:37 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRBLS-0003t3-KV for icar-web-archive@ietf.org; Mon, 08 Nov 2004 10:22:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRBDK-0004Hf-Rl; Mon, 08 Nov 2004 10:13:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRAyb-0003Xq-U6 for icar@megatron.ietf.org; Mon, 08 Nov 2004 09:58:37 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15590 for <icar@ietf.org>; Mon, 8 Nov 2004 09:58:35 -0500 (EST)
Received: from ns.execdsl.net ([208.184.15.238] helo=EXECDSL.COM) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRAz0-0003BY-CM for icar@ietf.org; Mon, 08 Nov 2004 09:59:12 -0500
Received: from [130.129.133.92] (HELO JLaptop.stevecrocker.com) by EXECDSL.COM (CommuniGate Pro SMTP 3.3) with ESMTP id 7906950 for icar@ietf.org; Mon, 08 Nov 2004 09:57:48 -0500
Message-Id: <6.1.2.0.0.20041108095627.03b67ec0@localhost>
X-Sender: joel@stevecrocker.com@localhost
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Mon, 08 Nov 2004 09:57:46 -0500
To: icar@ietf.org
From: "Joel M. Halpern" <joel@stevecrocker.com>
Subject: Re: [Icar] Thoughts on ICAR direction
In-Reply-To: <002c01c4c54d$4cdd9440$90878182@DFNJGL21>
References: <p06020428bdb18a2866e4@[192.168.2.2]> <002c01c4c54d$4cdd9440$90878182@DFNJGL21>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
X-BeenThere: icar@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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: 9182cfff02fae4f1b6e9349e01d62f32

Note that we have not waited for the working group to even fully approve 
the document before trying to make the experiment happen.

My concern, speaking personally, is that the community does not seem very 
interested in actually seeing a well defined pool of early reviewers happen.

Yours,
Joel

At 11:42 PM 11/7/2004, Spencer Dawkins wrote:
>In all fairness, ICAR was chartered pre-July14, so the only "legal" way 
>forward was to develop a full BCP before implementing the BCP procedures 
>to find out if they actually work! July14 - now approved as BCP 93, RFC 
>3933 <draft-klensin-process-july14-02.txt>, and coming soon to an RFC 
>mirror near you - has as its goal gathering experimental experience with 
>process changes before publishing the usual BCP document - and 
>specifically calls out opportunities for trials in one or two corners of 
>the IETF, rather than mandating deployment to the entire IETF community at 
>once, as a normal BCP document would do. So, I agree completely.


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