Overview
Robert Elliot Kahn (born 1938) established the open-architecture networking principle at DARPA and co-designed TCP/IP with Vint Cerf. He had earlier been central to ARPANET's design and to its 1972 public demonstration. He shared the 2004 Turing Award with Cerf.
What You Need
- Born 1938, United States
- Anchor year: 1974 — the TCP/IP paper
- Strand: canon
Steps
The problem as it stood
Kahn was running a satellite and packet radio programme at DARPA and needed those networks to interoperate with ARPANET. Each had different characteristics, and none of their operators would accept redesigning around another's requirements.
What he actually did
Kahn set out the open-architecture rules: each network keeps its own internal design; there is no global control; gateways do not retain per-connection state; and communication is best effort, with reliability handled at the endpoints. He and Cerf then designed the protocol implementing them.
How it worked
The constraints do the work. Stateless gateways mean any route can be used and failures do not lose connections. No global control means no organisation must approve a new network joining. Best-effort delivery means a network need not guarantee anything it cannot.
What it made possible
Growth without permission. The internet expanded from a few networks to a global system because joining required nothing of anyone else — the same property that let it absorb streaming video, an application nobody designing it in 1974 had in mind.
What happened to him
He founded the Corporation for National Research Initiatives and worked on digital object architecture and persistent identifiers, the basis of the DOI system.
Where the credit landed
Kahn is credited jointly with Cerf and is somewhat the less publicly visible of the two, partly because Cerf has held prominent industry roles. He has a separate page here because the architectural principles are separably his: he set the constraints, and the protocol was designed to satisfy them.
Pro Tips
- Stateless gateways mean failures do not lose connections.
- No global control means new networks join without permission.
- The constraints came first; the protocol was designed to satisfy them.
Knowledge Base
What You'll Learn
The internet's durability comes from what its designers refused to require.
Growth without permission
Compare a broadcast network. Adding a transmitter needs a licence, a frequency allocation and agreement with the incumbent. Adding a network to the internet needs an address block and a peer willing to exchange traffic. That asymmetry explains why internet delivery overtook broadcast delivery so quickly once bandwidth allowed, and why the transition looks less like an upgrade than like a different kind of thing.
Where This Fits
This guide covers one specific part of the history of media technology. The wider picture — how each link in the chain from capture through transmission to display was actually built, who built it, and why the credit so often landed somewhere else — is in A History of Broadcast Technology: The Chain From Capture to Screen, which frames the discipline as a whole and links out to the detailed guides underneath it, including this one. If you are starting from scratch rather than solving a specific problem, read that first and come back here.
FAQ
Q: What is open-architecture networking?
A: The principle that each network joining an internetwork keeps its own internal design, no network controls the others, gateways hold no per-connection state, and delivery is best effort with reliability handled at the endpoints.
Q: What did Kahn do that Cerf did not?
A: Kahn set out the architectural principles and the problem, drawing on his ARPANET and packet radio work; the two then designed the protocol together.