Re: archives (was The other parts of the report....

"Spencer Dawkins" <spencer@mcsr-labs.org> Sat, 11 September 2004 12:00 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 IAA11938; Sat, 11 Sep 2004 08:00:49 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C66d1-0007UT-23; Sat, 11 Sep 2004 08:05:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C66VF-0001BA-44; Sat, 11 Sep 2004 07:57:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C66Ut-0000vp-W5 for ietf@megatron.ietf.org; Sat, 11 Sep 2004 07:56:52 -0400
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 HAA11707 for <ietf@ietf.org>; Sat, 11 Sep 2004 07:56:50 -0400 (EDT)
Received: from rwcrmhc12.comcast.net ([216.148.227.85]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C66ZA-0007Hg-NV for ietf@ietf.org; Sat, 11 Sep 2004 08:01:17 -0400
Received: from dfnjgl21 (c-24-1-99-5.client.comcast.net[24.1.99.5]) by comcast.net (rwcrmhc12) with SMTP id <2004091111561401400md9q4e> (Authid: sdawkins@comcast.net); Sat, 11 Sep 2004 11:56:15 +0000
Message-ID: <050a01c497f6$567e4000$0400a8c0@DFNJGL21>
From: Spencer Dawkins <spencer@mcsr-labs.org>
To: ietf@ietf.org
References: <66EDBDB3-0331-11D9-B4E7-000A95E35274@cisco.com>
Date: Sat, 11 Sep 2004 06:55:24 -0500
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="response"
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.1 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: 7bit
Subject: Re: archives (was The other parts of the report....
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Spencer Dawkins <spencer@mcsr-labs.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: 7bit

Dear Harald-the-General-AD,

Can we PLEASE do as Melinda says - change the policy now for new 
drafts? so we can stop having part of this conversation and, in the 
meantime, stop making the problem worse?

I review documents for Harald as part of Gen-ART. It is really nice to 
be able to look back at previous versions of a draft and see what's 
been changing. I can trivially do this on a number of other sites, but 
not on the IETF site. This defines "dumb".

Henrik Levkowetz from the Proto team showed me a beautiful "history of 
the draft from 00 to RFC, including ID-Tracker" prototype in San 
Diego - but we can't implement it with our current boilerplate. This 
defines "dumber".

And we know that poor documentation of where we've been before is a 
problem. We've even reached IETF consensus on this. From RFC 3774:

2.7.  Working Group Dynamics can make Issue Closure Difficult

   The IETF appears to be poor at making timely and reasonable 
decisions
   that can be guaranteed to be adhered to during the remainder of a
   process or until shown to be incorrect.

... deleted down to

   Participants are frequently allowed to re-open previously closed
   issues just to replay parts of the previous discussion without
   introducing new material.  This may be either because the decision
   has not been clearly documented, or it may be a maneuver to try to
   get a decision changed because the participant did not concur with
   the consensus originally.  In either case, revisiting decisions 
stops
   the process from moving forward, and in the worst cases, can
   completely derail a working group.

Please note that 3774 is Informational - it is pointedly NOT a "Best 
Current Practice"!!!

Is this a change that requires the IPR working group to express an 
opinion, or can we just do it? and stop vaguely pointing new 
participants with recycled ideas to "the mailing list", some of which 
have been in existence since before HTTP/0.9?

Spencer

From: "Melinda Shore" <mshore@cisco.com>

>
> On the other hand, I'd hate to see indecision about what to do
> about old ids seep into indecision about what to do about new
> ids going forward.  It seems to me that a new policy saying that
> any ids submitted in the future will be archived by the IETF unless
> the authors object is far better than allowing the current
> situation to continue. 



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