History of the Internet

Ned Freed and the Filename That Had to Be Reassembled Before It Could Be Distrusted

RFC 2231 let a long internationalised MIME parameter travel as numbered pieces. A receiver has to reconstruct the pieces in order before decoding them—but a valid result is still content-disposition metadata, not a safe pathname, an identity claim or permission to act.

Version Number Promised the Next Message, Not This One: RFC 2068

The Version Number Promised the Next Message, Not This One: RFC 2068

In January 1997, an HTTP message that began with `HTTP/1.1` was making a carefully bounded promise. The label described the sender’s message format and the highest HTTP capability it could support in further communication. It did not say which HTTP/1.1 features this particular message had exercised, and it did not travel unchanged through every proxy to become an end-to-end receipt.

Address Was Easy to Read. It Was Not the Address on the Wire: RFC 2155

The Address Was Easy to Read. It Was Not the Address on the Wire: RFC 2155

RFC 2155 gave an APPN management console a human-readable data-link address while warning that the value was for display only. The actual bytes in the DLC header belonged to another evidence source. That small boundary still matters whenever an operator mistakes a legible label, a populated row or a familiar node name for proof of live network identity.

RFC 2067: The Standard Deleted Three Legal Packet Shapes

In 1997, Internet engineers advanced IP over HIPPI by making the specification smaller. Three packet forms allowed by RFC 1374 disappeared: a short burst could no longer come first, the D1 area could no longer contain fill, and the D2 offset could no longer be nonzero. RFC 2067 said implementations in use did not exercise those freedoms. It also confined its interoperability promise to one compliant switch or a simple point-to-point link. Running code justified subtraction; topology limited the claim.

Signature Knew Who Spoke. It Could Not Know Whether the Link Was Real: RFC 2154

The Signature Knew Who Spoke. It Could Not Know Whether the Link Was Real: RFC 2154

RFC 2154 let an OSPF advertisement carry its origin evidence through every flooding hop. That was a remarkable change from trusting only the neighbour that handed over the packet. Yet the RFC drew its own harder boundary: a router could sign a false metric, a dead link or a nonexistent stub route perfectly.

Ward Christensen and the 128-Byte Agreement That Left the Ends Free

XMODEM became useful by declining to become a platform. Ward Christensen put a small, deterministic agreement on the line, then left almost every other decision—dialling, storage, filenames, interface and improvement—to the computers and people at either end.

RFC 2066: The Character Set Was Already Right. The Reply Still Had to Arrive

Telnet had a rule for avoiding endless politeness: do not acknowledge a request for a mode already in effect. RFC 2066 made a narrow but consequential exception. A receiver already using one of the proposed character sets still had to send `ACCEPTED`, because silence would force the requester to guess by timeout. When both sides requested a change at once, the protocol made the server reject and the client answer. Determinacy came from an explicit receipt and a deliberately asymmetric tie-breaker.

Namespace Arrived. Understanding Did Not: RFC 2153

The Namespace Arrived. Understanding Did Not: RFC 2153

RFC 2153 gave proprietary PPP extensions a shared outer address: Code or Type 0, an OUI, a Kind and vendor-defined values. That prevented private meanings from colliding in the public fields. It did not make those meanings public, prove that a peer understood them, or turn receipt into permission and interoperability.

RFC 2065: The DNS Reply Crossed an Ordinary Server. Its Signature Carried the Trust

In January 1997, RFC 2065 proposed a security upgrade that did not require every machine carrying a DNS answer to become its judge. A security-aware resolver could retrieve signed records through a server that knew little about the new machinery and verify the evidence itself. The document’s restraint was as important as its cryptography: it authenticated public DNS data, while leaving secrecy and access control to other systems.

Text Looked Readable. The Gateway Still Had Choices: RFC 2152

The Text Looked Readable. The Gateway Still Had Choices: RFC 2152

UTF-7 let a 1997 mail reader leave much of an ASCII message in plain sight while carrying the rest of Unicode through a seven-bit channel. That readability was useful, but it was never a preservation receipt: punctuation could take more than one legal route, shifted text could not cross a line, and a decoder could recover characters without recovering the bytes or editorial choices that arrived at the gateway.

Server Stopped Speaking It. The Client Still Had to Understand: RFC 2062

The Server Stopped Speaking It. The Client Still Had to Understand: RFC 2062

In December 1996, IMAP drew a line that software migrations still struggle to express. A new server could retire an old command without demanding that every client forget how to read it. RFC 2062 made compatibility directional: stop producing obsolete syntax, keep only the receiving tolerance needed to drain the installed past.

Reply Was an Observation, Not Authority: RFC 2151 and the Limits of Diagnostic Tools

The Reply Was an Observation, Not Authority: RFC 2151 and the Limits of Diagnostic Tools

RFC 2151 put an Internet laboratory on an ordinary user's desk. Its commands made names, round trips, intermediate routers and remote services visible, but the very clarity of their output invited a category error: a tool could report what answered without acquiring authority to say what the whole system was.

Dina Katabi and the Feedback Field That Was Not a Bandwidth Grant

A packet leaves its sender asking to increase the flow by a certain amount. The first router accepts the request; the second writes a smaller number; the receiver sends that surviving value back. XCP turned congestion control into an explicit negotiation, but the number in its header was deliberately narrower than a promise of bandwidth.

RFC 2150 and the Long Walk from a URL to Centre Stage

A cultural work could be scanned, uploaded and assigned a URL while remaining far from the institutions that determined how it would be described, funded, preserved, taught and heard. RFC 2150 captured both the Internet’s remarkable power to carry culture and the larger stack of authority that carriage alone could not supply.

Stephen Casner and the Timestamp That Was Not a Clock

Two packets leave in sequence and carry the same timestamp. That looks like a broken clock only if the number is asked to describe transmission. In RTP, the two packets may simply be fragments of one video frame. Stephen Casner and his coauthors made that distinction part of the protocol: packet order, media position and common time are different facts.

Sharon Goldberg and the Packet That Told a Clock to Stop Asking

The dangerous packet was not large, fast or obviously hostile. It looked like a time server asking a client to back away. In the `ntpd` versions studied by Sharon Goldberg and three collaborators, that courtesy message could be forged—and its requested silence could last far longer than the exchange that supposedly justified it.

Anja Feldmann and the Traffic Matrix No Single Link Could Reveal

A red link on a network map looks like an answer: this is where the load is. For Anja Feldmann and her collaborators, it was only the start of the question. The counter could not say which demands had converged there, which routing decisions had brought them together, or where the traffic would move after a configuration change.

Jerry Saltzer and the Link That Carried a Name but No Permission

A path can tell a computer where a file is without answering whether the person following it may read the file. Jerry Saltzer’s account of protection in Multics turned that separation into an operating rule—and exposed how much revocation, audit and institutional power can be hidden inside a seemingly convenient link.

Eve Schooler and the Invitation That Did Not Carry the Conversation

The most consequential line in an Internet call is not the one carrying a voice. It is the one that finds the other person, proposes a session and then gets out of the way. Eve Schooler’s path from experimental conference control to the early Session Initiation Protocol helps explain why that separation became a durable source of both freedom and power.

Lixia Zhang and the Data Packet That Did Not Need Its Original Server

The revealing moment in Named Data Networking is not when a packet reaches a machine. It is when an Interest is answered by a copy found somewhere else—and the receiver can still ask who signed the data, whether that key was entitled to sign this name, and whether a fresher version is required. Lixia Zhang helped turn that separation into an Internet architecture research programme.