RE: [newtrk] draft-rousskov-newtrk-id-state-00

Larry Masinter <LMM@acm.org> Tue, 06 April 2004 05:16 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 BAA20263 for <newtrk-archive@lists.ietf.org>; Tue, 6 Apr 2004 01:16:07 -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 i36532Pr026863 for <newtrk-outgoing@darkwing.uoregon.edu>; Mon, 5 Apr 2004 22:03:03 -0700 (PDT)
Received: (from majordom@localhost) by darkwing.uoregon.edu (8.12.11/8.12.11/Submit) id i36532oZ026856 for newtrk-outgoing; Mon, 5 Apr 2004 22:03:02 -0700 (PDT)
Received: from smtp-relay-7.sea.adobe.com (smtp-relay-7.adobe.com [192.150.22.7]) by darkwing.uoregon.edu (8.12.11/8.12.11) with ESMTP id i36531UH026473 for <newtrk@lists.uoregon.edu>; Mon, 5 Apr 2004 22:03:02 -0700 (PDT)
Received: from inner-relay-1.corp.adobe.com (inner-relay-1 [153.32.1.51]) by smtp-relay-7.sea.adobe.com (8.12.10/8.12.10) with ESMTP id i3652sSP012593; Mon, 5 Apr 2004 22:02:54 -0700 (PDT)
Received: from calsj-dev (calsj-dev.corp.adobe.com [153.32.1.193]) by inner-relay-1.corp.adobe.com (8.12.9/8.12.9) with ESMTP id i3652o3k010544; Mon, 5 Apr 2004 22:02:50 -0700 (PDT)
Received: from MasinterT40 ([130.248.176.33]) by mailsj-v1.corp.adobe.com (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTP id <0HVQ003SQGOM82@mailsj-v1.corp.adobe.com>; Mon, 05 Apr 2004 22:02:50 -0700 (PDT)
Date: Mon, 05 Apr 2004 22:02:39 -0700
From: Larry Masinter <LMM@acm.org>
Subject: RE: [newtrk] draft-rousskov-newtrk-id-state-00
In-reply-to: <Pine.BSF.4.58.0404052156450.74101@measurement-factory.com>
To: 'Alex Rousskov' <rousskov@measurement-factory.com>, newtrk@lists.uoregon.edu
Message-id: <0HVQ003SRGON82@mailsj-v1.corp.adobe.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Thread-index: AcQbjlpy0UiayGN7Qfy/oqkuuNPCSwAA8QIg
Sender: owner-newtrk@lists.uoregon.edu
Precedence: bulk
Reply-To: Larry Masinter <LMM@acm.org>
Content-Transfer-Encoding: 7bit

> http://www.ietf.org/internet-drafts/draft-rousskov-newtrk-id-state-00.txt

There are a couple of problems with the mechanism. The state of
a draft, the state of consensus on a draft, changes more rapidly
than the draft itself. So putting the state of the draft inside
the draft leads to a problem -- you submit a draft, then poll the
working group for consensus, then, after the working group has
discussed the draft, the state changes.

Since the status of drafts and working group progress changes frequently
and, unlike drafts, doesn't need to be stable, my suggestion is to
leave the internet drafts alone, and focus on the working group
web page.

Secondly, it's unlikely that the status will fit into a limited number
of neat categories. While it would be nice if you could just
assign a token out of a simple enumeration, but often the status
is much more complex.

My suggestion is this:

Every working group has a web page, but the chairs and draft authors
don't have much input into it.

http://www.ietf.org/html.charters/newtrk-charter.html

says "No Current Internet-Drafts", for example. What if each
working group had, on its web page, for each internet draft,
a "status" field which a working group chair could change?

In fact, what if each Internet Draft had a web page which listed,
at a minimum, its status, but also might contain open issues,
proposed resolutions, pointers to discussions in the mail archives,
etc.? 

This would give you more transparency, it would allow for
better updates, and would give participants better information.
We used issue-list tables in many working groups, and they've
been quite useful. Why don't we make them more generally available?

In the simplest case, the draft-status page could be auto-generated,
with a simple administrative form for updating the status among the
enumerated set, but we could make it possible for people to make
more extensive updates.

It might be convenient if each Internet Draft contained the URL
of the web page that described its status. (And, even better, an issue
list with issues, proposals, possible resolutions, etc, but that's
another story).

Larry
-- 
http://larry.masinter.net

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