Re: Call for Comment: RFC 4693 experiment

Harald Alvestrand <harald@alvestrand.no> Thu, 07 February 2008 02:33 UTC

Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietfarch-ietf-announce-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 157713A6FE3 for <ietfarch-ietf-announce-archive@core3.amsl.com>; Wed, 6 Feb 2008 18:33:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from core3.amsl.com ([127.0.0.1]) by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lKFBUXEkDJbn; Wed, 6 Feb 2008 18:33:19 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0BF3B3A6C1A; Wed, 6 Feb 2008 18:33:19 -0800 (PST)
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 811703A6D48; Wed, 6 Feb 2008 18:33:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from core3.amsl.com ([127.0.0.1]) by localhost (mail.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id izQUDd3yggah; Wed, 6 Feb 2008 18:33:16 -0800 (PST)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by core3.amsl.com (Postfix) with ESMTP id A08EA3A6C7E; Wed, 6 Feb 2008 18:33:16 -0800 (PST)
Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id C1ED92596BA; Thu, 7 Feb 2008 03:34:46 +0100 (CET)
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14571-10; Thu, 7 Feb 2008 03:34:41 +0100 (CET)
Received: from [192.168.1.54] (162.80-203-220.nextgentel.com [80.203.220.162]) by eikenes.alvestrand.no (Postfix) with ESMTP id 97A482580CF; Thu, 7 Feb 2008 03:34:41 +0100 (CET)
Message-ID: <47AA6E26.20305@alvestrand.no>
Date: Thu, 07 Feb 2008 03:34:14 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Thunderbird 1.5.0.14pre (X11/20071023)
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
Subject: Re: Call for Comment: RFC 4693 experiment
References: <E1JFE8L-0006Gq-9L@ietf.org> <302CC207-4580-4F03-BB3A-C686FDBA7F5D@cisco.com>
In-Reply-To: <302CC207-4580-4F03-BB3A-C686FDBA7F5D@cisco.com>
X-Enigmail-Version: 0.94.2.0
X-Virus-Scanned: by amavisd-new at alvestrand.no
Cc: ietf@ietf.org, IETF Announcement list <ietf-announce@ietf.org>, iesg@iesg.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ietf-announce.ietf.org>
List-Unsubscribe: <http://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <http://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

Cullen Jennings skrev:
>
> I'd like to comment as an individual on one part of our process for
> doing IONs.
>
> The process for publishing them has many bottlenecks and delays and we
> need a better way of doing it. If we decide to continue with IONs, I
> will provide detailed comments on issues with how we are doing them.
> Overall I think we would need tools so that an ION author can put a
> new version, reviewers could easily see the diffs from the previous
> version, and when the document is approved by the approving body, it
> gets posted and does not require manual editing of the document after
> it was approved. 
one comment... the procedure as described in the ION RFC has exactly two
requirements:

- that one should be able to tell who approved it, and when
- that one should be able to tell the difference between a final
document and a draft.

I think we need to continue to have both of these properties.

There's no requirement that a process exist for handling them, or even
that it be consistent between IONs. The existing process is,
deliberately, unconstrained by the RFC.

I could argue that we might need fewer tools, not more; any tool you
create increases the number of tools one has to learn in order to get
one's job done. But that's part of what the experiment has been about.

                      Harald

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
http://www.ietf.org/mailman/listinfo/ietf-announce