The first computers were connected in 1969 and the Network Control Protocol was implemented in 1970, development of which was led by Steve Crocker at UCLA and other graduate students, including Jon Postel and others.[9][10][11] The network was declared operational in 1971. Further software development enabled remote login and file transfer, which was used to provide an early form of email.[12] The network expanded rapidly and operational control passed to the Defense Communications Agency in 1975.
Bob Kahn moved to DARPA and, together with Vint Cerf at Stanford University, formulated the Transmission Control Program for internetworking.[13] As this work progressed, a protocol was developed by which multiple separate networks could be joined into a network of networks; this incorporated concepts pioneered in the French CYCLADES project directed by Louis Pouzin. Version 4 of TCP/IP was installed in the ARPANET for production use in January 1983 after the Department of Defense made it standard for all military computer networking.[14][15]
Access to the ARPANET was expanded in 1981 when the National Science Foundation (NSF) funded the Computer Science Network (CSNET). In the early 1980s, the NSF funded the establishment of national supercomputing centers at several universities and provided network access and network interconnectivity with the NSFNET project in 1986. The ARPANET was formally decommissioned in 1990, after partnerships with the telecommunication and computer industry had assured private sector expansion and commercialization of an expanded worldwide network, known as the Internet.[16]
Historically, voice and data communications were based on methods of circuit switching, as exemplified in the traditional telephone network, wherein each telephone call is allocated a dedicated end-to-end electronic connection between the two communicating stations. The connection is established by switching systems that connected multiple intermediate call legs between these systems for the duration of the call.
The traditional model of the circuit-switched telecommunication network was challenged in the early 1960s by Paul Baran at the RAND Corporation, who had been researching systems that could sustain operation during partial destruction, such as by nuclear war. He developed the theoretical model of distributed adaptive message block switching.[17] However, the telecommunication establishment rejected the development in favor of existing models. Donald Davies at the United Kingdom's National Physical Laboratory (NPL) independently arrived at a similar concept in 1965.[18][19]
The earliest ideas for a computer network intended to allow general communications among computer users were formulated by computer scientistJ. C. R. Licklider of Bolt Beranek and Newman (BBN), in April 1963, in memoranda discussing the concept of the "Intergalactic Computer Network". Those ideas encompassed many of the features of the contemporary Internet. In October 1963, Licklider was appointed head of the Behavioral Sciences and Command and Control programs at the Defense Department's Advanced Research Projects Agency (ARPA). He convinced Ivan Sutherland and Bob Taylor that this network concept was very important and merited development, although Licklider left ARPA before any contracts were assigned for development.[20]
Sutherland and Taylor continued their interest in creating the network, in part, to allow ARPA-sponsored researchers at various corporate and academic locales to utilize computers provided by ARPA, and, in part, to quickly distribute new software and other computer science results.[21] Taylor had three computer terminals in his office, each connected to separate computers, which ARPA was funding: one for the System Development Corporation (SDC) Q-32 in Santa Monica, one for Project Genie at the University of California, Berkeley, and another for Multics at the Massachusetts Institute of Technology. Taylor recalls the circumstance: "For each of these three terminals, I had three different sets of user commands. So, if I was talking online with someone at S.D.C., and I wanted to talk to someone I knew at Berkeley, or M.I.T., about this, I had to get up from the S.D.C. terminal, go over and log into the other terminal and get in touch with them. I said, 'Oh Man!', it's obvious what to do: If you have these three terminals, there ought to be one terminal that goes anywhere you want to go. That idea is the ARPANET".[22]
Donald Davies' work caught the attention of ARPANET developers at Symposium on Operating Systems Principles in October 1967.[23] He gave the first public presentation, having coined the term packet switching, in August 1968 and incorporated it into the NPL network in England.[24][25] The NPL network and ARPANET were the first two networks in the world to implement packet switching.[26][27][28] Roberts said the computer networks built in the 1970s were similar "in nearly all respects" to Davies' original 1965 design.[29]
In February 1966, Bob Taylor successfully lobbied ARPA's Director Charles M. Herzfeld to fund a network project. Herzfeld redirected funds in the amount of one million dollars from a ballistic missile defense program to Taylor's budget.[30] Taylor hired Larry Roberts as a program manager in the ARPA Information Processing Techniques Office in January 1967 to work on the ARPANET.[31] Roberts met Paul Baran in February 1967, but did not discuss networks.[32][33]
Roberts asked Frank Westervelt to explore the questions of message size and contents for the network, and to write a position paper on the intercomputer communication protocol including “conventions for character and block transmission, error checking and re-transmission, and computer and user identification."[31] In April 1967, ARPA held a design session on technical standards. The initial standards for identification and authentication of users, transmission of characters, and error checking and retransmission procedures were discussed.[34] Roberts' proposal was that all mainframe computers would connect to one another directly. The other investigators were reluctant to dedicate these computing resources to network administration. After the design session, Wesley Clark proposed minicomputers should be used as an interface to create a message switching network. Roberts modified the ARPANET plan to incorporate Clark's suggestion and named the minicomputers Interface Message Processors (IMPs).[31][35][36][37]
The plan was presented at the inaugural Symposium on Operating Systems Principles in October 1967.[38] Donald Davies' work on packet switching and the NPL network, presented by a colleague (Roger Scantlebury), and that of Paul Baran, came to the attention of the ARPA investigators at this conference.[39][23] Roberts applied Davies' concept of packet switching for the ARPANET,[40][41] and sought input from Paul Baran on dynamic routing.[42] The NPL network was using line speeds of 768 kbit/s, and the proposed line speed for the ARPANET was upgraded from 2.4 kbit/s to 50 kbit/s.[43]
By mid-1968, Roberts and Barry Wessler wrote a final version of the IMP specification based on a Stanford Research Institute (SRI) report that ARPA commissioned to write detailed specifications describing the ARPANET communications network.[37] Roberts gave a report to Taylor on 3 June, who approved it on 21 June. After approval by ARPA, a Request for Quotation (RFQ) was issued for 140 potential bidders. Most computer science companies regarded the ARPA proposal as outlandish, and only twelve submitted bids to build a network; of the twelve, ARPA regarded only four as top-rank contractors. At year's end, ARPA considered only two contractors and awarded the contract to build the network to BBN in January 1969.[26]
1969 ARPANET IMP
The initial, seven-person BBN team were much aided by the technical specificity of their response to the ARPA RFQ, and thus quickly produced the first working system. The "IMP guys" were led by Frank Heart; the theoretical design of the network was led by Bob Kahn; the team included Dave Walden, Severo Ornstein, William Crowther and several others.[44][45][46] The BBN-proposed network closely followed Roberts' ARPA plan: a network composed of small computers, the IMPs (similar to the later concept of routers), that functioned as gateways interconnecting local resources. Routing, flow control, software design and network control were developed by the BBN team.[44][47] At each site, the IMPs performed store-and-forward packet switching functions and were interconnected with leased lines via telecommunication data sets (modems), with initial data rates of 50kbit/s.[43][48][49] The host computers were connected to the IMPs via custom serial communication interfaces. The system, including the hardware and the packet switching software, was designed and installed in nine months.[26][37][50] The BBN team continued to interact with the NPL team with meetings between them taking place in the U.S. and the U.K.[51][52][53]
As with the NPL network, the first-generation IMPs were built by BBN using a rugged computer version of the HoneywellDDP-516 computer, configured with 24KB of expandable magnetic-core memory, and a 16-channel Direct Multiplex Control (DMC) direct memory access unit.[54] The DMC established custom interfaces with each of the host computers and modems. In addition to the front-panel lamps, the DDP-516 computer also features a special set of 24 indicator lamps showing the status of the IMP communication channels. Each IMP could support up to four local hosts and could communicate with up to six remote IMPs via early Digital Signal 0 leased telephone lines. The network connected one computer in Utah with three in California. Later, the Department of Defense allowed the universities to join the network for sharing hardware and software resources.
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.[55]
The ARPANET used distributed computation and incorporated frequent re-computation of routing tables (automatic routing was technically challenging at the time). These features increased the survivability of the network in the event of significant interruption. Furthermore, the ARPANET was designed to survive subordinate network losses.[56][57] However, the Internet Society agrees with Herzfeld in a footnote in their online article, A Brief History of the Internet:
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.[58]
Paul Baran, the first to put forward a theoretical model for communication using packet switching, conducted the RAND study referenced above.[59][17] Though the ARPANET did not exactly share Baran's project's goal, he said his work did contribute to the development of the ARPANET.[60] Minutes taken by Elmer Shapiro of Stanford Research Institute at the ARPANET design meeting of 9–10 October 1967 indicate that a version of Baran's routing method ("hot potato") may be used,[61] consistent with the NPL team's proposal at the Symposium on Operating System Principles in Gatlinburg.[62]
Later, in the 1970s, ARPA did emphasize the goal of "command and control". According to Stephen J. Lukasik, who was deputy director (1967–1970) and Director of DARPA (1970–1975):[63]
The goal was to exploit new computer technologies to meet the needs of military command and control against nuclear threats, achieve survivable control of US nuclear forces, and improve military tactical and management decision making.[64]
The first four nodes were designated as a testbed for developing and debugging the 1822 protocol, which was a major undertaking. While they were connected electronically in 1969, network applications were not possible until the Network Control Protocol was implemented in 1970 enabling the first two host-host protocols, remote login (Telnet) and file transfer (FTP) which were specified and implemented between 1969 and 1973.[10][11][65] The network was declared operational in 1971. Network traffic began to grow once email was established at the majority of sites by around 1973.[12]
First ARPANET IMP log: the first message ever sent via the ARPANET, 10:30 pm PST on 29 October 1969 (6:30 UTC on 30 October 1969). This IMP Log excerpt, kept at UCLA, describes setting up a message transmission from the UCLA SDS Sigma 7 Host computer to the SRI SDS 940 Host computer.
The initial ARPANET configuration linked UCLA, ARC, UCSB, and the University of Utah School of Computing. The first node was created at UCLA, where Leonard Kleinrock could evaluate network performance and examine his theories on message delay.[66][67][68] The locations were selected not only to reduce leased line costs but also because each had specific expertise beneficial for this initial implementation phase:[1]
University of California, Los Angeles (UCLA), where Kleinrock had established a Network Measurement Center (NMC), with an SDSSigma 7 being the first computer attached to it;
The first successful host-to-host connection on the ARPANET was made between Stanford Research Institute (SRI) and UCLA, by SRI programmer Bill Duvall and UCLA student programmer Charley Kline, at 10:30 pm PST on 29 October 1969 (6:30 UTC on 30 October 1969).[69] Kline connected from UCLA's SDS Sigma 7 Host computer (in Boelter Hall room 3420) to the Stanford Research Institute's SDS 940 Host computer. Kline typed the command "login," but initially the SDS 940 crashed after he typed two characters. About an hour later, after Duvall adjusted parameters on the machine, Kline tried again and successfully logged in. Hence, the first two characters successfully transmitted over the ARPANET were "lo".[70][71][72] The first permanent ARPANET link was established on 21 November 1969, between the IMP at UCLA and the IMP at the Stanford Research Institute. By 5 December 1969, the initial four-node network was established.
Elizabeth Feinler created the first Resource Handbook for ARPANET in 1969 which led to the development of the ARPANET directory.[73] The directory, built by Feinler and a team made it possible to navigate the ARPANET.[74][75]
In 1968, Roberts contracted with Kleinrock to measure the performance of the network and find areas for improvement.[42][76][77] Building on his earlier work on queueing theory and optimization of packet delay in communication networks, Kleinrock specified mathematical models of the performance of packet-switched networks, which underpinned the development of the ARPANET as it expanded rapidly in the early 1970s.[26][39][42]
Roberts engaged Howard Frank to consult on the topological design of the network. Frank made recommendations to increase throughput and reduce costs in a scaled-up network.[78] By March 1970, the ARPANET reached the East Coast of the United States, when an IMP at BBN in Cambridge, Massachusetts was connected to the network. Thereafter, the ARPANET grew: 9 IMPs by June 1970 and 13 IMPs by December 1970, then 18 by September 1971 (when the network included 23 university and government hosts); 29 IMPs by August 1972, and 40 by September 1973. By June 1974, there were 46 IMPs, and in July 1975, the network numbered 57 IMPs. By 1981, the number was 213 host computers, with another host connecting approximately every twenty days.[1]
Support for inter-IMP circuits of up to 230.4 kbit/s was added in 1970, although considerations of cost and IMP processing power meant this capability was not actively used.
Larry Roberts saw the ARPANET and NPL projects as complementary and sought in 1970 to connect them via a satellite link. Peter Kirstein's research group at University College London (UCL) was subsequently chosen in 1971 in place of NPL for the UK connection. In June 1973, a transatlantic satellite link connected ARPANET to the Norwegian Seismic Array (NORSAR),[79] via the Tanum Earth Station in Sweden, and onward via a terrestrial circuit to a TIP at UCL. UCL provided a gateway for interconnection of the ARPANET with British academic networks, the first international resource sharing network, and carried out some of the earliest experimental research work on internetworking.[80]
1971 saw the start of the use of the non-ruggedized (and therefore significantly lighter) Honeywell 316 as an IMP. It could also be configured as a Terminal Interface Processor (TIP), which provided terminal server support for up to 63 ASCII serial terminals through a multi-line controller in place of one of the hosts.[81] The 316 featured a greater degree of integration than the 516, which made it less expensive and easier to maintain. The 316 was configured with 40 kB of core memory for a TIP. The size of core memory was later increased, to 32 kB for the IMPs, and 56 kB for TIPs, in 1973.
In 1975, BBN introduced IMP software running on the Pluribusmulti-processor. These appeared in a few sites. In 1981, BBN introduced IMP software running on its own C/30 processor product.
ARPA was intended to fund advanced research. The ARPANET was a research project that was communications-oriented, rather than user-oriented in design.[82] Nonetheless, in the summer of 1975, operational control of the ARPANET passed to the Defense Communications Agency.[1] At about this time, the first ARPANET encryption devices were deployed to support classified traffic.
The ARPANET Completion Report, written in 1978 and published in 1981 jointly by BBN and DARPA,[83] concludes that:
... it is somewhat fitting to end on the note that the ARPANET program has had a strong and direct feedback into the support and strength of computer science, from which the network, itself, sprang.[84]
The transatlantic connectivity with NORSAR and UCL later evolved into the SATNET. The ARPANET, SATNET and PRNET were interconnected in 1977.
The DoD made TCP/IP the standard communication protocol for all military computer networking in 1980.[85] NORSAR and University College London left the ARPANET and began using TCP/IP over SATNET in 1982.[86]
On January 1, 1983, known as flag day, TCP/IP protocols became the standard for the ARPANET, replacing the earlier Network Control Protocol.[87][15]
In September 1984 work was completed on restructuring the ARPANET giving U.S. military sites their own Military Network (MILNET) for unclassified defense department communications.[88][89] Both networks carried unclassified information and were connected at a small number of controlled gateways which would allow total separation in the event of an emergency. MILNET was part of the Defense Data Network (DDN).[90]
Separating the civil and military networks reduced the 113-node ARPANET by 68 nodes. After MILNET was split away, the ARPANET would continue to be used as an Internet backbone for researchers, but be slowly phased out.
In 1985, the NSF funded the establishment of national supercomputing centers at several universities and provided network access and network interconnectivity with the NSFNET project in 1986. NSFNET became the Internet backbone for government agencies and universities.
The ARPANET project was formally decommissioned in 1990. The original IMPs and TIPs were phased out as the ARPANET was shut down after the introduction of the NSFNet, but some IMPs remained in service as late as July 1990.[91][92]
In the wake of the decommissioning of the ARPANET on 28 February 1990, Vinton Cerf wrote the following lamentation, entitled "Requiem of the ARPANET":[93]
It was the first, and being first, was best,
but now we lay it down to ever rest.
Now pause with me a moment, shed some tears.
For auld lang syne, for love, for years and years
of faithful service, duty done, I weep.
Lay down thypacket, now, O friend, and sleep.
ARPANET and related projects. Figure from 1990.[94]
The technological advancements and practical applications achieved through the ARPANET were instrumental in shaping modern computer networking including the Internet. Development and implementation of the concepts of packet switching, decentralized networks, and communication protocols, notably TCP/IP, laid the foundation for a global network that revolutionized communication, information sharing and collaborative research across the world.[95]
The ARPANET was related to many other research projects, which either influenced the ARPANET design, or were ancillary projects, or spun out of the ARPANET.
Because it was never a goal for the ARPANET to support IMPs from vendors other than BBN, the IMP-to-IMP protocol and message format were not standardized. However, the IMPs did nonetheless communicate amongst themselves to perform link-state routing, to do reliable forwarding of messages, and to provide remote monitoring and management functions to ARPANET's Network Control Center. Initially, each IMP had a 6-bit identifier and supported up to 4 hosts, which were identified with a 2-bit index. An ARPANET host address, therefore, consisted of both the port index on its IMP and the identifier of the IMP, which was written with either port/IMP notation or as a single byte; for example, the address of MIT-DMG (notable for hosting development of Zork) could be written as either 1/6 or 70. An upgrade in early 1976 extended the host and IMP numbering to 8-bit and 16-bit, respectively.[citation needed]
In addition to primary routing and forwarding responsibilities, the IMP ran several background programs, titled TTY, DEBUG, PARAMETER-CHANGE, DISCARD, TRACE, and STATISTICS. These were given host numbers in order to be addressed directly and provided functions independently of any connected host. For example, "TTY" allowed an on-site operator to send ARPANET packets manually via the teletype connected directly to the IMP.[citation needed]
The starting point for host-to-host communication on the ARPANET in 1969 was the 1822 protocol, which defined the transmission of messages to an IMP.[98] The message format was designed to work unambiguously with a broad range of computer architectures. An 1822 message essentially consisted of a message type, a numeric host address, and a data field. To send a data message to another host, the transmitting host formatted a data message containing the destination host's address and the data message being sent, and then transmitted the message through the 1822 hardware interface. The IMP then delivered the message to its destination address, either by delivering it to a locally connected host, or by delivering it to another IMP. When the message was ultimately delivered to the destination host, the receiving IMP would transmit a Ready for Next Message (RFNM) acknowledgment to the sending, host IMP.[citation needed]
Unlike modern Internet datagrams, the ARPANET was designed to reliably transmit 1822 messages, and to inform the host computer when it loses a message; the contemporary IP is unreliable, whereas the TCP is reliable. Nonetheless, the 1822 protocol proved inadequate for handling multiple connections among different applications residing in a host computer. This problem was addressed with the Network Control Protocol (NCP), which provided a standard method to establish reliable, flow-controlled, bidirectional communications links among different processes in different host computers. The NCP interface allowed application software to connect across the ARPANET by implementing higher-level communication protocols, an early example of the protocol layering concept later incorporated in the OSI model.[65]
NCP was developed under the leadership of Steve Crocker, then a graduate student at UCLA. Crocker created and led the Network Working Group (NWG) which was made up of a collection of graduate students at universities and research laboratories, including Jon Postel and Vint Cerf at UCLA. They were sponsored by ARPA to carry out the development of the ARPANET and the software for the host computers that supported applications.
NCP provided a standard set of network services that could be shared by several applications running on a single host computer. This led to the evolution of application protocols that operated, more or less, independently of the underlying network service, and permitted independent advances in the underlying protocols.[citation needed]
The various application protocols such as TELNET for remote time-sharing access and File Transfer Protocol (FTP), the latter used to enable rudimentary electronic mail, were developed and eventually ported to run over the TCP/IP protocol suite. In the 1980s, FTP for email was replaced by the Simple Mail Transfer Protocol and, later, POP and IMAP.[citation needed]
Telnet was developed in 1969 beginning with RFC 15, extended in RFC 855.[citation needed]
The original specification for the File Transfer Protocol was written by Abhay Bhushan and published as RFC114 on 16 April 1971. By 1973, the File Transfer Protocol (FTP) specification had been defined (RFC354) and implemented, enabling file transfers over the ARPANET.[citation needed]
In 1971, Ray Tomlinson, of BBN sent the first network e-mail (RFC524, RFC561).[12][99] An ARPA study in 1973, a year after network e-mail was introduced to the ARPANET community, found that three-quarters of the traffic over the ARPANET consisted of email messages.[100][101][102] E-mail remained a very large part of the overall ARPANET traffic.[103]
Stephen J. Lukasik directed DARPA to focus on internetworking research in the early 1970s. Bob Kahn moved from BBN to DARPA in 1972, first as program manager for the ARPANET, under Larry Roberts, then as director of the IPTO when Roberts left to found Telenet. Kahn worked on both satellite packet networks and ground-based radio packet networks, and recognized the value of being able to communicate across both. Steve Crocker, now at DARPA, and the leaders of British and French network projects founded the International Network Working Group in 1972 and, on Crocker's recommendation, Vint Cerf, now on the faculty at Stanford University, became its Chair.[104][105][106] This group considered how to interconnect packet switching networks with different specifications, that is, internetworking. Research led by Kahn and Cerf resulted in the formulation of the Transmission Control Program,[13] which incorporated concepts from the French CYCLADES project directed by Louis Pouzin.[107] Its specification was written by Cerf with Yogen Dalal and Carl Sunshine at Stanford in December 1974 (RFC675). The following year, testing began through concurrent implementations at Stanford, BBN and University College London.[86] At first a monolithic design, the software was redesigned as a modular protocol stack in version 3 in 1978. Version 4 was installed in the ARPANET for production use in January 1983, replacing NCP. The development of the complete Internet protocol suite by 1989, as outlined in RFC1122 and RFC1123, and partnerships with the telecommunication and computer industry laid the foundation for the adoption of TCP/IP as a comprehensive protocol suite as the core component of the emerging Internet.[15]
The Purdy Polynomial hash algorithm was developed for the ARPANET to protect passwords in 1971 at the request of Larry Roberts, head of ARPA at that time. It computed a polynomial of degree 224 + 17 modulo the 64-bit prime p = 264 − 59. The algorithm was later used by Digital Equipment Corporation (DEC) to hash passwords in the VMS operating system and is still being used for this purpose.[citation needed]
Because of its government funding, certain forms of traffic were discouraged or prohibited.
Leonard Kleinrock claims to have committed the first illegal act on the Internet, having sent a request for return of his electric razor after a meeting in England in 1973. At the time, use of the ARPANET for personal reasons was unlawful.[108][109]
In 1978, against the rules of the network, Gary Thuerk of Digital Equipment Corporation (DEC) sent out the first mass email to approximately 400 potential clients via the ARPANET. He claims that this resulted in $13 million worth of sales in DEC products, and highlighted the potential of email marketing.[citation needed]
A 1982 handbook on computing at MIT's AI Lab stated regarding network etiquette:[110]
It is considered illegal to use the ARPANet for anything which is not in direct support of Government business ... personal messages to other ARPANet subscribers (for example, to arrange a get-together or check and say a friendly hello) are generally not considered harmful ... Sending electronic mail over the ARPANet for commercial profit or political purposes is both anti-social and illegal. By sending such messages, you can offend many people, and it is possible to get MIT in serious trouble with the Government agencies which manage the ARPANet.
"Scenario", an episode of the U.S. television sitcom Benson (season 6, episode 20—dated February 1985), was the first incidence of a popular TV show directly referencing the Internet or its progenitors. The show includes a scene in which the ARPANET is accessed.[112]
There is an electronic music artist known as "Arpanet", Gerald Donald, one of the members of Drexciya. The artist's 2002 album Wireless Internet features commentary on the expansion of the internet via wireless communication, with songs such as NTT DoCoMo, dedicated to the mobile communications giant based in Japan.[citation needed]
The 1993 television series The X-Files featured the ARPANET in a season 5 episode, titled "Unusual Suspects". John Fitzgerald Byers offers to help Susan Modeski (known as Holly ... "just like the sugar") by hacking into the ARPANET to obtain sensitive information.[114][better source needed]
In the spy-drama television series The Americans, a Russian scientist defector offers access to ARPANET to the Russians in a plea to not be repatriated (Season 2 Episode 5 "The Deal"). Episode 7 of Season 2 is named 'ARPANET' and features Russian infiltration to bug the network.
In the television series Person of Interest, main character Harold Finch hacked the ARPANET in 1980 using a homemade computer during his first efforts to build a prototype of the Machine.[115][116] This corresponds with the real life virus that occurred in October of that year that temporarily halted ARPANET functions.[117] The ARPANET hack was first discussed in the episode 2PiR (stylized 2R) where a computer science teacher called it the most famous hack in history and one that was never solved. Finch later mentioned it to Person of Interest Caleb Phipps and his role was first indicated when he showed knowledge that it was done by "a kid with a homemade computer" which Phipps, who had researched the hack, had never heard before.
In the third season of the television series Halt and Catch Fire, the character Joe MacMillan explores the potential commercialization of the ARPANET.
^"An Internet Pioneer Ponders the Next Revolution". The New York Times. 20 December 1999. Retrieved 20 February 2020. Mr. Taylor wrote a white paper in 1968, a year before the network was created, with another ARPA research director, J. C. R. Licklider. The paper, "The Computer as a Communications Device," was one of the first clear statements about the potential of a computer network.
^Hafner, Katie (30 December 2018). "Lawrence Roberts, Who Helped Design Internet's Precursor, Dies at 81". The New York Times. ISSN0362-4331. Retrieved 20 February 2020. He decided to use packet switching as the underlying technology of the Arpanet; it remains central to the function of the internet. And it was Dr. Roberts's decision to build a network that distributed control of the network across multiple computers. Distributed networking remains another foundation of today's internet.
^"Computer Pioneers - Donald W. Davies". IEEE Computer Society. Retrieved 20 February 2020. In 1965, Davies pioneered new concepts for computer communications in a form to which he gave the name "packet switching." ... The design of the ARPA network (ArpaNet) was entirely changed to adopt this technique.
^"A Flaw In The Design". The Washington Post. 30 May 2015. The Internet was born of a big idea: Messages could be chopped into chunks, sent through a network in a series of transmissions, then reassembled by destination computers quickly and efficiently. Historians credit seminal insights to Welsh scientist Donald W. Davies and American engineer Paul Baran. ... The most important institutional force ... was the Pentagon's Advanced Research Projects Agency (ARPA) ... as ARPA began work on a groundbreaking computer network, the agency recruited scientists affiliated with the nation's top universities.
^ abAbbate, Janet (2000). Inventing the Internet. Cambridge, MA: MIT Press. pp. 39, 57–58. ISBN978-0-2625-1115-5. Baran proposed a "distributed adaptive message-block network" [in the early 1960s] ... Roberts recruited Baran to advise the ARPANET planning group on distributed communications and packet switching. ... Roberts awarded a contract to Leonard Kleinrock of UCLA to create theoretical models of the network and to analyze its actual performance.
^ abCerf, V.; Kahn, R. (1974). "A Protocol for Packet Network Intercommunication"(PDF). IEEE Transactions on Communications. 22 (5): 637–648. doi:10.1109/TCOM.1974.1092259. ISSN1558-0857. The authors wish to thank a number of colleagues for helpful comments during early discussions of international network protocols, especially R. Metcalfe, R. Scantlebury, D. Walden, and H. Zimmerman; D. Davies and L. Pouzin who constructively commented on the fragmentation and accounting issues; and S. Crocker who commented on the creation and destruction of associations.
^Roberts, Lawrence G. (November 1978). "The Evolution of Packet Switching"(PDF). IEEE Invited Paper. Archived from the original(PDF) on 31 December 2018. Retrieved 10 September 2017. In nearly all respects, Davies' original proposal, developed in late 1965, was similar to the actual networks being built today.
^Markoff, John, Innovator who helped create PC, Internet and the mouse, New York Times, 15 April 2017, p.A1
^Waldrop, M. Mitchell (2018). The Dream Machine. Stripe Press. pp. 285–6. ISBN978-1-953953-36-0. Oops. Roberts knew Baran slightly and had in fact had lunch with him during a visit to RAND the previous February. But he certainly didn't remember any discussion of networks. How could he have missed something like that?
^O'Neill, Judy (5 March 1990). "An Interview with PAUL BARAN"(PDF). p. 37. On Tuesday, 28 February 1967 I find a notation on my calendar for 12:00 noon Dr. L. Roberts.
^ abRoberts, Lawrence G. (November 1978). "The evolution of packet switching"(PDF). Proceedings of the IEEE. 66 (11): 1307–13. doi:10.1109/PROC.1978.11141. S2CID26876676. Significant aspects of the network's internal operation, such as routing, flow control, software design, and network control were developed by a BBN team consisting of Frank Heart, Robert Kahn, Severo Omstein, William Crowther, and David Walden
^F.E. Froehlich, A. Kent (1990). The Froehlich/Kent Encyclopedia of Telecommunications: Volume 1 - Access Charges in the U.S.A. to Basics of Digital Communications. CRC Press. p. 344. ISBN0824729005. Although there was considerable technical interchange between the NPL group and those who designed and implemented the ARPANET, the NPL Data Network effort appears to have had little fundamental impact on the design of ARPANET. Such major aspects of the NPL Data Network design as the standard network interface, the routing algorithm, and the software structure of the switching node were largely ignored by the ARPANET designers. There is no doubt, however, that in many less fundamental ways the NPL Data Network had and effect on the design and evolution of the ARPANET.
^ARPANET Information Brochure. May 1980. p. 12. The complete network is formed by interconnecting the nodes through wideband communication lines, normally 50,000 bits per second (50KBPS), supplied by common carriers
^BBN Report No. 1928(PDF) (Report). January 1970. we designed and implemented a test program to obtain data on the performance of the fifty kilobit communication circuits
^Leiner, Barry M.; Cerf, Vinton G.; Clark, David D.; Kahn, Robert E.; Kleinrock, Leonard; Lynch, Daniel C.; Postel, Jon; Roberts, Larry G.; Wolff, Stephen (1997). "Brief History of the Internet". Internet Society. (footnote 5)
^Lukasik, Stephen J. (2011). "Why the Arpanet Was Built". IEEE Annals of the History of Computing. 33 (3): 4–20. doi:10.1109/MAHC.2010.11. S2CID16076315.
^Clarke, Peter (1982). Packet and circuit-switched data networks(PDF) (PhD thesis). Department of Electrical Engineering, Imperial College of Science and Technology, University of London. "Many of the theoretical studies of the performance and design of the ARPA Network were developments of earlier work by Kleinrock ... Although these works concerned message switching networks, they were the basis for a lot of the ARPA network investigations ... The intention of the work of Kleinrock [in 1961] was to analyse the performance of store and forward networks, using as the primary performance measure the average message delay. ... Kleinrock [in 1970] extended the theoretical approaches of [his 1961 work] to the early ARPA network."
^Heart, F.; McKenzie, A.; McQuillian, J.; Walden, D. (4 January 1978). Arpanet Completion Report(PDF) (Technical report). Burlington, MA: Bolt, Beranek and Newman.
^"III". A History of the ARPANET: The First Decade (Report). Arlington, VA: Bolt, Beranek & Newman Inc. 1 April 1981. p. 132. section 2.3.4
^Leiner, Barry M.; Cerf, Vinton G.; Clark, David D.; Kahn, Robert E.; Kleinrock, Leonard; Lynch, Daniel C.; Postel, Jon; Roberts, Larry G.; Wolff, Stephen (7 October 2009). "A brief history of the internet". ACM SIGCOMM Computer Communication Review. 39 (5): 22–31. doi:10.1145/1629607.1629613. ISSN0146-4833. S2CID15845974.
^ abby Vinton Cerf, as told to Bernard Aboba (1993). "How the Internet Came to Be". Archived from the original on 26 September 2017. Retrieved 25 September 2017. We began doing concurrent implementations at Stanford, BBN, and University College London. So effort at developing the Internet protocols was international from the beginning. ... Mar '82 - Norway leaves the ARPANET and become an Internet connection via TCP/IP over SATNET. Nov '82 - UCL leaves the ARPANET and becomes an Internet connection.
^McKenzie, Alexander (2011). "INWG and the Conception of the Internet: An Eyewitness Account". IEEE Annals of the History of Computing. 33 (1): 66–71. doi:10.1109/MAHC.2011.9. ISSN1934-1547. S2CID206443072.
^"The internet's fifth man". The Economist. 30 November 2013. ISSN0013-0613. Retrieved 22 April 2020. In the early 1970s Mr Pouzin created an innovative data network that linked locations in France, Italy and Britain. Its simplicity and efficiency pointed the way to a network that could connect not just dozens of machines, but millions of them. It captured the imagination of Dr Cerf and Dr Kahn, who included aspects of its design in the protocols that now power the internet.
^Still, tapping into the ARPANET to fetch a shaver across international lines was a bit like being a stowaway on an aircraft carrier. The ARPANET was an official federal research facility, after all, and not something to be toyed with. Kleinrock had the feeling that the stunt he'd pulled was slightly out of bounds. 'It was a thrill. I felt I was stretching the Net'. – Hafner & Lyon 1996, Chapter 7
^Stacy, Christopher C. (7 September 1982). Getting Started Computing at the AI Lab (Report). MIT Artificial Intelligence Laboratory Working Papers. hdl:1721.1/41180. WP-235.
Norberg, Arthur L.; O'Neill, Judy E. (1996). Transforming Computer Technology: Information Processing for the Pentagon, 1962–1982. Johns Hopkins University. pp. 153–196. ISBN978-0-8018-6369-1.
Kahn, Robert E. (24 April 1990). "Oral history interview with Robert E. Kahn". University of Minnesota, Minneapolis: Charles Babbage Institute. Retrieved 15 May 2008. Focuses on Kahn's role in the development of computer networking from 1967 through the early 1980s. Beginning with his work at BBN, Kahn discusses his involvement as the ARPANET proposal was being written and then implemented, and his role in the public demonstration of the ARPANET. The interview continues into Kahn's involvement with networking when he moves to IPTO in 1972, where he was responsible for the administrative and technical evolution of the ARPANET, including programs in packet radio, the development of a new network protocol (TCP/IP), and the switch to TCP/IP to connect multiple networks.
Cerf, Vinton G. (24 April 1990). "Oral history interview with Vinton Cerf". University of Minnesota, Minneapolis: Charles Babbage Institute. Retrieved 1 July 2008. Cerf describes his involvement with the ARPA network, and his relationships with Bolt Beranek and Newman, Robert Kahn, Lawrence Roberts, and the Network Working Group.
Baran, Paul (5 March 1990). "Oral history interview with Paul Baran". University of Minnesota, Minneapolis: Charles Babbage Institute. Retrieved 1 July 2008. Baran describes his work at RAND, and discusses his interaction with the group at ARPA who were responsible for the later development of the ARPANET.
Lukasik, Stephen (17 October 1991). "Oral history interview with Stephen Lukasik". University of Minnesota, Minneapolis: Charles Babbage Institute. Retrieved 1 July 2008. Lukasik discusses his tenure at the Advanced Research Projects Agency (ARPA), the development of computer networks and the ARPANET.
Davies, D.W.; Bartlett, K.A.; Scantlebury, R.A.; Wilkinson, P.T. (1967). "A digital communication network for computers giving rapid response at remote terminals". Proceedings of the first ACM symposium on Operating System Principles (SOSP '67). Association for Computing Machinery. pp. 2.1–2.17. doi:10.1145/800001.811669. S2CID15215451.
Roberts, Lawrence G.; Wessler, Barry D. (1970). "Computer network development to achieve resource sharing". Proceedings of the May 5-7, 1970, Spring Joint Computer Conference (AFIPS '70 (Spring)). Association for Computing Machinery. pp. 543–9. doi:10.1145/1476936.1477020. S2CID9343511.
Ornstein, Severo; Heart, Frank; Crowther, William; Russell, S. B.; Rising, H. K.; Michel, A. (1972). The Terminal IMP for the ARPA Computer Network. 1972 Spring Joint Computer Conference. AFIPS Proc. Vol. 40. pp. 243–254. doi:10.1145/1478873.1478906.
McQuillan, John; Crowther, William; Cosell, Bernard; Walden, David; Heart, Frank (1972). Improvements in the Design and Performance of the ARPA Network. 1972 Fall Joint Computer Conference part II. AFIPS Proc. Vol. 41. pp. 741–754. doi:10.1145/1480083.1480096.
Ornstein, Severo; Heart, Frank; Crowther, William; Russell, S. B.; Rising, H. K.; Michel, A. (1972). The Terminal IMP for the ARPA Computer Network. 1972 Spring Joint Computer Conference. AFIPS Proc. Vol. 40. pp. 243–254. doi:10.1145/1478873.1478906.
Feinler, E.; Postel, J. (1976). ARPANET Protocol Handbook. SRI International. OCLC2817630. NTIS ADA027964.
Feinler, E.J.; Landsberden, J.M.; McGinnis, A.C. (1976). ARPANET Resource Handbook. Stanford Research Institute. OCLC1110650114. NTIS ADA040452.
NTIS documents may be available from "National Technical Reports Library". NTIS National Technical Information Service. U.S. Department of Commerce. 2014.
Waldrop, Mitch (April 2008). "DARPA and the Internet Revolution". 50 years of Bridging the Gap. DARPA. pp. 78–85. Archived from the original on 15 September 2012. Retrieved 26 August 2012.
