Autosave: 2024-10-24 07:31:52

neuron/85c93482-be2b-476d-8d37-e67e35658655/385af4b4_Baran_distributed_networks.md

@@ -3,7 +3,7 @@ tags: [fleeting, networks, ARPANET, packet-switching]
 created: Tuesday, October 22, 2024
 ---
 
-# 385af4b4-43ea-4a5f-85a3-5791d95109aa
+# 385af4b4-Baran_distributed_networks
 
 ## Paul Baran's concept of a distributed network and influence on architecture of the ARPANET
 

neuron/85c93482-be2b-476d-8d37-e67e35658655/861cc26e_ARPA_origins.md

@@ -3,9 +3,7 @@ tags: [fleeting, computer-history, ARPA]
 created: Monday, October 14, 2024
 ---
 
-# 861cc26e-5f59-4615-821d-fe3ee5e1014d
-
-## Origins of ARPA
+# 861cc26e_ARPA_origins
 
 After Sputnik, Eisenhower wanted a dedicated, cross-departmental division within
 the US government to focus on advanced technological research so that they would

neuron/85c93482-be2b-476d-8d37-e67e35658655/cfbef1c4_web_precursors.md

@@ -3,7 +3,7 @@ tags: [fleeting, modems, computer-history, internet, bulletin-boards]
 created: Monday, October 14, 2024
 ---
 
-# cfbef1c4-95ea-4fd1-85b8-536492e45e31
+# cfbef1c4_web_precursors
 
 ## Early precursors to the commercial internet
 

neuron/85c93482-be2b-476d-8d37-e67e35658655/e470bf3d_IMPs_in_the_ARPANET.md

@@ -0,0 +1,38 @@
+---
+tags: [ARPA, ARPANET, networks, computer-history]
+created: Friday, October 18, 2024
+---
+
+# e470bf3d-IMPs_in_the_ARPANET
+
+Within the #ARPANET, IMPs (Information Message Processors) were nodes
+distinguished from [hosts](./Network_hosts.md). They were computers designed to
+receive and route the the packets from one host to another, described as
+"adaptive routing".
+
+Their job was to:
+
+- packetize or reassemble the data from the host
+- find the most efficient pathway from one host to another
+- store packets in their buffers whilst attending to other requests
+- retry the transmission a set number of times in the case of error or data
+  corruption
+- confirm successful transmission
+
+These responsibilities required the IMP to "know" the location and addresses of
+other IMPs and hosts on the [network](./Network_fundamentals.md) and their
+proximity to them.
+
+From the point of view of the host user, the existence of the IMPs would be
+hidden. Hosts would connect to eachother transparently - it would appear as if
+you were directly connecting to the other host rather than an IMP.
+
+Thus an IMP was a subnetwork within the broader ARPANET: the IMP would be the
+core of this subnetwork and the links to its direct hosts, the periperhy.
+Initially, in its full extent, the ARPANET comprised a network of these
+subnetworks.
+
+![IMP diagram](static/IMP-network.png)
+
+IMPs were later known as 'gateways' and were the precursors to what we today
+call routers.

neuron/85c93482-be2b-476d-8d37-e67e35658655/f0f70a3c_ARPANET_motivations.md

@@ -0,0 +1,33 @@
+---
+tags: [ARPA, ARPANET, networks, computer-history]
+created: Friday, October 18, 2024
+---
+
+# f0f70a3c-ARPANET-motivations
+
+It is inaccurate to say that the chief motivation in creating the ARPANET was to
+create a network that could withstand nuclear conflict, where mulitple nodes
+could be hit and the network could still go on functioning.
+
+Ideas that originated from this concern _did_ influence the project (chiefly
+[Paul Baran's work on distributed networks](./385af4b4_baran_distributed_networks.md)
+at RAND), but this was not the concern of the ARPANET.
+
+ARPA's objectives were focused more on reducing efficiency in the academic and
+military projects it sponsored.
+
+Different models of computer were used throughout the
+military-industrial-academic complex. Users required different logins and a
+knowledge of different operating systems and programming languages in order to
+be able to use them.
+
+At the same time, there was a duplication of hardware. Different projects would
+all require their own computer to do their research. It would be better if the
+same computer could be accessed by multiple teams through time-sharing (already
+in existene) and a network.
+
+Finally, results from different research projects were being duplicated.
+Different teams would be producing the same data independently of one another
+because the data could not be readily shared. If this redundancy could be
+removed, and the data accessed and shared between multiple projects, teams could
+focus on new research and the production of novel applications.

neuron/85c93482-be2b-476d-8d37-e67e35658655/index.md

@@ -13,26 +13,26 @@ computer science.
 
 ![not-by-ai-badge](static/not-by-ai-alternative--light.svg)
  
-**Build ID:** a78874c0-3838-49d0-b534-e6363f801ef8
+**Build ID:** 85c93482-be2b-476d-8d37-e67e35658655
 
-**Published:** Wed 23 Oct 2024 17:50:20
+**Published:** Thu 24 Oct 2024 07:31:51
 
 ### Recent edits 
 
-- [[385af4b4_43ea_4a5f_85a3_5791d95109aa]] 
-- [[cfbef1c4_95ea_4fd1_85b8_536492e45e31]] 
-- [[861cc26e_5f59_4615_821d_fe3ee5e1014d]] 
+- [[cfbef1c4_web_precursors]] 
+- [[861cc26e_ARPA_origins]] 
+- [[f0f70a3c_ARPANET_motivations]] 
+- [[e470bf3d_IMPs_in_the_ARPANET]] 
+- [[385af4b4_Baran_distributed_networks]] 
 - [[Compile_Python_app_to_single_executable]] 
 - [[VirtualMemory]] 
 - [[Zero_property_of_multiplication]] 
-- [[Working_with_CSVs_in_Python]] 
-- [[Variables_and_data_types_in_Bash]] 
 
 
-### All notes (464) 
+### All notes (466) 
 
-- [[385af4b4_43ea_4a5f_85a3_5791d95109aa]] 
-- [[861cc26e_5f59_4615_821d_fe3ee5e1014d]] 
+- [[385af4b4_Baran_distributed_networks]] 
+- [[861cc26e_ARPA_origins]] 
 - [[API_Gateway]] 
 - [[AWS_CLI]] 
 - [[AWS_SAM_and_Docker]] 
@@ -484,7 +484,9 @@ computer science.
 - [[Working_with_numbers_in_Bash]] 
 - [[Zero_property_of_multiplication]] 
 - [[Zip_function_in_Python]] 
-- [[cfbef1c4_95ea_4fd1_85b8_536492e45e31]] 
+- [[cfbef1c4_web_precursors]] 
+- [[e470bf3d_IMPs_in_the_ARPANET]] 
+- [[f0f70a3c_ARPANET_motivations]] 
 - [[fs]] 
 - [[http_in_Node]] 
 - [[journald]] 

zk/385af4b4_Baran_distributed_networks.md

@@ -3,7 +3,7 @@ tags: [fleeting, networks, ARPANET, packet-switching]
 created: Tuesday, October 22, 2024
 ---
 
-# 385af4b4-43ea-4a5f-85a3-5791d95109aa
+# 385af4b4-Baran_distributed_networks
 
 ## Paul Baran's concept of a distributed network and influence on architecture of the ARPANET
 

zk/861cc26e_ARPA_origins.md

@@ -3,9 +3,7 @@ tags: [fleeting, computer-history, ARPA]
 created: Monday, October 14, 2024
 ---
 
-# 861cc26e-5f59-4615-821d-fe3ee5e1014d
-
-## Origins of ARPA
+# 861cc26e_ARPA_origins
 
 After Sputnik, Eisenhower wanted a dedicated, cross-departmental division within
 the US government to focus on advanced technological research so that they would

zk/cfbef1c4_web_precursors.md

@@ -3,7 +3,7 @@ tags: [fleeting, modems, computer-history, internet, bulletin-boards]
 created: Monday, October 14, 2024
 ---
 
-# cfbef1c4-95ea-4fd1-85b8-536492e45e31
+# cfbef1c4_web_precursors
 
 ## Early precursors to the commercial internet
 

zk/e470bf3d_IMPs_in_the_ARPANET.md

@@ -0,0 +1,38 @@
+---
+tags: [ARPA, ARPANET, networks, computer-history]
+created: Friday, October 18, 2024
+---
+
+# e470bf3d-IMPs_in_the_ARPANET
+
+Within the #ARPANET, IMPs (Information Message Processors) were nodes
+distinguished from [hosts](./Network_hosts.md). They were computers designed to
+receive and route the the packets from one host to another, described as
+"adaptive routing".
+
+Their job was to:
+
+- packetize or reassemble the data from the host
+- find the most efficient pathway from one host to another
+- store packets in their buffers whilst attending to other requests
+- retry the transmission a set number of times in the case of error or data
+  corruption
+- confirm successful transmission
+
+These responsibilities required the IMP to "know" the location and addresses of
+other IMPs and hosts on the [network](./Network_fundamentals.md) and their
+proximity to them.
+
+From the point of view of the host user, the existence of the IMPs would be
+hidden. Hosts would connect to eachother transparently - it would appear as if
+you were directly connecting to the other host rather than an IMP.
+
+Thus an IMP was a subnetwork within the broader ARPANET: the IMP would be the
+core of this subnetwork and the links to its direct hosts, the periperhy.
+Initially, in its full extent, the ARPANET comprised a network of these
+subnetworks.
+
+![IMP diagram](../img/IMP-network.png)
+
+IMPs were later known as 'gateways' and were the precursors to what we today
+call routers.

zk/f0f70a3c_ARPANET_motivations.md

@@ -0,0 +1,33 @@
+---
+tags: [ARPA, ARPANET, networks, computer-history]
+created: Friday, October 18, 2024
+---
+
+# f0f70a3c-ARPANET-motivations
+
+It is inaccurate to say that the chief motivation in creating the ARPANET was to
+create a network that could withstand nuclear conflict, where mulitple nodes
+could be hit and the network could still go on functioning.
+
+Ideas that originated from this concern _did_ influence the project (chiefly
+[Paul Baran's work on distributed networks](./385af4b4_baran_distributed_networks.md)
+at RAND), but this was not the concern of the ARPANET.
+
+ARPA's objectives were focused more on reducing efficiency in the academic and
+military projects it sponsored.
+
+Different models of computer were used throughout the
+military-industrial-academic complex. Users required different logins and a
+knowledge of different operating systems and programming languages in order to
+be able to use them.
+
+At the same time, there was a duplication of hardware. Different projects would
+all require their own computer to do their research. It would be better if the
+same computer could be accessed by multiple teams through time-sharing (already
+in existene) and a network.
+
+Finally, results from different research projects were being duplicated.
+Different teams would be producing the same data independently of one another
+because the data could not be readily shared. If this redundancy could be
+removed, and the data accessed and shared between multiple projects, teams could
+focus on new research and the production of novel applications.