Re: URL Process List

Dan_Zigmond@wink.com Thu, 13 February 1997 18:57 UTC

Received: from cnri by ietf.org id aa00265; 13 Feb 97 13:57 EST
Received: from services.Bunyip.Com by CNRI.Reston.VA.US id aa01250; 13 Feb 97 13:57 EST
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id NAA21798 for uri-out; Thu, 13 Feb 1997 13:22:10 -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 NAA21793 for <uri@services.bunyip.com>; Thu, 13 Feb 1997 13:22:08 -0500
From: Dan_Zigmond@wink.com
Received: from r2d2.wink.com by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA06370 (mail destined for uri@services.bunyip.com); Thu, 13 Feb 97 13:22:06 -0500
Received: from solo.wink.com by wink.com (4.1/SMI-4.1) id AB11525; Thu, 13 Feb 97 10:21:26 PST
Received: by solo.wink.com(Lotus SMTP MTA v1.05 (274.9 11-27-1996)) id 8825643D.0063B909 ; Thu, 13 Feb 1997 10:09:14 -0700
X-Lotus-Fromdomain: WINK
To: R.PETKE@csi.compuserve.com
Cc: Uri@bunyip.com
Message-Id: <8825643D.0061D08F.00@solo.wink.com>
Date: Thu, 13 Feb 1997 09:59:09 -0700
Subject: Re: URL Process List
Sender: owner-uri@bunyip.com
Precedence: bulk


As someone trying to get some new URL schemes through the process, I think
defining this process is very important.  And, as I think someone pointed
out at the San Jose BOF, companies are more likely to follow a
standradization process if it is well-defined.  Right now we have people
and companies creating and using non-standard URL schemes without much
attention being paid to consistency and interoperability.

I think it would be worth scheduling a meeting in memphis to discuss the
I-D and plan a roadmap mor completing this process.

     Dan


Dan Zigmond
Wink Communications
dan.zigmond@wink.com