History of the Internet

Susan Eggers and the Core That Learned to Share Its Empty Slots

A wide processor can look powerful on a block diagram while leaving execution units idle whenever one instruction stream runs out of independent work. Susan Eggers and her collaborators asked a sharper question: what if several independent threads could compete for those otherwise wasted slots in the same cycle? Their answer, simultaneous multithreading, changed processor throughput—but its enduring value lies as much in the boundary they measured as in the speedup they reported.

RFC 2169: An HTTP Route Is Not a Resource Authority

In 1997, RFC 2169 made an intentionally modest proposal: use ordinary HTTP requests to ask a resolver about a URN. Its value was not that HTTP could settle identity. It was that a familiar transport could carry a narrowly defined question while leaving authority, access and retrieval to other layers.

Version 3 Stayed. The Service Changed: RFC 2126’s Compatibility Trap

An old peer could return a perfectly parseable Class 0 confirmation to a Class 2 request that offered no alternative. The TCP connection was open, the TPKT version was familiar, and the reply was still unacceptable. RFC 2126 made that difference explicit.

Permission Came Before the Call: RFC 2125’s Two-Stage Bandwidth Decision

Two peers could agree that another line should be tried and still have no new bandwidth. RFC 2125 made that gap explicit: BAP first obtained a response to the proposed action, then a separate Call-Status message reported what happened when somebody actually placed the call.

Irene Greif and the Atomic Commit That Could Not Preserve an Author’s Intent

The Collaborative Editing System made shared document changes serializable and recoverable. Its design also exposed a limit that still matters: a transaction can protect bytes from half-finished change without knowing what a writer meant, whether collaborators noticed, or whose judgment should prevail.

Verdict Left the FAS. The Switch Still Had to Make It Real

The Verdict Left the FAS. The Switch Still Had to Make It Real

RFC 2124 put connection policy in an external service, but it never made the service’s answer identical to the connection that followed. Its message chain preserved a more useful truth: a decision, an execution and an accounting record are different events.

RFC 2123: A Flow Record Was a Rule-Set Projection, Not the Wire

NeTraMet did not preserve traffic as such. Before a packet could become a flow row, a downloaded rule set decided which protocol mattered, which attributes survived, which direction counted as source, and how much detail the meter could afford. RFC 2123 made that editorial machinery visible—and showed why a valid counter still needed its rule version, resource state and collection history.

Gladys West’s 1982 Earth Ellipsoid Was a Geodetic Receipt, Not a GPS Blueprint

When Gladys B. West died on January 17, 2026, Virginia’s General Assembly memorialized a career whose satellite-geodesy work had become shorthand for the foundations of GPS. That shorthand is useful only if its evidentiary limits remain visible. West’s 1982 paper, “Mean Earth ellipsoid determined from SEASAT 1 altimetric observations,” is a strong technical receipt for a particular geodetic estimation problem: a defined set of SEASAT-1 altimetric geoid observations, specific potential-coefficient models, a stated assumption about which geoid was the best available reference, and a minimization procedure used to adjust an ellipsoid. It is not evidence that one numerical solution was copied unchanged into every later GPS receiver, nor that WGS 84, the GPS constellation, its signals, receiver software or modern high-precision positioning can be reduced to one paper or one inventor.

Link Opened a Session, Not an Object: RFC 2122’s VEMMI Boundary

The Link Opened a Session, Not an Object: RFC 2122’s VEMMI Boundary

A `vemmi` hyperlink looked like an address, but its destination was not a file waiting to be fetched. RFC 2122 used the Web as a dispatch surface for a different system: a local client would open a continuing multimedia session, negotiate service and identity, and later decide whether executable objects could run. The link named an entrance. It did not certify what lay beyond it.

Sophie Wilson and the Receipt That Arrived with ARM1 Silicon

When ARM1 returned from fabrication on 26 April 1985, the board was already waiting and much of its software had already run—on models and simulators. The chip's immediate boot was not a miracle of a naturally flawless RISC design. It was the visible receipt for months of architecture, verification, software and physical implementation work, and its meaning stopped well before yield, qualification, volume production or market success.

Root Was a Coordination Shortcut, Not a World Directory: RFC 2120

The Root Was a Coordination Shortcut, Not a World Directory: RFC 2120

X.500 drew a clean Directory Information Tree, but its root carried an awkward human obligation. Every administrator of a first-level Directory System Agent was expected to coordinate with every other one through bilateral agreements or private arrangements outside the standard. RFC 2120 recorded how a working service escaped that expanding mesh with a root DSA—and why replacing its proprietary machinery required three migration tracks rather than a flag-day upgrade.

Reset Was in the Next Packet: RFC 2118’s MPPC Recovery

The Reset Was in the Next Packet: RFC 2118’s MPPC Recovery

RFC 2118 gave Microsoft Point-to-Point Compression a continuous memory and a deliberately spare recovery signal. When packet loss broke that shared history, the receiver asked for a reset—but it was the sender’s next `FLUSHED` data packet, not a separate Reset-Ack, that established the new decoding boundary.

Adele Goldberg and the Contract That Let Smalltalk-80 Travel

The Blue Book turned a live system into a portable agreement: preserve the image, implement the object memory, bytecodes, contexts and primitives, and let unlike machines run the same Smalltalk-80. The agreement made reimplementation possible; it never promised equal speed, fonts, windows, devices or feel.

Join Had No Receipt. The Tree Survived by Refresh: RFC 2117

The Join Had No Receipt. The Tree Survived by Refresh: RFC 2117

RFC 2117 did not build a sparse multicast tree as one transaction. A local membership indication created one record; a Join/Prune refreshed records hop by hop; a source initially reached a rendezvous point inside Register messages; a branch could later move to source-specific state. The protocol scaled because every router could remember just enough, forget stale state, and repair a missed message on the next refresh. That made the tree workable, not globally certain.

Browser Remembered the Session. It Did Not Prove the Person: RFC 2109

The Browser Remembered the Session. It Did Not Prove the Person: RFC 2109

In RFC 2109’s model shop, a server called a browser-held value `Customer="WILE_E_COYOTE"`. Later requests returned that value while separate cookies accumulated for a rocket launcher and a shipping method. The exchange made stateless HTTP remember a sequence. It did not make the label an authenticated person, a fresh instruction or evidence that the order succeeded.

MIB Located the Address. The Repeater Still Had No MAC

The MIB Located the Address. The Repeater Still Had No MAC

A management station could ask which hub port had carried a source address, rank the busiest ports and reconstruct a shared-Ethernet topology. RFC 2108 made those answers comparable without pretending that the repeater itself understood a packet.

Kathleen Booth and the Line Between a Symbol and a Machine Order

In 1947, Kathleen Britten and Andrew Booth described a way to move from a mathematical plan to the exact fields their calculator would obey. The abbreviated notation made that crossing legible. It did not make the machine understand what the calculation meant.

Address Said Home. The Dial-Up Line Said Away: RFC 2107

The Address Said Home. The Dial-Up Line Said Away: RFC 2107

RFC 2107 let a remote dial-in client borrow the routing appearance of home. The illusion depended on a Foreign Agent, a Home Agent, a shared secret, a Tunnel ID and state that had to be created and destroyed in the right order.