Prerequisites

Blueprints · 222 words · 1 min read

TCP/IP: The Language Machines Learned to Speak

How Vint Cerf and Bob Kahn designed the protocol suite that became the backbone of the internet.

#The Problem: Babel’s Tower of Networks

In the early 1970s, computer networks existed — but they couldn’t talk to each other. ARPANET used NCP, European networks used X.25, and proprietary corporate systems spoke their own dialects. It was a digital Tower of Babel.

Vint Cerf and Bob Kahn proposed a radical idea: a protocol that didn’t care what network you were on. The Transmission Control Protocol (TCP) and Internet Protocol (IP) would act as universal translators, routing packets across any combination of networks.

#The Architecture

TCP/IP introduced a layered model that remains the foundation of all internet communication:

┌─────────────────────┐
│   Application Layer  │  HTTP, FTP, SMTP, DNS
├─────────────────────┤
│   Transport Layer    │  TCP, UDP
├─────────────────────┤
│   Internet Layer     │  IP, ICMP, ARP
├─────────────────────┤
│   Link Layer         │  Ethernet, Wi-Fi
└─────────────────────┘

Each layer has one job and trusts the layers below it to handle their responsibilities. This separation of concerns — a concept we’ll see echoed throughout software architecture — made the system both robust and extensible.

#Why This Matters

TCP/IP is the foundational protocol of everything that follows in this tech tree. Every HTTP request, every database query over a network, every git push — they all ride on TCP/IP. Understanding this protocol is understanding the plumbing of the digital world.

#Key Takeaways

  • Packet switching beats circuit switching for resilient, efficient networks
  • Layered architecture allows independent evolution of each layer
  • End-to-end principle: keep the network simple, push complexity to the edges
  • Open standards won against proprietary protocols because anyone could implement them