Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!security!genrad!grkermit!masscomp!clyde!floyd!harpo!eagle!mhuxl!houxm!hogpc!mel
From: mel@hogpc.UUCP
Newsgroups: net.unix,net.bugs.uucp
Subject: Re: Area-code as uucp domains
Message-ID: <325@hogpc.UUCP>
Date: Tue, 24-Jan-84 11:41:26 EST
Article-I.D.: hogpc.325
Posted: Tue Jan 24 11:41:26 1984
Date-Received: Fri, 27-Jan-84 07:41:40 EST
Lines: 14

A uucp domain does NOT need a person "responsible", anymore than netnews
needs a person responsible.  The purpose of the domain is to limit the
number of sites that must be considered in chosing a unique site name,
i.e. (415)vortex must be unique in the Bay area, and (617)vortex must
be unique in the Boston area, but both may exist on uucp.  It wouldn't
take more than a day's research to find conflicts within the domain of
an area code (a short query on Usenet would do it, as would asking
the administrator of the nearest large node).  The name server problem
is a non-problem.  The larger nodes in an area could easily serve to
pass on traffic (as they do now) for the smaller systems around them.
We don't need a centralized, militaristic, IBM type solution to the
uucp domain problem.  A simple, easy to use and understand, domain
naming scheme needs to be defined and used.  All the rest will come
in the usual decentralized UNIX fashion.   Mel Haas  ,  (201)houxe!mel