[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ih] Peter Salus / Baran's work
- Subject: [ih] Peter Salus / Baran's work
- From: dave.walden.family at gmail.com (Dave Walden)
- Date: Tue, 13 Jan 2015 14:29:31 -0500
- In-reply-to: <[email protected] mail.com>
- References: <[email protected]> <[email protected]> <CAAbKA3V5+iSJ8rd+P=3PkykYKCVQJKrE59pVj-153+6CNwbcEQ@mail.gmail.com>
ARPANET always had adaptive routing, and it was
pretty good for the job for a while. Later, the
old ARPANET "distance vector" routing was
replaced by the new ARPANET "link state"
routing. These routing algorithms *did* work
around damage or other changes to the
"environment", i.e., phone lines and packet
switching going up and down, changes to the
network configuration of phone lines and
packet-switch sites, etc. As things moved beyond
the ARPANET, i.e., the Internet came into being
and expanded, lots more routing work happened, as I remember.
At 01:21 PM 1/13/2015, Bill Ricker wrote:
???Hmm, that makes sense.?
>(D)ARPAnet initially had fixed routing, not
>useful in damage-prone environment.
>It was ???TCP/IP that introduced adaptive routing around damage.?
>(USEnet evolved adaptive routing, i don't recall how that was related .)
>
>Also note that the Military nearly adopted the
>ISO OSI protocol stack not the TCP/IP Internet
>stack, even though DARPA had subsidized the (pre-Web/NSF/NSCC) development !?