3 Internet History: ARPANET and TCP/IP

fundamentals

history

internet

3.1 Start With the Decision

This section: Start With the Decision — ARPANET was an early network linking distant machines.

ARPANET was an early network linking distant machines. Packet switching sends data in separate pieces across a network. A protocol is a shared set of rules for exchanging data; TCP/IP is the set of rules that helped networks exchange those pieces. ARPANET joined distant machines, but one network was not yet an Internet. Packet switching and TCP/IP made links work across faults and borders.

3.2 Route Overview

This section: Route Overview — This is part 1 of 2.

This is part 1 of 2. Continue with Internet History: Web, Mobile, and IoT.

3.3 Part Objectives

This section: Part Objectives

Trace packet switching from Cold War research to ARPANET.
Explain why TCP/IP created an open network of networks.

3.4 In 60 Seconds

This section: In 60 Seconds — Picture a field unit sending a reading through a local bridge and several networks.

Connect Each Historic Idea to a Modern Failure Test

Picture a field unit sending a reading through a local bridge and several networks. The parts come from different eras, yet one broken hand-off can still make the current service show a plausible old value.

TCP means a connected byte stream that tracks order and loss. A gateway is the device or service that joins two system paths. Firmware is the stored device code and its version.

Trace one record with its source, time, unit, and code version. Break a link, repeat the record, restart the bridge, and reject a stale result at the receiver. Use the historical milestones to explain why each boundary exists, not as proof that the deployed path works.

This runway does not turn a timeline into a full design review. The deeper sections connect open networking, layered communication, the web, mobile systems, and embedded devices to the evidence a current system still needs.

The Internet did not appear as one invention. It grew from packet-switching research, ARPANET experiments, the TCP/IP split, DNS naming, the World Wide Web, and later mobile, cloud, and IoT protocols. The same choices that made a few research computers interoperate—open standards, layered protocols, fault-tolerant routing, and simple packet forwarding—still explain why constrained IoT devices can talk to cloud services today.

3.5 Start With the Story

This section: Start With the Story — You will connect packet switching, TCP/IP, and later Internet services to the open networks that IoT devices use today.

You will connect packet switching, TCP/IP, and later Internet services to the open networks that IoT devices use today. Start with the problem of carrying messages across different networks, then follow the historical milestones.

Trace the deployed event through four beats to see why an interoperable Internet path matters to the device at the edge.

Motion Marley creates a deployed sensor event while Gateway Gus and Packet Pete prepare it for a route beyond the device. — Open packet paths connect a deployed event to the people and services that act on it.

Radio Remi, Packet Pete, and Gateway Gus face two disconnected network benches with a visible gap between their cables. — Open packet paths connect a deployed event to the people and services that act on it.

Chapter Roadmap

In 60 Seconds
Start With the Story
What To Watch For
Minimum Viable Understanding
Prerequisites
The Cold War Seeds (1957-1965)
Checkpoint: Packet Switching
ARPANET: The First Internet (1969-1983)
The Internet Is Born (1983-1990)

3.6 Learning Objectives

This section: Learning Objectives

By the end of this chapter, you will be able to:

Trace the Internet’s origin: Explain how ARPANET evolved from a Cold War research project into the global Internet
Identify key pioneers: Describe the contributions of Vint Cerf, Bob Kahn, Tim Berners-Lee, and other Internet architects
Compare switching paradigms: Differentiate packet switching from circuit switching and explain why packet switching was revolutionary for network resilience
Map the timeline: Place key Internet milestones in chronological order from the 1960s to the present
Connect history to IoT: Explain how each era of networking evolution—from ARPANET to TCP/IP to the Web—enabled today’s Internet of Things
Evaluate architectural decisions: Assess how early design choices (open standards, layered protocols, end-to-end principle) shaped the modern IoT ecosystem

3.7 What To Watch For

This section: What To Watch For

Packet switching: Messages are split into packets that share links and can route around failures.
Layering: Link, internet, transport, and application responsibilities stay separate so each layer can evolve.
Open standards: RFCs, freely usable protocols, and interoperable implementations let independent systems connect.
The end-to-end principle: The network core forwards packets while reliability, identity, encryption, and application meaning mostly live at the endpoints.
IoT consequence: MQTT, CoAP, 6LoWPAN, Thread, Matter, and cloud gateways build on those older Internet design choices rather than replacing them.

3.8 Minimum Viable Understanding

This section: Minimum Viable Understanding

If you only have 5 minutes:

1969: ARPANET sends first message between UCLA and Stanford Research Institute — the first two “nodes” on what would become the Internet. The message was “LOGIN” but the system crashed after “LO”
1974: Vint Cerf and Bob Kahn publish the TCP/IP paper that defines how all Internet communication works — still in use today, 50+ years later
1983: January 1st—“Flag Day”—ARPANET switches from NCP to TCP/IP. This is the true “birthday” of the Internet
1991: Tim Berners-Lee launches the World Wide Web at CERN, making the Internet accessible to everyone
1999: Kevin Ashton coins the term “Internet of Things,” imagining a world where physical objects connect to the Internet

For Beginners: Why the Internet’s History Matters

Imagine you turn on a smart light bulb with your phone. That simple action uses ideas invented by dozens of brilliant people over 50 years:

The packet that carries your command was shaped by packet-switching work from Paul Baran, Donald Davies, Leonard Kleinrock, and others in the 1960s
The TCP/IP protocol that routes it was designed by Vint Cerf and Bob Kahn in the 1970s
The web interface you tap was created by Tim Berners-Lee in the 1990s
The wireless connection uses standards refined over decades

Every IoT device stands on those design choices. Understanding the story helps you understand why the Internet works the way it does, not just how to configure it.

ARPANET and the Origins of Packet Switching

Temperature Terry says: “Hey Sensor Squad! Did you know the Internet started with just FOUR computers? And the very first message ever sent was supposed to be ‘LOGIN’ but the computer CRASHED after only two letters — ‘LO’! So the first Internet message was accidentally ‘LO’ — like ‘Lo and behold!’ Pretty funny, right?”

Light Lucy adds: “The people who built the Internet were really young! Vint Cerf was only 26 when he started working on ARPANET, and the team that sent that first message included a graduate student named Charley Kline who was just 21!”

Max the Motion Sensor explains: “Before packet networking, a phone call held a reserved path for the whole conversation — like keeping a private road open until you hang up.”

Bella the Buzzer chimes in: “And now, decades later, there are more IoT connections than people on Earth! From those 4 computers to an estimated 21.1 billion IoT connections in 2025 (IoT Analytics). IoT Analytics October 2025 forecast That’s what happens when really smart people share really great ideas!”

3.9 Prerequisites

This section: Prerequisites — No prior networking knowledge is required.

No prior networking knowledge is required. This chapter tells the story chronologically and explains each concept as it appears. If you want to dive deeper into networking after reading this, see OSI and TCP/IP Models.

3.10 The Cold War Seeds (1957-1965)

This section: The Cold War Seeds (1957-1965) — The Internet wasn’t built to share cat videos — it was born from fear.

The Internet wasn’t built to share cat videos — it was born from fear. When the Soviet Union launched Sputnik in 1957, the United States realized it was falling behind in science and technology. President Eisenhower responded by creating ARPA (Advanced Research Projects Agency) in 1958 — a small government agency tasked with making sure America would never be surprised by technological achievement again.

ARPA had an unusual approach: instead of building things itself, it funded brilliant researchers at universities and gave them freedom to explore radical ideas. This culture of open research and collaboration would become the DNA of the Internet itself.

3.10.1 The Problem of Survivable Communication

In the early 1960s, military planners faced a terrifying question: how do you maintain communication after a nuclear attack? The existing telephone system was centralized — if a few key switching centers were destroyed, the entire network could collapse.

Those switching centers were physical places, not just boxes in a diagram. A map of central-office sites shows how dense the public telephone network had become in cities and suburbs, while long-distance trunk maps show high-capacity routes concentrating traffic between regions. Packet switching did not merely replace a voice call with a data packet; it changed the geography of resilience. The design goal shifted from holding one reserved path through specific offices to letting many packets use available links and route around damaged or congested parts of the network.

Three researchers, working independently on three continents, arrived at the same revolutionary idea:

Pioneer	Location	Year	Contribution
Paul Baran	RAND Corporation, USA	1962	Designed “distributed adaptive message block switching” — breaking messages into blocks that could route around damage
Donald Davies	National Physical Laboratory, UK	1965	Independently invented “packet switching” — the term we still use today
Leonard Kleinrock	MIT/UCLA, USA	1961	Published the first paper on queuing theory for packet networks — the mathematical foundation

Putting Numbers to It

Baran described a distributed network with about 3-4 links per node as a useful level of redundancy. That design insight does not by itself guarantee survival of any particular fraction of node failures. In a separate simplified model with $n$ independent paths, the probability of at least one path delivering a message is:

$P(\text{delivery}) = 1 - \prod_{i=1}^{n} (1 - p_i)$

With 3 independent paths each having 90% reliability: $P = 1 - (0.1)^3 = 99.9\%$ . Shared failures or correlated paths would lower the real-world result.

Interactive Network Reliability Calculator: Explore how redundant paths improve reliability:

3.10.2 Circuit Switching vs Packet Switching

The telephone network used circuit switching — when you made a call, a dedicated physical circuit was established from your phone to the other person’s phone. This circuit was yours alone for the entire call, even during silences.

Packet switching was radically different:

Break the message into small packets (typically 1,000-1,500 bytes each)
Each packet travels independently — it can take any available route
Packets are reassembled at the destination — the receiver puts them back in order
The network is shared — many conversations use the same wires simultaneously

This is like the difference between hiring a private taxi (circuit switching) versus using a postal service (packet switching). The postal service is far more efficient because one mail truck carries hundreds of letters simultaneously.

Physics Phoebe, Physics and measurement-foundations expert

Checkpoint: Packet Switching

You now know:

The survivability problem was about avoiding a few centralized telephone switching centers.
Packet switching breaks a message into independently routed packets, typically 1,000-1,500 bytes each.
Baran’s quantitative example shows why redundancy matters: with 3 paths at 90% reliability, delivery rises to 99.9%.

3.11 ARPANET: The First Internet (1969-1983)

This section: ARPANET: The First Internet (1969-1983)

3.11.1 The First Message

On October 29, 1969, at 10:30 PM, a 21-year-old UCLA graduate student named Charley Kline sat at an SDS Sigma 7 computer and attempted to log in to a computer at Stanford Research Institute (SRI), 350 miles away. He typed “L”… then “O”… then “G”… and the system crashed.

The first message ever sent over ARPANET was “LO” — an accidental abbreviation that would be poetic only in hindsight. An hour later, they tried again and successfully transmitted “LOGIN.”

The four original ARPANET nodes were:

Node	Institution	IMP Number	Connected
1	UCLA	IMP #1	September 2, 1969
2	Stanford Research Institute (SRI)	IMP #2	October 1, 1969
3	UC Santa Barbara	IMP #3	November 1, 1969
4	University of Utah	IMP #4	December 1, 1969

The “IMP” (Interface Message Processor) was the ancestor of today’s router — a Honeywell DDP-516 minicomputer that weighed 900 pounds and cost $82,200 (about $680,000 in today’s money).

3.11.2 Growing the Network

ARPANET grew steadily through the 1970s:

1970: ALOHAnet in Hawaii pioneers wireless packet networking (ancestor of Wi-Fi)
1971: Ray Tomlinson sends the first email and picks ”@” to separate user from machine
1972: ARPANET demonstrated publicly at ICCC conference — 40 machines connected
1973: First international connections — University College London (UK) and NORSAR (Norwegian Seismic Array, Norway)
1974: Vint Cerf and Bob Kahn publish “A Protocol for Packet Network Intercommunication” — the TCP paper

That growth is easier to understand as a map than as a slogan. In December 1969, ARPANET was a four-node western U.S. experiment linking UCLA, SRI, UC Santa Barbara, and the University of Utah. By the mid-1970s, the map had spread across research sites, military labs, and international links. Later host-count curves make the same point on a log scale: the Internet grew by orders of magnitude because new hosts could join a shared packet network without redesigning the whole system around each pair of endpoints.

3.11.3 The Fathers of the Internet: Cerf and Kahn

Vint Cerf and Bob Kahn are often called the “Fathers of the Internet” for their 1974 paper defining TCP (Transmission Control Protocol). Their key insight was creating a universal protocol that could connect different types of networks — ARPANET, radio networks, satellite networks — into one seamless “inter-network” (which became shortened to “Internet”).

Their original TCP combined what we now know as TCP and IP into a single protocol. In 1978, they split it into two layers:

IP (Internet Protocol): Handles addressing and routing — getting packets to the right destination
TCP (Transmission Control Protocol): Handles reliability — making sure all packets arrive and are in order

This split was crucial. It meant that different applications could choose different transport protocols. Today, IoT devices often use UDP (User Datagram Protocol) instead of TCP because UDP is lighter weight — a choice made possible by this architectural decision from 1978.

Putting Numbers to It

The original TCP/IP design had to work with the constraints of 1970s hardware. An early ARPANET IMP had about 12K 16-bit words of memory, not 12 KB. Its maximum packet was 1,008 bits = 126 bytes; a common Ethernet MTU today is 1,500 bytes of network-layer payload, or $1500/126 \approx 11.9$ times that packet size (the units and layers differ). Links have grown from about 50 kb/s to Tb/s scale, an order-of-magnitude ratio of roughly $10^7$ . Actual throughput depends on equipment and link conditions, while the internetworking design still works across this range.

3.12 The Internet Is Born (1983-1990)

This section: The Internet Is Born (1983-1990)

3.12.1 Flag Day: January 1, 1983

The true birthday of the Internet is January 1, 1983 — “Flag Day” — when every machine on ARPANET simultaneously switched from the old NCP (Network Control Protocol) to TCP/IP. There was no gradual migration. At midnight, NCP stopped working and TCP/IP was the only option.

This was a massive coordinated effort. Every host on the network had to be ready. Buttons reading “I have TCP/IP — ask me how” were distributed at networking conferences. The transition went remarkably smoothly.

Quick Check: Test your understanding of the Internet’s “birthday”:

3.12.2 Domain Name System (1983-1984)

Before DNS, you had to know a computer’s numerical IP address to reach it. Paul Mockapetris invented the Domain Name System in 1983, allowing human-readable names like “usc.edu” instead of “128.125.253.136.”

For IoT deployments, DNS is not just a convenience. Resolver choice, cache TTLs, CNAME chains, and failover records determine how quickly devices recover when cloud endpoints move or regional services fail. A resilient design records which names the device resolves, how long it caches answers, what happens when DNS returns NXDOMAIN, and whether provisioning can update endpoint names without reflashing firmware.

Try the resolution workbench below to see what a resolver actually does with one of those names: trace a recursive client query through iterative root, TLD, and authoritative referrals, watch a TTL cache hit skip that trip entirely, and follow a CNAME chain or NXDOMAIN response.

The original top-level domains were:

Domain	Purpose	Year
.com	Commercial	1985
.edu	Educational	1985
.gov	Government	1985
.mil	Military	1985
.org	Organizations	1985
.net	Network providers	1985

The first .com domain ever registered was symbolics.com on March 15, 1985.

3.12.3 Key Developments

1983: BSD Unix includes TCP/IP — making it free and widely available
1984: ARPANET splits into ARPANET (research) and MILNET (military)
1986: NSFNET backbone created — connecting 5 supercomputing centers at 56 Kbps
1988: The Morris Worm — first major Internet security incident, infecting ~6,000 of the 60,000 connected computers
1989: Tim Berners-Lee proposes the World Wide Web at CERN

This section:

3.13 Continue to the Next Part

This section: Continue to the Next Part — Carry this evidence into Internet History: Web, Mobile, and IoT, which begins with Checkpoint: TCP/IP and DNS.

Carry this evidence into Internet History: Web, Mobile, and IoT, which begins with Checkpoint: TCP/IP and DNS.

Find help

Search reviewed answers

3 reviewed answers.

Where should I start in a module?

Open the module page from the sidebar to see its chapters in order. Use the module map to return to a topic you need.

Modules and paths

Reviewed 2026-10-16

What can I try when a project does not work?

Check the symptom, then work through the diagnostic steps. Keep the error message and the smallest example that reproduces it.

When you are stuck

Reviewed 2026-10-16

How do interactive examples work?

Use the interactive guide to check how examples and simulations work before changing your project.

Interactive examples guide

Reviewed 2026-10-16