The History of TCP/IP

TCP/IP is the common language every network on the internet agrees to speak. Its history is the story of how a pair of protocols turned a scattering of incompatible research networks into a single, worldwide internet.

The problem TCP/IP was built to solve

By the early 1970s, packet-switched networking had proven itself on ARPANET, and other experimental networks had appeared alongside it, including ones that used radio and satellite links. Each worked well on its own, but they could not talk to one another. A message that reached the edge of one network had no way to cross into the next. What was missing was a way to knit separate networks into a network of networks, an internet.

TCP/IP was the answer. It is a family of protocols whose job is to let computers on completely different networks package, address and deliver data to one another. Its arrival is the reason we can speak of a single internet at all rather than a patchwork of isolated systems.

Cerf, Kahn and the founding design

The foundational design of TCP/IP is credited to Vint Cerf and Robert Kahn, who in the mid-1970s published the influential work describing how independent packet networks could be interconnected. Their approach introduced the idea of gateways, machines that sit between networks and pass packets from one to another, and a shared addressing scheme so that any computer could be identified no matter which network it sat on.

Crucially, they designed the system to make no demands on the underlying networks beyond the ability to carry packets. This "network agnosticism" is why the same protocols could later run over telephone lines, fibre, wireless and technologies that had not even been invented yet. As with the rest of internet history, the design was refined by a broad community of engineers through openly published technical documents.

Splitting into TCP and IP

The original proposal was a single protocol, but as the work matured, engineers separated it into two complementary parts. This split is central to understanding TCP/IP.

The Internet Protocol (IP) handles addressing and routing. It gives every device an IP address and works out how to move a packet, hop by hop, toward its destination. IP is deliberately simple and makes no promises: it does its best to deliver each packet but does not guarantee arrival or order.

The Transmission Control Protocol (TCP) sits on top and adds reliability. It numbers the packets, checks that they all arrive, asks for any missing ones to be resent, and puts them back in the correct order. Splitting the two meant that applications needing guaranteed delivery could use TCP, while those valuing speed over perfection could use lighter alternatives like UDP directly over IP.

The 1983 flag day

Designing a protocol is one thing; getting a whole network to adopt it is another. For years, ARPANET ran on its original host protocol, NCP, while TCP/IP was tested alongside it. Eventually the decision was made to switch over completely on a single planned date, the start of 1983, an event often called the "flag day". After it, every host on ARPANET spoke TCP/IP, and NCP was switched off.

That changeover is widely treated as the moment the modern internet, defined by a shared protocol rather than a single network, truly began. You can see how it fits into the broader timeline in our history of the internet.

How TCP/IP took over the world

Through the 1980s and beyond, TCP/IP spread far past its research origins. It was bundled into popular operating systems, which made it the natural choice for connecting any computer to any other. Competing networking schemes existed, some backed by large companies and standards bodies, but TCP/IP's openness, simplicity and head start won out. It became the default plumbing of the connected world.

Its original addressing scheme, IPv4, offered a few billion addresses, which once seemed limitless. As the internet exploded in size, that supply came under strain, a story told in our guide to IPv4 address exhaustion. The response included the address-sharing trick of Network Address Translation and a far larger successor, IPv6, but both are extensions of the same TCP/IP family, not replacements for it.

Why TCP/IP still runs everything

Decades on, TCP/IP remains the foundation of essentially all internet communication. When you load a page, stream a film or send a message, IP is addressing and routing your packets while TCP or a sibling protocol manages their delivery. Its longevity comes from that early decision to keep the core simple and let the edges innovate, a principle that has let the internet reinvent everything above it without ever having to replace the layer underneath.

To glimpse TCP/IP at work, look no further than your own IP address, the label IP uses to route data to you. The friendly checkers at IP Animals will show you exactly what it is.