Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 5/3/83; site amd70.UUCP Path: utzoo!linus!decvax!decwrl!amd70!phil From: phil@amd70.UUCP (Phil Ngai) Newsgroups: net.mail Subject: Re: Area-code as uucp domains Message-ID: <4296@amd70.UUCP> Date: Sun, 5-Feb-84 14:14:14 EST Article-I.D.: amd70.4296 Posted: Sun Feb 5 14:14:14 1984 Date-Received: Thu, 9-Feb-84 00:52:19 EST References: <426@psuvax.UUCP>, <758@ulysses.UUCP>, <3508@utzoo.UUCP> Organization: AMD, Santa Clara, CA Lines: 30 > What I see domains as is an attempt to make one machine responsible > for a magic area so that all mail sent to any machine in that area > can be sent through that site who can guarantee that the mail will > be delivered. If there is something more to domains, then would > somebody please explain it to me, because I have really looked and > that is all that I have found. I don't think a domain is supposed to be an area in the geographic sense. If you mean an entity, that would seem correct. But the DEC domain will overlap the ATT domain geographically. > omniscient machines may not know about it. The harder trick > is to make sure that no new machine can be added to your > domain whithout you hearing about it. if everybody new > understood that they would send the site administrator mail > at the major site saying "I just got frozzbozz my 68000 box > up today and I now am polling gimpex in your domain so > you have to know about me", but people don't seem to be > doing this. The domain administrator presumably educates the administrators of the machines in his/her domain that they have to keep him up to date regarding their status. That is, gimpex knows not to add the frozzbozz connection without telling the domain administrator. Gimpex knows this because that was part of joining the domain they are in. Of course frozzbozz doesn't know the protocols, but gimpex should. This is just a layman's interpretation.-- Phil Ngai (408) 988-7777 {ucbvax,decwrl,ihnp4,allegra,intelca}!amd70!phil