Fw: I-D ACTION:draft-ietf-urlreg-noreg-00.txt

After some consideration (no, I'm really not dead), here's my take on where we are.  

This draft, together from the notes of the Munich meeting and some conversation since, seems to suggest that we may be able to solve the problems we originally confronted with two mechanisms:

* for experimental and developmental purposes, Yaron's draft describes a workable mechanism, with no administrative overhead, thus encouraging its use; 

* for URL schemes intended to be 'permanent', Larry Masinter's work addresses guidelines for what should be in a doc that describes a URL scheme.  It would provide guidance to draft writers and a consistent touchstone for IESG evaluation.  

One potential hole in this coverage may be the existing aol:-type scenario; I suggest that could be addressed by encouraging such 'owners' to document their URL schemes with Informationals, again with Larry's work as a guide. Or, if there is enough concern about ensuring such documentation, this group could produce a current-practice doc outlining those known cases.  

What else have I missed?  I'm thinking agenda for the Washington meeting (it looks like I'll actually attend THIS meeting)....  

24 hours in a day, 24 beers in a case.  Coincidence?  
Ian King <[email protected]>  

a/k/a <[email protected]>
Software QA Lead, Internet Services Business Unit
Microsoft Corporation

----------
> From: [email protected]
> To: [email protected]
> Cc: [email protected]
> Subject: I-D ACTION:draft-ietf-urlreg-noreg-00.txt
> Date: Tuesday, November 04, 1997 7:30 AM
> 
> A New 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		: Uniform Resource Locators (URL): NOREG URL Naming Scheme
> 	Author(s)	: Y. Goland
> 	Filename	: draft-ietf-urlreg-noreg-00.txt
> 	Pages		: 2
> 	Date		: 03-Nov-97
> 	
>    This document proposes mapping DNS names into the URL scheme space
>    for the purpose of preventing namespace collisions amongst URL
>    schemes whose syntax and functionality are not appropriate for
>    standardization.
> 
> Internet-Drafts are available by anonymous FTP.  Login with the username
> "anonymous" and a password of your e-mail address.  After logging in,
> type "cd internet-drafts" and then
> 	"get draft-ietf-urlreg-noreg-00.txt".
> A URL for the Internet-Draft is:
> ftp://ds.internic.net/internet-drafts/draft-ietf-urlreg-noreg-00.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-noreg-00.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.
>