RE: [newtrk] a crufty last call

Larry Masinter <LMM@acm.org> Thu, 14 October 2004 16:54 UTC

Received: from darkwing.uoregon.edu (root@darkwing.uoregon.edu [128.223.142.13]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06760 for <newtrk-archive@lists.ietf.org>; Thu, 14 Oct 2004 12:54:00 -0400 (EDT)
Received: from darkwing.uoregon.edu (majordom@localhost [127.0.0.1]) by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i9EGTm89012321; Thu, 14 Oct 2004 09:29:48 -0700 (PDT)
Received: (from majordom@localhost) by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i9EGTm01012313; Thu, 14 Oct 2004 09:29:48 -0700 (PDT)
Received: from psmtp.com (exprod6ob2.obsmtp.com [64.18.1.212]) by darkwing.uoregon.edu (8.12.11/8.12.11) with SMTP id i9EGTjtW012250 for <newtrk@lists.uoregon.edu>; Thu, 14 Oct 2004 09:29:45 -0700 (PDT)
Received: from source ([192.150.22.8]) by exprod6ob2.obsmtp.com ([64.18.5.12]) with SMTP; Thu, 14 Oct 2004 09:29:33 PDT
Received: from inner-relay-3.corp.adobe.com (inner-relay-3 [153.32.251.51]) by smtp-relay-8.adobe.com (8.12.10/8.12.10) with ESMTP id i9EGTObA014430 for <newtrk@lists.uoregon.edu>; Thu, 14 Oct 2004 09:29:35 -0700 (PDT)
Received: from calsj-dev (calsj-dev.corp.adobe.com [153.32.1.193]) by inner-relay-3.corp.adobe.com (8.12.9/8.12.9) with ESMTP id i9EGTO0S021006 for <newtrk@lists.uoregon.edu>; Thu, 14 Oct 2004 09:29:24 -0700 (PDT)
Received: from MasinterT40 ([130.248.178.41]) by mailsj-v1.corp.adobe.com (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTP id <0I5L00JL61T0V4@mailsj-v1.corp.adobe.com> for newtrk@lists.uoregon.edu; Thu, 14 Oct 2004 09:29:24 -0700 (PDT)
Date: Thu, 14 Oct 2004 09:29:24 -0700
From: Larry Masinter <LMM@acm.org>
Subject: RE: [newtrk] a crufty last call
In-reply-to: <p0602045ebd9426e3c579@[192.168.1.103]>
To: newtrk@lists.uoregon.edu
Message-id: <0I5L00JL71T0V4@mailsj-v1.corp.adobe.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Thread-index: AcSx8slCD3sbjbVfQguDdCN88UPedQAFnhAg
Sender: owner-newtrk@lists.uoregon.edu
Precedence: bulk
Reply-To: Larry Masinter <LMM@acm.org>
Content-Transfer-Encoding: 7bit

I wish the proposal were expressed in the positive sense rather
than negative.  Rather than a "Decommissioning Procedure",
talk about a "Retention Procedure".

The result may be the similar, but the sense of movement
and the purpose of the committee would be different. The
committee's job is to solicit someone making the case that
a document should not be moved to Historic, and, to some degree,
to evaluate the cases made.

Once the committee's charter is seen as a positive
progression rather than a negative, other activities
come to mind.

I'd like to see the committee not just solicit cases
of implementation experience and active use, but also
look for documents where the actual implementations and
use diverge from the document actually published, and to
solicit active work to update the specification to match
practice, or at least gather errata.

I'd like to see the documentation of active use and
implementation experience gathered, edited, and published
as a positive contribution that will improve the value
of the IETF's output.

If the work product is "some documents now classified
as Historic", that's not very valuable. If the work product
is "some documents' current status and use published,
others left to go to Historic", that's much more valuable
to the community.

Larry




> -----Original Message-----
> From: owner-newtrk@lists.uoregon.edu 
> [mailto:owner-newtrk@lists.uoregon.edu] On Behalf Of Margaret 
> Wasserman
> Sent: Thursday, October 14, 2004 5:58 AM
> To: scott bradner; newtrk@lists.uoregon.edu
> Subject: Re: [newtrk] a crufty last call
> 
> 
> Hi All,
> 
> >consider this question
> >	"should this working group develop process(es) with the aims
> >	 described in the ID draft-ietf-newtrk-cruft-00.txt?"
> 
> I'll go against the grain with a "no" vote.
> 
> I am not against the idea of moving documents that shouldn't be on 
> the standards track to Historic, but I don't see any reason why we 
> need a WG to develop processes to do that.  Nor do I understand why 
> we need an officially constituted committee.
> 
> It is my opinion that if the main advocates of this work had chosen 
> to spend their time and effort doing the actual work of moving crufty 
> drafts to Historic instead of arguing about an official "procedure" 
> for doing it, we'd be done now.
> 
> Margaret
> .
> newtrk resources:_____________________________________________________
> web user interface: http://darkwing.uoregon.edu/~llynch/newtrk.html
> mhonarc archive: 
> http://darkwing.uoregon.edu/~llynch/newtrk/index.html

.
newtrk resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/newtrk.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/newtrk/index.html