URL Process List

Rich Petke <R.PETKE@csi.compuserve.com> Thu, 13 February 1997 16:34 UTC

Received: from cnri by ietf.org id aa26120; 13 Feb 97 11:34 EST
Received: from services.Bunyip.Com by CNRI.Reston.VA.US id aa20031; 13 Feb 97 11:34 EST
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id KAA19879 for uri-out; Thu, 13 Feb 1997 10:55:30 -0500
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id KAA19874 for <uri@services.bunyip.com>; Thu, 13 Feb 1997 10:55:28 -0500
Received: from dub-img-2.compuserve.com by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA04611 (mail destined for uri@services.bunyip.com); Thu, 13 Feb 97 10:55:26 -0500
Received: by dub-img-2.compuserve.com (8.6.10/5.950515) id KAA14182; Thu, 13 Feb 1997 10:55:24 -0500
Date: Thu, 13 Feb 1997 10:53:56 -0500
From: Rich Petke <R.PETKE@csi.compuserve.com>
To: URI <uri@bunyip.com>
Subject: URL Process List
Message-Id: <CSI_6310-120121@CompuServe.COM>
Sender: owner-uri@bunyip.com
Precedence: bulk

Last month I announced the availability of a list (ietf-url@imc.org) for the
discussion of the PROCESS  related to the development of new new URL schemes.
The idea was to keep these discussions (and any WG that forms out of these
discussions) separate from the issues related to advancing the existing URL RFCs
to draft status.

To date only 28 people have subscribed to ietf-url@imc.org.

Larry Masinter started the ball rolling by publishing an I-D for a proposed
process BUT there has been very little discussion on the draft or on the topic
as a whole.

The key question that has to be asked is:  Is there still interest in the URI
community for developing this process document?

If yes, we need to move forward with a charter.  If not, we can always find
something else to do with our time and not have to worry about scheduling in
Memphis.

Rich Petke (r.petke@csi.compuserve.com)