Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!ucbarpa.Berkeley.EDU!jordan
From: jordan@ucbarpa.Berkeley.EDU.UUCP
Newsgroups: news.sysadmin
Subject: Re: UUCP domains (and a few misunderstandings)
Message-ID: <17718@ucbvax.BERKELEY.EDU>
Date: Thu, 5-Mar-87 19:06:29 EST
Article-I.D.: ucbvax.17718
Posted: Thu Mar  5 19:06:29 1987
Date-Received: Sat, 7-Mar-87 02:33:42 EST
References: <145@tdi2.UUCP>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: jordan@ucbarpa.Berkeley.EDU (Jordan Hayes)
Organization: Experimental Computer Facility (XCF), UC Berkeley
Lines: 31

Brandon Allbery <brandon@tdi2.UUCP> writes:

	An earlier posting contained a complaint about UUCP domains,
	and used the site "hplabs.HP.COM" as an example.  THIS SITE IS
	NOT A UUCP DOMAIN SITE, IT IS AN ARPA INTERNET DOMAIN SITE.
	There's a big difference:  the Internet was set up for domains
	to begin with, so the map from everyone in one large ARPA
	domain to smaller subdomains COM, HP.COM is easy.

Ahem.  The domain system has nothing to do whatsoever with the
underlying transport medium.  It is a specification of naming labels,
and no more.  There is no "UUCP domain" and there is no "ARPA Internet
domain" ...

	The UUCP domain should be split up into regions; each region
	has one or more ``primary'' sites which is known to the
	regional ``primary'' sites of other systems.

I think you should go back and read the last 3 years of net.mail to
find out what's wrong with this statement (hint: domain names do not
specify geography or routing) ... the structure of the network simply
does not provide for mechanisms like those you propose.  Links
generally (except in largely populated areas) don't follow geographic
logic.

I am, however, convinced that there can be a way to implement dynamic
routing in a slow transport medium ("slow" == "slow enough that the
expense of using the transport medium itself for regular propagation of
routing information is prohibitive").

/jordan