- From: Paul Hoffman <ietf-lists@proper.com>
- Date: Thu, 15 Jun 1995 10:14:26 -0700
- To: Michael.Mealling@oit.gatech.edu (Michael Mealling)
- Cc: Michael.Mealling@oit.gatech.edu, uri@bunyip.com
>This is what I wanted to hear. So I you suggest I create a new hierarchy >if current names don't mach. Therefore you are allowing for a new >namespace, correct? If you mean that we're not insisting on a specifc namespace within the DNS, that is absolutely correct. Your x-dns-2 URN resolver can be at "urn.gatech.edu" or "urn.cs.gatech.edu" or "cs.gatech.edu" or "blarg.gatech.edu". The "urn" part of the domain name was following the (possibly misguided) current habit of Internet sites to create a name that matches the function of a host, even if that name points to the same host as something else. We did not put any domain naming restrictions in the x-dns-2 draft, and we certainly didn't mean to imply any. Further, I expect that there may be companies that let you create a domain name based on their "base name" and will provide you with DNS resolution service. For example, if you can't get your sysop to run a URN resolver, but you think she/he will in the future, you might go to URNsRUs. They'll set up the domain name "oit.gatech.edu.urnsrus.com" and have it point to their resolver. Later, when your sysop comes to her/his senses, you pay the folks at URNsRUs a small amount of money and they change where "oit.gatech.edu.urnsrus.com" points to, namely to your own host. --Paul Hoffman --Proper Publishing
Received on Thursday, 15 June 1995 13:11:14 UTC