Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site sdcsvax.UUCP
Path: utzoo!watmath!clyde!cbosgd!ihnp4!houxm!vax135!cornell!uw-beaver!tektronix!hplabs!sdcrdcf!sdcsvax!jww
From: jww@sdcsvax.UUCP (Joel West)
Newsgroups: net.mail
Subject: Re: The TRUTH about .UUCP
Message-ID: <1118@sdcsvax.UUCP>
Date: Mon, 30-Sep-85 13:06:55 EDT
Article-I.D.: sdcsvax.1118
Posted: Mon Sep 30 13:06:55 1985
Date-Received: Fri, 4-Oct-85 06:09:12 EDT
References: <593@down.FUN> <10476@ucbvax.ARPA> <12317@Glacier.ARPA> <10490@ucbvax.ARPA>
Distribution: net
Organization: CACI, Inc - Federal, La Jolla
Lines: 22
Summary: Jordan is right

In article <10490@ucbvax.ARPA>, jordan@ucbvax.ARPA (Jordan Hayes) writes:
> 	1) Addresses should be global. Relative addressing leads
> 	   to ambiguity and headache.
> 
> 	2) The current bang addressing scheme is old and has outlived
> 	   its usefulness.
> 
> 	3) If something is not done, the structure of UUCP as we know
> 	   it will fail to make the transition back into a useful
> 	   network -- it used to be useful when it was smaller, but
> 	   now it is bigger, and has undergone growing pains that have
> 	   made magic (and moby expensive) techniques such as pathalias
> 	   and 1Mb of map data the only way to make any sense of
> 	   the topology of the net. One big, hacky workaround.

The generalization in #2 is a bit sweeping, but other than that, I'm
afraid I must agree with Mr. Hayes.  Fortunately, there are some
people out there who are doing rather than just talking.

	Joel West	CACI, Inc. - Federal (c/o UC San Diego)
	{ucbvax,decvax,ihnp4}!sdcsvax!jww
	jww@SDCSVAX.ARPA


Brought to you by Super Global Mega Corp .com