Re: Yet Another Attribute Parameter

Michael Mealling (michaelm@rwhois.net)
Wed, 18 Dec 1996 09:57:49 -0500


Message-Id: <32B8066D.2A8D@rwhois.net>
Date: Wed, 18 Dec 1996 09:57:49 -0500
From: Michael Mealling <michaelm@rwhois.net>
To: Larry Masinter <masinter@parc.xerox.com>
Cc: howes@netscape.com, ietf-asid@umich.edu, uri@bunyip.com
Subject: Re: Yet Another Attribute Parameter

Larry Masinter wrote:
> This is an issue for the new URL working group, to give guidelines on
> what belongs in a URL and what doesn't, so I hope you don't mind if I
> bring uri@bunyip.com into it. (The conversation should move to
> ietf-url@imc.org as soon as that's created.)

I hope this won't take long since I'm sure several people are getting
two copies of this thread....anyway.....

> Michael:
> > In RWhois we are working on a UDP version. Several other protocols have
> > both UDP and TCP connection styles. The problem is that URLs don't specify
> > which service to use. ...
> Tim:
> > After thinking about this a bit, I think it makes more sense to
> > include this information in the URL itself. A URL is supposed to be
> > self-contained, including everything you need to know to access some
> > resource. If the protocol you use runs over both TCP and UDP, there
> > should be a way in the URL format to indicate which one (or not, if it
> > doesn't matter).
> 
> The precedent hasn't really been that way. For example, 'ftp:' URLs
> don't tell you the media type, and our attempt to make people use URLs
> that tell you whether the remote file is text or binary has basically
> failed.

That, among others, is why I didn't put it in the RWhois URL draft...

> If the protocol runs over both TCP and UDP, why not just say 'try UDP
> and if it doesn't work, use TCP, and remember that UDP doesn't work to
> that host'.

Primarily for the reason that if the UDP service doesn't exist then
the poor user has to wait for some timeout period to expire before
the TCP connection is tried.

> Is this acceptable? Is there any consensus on putting this guideline
> into the URL process document?

I'd like some language on how to deal with timing out the UDP query
so that the user doesn't wait to long just to find out if a service
is available or not.

There is a solution but it requires the use of the SRV record which is
not in widespread use yet....

-MM

-- 
------------------------------------------------------------------------------
Michael Mealling	| 505 Huntmar Park Drive       | Phone:  (703)742-0400
Software Engineer	| Herndon, VA 22070	       | Fax:    (703)742-9552
Network Solutions	| <URL:http://www.netsol.com>  | michaelm@rwhois.net