Lists Home |
Date Index |
- From: Ron Daniel <RDaniel@DATAFUSION.net>
- To: Kent Sievers <firstname.lastname@example.org>, email@example.com
- Date: Tue, 8 Jun 1999 13:12:28 -0700
> -----Original Message-----
> From: Kent Sievers [SMTP:firstname.lastname@example.org]
> Sent: Tuesday, June 08, 1999 11:34 AM
> To: email@example.com
> Subject: Re: All this buisiness about namespace URNs...
> Clearly, if we had a DNS server that was capable of mapping the URN of
> a name space to a URL then the requirements would be met of having
> both a unique identifier and a way of getting information about the
> Is someone stepping forward to do this sort of thing? .
[Ron Daniel] This has been done. See RFC 2168 and 2169 (if memory
serves, I'm offline at the moment). The first defines a new resource
record, NAPTR, which has been implemented in BIND for a couple of
years now. It is used for finding one or more 'resolvers'. The
second RFC defines a trivial protocol for communicating with resolvers
using HTTP. Together, they will let URNs in a new "foo" namespace be
mapped to a URL.
The bottleneck here is that for the "foo" namespace you need to get
the domain name "foo.urn.net" and put the NAPTR resource record
there. The only way to get that domain is to fill
out the application form the IETF's URN WG has been defining.
It doesn't cost anything right now, and there are no plans to charge
for such names that I know of, but its safe to see the registration
procedure is not a smooth and polished process. (The purpose of the
procedure is to prevent cyber-squatting on URN namespace identifiers,
and to insulate the owner of the urn.net domain from lawsuits if
he had to make the call on whether or not to register "foo").
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)