Tutorials Streaming

Robert Kahn: Open Architecture as a Design Principle

By Infinite Creation · Profile
Historical photograph of Robert Kahn.Archival scan, shown at its original size. Image credit & licence

At a Glance

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.

  • Born 1938, United States
  • Anchor year: 1974, the TCP/IP paper
  • Strand: canon

Career

1

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.

2

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.

3

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.

4

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.

5

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.

6

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.

Known For

  • 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.

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

TCP/IP carries almost all media now, the modern transmission link in A History of Broadcast Technology.

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.

Vocabulary

Internetworking. Connecting separately run networks so traffic can pass between them, without any of them having to change internally. The idea that turns many networks into one internet.

Open architecture. A design where no network needs permission or modification to join, because the rules of interconnection are public and minimal. What allowed growth without a central authority approving each addition.

Gateway. A device sitting between two networks and passing traffic across the boundary. Handles the differences between them so neither network needs to understand the other.

Protocol layering. Dividing communication into levels, each using the one below and ignoring its details. Lets a physical medium change without affecting applications, and applications change without affecting the network.

Sources

The paper was checked against its publication record. Checked 20 August 2026.

Translate this page

Machine translation provided by Google Translate, on Google’s servers. We do not check these translations and they will get technical terms wrong. The English page is the authoritative one. Following a link sends this page’s address to Google. Your browser may also offer to translate this page itself, which keeps the request on your device.