Article View: net.mail.headers
Article #294Re: routing *TO* ARPA.NET (changed title)
From: scw
Date: Fri, 11 May 1984 05:09
Date: Fri, 11 May 1984 05:09
39 lines
2627 bytes
2627 bytes
Two reasonable points have already been raised about my proposal.
1) What is to keep site a from thinking that site b is a vector to the
ARPA-net and vice-versa, causing a loop.
Well, I can think of several (1) cooperating systems with hardwired paths
(not elegant but it works reasonably well, this is what is currently in
use around ucla). (2) Looking at the path (don't send it back to someone
that just (or somewhere) had it) this is reasonable, and perhaps should be a
part of any system (3) Routing tables, updated regulary/periodicly.
I would suspect that (3) is the best way to go. Especially if we can implement
some reasonable mechanisim for detecting undelivered messages, picking them
up and forwarding/rerouting them, and perhaps a method of automagicly
reconfigureing the routing tables.
2) This implies that any site need to know how to get to any site on the
ARPA-NET. The implication is that this is most of the intra-uucp routing
problem.
The nice part of this delivery system is that there is NO one ARPA-NET routing
center, by definition *ANY* ARPA host has a complete routing table. This is
possiable for several reasons. (1) A limited (semi-fixed) number of sites,
unlike uucp.anarchy where systems come and go almost at will, it takes:
(2) A central control point that assigns site numbers (and approves names??),
and limits access to (membership on) the net. (3) Each site has a FIXED name
(number actually) and there is hardware (IMPs?/TIPs?) that does the actual
routing of packets (this is all hearsay, from quite a while ago, and third hand
at that).
NOTE: This is not attempting to address the problem of intra-uucp domain
addressing, it is only a suggestion for the problem of inter-domain
communications (messages that cross the ARPA-NET/uucp.anarchy) boundry with
some specific path information.
--
Stephen C. Woods (VA Wadsworth Med Ctr./UCLA Dept. of Neurology)
uucp: { {ihnp4, uiucdcs}!bradley, hao, trwrb, sdcsvax!bmcg}!cepu!scw
ARPA: cepu!scw@ucla-locus location: N 34 06'37" W 118 25'43"
Technical Details
Message-ID:
<249@cepu.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!watmath!clyde!akgua!sdcsvax!bmcg!cepu!scwReferences:
<229@hocsd.UUCP>Show Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site cepu.UUCP Path: arc1-ca.pugleaf.net!utzoo!watmath!clyde!akgua!sdcsvax!bmcg!cepu!scw From: scw@cepu.UUCP Newsgroups: net.mail.headers Subject: Re: routing *TO* ARPA.NET (changed title) Message-ID: <249@cepu.UUCP> Date: Fri, 11-May-84 01:09:08 EDT Article-I.D.: cepu.249 Posted: Fri May 11 01:09:08 1984 Date-Received: Sun, 6-May-84 01:17:18 EDT References: <229@hocsd.UUCP> Organization: VA Wadsworth Med. Center; LA CA Lines: 39