# URN->URL lookup

moore@cs.utk.edu
Thu, 28 Oct 93 23:39:59 -0400

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Fred Swartz: "URLs -- the ftp case"
- Previous message: Karen R. Sollins: "Thumbnail Sketch of the UR* Arena"

    Date: Thu, 28 Oct 93 23:39:59 -0400

    From: moore@cs.utk.edu

    Message-Id: <9310290339.AA01727@thud.cs.utk.edu>

    To: uri@bunyip.com

    Subject: URN->URL lookup

I'm also of the opinion that we are better off trying to establish
a single standard protocol for URN->URL lookup. I don't think this
will be as difficult as (say) getting agreement on the system
architecture or the format of URLs, because there aren't a lot
of pre-existing systems with which we need to be compatible.

Something like: convert the URN prefix to a domain name, look up
that name in the DNS, DNS returns a list of domains running whois++
servers, one of which is then queried for location information.

This approach appears to be (relatively) easy to define, simple to
implement, low overhead for the client, and fairly scalable.

As I see it, the danger is in NOT defining such a protocol now.

URN->URL lookup is essential for a project I'm currently working on.
If there's no standard way to resolve URNs, we're going to have to come
up with one for this project, even if it only works for our stuff.
I'll bet there are a half dozen other groups with the same needs and
similar time constraints, who are coming to the same conculsion...

Keith

- Next message: Fred Swartz: "URLs -- the ftp case"
- Previous message: Karen R. Sollins: "Thumbnail Sketch of the UR* Arena"