David Clark

What they built

Chief Protocol Architect for the Internet from 1981 to 1989, shaping the IETF's early culture and the end-to-end architectural philosophy. At MIT CSAIL he has led the NewArch project, the "tussle in cyberspace" line of work, and ongoing research on network security, economic design, and alternative Internet architectures. Author of Designing an Internet (MIT Press, 2018).

In their own words

• "We reject: kings, presidents, and voting. We believe in: rough consensus and running code." — IETF plenary, "A Cloudy Crystal Ball: Visions of the Future," July 1992. This was a critique of top-down standards bodies (notably OSI), not a general motto; the context was an OSI-vs-Internet standards war where IETF's informality was on trial.
• "Networks and distributed systems … are composed of elements whose interests are not necessarily aligned." — Designing an Internet, 2018 (quoted in Internet Governance Project review)
• "Most of the communication on the Internet would be between parties who were prepared to communicate but did not know whether to trust each other." — Designing an Internet, on the original trust-model blind spot
• "Saving one round trip in the case of a setup packet … is not justified if the result forces a complex mechanism into the network architecture that could otherwise be separated and performed in the larger ecosystem." — Designing an Internet, on the end-to-end argument as economic discipline, not just engineering taste

Principles as they articulated them

• End-to-end as a default, not a dogma. The network stays minimal so function can move to the ecosystem that needs it. But he has walked this back over the years: when requirements can only be met in the core (e.g., some security properties), the end-to-end principle must yield.
• Tussle is the organizing frame. Design does not solve social conflict; it "tilts the playing field." His advice to architects is to design for tussle to be visible and negotiable, not to try to engineer it out.
• Trust is the unsolved primitive. The original Internet assumed mutual trust between communicating endpoints. Nearly all present-day problems (spam, DDoS, misinformation) trace to that assumption failing.
• There is no single correct Internet. Designing an Internet is built around the counterfactual of alternative architectures, each optimizing different values — a rebuke to "the Internet is what it had to be" narratives.

What surprised me in research

• Clark is far less famous than Cerf or Berners-Lee but was arguably the cultural architect of the IETF. The "rough consensus" line was a political move in a standards war, not a general aphorism, and it worked.
• Designing an Internet (2018) is unusually candid for an insider: he enumerates what the original team got wrong (trust), what they got accidentally right (separating control from data), and what is actively still wrong (economic sustainability of security investments).
• He rejects the "redesign would fix it" framing that many in the clean-slate community hold. His position: "a redesigned Internet cannot engineer away social problems." This puts him at odds with some of his own NewArch collaborators.
• His "tussle in cyberspace" framework (co-authored with Wroclawski, Sollins, Braden, 2002) is one of the earliest explicit treatments of network architecture as political economy rather than pure engineering.

Recent or later work

• Senior Research Scientist at MIT CSAIL; continues to lead the Advanced Network Architecture (ANA) group.
• Designing an Internet (MIT Press, 2018; paperback 2024) — his mature synthesis. The book is a counterfactual: "what other Internets could we have built, and what would they have optimized?"
• Ongoing work on Internet economics, measurement, and the relationship between architecture and policy. Co-authored reports on cybersecurity and Internet governance for NSF and the Internet Society.
• Continues to publish on requirements for a future Internet, but his emphasis has shifted from architectural purity to the interplay of architecture, economics, and governance.

Sources

• https://mitpress.mit.edu/9780262547703/designing-an-internet/ — Designing an Internet — mitpress.mit.edu
• https://www.internetgovernance.org/2018/12/05/clarks-designing-an-internet-a-review/ — Clark's "Designing an Internet" — A Review — internetgovernance.org
• https://groups.csail.mit.edu/ana/People/DDC/future_ietf_92.pdf — A Cloudy Crystal Ball: Visions of the Future (IETF 1992) — csail.mit.edu
• https://courses.cs.duke.edu/common/compsci092/papers/govern/consensus.pdf — 'Rough Consensus and Running Code' and the Internet-OSI Standards War — cs.duke.edu
• https://en.wikipedia.org/wiki/David_D._Clark — David D. Clark — wikipedia.org
• https://dspace.mit.edu/handle/1721.1/141605 — Designing an Internet (MIT DSpace) — dspace.mit.edu