ARPANET

The Advanced Research Projects Agency Network (ARPANET) was an early packet switching network and the first network to implement the protocol suite TCP/IP. Both technologies became the technical foundation of the Internet. ARPANET was initially funded by the Advanced Research Projects Agency (ARPA, later Defense Advanced Research Projects Agency (DARPA)) of the United States Department of Defense.

Packet switching was based on concepts and designs by Americans Leonard Kleinrock and Paul Baran, British scientist Donald Davies^[1][2] and Lawrence Roberts of the Lincoln Laboratory.^[3] The TCP/IP communication protocols were developed for ARPANET by computer scientists Robert Kahn and Vint Cerf, and incorporated concepts by Louis Pouzin for the French CYCLADES project.

History

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 communication link to communicate with more than one machine by collecting data into datagrams and transmitting these as packets onto the attached network link, as soon as the link becomes idle. Thus, not only can the link be shared, much as a single post box can be used to post letters to different destinations, but each packet can be routed independently of other packets.^[4]

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

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

Meanwhile, since the early 1960s, Paul Baran at the RAND Corporation had been researching systems that could survive nuclear war^[8] and presented in the United Kingdom National Physical Laboratory (NPL) the first public demonstration of packet switching on 5 August 1968.^[9]

Creation

Len Kleinrock and the first Interface Message Processor^[10]

By mid-1968, Taylor had prepared a complete plan for a computer network, and, after ARPA's approval, a Request for Quotation (RFQ) was issued for 140 potential bidders. Most computer science companies regarded the ARPA–Taylor 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 Technologies on 7 April 1969. 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. This team was led by Frank Heart. The BBN-proposed network closely followed Taylor's ARPA plan: a network composed of small computers called Interface Message Processors, similar to the later concept of routers, that functioned as gateways interconnecting local resources. 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. 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.^[11]

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

Misconceptions of design goals

It is commonly stated that ARPANET was designed to survive a nuclear attack. In A Brief History of the Internet, the Internet Society denies this:

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

The RAND study was conducted by Paul Baran and pioneered packet switching.^[8] In an interview he confirmed that ARPANET did not share his project's goal, but also argued that his work had greatly contributed to the development of ARPANET.^[14] Additionally, minutes taken by Elmer Shapiro of Stanford Research Institute at the ARPANET design meeting of Oct. 9-10 1967 indicate that a version of Baran's routing method and suggestion of using a fixed packet size was expected to be employed.^[15]

The ARPANET incorporated distributed computation (and frequent re-computation) of routing tables. This was a major contribution to the good survivability that the ARPANET had, in the face of significant destruction - even by a nuclear attack. Such auto-routing was technically quite challenging to construct at the time. The fact that it was incorporated into the early ARPANET made many believe that this had been a design goal.

The ARPANET was in fact designed to survive subordinate-network losses, but 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.^[16]

The ARPANET was operated by the military during the two decades of its existence, until 1990.^[17][18]

ARPANET deployed

Historical document: First ARPANET IMP log: the first message ever sent via the ARPANET, 10:30 pm, 29 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 consisted of four IMPs:^[19]

• University of California, Los Angeles (UCLA), where Leonard Kleinrock had established a Network Measurement Center, with an SDS Sigma 7 being the first computer attached to it;
• The Augmentation Research Center at Stanford Research Institute (now SRI International), where Douglas Engelbart had created the ground-breaking NLS system, a very important early hypertext system, and would run the Network Information Center (NIC), with the SDS 940 that ran NLS, named "Genie", being the first host attached;
• University of California, Santa Barbara (UCSB), with the Culler-Fried Interactive Mathematics Center's IBM 360/75, running OS/MVT being the machine attached;
• The University of Utah's Computer Science Department, where Ivan Sutherland had moved, running a DEC PDP-10 operating on TENEX.

The first successful message on the ARPANET was sent by UCLA student programmer Charley Kline, at 10:30 pm on 29 October 1969, from Boelter Hall 3420.^[20] Kline transmitted from the university's SDS Sigma 7 Host computer to the Stanford Research Institute's SDS 940 Host computer. The message text was the word login; on an earlier attempt 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, after the programmers repaired the code that caused the crash, the SDS Sigma 7 computer effected a full login. 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 entire four-node network was established.^[21]

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

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

In 1975, the ARPANET was declared "operational". The Defense Communications Agency took control since ARPA was intended to fund advanced research.^[19]

In September of 1984 work was completed on restructuring the ARPANET giving U.S. military sites on their own Military Network (MILNET) for unclassified defense department communications.^[23][24] Controlled gateways connected the two networks. The combination was called the Defense Data Network (DDN).^[25] Separating the civil and military networks reduced the 113-node ARPANET by 68 nodes. The MILNET later became the NIPRNet.

Rules and etiquette

Because of its government ties, certain forms of traffic were discouraged or prohibited. A 1982 handbook on computing at MIT's AI Lab stated regarding network etiquette:^[26]

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.

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) 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.^[27] 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 few 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.^[28][29]

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

The ARPANET Completion Report, jointly published by BBN and ARPA, 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.^[31]

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

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 thy packet, now, O friend, and sleep.

-Vinton Cerf

Senator Albert Gore, Jr. began to craft the High Performance Computing and Communication Act of 1991 (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 9 December 1991 and led to the National Information Infrastructure (NII) which Al Gore called the "information superhighway". ARPANET was the subject of two IEEE Milestones, both dedicated in 2009.^[33][34]

Software and protocols

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

In 1983, TCP/IP protocols replaced NCP as the ARPANET's principal protocol, and the ARPANET then became one component of the early Internet.^[29]

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, Ray Tomlinson, of BBN sent the first network e-mail (RFC 524, RFC 561).^[36] By 1973, e-mail constituted 75 percent of ARPANET traffic.

File transfer

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

Voice traffic

The Network Voice Protocol (NVP) specifications were defined in 1977 (RFC 741), then implemented, but, because of technical shortcomings, conference calls over the ARPANET never worked well; the contemporary Voice over Internet Protocol (packet voice) was decades away.

Password Protection

The Purdy Polynomial hash algorithm was developed for ARPANET to protect passwords in 1971 at the request of Larry Roberts, head of ARPA at that time. It computed a polynomial of degree 2²⁴ + 17 modulo the 64-bit prime p = 2⁶⁴ - 59. The algorithm was later used by DEC to hash passwords in their OpenVMS operating system, and is still being used for this purpose.

ARPANET in popular culture

• Computer Networks: The Heralds of Resource Sharing, a 30-minute documentary film ^[37] featuring Fernando J. Corbato, J.C.R. Licklider, Lawrence G. Roberts, Robert Kahn, Frank Heart, William R. Sutherland, Richard W. Watson, John R. Pasta, Donald W. Davies, and economist, George W. Mitchell.
• "Scenario", a February 1985 episode of the U.S. television sitcom Benson (season 6, episode 20), 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.^[38]
• 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.
• Thomas Pynchon mentions ARPANET in his 2009 novel Inherent Vice, which is set in Los Angeles in 1970, and in his 2013 novel Bleeding Edge.
• 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.^[39]

See also

• .arpa, a top-level domain used exclusively for technical infrastructure purposes
• AMPRNet, AMateur Packet Radio Network
• Computer Networks: The Heralds of Resource Sharing—1972 documentary film
• Project Cybersyn—1970 Chilean national net project
• Usenet, "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. ISBN 978-0-8018-6369-1. 
• A History of the ARPANET: The First Decade (PDF) (Report). Arlington, VA: Bolt, Beranek & Newman Inc. 1 April 1981. 
• Hafner, Katie; Lyon, Matthew (1996). Where Wizards Stay Up Late: The Origins of the Internet. Simon and Schuster. ISBN 0-7434-6837-6. 
• Abbate, Janet (11 June 1999). Inventing the Internet. Cambridge, MA: MIT Press. pp. 36–111. ASIN B003VPWY6E. ISBN 0-262-01172-7. 
• 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-0-201-87674-1. 
• 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. ISBN 0-670-89976-3. 
• "The Computer History Museum, SRI International, and BBN Celebrate the 40th Anniversary of First ARPANET Transmission". Computer History Museum. 27 October 2009. 

Oral histories

• "Oral history interview with Robert E. Kahn". University of Minnesota, Minneapolis: Charles Babbage Institute. 24 April 1990. 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. 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: Charles Babbage Institute. 5 March 1990. 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.
• "Oral history interview with Leonard Kleinrock". University of Minnesota, Minneapolis: Charles Babbage Institute. 3 April 1990. 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. Retrieved 1 July 2008. 
• "Oral history interview with Stephen Lukasik". University of Minnesota, Minneapolis: Charles Babbage Institute. 17 October 1991. Retrieved 1 July 2008.  Lukasik discusses his tenure at the Advanced Research Projects Agency (ARPA), the development of computer networks and the ARPANET.

Detailed technical reference works

• Roberts, Larry; Marrill, Tom (October 1966). Toward a Cooperative Network of Time-Shared Computers. Fall AFIPS Conference. 
• Roberts, Larry (October 1967). Multiple computer networks and intercomputer communication. ACM Symposium on Operating System Principles. 
• 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. 
• Roberts, Larry; Wessler, Barry (May 1970). Computer Network Development to Achieve Resource Sharing. Proceedings of the Spring Joint Computer Conference, Atlantic City, New Jersey. 
• Heart, Frank; Kahn, Robert; Ornstein, Severo; Crowther, William; Walden, David (1970). The Interface Message Processor for the ARPA Computer Network (PDF). 1970 Spring Joint Computer Conference. AFIPS Proc. 36: 551–567. doi:10.1145/1476936.1477021. 
• Carr, Stephen; Crocker, Stephen; Cerf, Vinton (1970). Host-Host Communication Protocol in the ARPA Network. 1970 Spring Joint Computer Conference. AFIPS Proc. 36: 589–598. doi:10.1145/1476936.1477024. RFC 33. 
• 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. 40: 243–254. 
• 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. 41: 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 66 (11): 1307. doi:10.1109/PROC.1978.11141. 
• Roberts, Larry (September 1986). "The ARPANET & Computer Networks". ACM. 

External links

Wikimedia Commons has media related to ARPANET.

• "ARPANET Maps 1969 to 1977". California State University, Dominguez Hills (CSUDH). 4 January 1978. Retrieved 17 May 2012. 
• Walden, David C. (February 2003). "Looking back at the ARPANET effort, 34 years later". Living Internet. East Sandwich, Massachusetts: livinginternet.com. Retrieved 17 August 2005. 
• "Images of ARPANET from 1964 onwards". The Computer History Museum. Retrieved 29 August 2004.  Timeline.
• "Paul Baran and the Origins of the Internet". RAND Corporation. Retrieved 3 September 2005. 
• Kleinrock, Leonard. "The Day the Infant Internet Uttered its First Words". UCLA. Retrieved 11 November 2004.  Personal anecdote of the first message ever sent over the ARPANET
• "Doug Engelbart's Role in ARPANET History". 2008. Retrieved 3 September 2009. 
• "Internet Milestones: Timeline of Notable Internet Pioneers and Contributions". Retrieved 6 January 2012.  Timeline.
• Waldrop, Mitch (April 2008). "DARPA and the Internet Revolution". 50 years of Bridging the Gap. DARPA. pp. 78–85. Retrieved 26 August 2012. 
• "A picture of the ARPANET team". 

Telecommunications History Beacon Broadcasting Communications satellite Computer network Drums Electrical telegraph Fax Heliographs Hydraulic telegraph Internet Mass media Mobile phone Optical telecommunication Optical telegraphy Photophone Prepaid mobile phone Radio Radiotelephone Satellite communications Smoke signals Telecommunications history Telegraphy Telephone The Telephone Cases Television Timeline of communication technology Undersea telegraph line Videoconferencing Videophone Videotelephony Pioneers Edwin Howard Armstrong John Logie Baird Alexander Graham Bell Tim Berners-Lee Jagadish Chandra Bose Vint Cerf Claude Chappe Lee de Forest Philo Farnsworth Reginald Fessenden Elisha Gray Guglielmo Marconi Alexander Stepanovich Popov Johann Philipp Reis Nikola Tesla Camille Papin Tissot Alfred Vail Charles Wheatstone Vladimir K. Zworykin Transmission media Coaxial cable Free-space optical Optical fiber Radio waves Telephone lines Terrestrial microwave Molecules Network topology and switching Links Nodes Terminal node Network switching (circuit packet) Telephone exchange Multiplexing Space-division Frequency-division Time-division Polarization-division Orbital angular-momentum Code-division Networks ARPANET BITNET Computer Ethernet FidoNet Internet ISDN LAN Mobile NGN Public Switched Telephone Radio Telecommunications equipment Television Telex WAN Wireless World Wide Web By continent Telecommunications in Africa Sovereign states Algeria Angola Benin Botswana Burkina Faso Burundi Cameroon Cape Verde Central African Republic Chad Comoros Democratic Republic of the Congo Republic of the Congo Djibouti Egypt Equatorial Guinea Eritrea Ethiopia Gabon The Gambia Ghana Guinea Guinea-Bissau Ivory Coast (Côte d'Ivoire) Kenya Lesotho Liberia Libya Madagascar Malawi Mali Mauritania Mauritius Morocco Mozambique Namibia Niger Nigeria Rwanda São Tomé and Príncipe Senegal Seychelles Sierra Leone Somalia South Africa South Sudan Sudan Swaziland Tanzania Togo Tunisia Uganda Zambia Zimbabwe States with limited recognition Sahrawi Arab Democratic Republic Somaliland Dependencies and other territories Mayotte / Réunion (France) Saint Helena / Ascension Island / Tristan da Cunha (United Kingdom) Western Sahara Telecommunications in Asia Sovereign states Afghanistan Armenia Azerbaijan Bahrain Bangladesh Bhutan Brunei Burma (Myanmar) Cambodia China Cyprus East Timor (Timor-Leste) Egypt Georgia India Indonesia Iran Iraq Israel Japan Jordan Kazakhstan North Korea South Korea Kuwait Kyrgyzstan Laos Lebanon Malaysia Maldives Mongolia Nepal Oman Pakistan Philippines Qatar Russia Saudi Arabia Singapore Sri Lanka Syria Tajikistan Thailand Turkey Turkmenistan United Arab Emirates Uzbekistan Vietnam Yemen States with limited recognition Abkhazia Nagorno-Karabakh Northern Cyprus Palestine South Ossetia Taiwan Dependencies and other territories British Indian Ocean Territory Christmas Island Cocos (Keeling) Islands Hong Kong Macau Telecommunications in Europe Sovereign states Albania Andorra Armenia Austria Azerbaijan Belarus Belgium Bosnia and Herzegovina Bulgaria Croatia Cyprus Czech Republic Denmark Estonia Finland France Georgia Germany Greece Hungary Iceland Ireland Italy Kazakhstan Latvia Liechtenstein Lithuania Luxembourg Macedonia Malta Moldova Monaco Montenegro Netherlands Norway Poland Portugal Romania Russia San Marino Serbia Slovakia Slovenia Spain Sweden Switzerland Turkey Ukraine United Kingdom States with limited recognition Abkhazia Kosovo Nagorno-Karabakh Northern Cyprus South Ossetia Transnistria Dependencies and other territories Åland Faroe Islands Gibraltar Guernsey Jersey Isle of Man Svalbard Other entities European Union Telecommunications in North America Sovereign states Antigua and Barbuda Bahamas Barbados Belize Canada Costa Rica Cuba Dominica Dominican Republic El Salvador Grenada Guatemala Haiti Honduras Jamaica Mexico Nicaragua Panama Saint Kitts and Nevis Saint Lucia Saint Vincent and the Grenadines Trinidad and Tobago United States Dependencies and other territories Anguilla Aruba Bermuda Bonaire British Virgin Islands Cayman Islands Curaçao Greenland Guadeloupe Martinique Montserrat Navassa Island Puerto Rico Saint Barthélemy Saint Martin Saint Pierre and Miquelon Saba Sint Eustatius Sint Maarten Turks and Caicos Islands United States Virgin Islands Telecommunications in Oceania Sovereign states Australia Fiji Indonesia Kiribati Marshall Islands Federated States of Micronesia Nauru New Zealand Palau Papua New Guinea Samoa Solomon Islands Tonga Tuvalu Vanuatu Associated states of New Zealand Cook Islands Niue Dependencies and other territories American Samoa Christmas Island Cocos (Keeling) Islands Easter Island French Polynesia Guam Hawaii New Caledonia Norfolk Island Northern Mariana Islands Pitcairn Islands Tokelau Wallis and Futuna Telecommunications in South America Sovereign states Argentina Bolivia Brazil Chile Colombia Ecuador Guyana Paraguay Peru Suriname Uruguay Venezuela Dependencies and other territories Falkland Islands French Guiana South Georgia and the South Sandwich Islands Telecommunications Telecommunication Telecommunication Mass surveillance