# Re: URL/URN Implementation Status (query)

Mitra (mitra@path.net)
Tue, 14 Sep 1993 05:15:43 GMT

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Kevin Altis: "Re: URN/URL file links"
- Previous message: Larry Masinter: "Re: URL/URN Implementation Status (query)"
- Maybe in reply to: John Curran: "URL/URN Implementation Status (query)"
- Next in thread: David Durand: "Re: URL/URN Implementation Status (query)"

    From: mitra@path.net (Mitra)

    Subject: Re: URL/URN Implementation Status (query)

    Message-Id: <CDBvy8.31A@pandora.sf.ca.us>

    Date: Tue, 14 Sep 1993 05:15:43 GMT

John

We are using URL's in a couple of low-volume or gateway applications,
I intend that everything we write will use them from now on!

We arent using URN's at the moment, without a way to systematically look
them up then they arent much use. Anyway, without an agreement on
syntax it would be hard to use them anyway.

I do have a URN to URL mapper mostly built, its designed to be usable
by anyone allocating URN's from their own part of the name space.
I havent had time to work on it much since Amsterdam, but I'd happily
make the code available for someone else to play with.

The basic idea, was that we'd reserve part of the name space so
that the first part of the id was something like "INET" or "FQDN" and
the second part would be the FQDN and the third part would be
the unique number assigned by that FQDN. The requirement for
using "INET:xx.yyy.zzz" as your domain name, would be that you
agreed to put a URN->URL mapper at urn.xx.yyy.zzz at some well
known port. (Or, of course, to put a CNAME in urn.xx.yyy.zzz to point
at a resolver on someone else's machine)

- Mitra

- Next message: Kevin Altis: "Re: URN/URL file links"
- Previous message: Larry Masinter: "Re: URL/URN Implementation Status (query)"
- Maybe in reply to: John Curran: "URL/URN Implementation Status (query)"
- Next in thread: David Durand: "Re: URL/URN Implementation Status (query)"