TCP/IP
In the late 1960s, in the particular context of the Cold War, the United States sought to establish a military communication network capable of withstanding a Soviet nuclear attack. The U.S. Department of Defense, through its DARPA (Defense Advanced Research Projects Agency), launched the ARPAnet project in 1969, which aimed to interconnect the country’s main computing centers. Military constraints shaped the network’s design from the outset. There could be no Achilles’ heel, no central point whose destruction would compromise the entire system. Messages had to be able to take alternative routes dynamically if certain portions failed. More complex still, the network had to connect computers running different operating systems.
ARPAnet started with the NCP protocol, but its shortcomings became apparent in short order. In 1974, two researchers changed the game: Vinton Cerf and Robert Kahn published “A Protocol for Packet Network Interconnection”, a foundational article that introduced TCP. This publication outlined what would become TCP/IP, standardizing communication between machines. The genius of TCP/IP lies in its layered structure. IP handles routing data packets from one point to another on the network, while TCP ensures transmission control and reassembles complete messages upon arrival. This division of labor makes the system more robust and easier to evolve, an engineering principle that would prove its worth.
In 1983, TCP/IP officially replaced NCP on ARPAnet. Although this point is widely debated and debatable, the concept of the Internet was truly born at this moment, in the literal sense of the term. TCP/IP’s success rests on three decisive advantages. It works on any hardware, computer, or physical network. It maintains communication when part of the network fails through dynamic routing. It breaks messages into packets that can take different paths before being reassembled. First-generation IP addressing uses 32-bit addresses that uniquely identify each machine. The system classifies these addresses into categories A, B, and C to simplify management. But the explosive growth of the network quickly revealed the limitations of this approach. Computer scientists then developed workarounds such as subnetting, while awaiting IPv6 and its 128-bit addresses.
The TCP/IP architecture is organized in four layers: Network Access for physical connection, Internet (IP) for routing, Transport (TCP/UDP) for transmission, and Application for user programs. This hierarchy facilitates adding new functionality without disrupting the existing system, a tremendous advantage for the system’s evolution. Several auxiliary protocols complement TCP/IP. ARP translates logical IP addresses into physical network card addresses. ICMP carries control and error messages. These mechanisms contribute to the overall system’s reliability and efficiency.
Berkeley UNIX contributed to TCP/IP’s dissemination during the 1980s. Native integration of the protocol into BSD facilitated its adoption by universities and research centers that extensively used this operating system. Technical documentation was public and accessible to all in the form of RFCs, documents open to community contributions. This decentralized approach stimulated innovation and continuous improvement, an approach that would durably influence technological development.
The explosion of the World Wide Web in the 1990s spectacularly validated the choice of TCP/IP. The protocol absorbed without flinching an exponential growth in the number of users and the arrival of resource-intensive applications. Its flexibility allowed the addition of advanced features such as multicast for broadcasting to multiple recipients, and quality of service to prioritize certain flows. The history of TCP/IP continues to be written. The anticipated exhaustion of IPv4 addresses and new security and performance needs drove the development of IPv6 in the 1990s. This version offers a virtually infinite address space—3.4×1038 addresses—and substantial improvements. Migration to IPv6 is progressing very slowly, complicated by the need to maintain compatibility with existing systems.
From military project to universal standard, TCP/IP has spread to all contemporary domains. Computers of course, but also smartphones, connected devices, industrial equipment—the list grows longer every day. This ubiquity stems from its remarkable ability to adapt to technological developments without breaking with its legacy. The standardization of TCP/IP made possible the emergence of a global network where billions of machines communicate, regardless of their origin or geographic location.