RE: I-D ACTION:draft-ietf-urlreg-procedures-01.txt

I seem to recall that there was considerable discussion about vnd, and the
consensus was that it was redundant or actually undesirable.  Does anyone
else want to speak up in favor of vnd?  

I agree that NOREG isn't the only way to do a "no registration" URL scheme,
but IMHO it's a good one -- understandable, self-documenting (in the sense
that you know who owns it), and unlikely to create namespace collisions.  

When the going gets weird, the weird turn pro.  
------------------------------------------------------------------
Ian King, Test Lead <[email protected]>
Electronic Bill Presentment & Payment
MICROSOFT CORPORATION

-----Original Message-----
From: Yaron Goland [mailto:[email protected]]
Sent: Tuesday, May 19, 1998 11:05 PM
To: '[email protected]'
Subject: RE: I-D ACTION:draft-ietf-urlreg-procedures-01.txt


I would like to see language added to the "vnd" tree registration process
which says something to the extent of "A vendor may register a prefix in the
vnd tree which the vendor is then free to use as a prefix for new schemes.
For example the SuperCorp corporation could register vnd.supercorp which
SuperCorp could then use to create any new schemes it wanted such as
vnd.supercorp.superproduct."

The idea is that a company can easily generate a very large number of
protocol schemes which is for their use only. Their desire to have a prefix
is strictly to prevent collisions.

BTW the NOREG draft
(http://www.ietf.org/internet-drafts/draft-ietf-urlreg-noreg-00.txt) meets
this need. But I'm not married to the idea of NOREG, just the existence of
the equivalent feature. Not everything needs to be or even should be
registered with IANA.

		Yaron


> -----Original Message-----
> From: Ian King 
> Sent: Monday, May 04, 1998 10:19 AM
> To: Alec Dun; [email protected]; [email protected];
> [email protected]; [email protected]; [email protected];
> [email protected]; [email protected];
> [email protected]; [email protected]; [email protected];
> [email protected]; [email protected]; 
> [email protected]; Lisa
> Dusseault; [email protected]; [email protected];
> [email protected]; [email protected];
> [email protected]; [email protected]; [email protected]; Yaron
> Goland
> Subject: FW: I-D ACTION:draft-ietf-urlreg-procedures-01.txt
> 
> 
> Hello!  I am forwarding this to you because you signed the 
> roster at the URLREG session in Los Angeles.  I'm also 
> forwarding this to you because (a) you may not be a member of 
> our mailing list ([email protected]) OR you may get so much 
> mailing list mail that this one might get lost in the noise.  :-)  
> 
> The discussion in Los Angeles was quite lively, and everyone 
> had strong opinions and good suggestions.  Hopefully, we have 
> captured that in this new procedures draft.  But, the only 
> way we can be certain is if YOU review it and give your 
> feedback!  Please help us get it right, please help us 
> conclude the work of our group, and please help us make the 
> right suggestions/choices/decisions for the Internet.  Please 
> review our draft!  
> 
> Thank you in advance for your time and consideration.  
> ----------------------
> Ian King, Software QA Lead
> Microsoft Internet Finance Server Toolkit
> MICROSOFT CORPORATION
> Redmond, Washington
> 
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] 
> Sent: Friday, May 01, 1998 11:23 AM
> Cc: [email protected]
> Subject: I-D ACTION:draft-ietf-urlreg-procedures-01.txt
> 
> 
> A Revised Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> This draft is a work item of the Uniform Resource Locator 
> Registration Procedures 
> Working Group of the IETF.
> 
> 	Title		: Registration Procedures for URL Scheme Names
> 	Author(s)	: R. Petke
> 	Filename	: draft-ietf-urlreg-procedures-01.txt
> 	Pages		: 4
> 	Date		: 30-Apr-98
> 	
>    This document defines the process by which new URL schemes are
>    registered.
> 
> 
> Internet-Drafts are available by anonymous FTP.  Login wih 
> the username
> "anonymous" and a password of your e-mail address.  After logging in,
> type "cd internet-drafts" and then
> 	"get draft-ietf-urlreg-procedures-01.txt".
> A URL for the Internet-Draft is:
> ftp://ds.internic.net/internet-drafts/draft-ietf-urlreg-proced
ures-01.txt

Internet-Drafts directories are located at:

	Africa:	ftp.is.co.za
	
	Europe: ftp.nordu.net
		ftp.nis.garr.it
			
	Pacific Rim: munnari.oz.au
	
	US East Coast: ds.internic.net
	
	US West Coast: ftp.isi.edu

Internet-Drafts are also available by mail.

Send a message to:	[email protected].  In the body type:
	"FILE /internet-drafts/draft-ietf-urlreg-procedures-01.txt".
	
NOTE:	The mail server at ds.internic.net can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.