Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 beta 3/9/83; site cwruecmp.UUCP Path: utzoo!watmath!clyde!floyd!harpo!decvax!cwruecmp!ccc From: ccc@cwruecmp.UUCP (Case Computer Club) Newsgroups: net.mail Subject: Re: Area-code as uucp domains Message-ID: <935@cwruecmp.UUCP> Date: Wed, 1-Feb-84 21:47:02 EST Article-I.D.: cwruecmp.935 Posted: Wed Feb 1 21:47:02 1984 Date-Received: Wed, 8-Feb-84 07:16:12 EST References: <426@psuvax.UUCP>, <758@ulysses.UUCP> Organization: CWRU Computer Engr. Cleveland, Ohio Lines: 12 There is something strangely artificial about using area codes as domain specifiers. Yes, artificial, because that's not the way the network is connected. For example, this machine (cwruecmp) is in Cleveland, OH, and receives its news from decvax. However, vortex also talks to decvax, and vortex is in California! What nicer way to play havoc with software? I propose the following solution: Why not use the usenet backbones which already exist as the uucp domains? This way, if machines start moving within a domain, let the backbone remember this fact and adjust accordingly. If a machine changes domains, it's fairly easy to notify the uucp world of that fact. Granted, this does make for slightly larger domains than would result from area codes. However, which would you rather remember, "@cwruecmp.decvax" or "@(216)cwruecmp"?