It was from the RAND study that the false rumor started, claiming that the ARPANET was somehow related to building a network resistant to nuclear war. This was never true of the ARPANET, but was an aspect of the earlier RAND study of secure communication. The later work on internetworking did emphasize robustness and survivability, including the capability to withstand losses of large portions of the underlying networks.
It was from the RAND study that the false rumor started, claiming that the ARPANET was somehow related to building a network resistant to nuclear war. This was never true of the ARPANET, but was an aspect of the earlier RAND study of secure communication. (emphasis mine)
I hate that kind of bullshit, using unjustifiably heavily loaded language to start and then backpedaling to the point where it pretends it’s clarifying subtle details but finally admits it’s pretty much just splitting hairs with definitions and vaguely nitpicking. It’s so disgustingly disingenuous and I’m not even sure it’s intentional, it’s just the subtly misleading way stuff like this often gets written but it really bothers me.
That’s a quote from The Internet Society. Here’s another quote from the same source:
According to Charles Herzfeld, ARPA Director (1965–1967):
The ARPANET was not started to create a Command and Control System that would survive a nuclear attack, as many now
claim. To build such a system was, clearly, a major military need, but it was not ARPA’s mission to do this; in fact, we would have
been severely criticized had we tried. Rather, the ARPANET came out of our frustration that there were only a limited number of
large, powerful research computers in the country, and that many research investigators, who should have access to them, were
geographically separated from them.
ARPANET, like the modern internet, were and are pretty resilient on the network level and one of the major components why it’s still working today is that it can route around problems. However, it absolutely needs to have a pretty thick forest for the routing to work and thus it’s not really viable for military as they generally don’t have the time nor resources to build such networks on the battlefield.
Switching network theory does come from RAND, but that’s more or less it. ARPANET founders didn’t have nuclear threat in mind when designing their network.
Obviously today we’ve drifted away from such resilience as half a dozen companies manage majority of everyday things on the net, but the underlying network is still pretty good and centralization of services is a story for another day.
ARPANET on Wikipedia.
I hate that kind of bullshit, using unjustifiably heavily loaded language to start and then backpedaling to the point where it pretends it’s clarifying subtle details but finally admits it’s pretty much just splitting hairs with definitions and vaguely nitpicking. It’s so disgustingly disingenuous and I’m not even sure it’s intentional, it’s just the subtly misleading way stuff like this often gets written but it really bothers me.
That’s a quote from The Internet Society. Here’s another quote from the same source:
ARPANET, like the modern internet, were and are pretty resilient on the network level and one of the major components why it’s still working today is that it can route around problems. However, it absolutely needs to have a pretty thick forest for the routing to work and thus it’s not really viable for military as they generally don’t have the time nor resources to build such networks on the battlefield.
Switching network theory does come from RAND, but that’s more or less it. ARPANET founders didn’t have nuclear threat in mind when designing their network.
Obviously today we’ve drifted away from such resilience as half a dozen companies manage majority of everyday things on the net, but the underlying network is still pretty good and centralization of services is a story for another day.
Interesting, thanks