# Re: Finding URN->URL servers

Martin Hamilton (M.T.Hamilton@lut.ac.uk)
Thu, 17 Feb 1994 15:44:22 +0000 (GMT)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Michael Mealling: "Re: Changes to URL document"
- Previous message: Karen R. Sollins: "urn functional spec"
- In reply to: Keith Moore: "Re: Finding URN->URL servers"
- Next in thread: Keith Moore: "Re: Finding URN->URL servers"
- Reply: Keith Moore: "Re: Finding URN->URL servers"

    From: Martin Hamilton <M.T.Hamilton@lut.ac.uk>

    Message-Id: <199402171544.PAA10693@lust.mrrl.lut.ac.uk>

    Subject: Re: Finding URN->URL servers

    To: moore@cs.utk.edu (Keith Moore)

    Date: Thu, 17 Feb 1994 15:44:22 +0000 (GMT)

    In-Reply-To: <199402162218.RAA10215@wilma.cs.utk.edu> from "Keith Moore" at Feb 16, 94 05:18:41 pm

Keith, you said:

/ Why don't we just use whois++ for this purpose? Then we can just register
/ a URN.ORG root and use ordinary A records:

How about urn.int, or perhaps just urn? :-)

/ underground.URN.ORG IN A server1.underground.com
/ IN A server2.underground.com
/ IN A server3.underground.com
/
/ would say, to look up a URN of the form URN:::::::underground:something, talk
/ to the whois++ server on that machine, and ask it for some locations for that
/ particular URN.

Let's see... use of TXT (or MX, or UR-RR :-) records would give us a
means of locating URN servers that's protocol independent (dare I say
future proof?), with multiple independent and widely deployed
implementations of URN->URL convertors (e.g. gopherd and httpd!).

Sounds good to me!

Martin

- Next message: Michael Mealling: "Re: Changes to URL document"
- Previous message: Karen R. Sollins: "urn functional spec"
- In reply to: Keith Moore: "Re: Finding URN->URL servers"
- Next in thread: Keith Moore: "Re: Finding URN->URL servers"
- Reply: Keith Moore: "Re: Finding URN->URL servers"