[12394] in Commercialization & Privatization of the Internet
Re: About the creation of new 3-letter domain(s)
daemon@ATHENA.MIT.EDU (Dennis Fazio)
Tue May 17 15:07:19 1994
From: dfazio@mr.net (Dennis Fazio)
To: mjo@msen.com
Date: Tue, 17 May 1994 10:02:26 -0500 (CDT)
Cc: com-priv@psi.com
In-Reply-To: <m0q3LfR-0013IqC@garnet.msen.com> from "Mike O'Connor" at May 17, 94 05:42:28 am
>How does one deal with the (growing) case of institutions aligned
>along boundaries that don't correspond to cities that don't happen to
>be the special provided-for case of "libraries" and "state gov't stuff
>that didn't already go for a .gov"? What if one wants to set up a
>regional domain park -- like lonestar.org for Texas or mi.org for
>Michigan? Having talked to Jon Postel, I can assure you that nothing
>less than an RFC effort which he'd likely vigorously OPPOSE would lead
>to having a domain park or much of anything else within .us.
I believe this is all covered in RFC 1480
>
>There's a big difference, in that directory services exist for postal
>mail and the phone service that clearly don't exist for the Internet.
>In the absence of explicit forwarding, there's no way that I'd ever
>find an Acme Corporation "hiding" under a .us via the Internet.
This is a directory services issue that is not yet solved for any
domain system let alone the US domain. When an Internet-wide directory
services system is widely deployed and used, it will work for any
domain naming scheme.
>
>I like less confusion in my life. If I see a geographic location, I'd
>like to think that the person I am corresponding with actually may be
>in that location, or else I start disregarding it altogether and it
>becomes some meaningless token, much as the OSI/X.400 C=US is largely
>meaningless with multinational corporations who may have their mail
>backbones in the US.
The vast majority of the US domain addresses will indeed be in the
physical locations specified in the domain name or working at the
multinational corporation whose headquarters is located in the place
specified in the domain name. Maybe a small
number may be "meaningless tokens", but that's no worse than any other
system that has 100% of its domain addresses as meaningless tokens.
--
Dennis Fazio, Minnesota Regional Network --|||-- Gabnet: (612) 342-2570