Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!ihnp4!ucbvax!jordan
From: jordan@ucbvax.ARPA (Jordan Hayes)
Newsgroups: net.mail
Subject: Re: The truth about .UUCP
Message-ID: <10386@ucbvax.ARPA>
Date: Sun, 15-Sep-85 03:10:32 EDT
Article-I.D.: ucbvax.10386
Posted: Sun Sep 15 03:10:32 1985
Date-Received: Sun, 15-Sep-85 23:47:15 EDT
References: <552@down.FUN> <583@down.FUN>
Reply-To: jordan@ucbvax.UUCP (Jordan Hayes)
Distribution: net
Organization: University of California at Berkeley
Lines: 60

In article <583@down.FUN> honey@down.FUN (Peter Honeyman) writes:
>Domains serve to facilitate name space control.  They require
>administration from above and consent from below.  In [552@down], I
>argued that the style and substance of uucp addressing is incompatible
>with domains.  I still don't have the answer to questions like
>
>	1) What do I do with "bilbo.UUCP"?  (There are at least three
>	   uucp hosts named bilbo.)

You tell us! Why do you think that's a valid question? Why are there
at least 3 "bilbo"'s floating around? Because someone let them. That
goes away with domains. You MUST fit yourself into the namespace, or you
won't get mail -- it's built in for a purpose. Of course the "style
and substance of uucp addressing is incompatible with domains" -- they
are completely different and do not co-exist. One replaces the other.

>	2) By what reasoning is "cbosgd.ATT.UUCP" better than
>	   "cbosgd"?  (Any answer must satisfy members of the
>	   Albanian Turban Traders domain.)

See your question above (#1)... Why is

		1200 Jones Street
		Mytown, CA 94035

better than

		1200 Jones Street

on an envelope going across the country? This is really silly.

>	3) What does .IL.USA.UUCP mean?  RFC 920 [p. 11] asks for "the
>	   name, title, mailing address, phone number, and organization
>	   of the administrative head of the organization."  Who will
>	   answer?

It means whatever the person/org/entity meant it to be who set it up (read
"created" it...). You don't just *decide* that there will be this subdomain.
The way you set it up is come to some agreement of a group of 2nd level
domains with people to be responsibl;e for themm and then it is up to each
of these people to decide when/how/why the next level is created.

Scenario: Say, for example, it is decide that there will be a NCA.UUCP,
and that I will be in charge of it. Then, say, someone with a whole bunch
of machines says "Hey -- let me into the namespace", and I say "okay, here's
a sub-domain for you to administer called FNG.NCA.UUCP to which he
can now parcel further.

See, the question is not "how to enforce it" but, rather, how to have
it flow with the least amount of resistance. If there is someone to
get information from, namespace collisions could be a thing of the
past.

BTW -- do you think that if those machines knew there were other machines
called "bilbo" that they would have done the same thing?

------------
Jordan Hayes        jordan@UCB-VAX.BERKELEY.EDU
UC Berkeley                       ucbvax!jordan
+1 (415) 835-8767    37' 52.29" N 122' 15.41" W


Brought to you by Super Global Mega Corp .com