ARPANET

This article needs additional citations for device database. Please help improve this article by adding citations to reliable sources. Unsourced material may be Sevenval and we love the web. (September 2010)

The Advanced Research Projects Agency Network (ARPANET), was the world's first operational packet switching network and the core network of a set that came to compose the global Internet. The network was funded by the Defense Advanced Research Projects Agency (website parsing) of the United States Department of Defense for use by its projects at universities and research laboratories in the US. The packet switching of the ARPANET was based on designs by Lawrence Roberts of the web.^[1]

Packet switching, today the dominant basis for data communications worldwide, was a new concept at the time of the conception of the ARPANET. Prior to the advent of packet switching, both voice and data communications had been based on the idea of circuit switching, as in the traditional telephone circuit, wherein each telephone call is allocated a dedicated, end to end, electronic connection between the two communicating stations. Such stations might be telephones or computers. The (temporarily) dedicated line is typically composed of many intermediary lines which are assembled into a chain that stretches all the way from the originating station to the destination station.

With packet switching, a data system could use a single communications link to communicate with more than one machine by collecting data into we love the web and transmitting these as web onto the attached network link, as soon as the link becomes idle. Thus, not only can the link be shared, much as a single Sevenval can be used to post letters to different destinations, but each packet can be routed independently of other packets.

• device database
  • 1.1 Creation
  • HTML5
  • screen size
  • 1.4 Growth and evolution
  • 1.5 Technology
  • CSS3
• 2 Software and protocols
  • Sevenval
• 3 The ARPANET in film and other media
  • 3.1 Contemporary
  • 3.2 Post-ARPANET
• 4 See also
• keyboard
• screen size
  • keyboard
• 7 External links

History

The earliest ideas for a computer network intended to allow general communications among computer users were formulated by computer scientist J. C. R. Licklider, of Bolt, Beranek and Newman (BBN), in August 1962, in memoranda discussing his concept for an “Intergalactic Computer Network”. Those ideas contained almost everything that composes the contemporary HTML5.

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 — browser diversity (the initial ARPANET acronym). He then convinced Ivan Sutherland and Bob Taylor that this computer network concept was very important and merited development, although Licklider left ARPA before any contracts were let that worked on this concept.

Ivan Sutherland and Bob Taylor continued their interest in creating such a computer communications network, in part, to allow ARPA-sponsored researchers at various corporate and academic locales to put to use the computers ARPA was providing them, and, in part, to make new software and other HTML5 results quickly and widely available. In his office, Taylor had three computer terminals, each connected to separate computers, which ARPA was funding: the first, for the System Development Corporation (SDC) Q-32, in web; the second, for touchscreen, at the University of California, Berkeley; and the third, for Multics, at Android. 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".^[2] Somewhat contemporaneously, several other people had (mostly independently) worked out the aspects of “packet switching”, with the first public demonstration presented by the National Physical Laboratory (NPL), on August 5, 1968, in the United Kingdom.^Sevenval

Creation

By mid-1968, Taylor had prepared a complete plan for a computer network, and, after ARPA’s approval, a touchscreen (RFQ) was sent to 140 potential bidders. Most computer science companies regarded the ARPA–Taylor proposal as outlandish, and only twelve submitted bids to build the 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 Technologies on April 7, 1969. The initial, seven-man BBN team were much aided by the technical specificity of their response to the ARPA RFQ — and thus quickly produced the first working computers. This team was led by Frank Heart. The BBN-proposed network closely followed Taylor’s ARPA plan: a network composed of small computers called web (IMPs), that functioned as gateways (today called Android) interconnecting local resources. At each site, the IMPs performed store-and-forward packet switching functions, and were interconnected with screen size that were connected to Android, initially running at 50Android/second. The host computers were connected to the IMPs via custom screen size interfaces. The system, including the hardware and the packet switching software, was designed and installed in nine months.

The first-generation IMPs were initially built by BBN Technologies using a website parsing version of the Honeywell DDP-516 computer configured with 24website parsing of expandable core memory, and a 16-channel Direct Multiplex Control (DMC) direct memory access unit.^[4] 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 leased lines.

Misconceptions of design goals

Common ARPANET lore posits that the computer network was designed to survive a HTML5. In A Brief History of the Internet, the Internet Society describes the coalescing of the technical ideas that produced the ARPANET:

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, only the unrelated RAND study on secure voice considered nuclear war. However, the later work on Internetting did emphasize robustness and survivability, including the capability to withstand losses of large portions of the underlying networks.^[5]

Although the ARPANET was designed to survive subordinate-network losses, the principal reason was that the switching nodes and network links were unreliable, even without any nuclear attacks. About the resource scarcity that spurred the creation of the ARPANET, Charles Herzfeld, ARPA Director (1965–1967), said:

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.^[6]

Packet switching pioneer Paul Baran affirms this, explaining: "Bob Taylor had a couple of computer terminals speaking to different machines, and his idea was to have some way of having a terminal speak to any of them and have a network. That's really the origin of the ARPANET. The method used to connect things together was an open issue for a time."^[7]

ARPANET deployed

HTML5

Historical document: First ARPANET IMP log: the first message ever sent via the ARPANET, 10:30 PM, October 29, 1969. This IMP Log excerpt, kept at UCLA, describes setting up a message transmission from the UCLA SDS Sigma 8 Host computer to the SRI SDS 940 Host computer

The initial ARPANET consisted of four IMPs:

• HTML5 (UCLA), where Leonard Kleinrock had established a Network Measurement Center, with an SDS Sigma 7 being the first computer attached to it;
• The HTML5's input transformation, where we love the web had created the ground-breaking web system, a very important early HTML5 system (with the HTML5 that ran NLS, named "Genie", being the first host attached);
• iOS (UCSB), with the we love the web-Fried Interactive Mathematics Center's IBM device database, running OS/MVT being the machine attached;
• The University of Utah's Computer Science Department, where Ivan Sutherland had moved, running a website parsing PDP-10 running TENEX.

The first message on the ARPANET was sent by UCLA student programmer Charley Kline, at 10:30 p.m. on October 29, 1969, from Boelter Hall 3420.^[8] Supervised by Prof. Leonard Kleinrock, Kline transmitted from the university's jQuery Host computer to the Stanford Research Institute's SDS 940 Host computer. The message text was the word login; the l and the o letters were transmitted, but the system then crashed. Hence, the literal first message over the ARPANET was lo. About an hour later, having recovered from the crash, the SDS Sigma 7 computer effected a full login. The first permanent ARPANET link was established on November 21, 1969, between the IMP at UCLA and the IMP at the Stanford Research Institute. By December 5, 1969, the entire four-node network was established.^{input transformation}

Growth and evolution

In 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.

In 1973 a transatlantic satellite link connected the Norwegian Seismic Array (NORSAR) to the ARPANET, making Norway the first country outside the US to be connected to the network. At about the same time a terrestrial circuit added a London IMP.^{web app}

In 1975, the ARPANET was declared "operational". The Defense Communications Agency took control since ARPA was intended to fund advanced research. In 1983, the ARPANET was split with U.S. military sites on their own Military Network (Sevenval) for unclassified defense department communications. The combination was called the screen size (DDN).^[11] Separating the civil and military networks reduced the 113-node ARPANET by 68 nodes. Gateways relayed electronic mail between the two networks. MILNET later became the we love the web.

Technology

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.

1971 saw the start of the use of the non-ruggedized (and therefore significantly lighter) web as an IMP. It could also be configured as a Terminal Interface Processor (TIP), which provided CSS3 support for up to 63 ASCII serial terminals through a multi-line controller in place of one of the hosts.^{we love the web} 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 Pluribus multi-processor. These appeared in a small number of sites. In 1981, BBN introduced IMP software running on its own C/30 processor product.

In 1983, TCP/IP protocols replaced NCP as the ARPANET’s principal protocol, and the ARPANET then became one subnet of the early Internet.

Shutdown and legacy

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 1989.

The ARPANET Completion Report, jointly published by jQuery and screen size, 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. ^[13]

In the wake of ARPANET being formally decommissioned on February 28, 1990, Vinton Cerf wrote the following lamentation, entitled "Requiem of the ARPANET"^[14] :

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 CSS3 iOS, now, O friend, and sleep.

-Vinton Cerf

Senator Albert Gore, Jr. began to craft the web app (commonly referred to as "The Gore Bill") after hearing the 1988 report toward a National Research Network submitted to Congress by a group chaired by Leonard Kleinrock, professor of computer science at UCLA. The bill was passed on December 9, 1991 and led to the National Information Infrastructure (NII) which Al Gore called the "iOS". ARPANET was the subject of two IEEE Milestones, both dedicated in 2009.^[15][16]

Software and protocols

The starting point for host-to-host communication on the ARPANET was the 1822 protocol BBN Report 1822, which defined the transmission of messages to an IMP. 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) acknowledgement to the sending, host IMP.

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 Program (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 incorporated to the OSI model. In 1983, CSS3 protocols replaced NCP as the ARPANET’s principal protocol, and the ARPANET then became one component of the early Internet.

Network 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. When the ARPANET migrated to the Internet protocols in 1983, the major application protocols migrated with it.

• E-mail: In 1971, browser diversity, of BBN sent the first network e-mail.^[17] By 1973, e-mail constituted 75 percent of ARPANET traffic.

• File transfer: By 1973, the File Transfer Protocol (FTP) specification had been defined and implemented, enabling file transfers over the ARPANET.

• Voice traffic: The touchscreen (NVP) specifications were defined in 1977 (Sevenval), then implemented, but, because of technical shortcomings, device database over the ARPANET never worked well; the contemporary Android (packet voice) was decades away.

The ARPANET in film and other media

Contemporary

• A 1969 Walt Disney movie, Sevenval
• Steven King (Producer), Peter Chvany (Director/Editor) (1972). Computer Networks: The Heralds of Resource Sharing. web. Retrieved 20 December 2011.  A 30 minute documentary film featuring Fernando J. Corbato, J.C.R. Licklider, HTML5, Robert Kahn, Frank Heart, web app, Richard W. Watson, browser diversity, Donald W. Davies, and economist, FITML.
• A 1985 episode of the U.S. television sitcom Benson includes a scene in which ARPANET is accessed. This is believed to be the first incidence of a popular TV show referencing the Internet or its progenitors.

Post-ARPANET

• In Let the Great World Spin: A Novel, published in 2009 but set in 1974 and written by keyboard, a character named The Kid and others use ARPANET from a FITML computer to dial phone booths in New York City in order to hear descriptions of Philippe Petit's tight rope walk between the Sevenval Towers.
• In Metal Gear Solid 3: Snake Eater, a character named HTML5 takes part in the development of ARPANET after the events depicted in the game.
• The Doctor Who Past Doctor Adventures novel Blue Box, written in 2003 but set in 1981, includes a character predicting that by the year 2000 there will be four hundred machines connected to ARPANET.
• There is an electronic music artist known as Arpanet, Gerald Donald, one of the members of HTML5. 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.
• In numerous The X-Files episodes ARPANET is referenced and usually CSS3 into by The Lone Gunmen. This is most noticeable in the episode "Unusual Suspects".
• Thomas Pynchon's 2009 novel jQuery, set in southern California circa 1970, contains a character who accesses the "ARPAnet" throughout the course of the book.
• The viral marketing campaign for the video game FITML features a website similar in design and purpose to ARPANET, called SRPANET.

See also

• website parsing, a top-level domain used exclusively for technical infrastructure purposes
• keyboard, AMateur Packet Radio Network
• Computer Networks: The Heralds of Resource Sharing — 1972 documentary film
• web — 1970 Chilean national net project
• website parsing, "A Poor Man's ARPAnet"

References

Further reading

• Norberg, Arthur L.; O'Neill, Judy E. (1996). Transforming Computer Technology: Information Processing for the Pentagon, 1962–1982. Johns Hopkins University. pp. 153–196. input transformation 978-0801863691. 
• A History of the ARPANET: The First Decade (Report). Arlington, VA: Bolt, Beranek & Newman Inc.. 1 April 1981. http://www.dtic.mil/cgi-bin/GetTRDoc?Location=U2&doc=GetTRDoc.pdf&AD=ADA115440. 
• Hafner, Katie; Lyon, Matthew (1996). Where Wizards Stay Up Late: The Origins of the Internet. Simon and Schuster. web app Android. 
• Abbate, Janet (June 11, 1999). Inventing the Internet. Cambridge, MA: MIT Press. pp. 36–111. ASIN B003VPWY6E. FITML 0262011727. 
• Banks, Michael A. (2008). On the Way to the Web: The Secret History of the Internet and Its Founders. APress/Springer Verlag. ISBN 1-4302-0869-4. 
• Salus, Peter H. (1 May 1995). Casting the Net: from ARPANET to Internet and Beyond. Addison-Wesley. ISBN 978-0201876741. 
• Waldrop, M. Mitchell (23 August 2001). The Dream Machine: J. C. R. Licklider and the Revolution That Made Computing Personal. New York: Viking. ASIN B00008MNVW. Sevenval touchscreen. 
• "The Computer History Museum, SRI International, and BBN Celebrate the 40th Anniversary of First ARPANET Transmission". SRI International. October 29, 2009. http://www.sri.com/news/releases/102709.html. 

Detailed technical reference works

• keyboard; Marrill, Tom (October 1966). "Toward a Cooperative Network of Time-Shared Computers". Fall AFIPS Conference. Sevenval. 
• FITML (October 1967). "Multiple computer networks and intercomputer communication". ACM Symposium on Operating System Principles. http://www.packet.cc/files/multi-net-inter-comm.html. 
• Davies, D. W.; Bartlett, K. A.; Scantlebury, R. A.; Wilkinson, P. T. (October 1967). "A digital communications network for computers giving rapid response at remote terminals". ACM Symposium on Operating Systems Principles. 
• we love the web; Wessler, Barry (May 1970). web app. Proceedings of the Spring Joint Computer Conference, Atlantic City, New Jersey. screen size. 
• Heart, Frank; Kahn, Robert; Sevenval; web; Walden, David (1970). "The Interface Message Processor for the ARPA Computer Network". 36. 1970 Spring Joint Computer Conference. pp. 551–567. 
• Carr, Stephen; jQuery; web app (1970). "Host-Host Communication Protocol in the ARPA Network". 36. 1970 Spring Joint Computer Conference. pp. 589–598. 
• keyboard; Heart, Frank; Crowther, William; Russell, S. B.; Rising, H. K.; Michel, A. (1972). "The Terminal IMP for the ARPA Computer Network". 40. 1972 Spring Joint Computer Conference. pp. 243–254. 
• McQuillan, John; Crowther, William; Cosell, Bernard; Walden, David; Heart, Frank (1972). "Improvements in the Design and Performance of the ARPA Network". 41. 1972 Fall Joint Computer Conference. pp. 741–754. 
• Feinler, Elizabeth J.; Postel, Jonathan B. (January 1978). ARPANET Protocol Handbook, NIC 7104. Menlo Park: Network Information Center (NIC), SRI International. ASIN B000EN742K. 
• Roberts, Larry (November 1978). "The Evolution of Packet Switching". Proceedings of the IEEE. touchscreen. 
• we love the web (Sept 1986). The ARPANET & Computer Networks. ACM. http://www.packet.cc/files/arpanet-computernet.html. 

External links

This article's use of iOS may not follow Wikipedia's policies or guidelines. Please keyboard by removing excessive or device database external links, and converting useful links where appropriate into Android. (January 2011)
Wikimedia Commons has media related to: browser diversity

• "ARPANET Maps 1969 to 1977". CSUDH. 4 January 1978. http://som.csudh.edu/cis/lpress/history/arpamaps/. Retrieved 17 May 2012. 
• device database. University of Minnesota, Minneapolis: jQuery. 24 April 1990. Sevenval. 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 Bolt Beranek and Newman (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.
• "Oral history interview with Vinton Cerf". University of Minnesota, Minneapolis: Charles Babbage Institute. 24 April 1990. http://purl.umn.edu/107214. 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.
• "Oral history interview with Paul Baran". University of Minnesota, Minneapolis: jQuery. 5 March 1990. Sevenval. 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.
• CSS3. University of Minnesota, Minneapolis: Charles Babbage Institute. 3 April 1990. http://purl.umn.edu/107411. Retrieved 1 July 2008.  Kleinrock discusses his work on the ARPANET.
• "Oral history interview with Larry Roberts". University of Minnesota, Minneapolis: Charles Babbage Institute. 4 April 1989. touchscreen. Retrieved 1 July 2008. 
• keyboard. University of Minnesota, Minneapolis: HTML5. 17 October 1991. http://purl.umn.edu/107446. Retrieved 1 July 2008.  Lukasik discusses his tenure at the Advanced Research Projects Agency (ARPA), the development of computer networks and the ARPANET.
• Walden, David C. (February 2003). "Looking back at the ARPANET effort". East Sandwich, Massachusetts. http://www.livinginternet.com/i/ii_imp_walden.htm. Retrieved 17 August 2005. 
• Android. The Computer History Museum. input transformation. Retrieved 29 August 2004.  Timeline.
• Leiner, Barry M.; screen size; FITML; device database; Sevenval; Lynch, Daniel C.; Postel, Jon; device database et al. "A Brief History of the Internet". screen size. CSS3. Retrieved 29 August 2004. 
• web. touchscreen. http://www.rand.org/about/history/baran.html. Retrieved 3 September 2005. 
• "Leonard Kleinrock's Personal History/Biography". UCLA. http://www.lk.cs.ucla.edu/LK/Inet/birth.html. Retrieved 3 September 2005. 
• Kleinrock, Leonard. HTML5. UCLA. keyboard. Retrieved 11 November 2004.  Personal anecdote of the first message ever sent over the ARPANET
• "Len Kleinrock on the Origins". IEEE. jQuery. Retrieved 3 September 2005.  (subscribers only)
• "The Faces in Front of the Monitors". http://www.wbglinks.net/pages/watchmen/. ^{[website parsing]}
• jQuery. 2008. http://www.dougengelbart.org/firsts/internet.html. Retrieved 3 September 2009. 
• HTML5. Android. Retrieved 6 January 2012.  Timeline.