# Jon Postel

> 1943–1998 · Computer Scientist
>
> **Recorded contribution:** RFC editor; DNS architecture; SMTP; "be liberal in what you accept" (Postel's law)

## How to use this dossier

Read for a causal chain, not a hero story: inherited problem → contribution → mechanism → downstream capability → limit. Then close the page and complete the reconstruction exercise from memory.

## 1. Historical orientation

Jon Postel (1943–1998) edited the Request for Comments series for decades and administered Internet protocol numbers, names, and eventually the Internet Assigned Numbers Authority at USC's Information Sciences Institute. He authored or edited foundational specifications including IP, TCP, SMTP, and DNS-related documents, but each protocol had other designers and implementation communities. 'Postel's law'—be conservative in what you send and liberal in what you accept—supported interoperability during early growth. Modern security practice recognizes its limit: permissive parsing can create ambiguity, fingerprinting differences, and attacks. Postel's deeper contribution was careful protocol stewardship and a lightweight, openly inspectable standards record.

## 2. The problem inherited

A growing internetwork needed stable protocol specifications and unique shared parameter assignments without a single vendor controlling every implementation.

## 3. The central contribution

Postel maintained the RFC publication and number-assignment commons that allowed independent implementations to converge on shared Internet protocols.

## 4. Reconstruct the mechanism

1. Publish protocol behavior, packet fields, state rules, and open questions as numbered archival documents.
2. Assign unique protocol numbers, ports, and other parameters from shared registries to prevent collisions.
3. Coordinate revisions through implementation experience and community discussion rather than proprietary control.
4. Test independent endpoints against the same specification, tightening validation where ambiguity threatens security or interoperability.

## 5. What changed downstream

- The RFC series became the Internet's durable engineering memory and standards medium.
- IANA registries made decentralized protocol implementation possible without identifier collisions.
- Postel's stewardship shaped a norm of open documentation and rough implementation consensus.

## 6. Attribution, limits, and uncertainty

- TCP/IP, SMTP, and DNS were collaborative; editing or authoring an RFC does not imply sole protocol invention.
- Postel's law can be unsafe when recipients interpret malformed inputs differently; strict canonical formats are often preferable.
- Early informal governance did not solve later global legitimacy, accountability, naming, and jurisdiction questions.

## 7. Reconstruction lab

Read one short RFC and implement a two-party parser from its grammar. Give both implementations ten malformed cases, compare disagreements, and revise the protocol to choose either strict rejection or one canonical recovery behavior.

## 8. Evidence trail

- [Jon Postel](https://www.internethalloffame.org/inductee/jon-postel/) — Internet Hall of Fame
- [RFC 1122: Requirements for Internet Hosts](https://www.rfc-editor.org/rfc/rfc1122) — Internet Engineering Task Force

---

*Research checked 2026-08-09. Dates, roles, and claims about living people are historical snapshots. Linked sources remain the authority; this dossier is original instructional synthesis.*