History of the Internet

Exit That Was Also a Delete: Why IMAP Needed UNSELECT

The Exit That Was Also a Delete: Why IMAP Needed UNSELECT

A mail client wanted to release one open mailbox. The most obvious command would also erase every message already marked for deletion. IMAP's later `UNSELECT` extension separated an ordinary state transition from an irreversible act.

Date That Could Not Reserve Disk: How Expires Let Usenet Separate Relevance from Retention

The Date That Could Not Reserve Disk: How Expires Let Usenet Separate Relevance from Retention

An article can carry a precise date and still make no promise about how long it will remain available. Usenet's `Expires` field let a poster say when a notice would stop being useful. The disks, deletion rules and archive exceptions remained under each serving site's control. The date travelled; the storage authority did not.

Session Ticket Could Not Remember the Protocol

The Session Ticket Could Not Remember the Protocol

A resumed TLS connection could reuse evidence from an earlier cryptographic session, but it could not inherit the grammar spoken over the old wire. ALPN made application-protocol choice a fresh, bounded decision: the client named what it could accept, the server chose one common protocol, and the new connection either acquired that meaning or ended before application bytes could be misunderstood.

Border That Could Not Live in a Header: How Distribution Scoped Usenet Without Making It Private

The Border That Could Not Live in a Header: How Distribution Scoped Usenet Without Making It Private

Usenet could carry a request for an article to remain local, national or organizational. It could not carry the border itself. That boundary existed in the agreements between relays, the names each site recognized and the gateways an operator controlled. `Distribution` was valuable because it made a desired scope visible; it was dangerous when visibility was mistaken for enforcement.

Second Date That Refused to Replace the First: How Injection-Date Separated Writing from Entry

The Second Date That Refused to Replace the First: How Injection-Date Separated Writing from Entry

A Netnews article could be finished on Monday, wait on a disconnected machine, and enter the network on Friday. One clock described when the writer declared the text ready; another was needed to decide whether the network was seeing fresh traffic or an old duplicate. The design became reliable only when it stopped asking one date to answer both questions.

Timeout That Could Speak Only After Fragment Zero

The Timeout That Could Speak Only After Fragment Zero

The receiver had pieces of the datagram, an identity for the unfinished whole and a timer measuring how long its memory would remain committed. What it did not have was the beginning. When the timer expired, IPv4 required the state to disappear; whether the failure could speak back to the sender depended on one missing piece whose offset was zero.

Number That Meant Somewhere, Not Something: How Xref Made Usenet Location Local

The Number That Meant Somewhere, Not Something: How Xref Made Usenet Location Local

One Usenet article could sit at a different number in every group and on every server. Xref turned that apparent contradiction into useful metadata: keep the article's identity global, but let each server publish its own filing coordinates.

Filename the Sender Was Not Allowed to Choose

The Filename the Sender Was Not Allowed to Choose

FTP’s `STOU` command made a remote server allocate a collision-free pathname and report it before transfer, turning one line of reply text into a narrow receipt for a naming decision—not proof that the upload finished, remained stored, or belonged to anyone.

List That Was Not Its Address: How List-Id Gave Mailing Lists a Stable Name

The List That Was Not Its Address: How List-Id Gave Mailing Lists a Stable Name

When a mailing list changed processors, the place used to submit a message could move while the community stayed put. List-Id turned that mismatch into a design rule: give the list one durable name, then keep routing, actions and authentication under separate authority.

Route the Relay Was Told to Forget: How SMTP Kept Source-Route Syntax After Removing Its Authority

The Route the Relay Was Told to Forget: How SMTP Kept Source-Route Syntax After Removing Its Authority

An old SMTP recipient can still arrive carrying a list of relays before the mailbox. A modern server must understand the form, yet it need not follow the list. That apparent contradiction records a deliberate transition: compatibility preserved the grammar after normal control of the route had moved elsewhere.

New Address That Was Not a Rename: How SMTP Split Forwarding from Referral

The New Address That Was Not a Rename: How SMTP Split Forwarding from Referral

Two mail servers can know exactly the same thing—that a mailbox has moved—and still owe the sender opposite answers. SMTP encoded the difference in `251` and `551`: one server accepted responsibility and forwarded; the other refused the old recipient and left the next attempt to the sender. The new address was evidence, not a command to rewrite identity everywhere.

Repairing the Instrument Did Not Replay the Performance

RTP MIDI gave a receiver enough history to correct a note that would not end, without promising to replay every note that had gone missing. Its recovery journal drew a useful boundary for the real-time Internet: the state of a performance could be repaired, but the time in which it should have happened could not be returned.

Offset That Could Not Name the File: How FTP Restart Assumed an Unchanged Object

The Offset That Could Not Name the File: How FTP Restart Assumed an Unchanged Object

After a large transfer breaks, a saved number feels like proof of progress. FTP could use that number to avoid sending the beginning again. But the number named a position, not the file version occupying that position. Resume worked only because both endpoints supplied an identity promise that `REST` itself never made.

Name the Message Had to Mint Itself: How Message-ID Worked Without a Registry

The Name the Message Had to Mint Itself: How Message-ID Worked Without a Registry

A relay can add a trace field and change a message’s bytes without changing the message. An author can revise one sentence and create a new message even while most bytes remain. `Message-ID` gave that distinction a durable name, then let replies and distributed news servers build state around it without consulting a central allocator.

A Return Label Was Not a Shared Instruction

A RADIUS proxy could carry another proxy's private state without knowing what it meant. The common agreement concerned preservation, relative order and return, not a universal interpretation of every value. That small distinction left room for independent implementations while exposing how little a successful handoff could prove about the whole chain.

A Reservation Could Survive Without Being Rechecked

RSVP learned to keep previously advertised state alive by naming it instead of repeating its description. That reduced routine work, but changed what the routine could discover. A missing record could ask for repair; a recognisable record with the wrong contents was a different problem.

Reply SMTP Could Not Divide: How LMTP Made Local Delivery Per-Recipient

The Reply SMTP Could Not Divide: How LMTP Made Local Delivery Per-Recipient

One message reaches the local-delivery boundary with two accepted recipients. One mailbox can take it; the other is temporarily over quota. SMTP has one final answer for that transaction, so the receiver must own what happens next. LMTP changed the shape of the answer: one ordered verdict for each accepted recipient, allowing the queue to remain where retry state already lived.

Knock That Brought the Client Back

The Knock That Brought the Client Back

A DHCP server could know that a setting should change while its client had no reason to ask again. FORCERENEW gave the server an opening in that quiet interval. It did not give the opening message the power to complete the change.

Philip F. Smith and the Routing Report That Could Observe, Not Command

A daily BGP report begun in 1999 made routing behaviour public at a moment when registry records and operator claims could not show what the network was actually announcing. Philip F. Smith’s long-running instrument matters because it also exposes its own limits: a selected path from a named viewpoint can discipline an argument, but it cannot become a licence to govern somebody else’s router.

Link the Origin Asked to Remove: Why HTTP 410 Was Not 404

The Link the Origin Asked to Remove: Why HTTP 410 Was Not 404

Two dead-looking links can lead to the same empty browser view while making very different claims. HTTP 404 leaves the reason and duration unresolved. HTTP 410 lets an origin say that access ended deliberately, is likely to stay ended, and should change how the rest of the Web maintains its references.