History of the Internet

Acknowledgment That Learned to Point: How TCP SACK Made Loss Visible

The Acknowledgment That Learned to Point: How TCP SACK Made Loss Visible

TCP's original acknowledgment could certify an unbroken prefix of a byte stream, but it could not describe the islands waiting beyond the first gap. Selective acknowledgment added a small map of those islands while leaving the sender—not the receiver—in charge of repair.

Router That Pointed Sideways: How ICMP Redirect Stayed Local

The Router That Pointed Sideways: How ICMP Redirect Stayed Local

ICMP Redirect let a gateway reveal a better local next hop without becoming a routing authority. Its power ended at the host that had just used it.

Number That Became Newer After Zero: How DNS Ordered Versions Without a Clock

The Number That Became Newer After Zero: How DNS Ordered Versions Without a Clock

At the edge of a 32-bit counter, DNS asks operators to accept an apparent impossibility: zero may be newer than 4,294,967,295. That rule let independent name servers agree on version order without sharing a clock, but only inside a deliberately bounded window.

Zone That Knocked: How DNS NOTIFY and IXFR Cut Staleness

The Zone That Knocked: How DNS NOTIFY and IXFR Cut Staleness

DNS once made every secondary wait before learning its authority was stale. In 1996, NOTIFY delivered the knock and IXFR carried only the edit.

Address You Needed DNS to Find: How Glue Broke the Delegation Loop

The Address You Needed DNS to Find: How Glue Broke the Delegation Loop

A DNS referral can name the server that knows the answer and still leave a resolver unable to reach it. Glue was the small, deliberately non-authoritative exception that let the resolver cross that gap without giving the parent zone control over the child's facts.

Address That Asked the Wire: How ARP Made Local Reachability Revisable

The Address That Asked the Wire: How ARP Made Local Reachability Revisable

Routing can choose the next IP address without knowing how to put a frame on the local cable. ARP filled that last gap with a public question, a private answer, and a memory designed to be corrected.

Connection That Had to Prove It Was New: Why TCP Needed a Three-Way Handshake

The Connection That Had to Prove It Was New: Why TCP Needed a Three-Way Handshake

A packet can arrive at the right address, carry a plausible number and still belong to a conversation that has already died. TCP's familiar opening exchange was designed around that ambiguity: before accepting a new connection, both endpoints must show that they have seen each other's current sequence space.

Packet That Had to Learn Its Size: How Path MTU Discovery Moved Fragmentation to the Edge

The Packet That Had to Learn Its Size: How Path MTU Discovery Moved Fragmentation to the Edge

A packet may cross a path whose narrowest link is invisible to its sender. The Internet spent four decades changing who should discover that limit, who should report it and who should decide what size to send next.

Two Kinds of Nothing: How DNS Learned to Separate NXDOMAIN from NODATA

An empty DNS answer can conceal two opposite realities: the requested name may be absent altogether, or it may be alive and carrying every record except the one requested. The Internet had to make that difference portable, cacheable and temporary before saving queries could stop meaning erasing data.

Error That Learned to Expire: How DNS Cached What Did Not Exist

The Error That Learned to Expire: How DNS Cached What Did Not Exist

The expensive DNS question is not always the one with a large answer. It may be the miss that thousands of resolvers repeat because nothing can be stored. Negative caching gave absence a scope, evidence and an expiry time—then forced operators to accept that a newly created name could remain invisible until yesterday’s “nothing” died.

Core That Had to Stop Being the Core: EGP and the Invention of Autonomous Systems

The Core That Had to Stop Being the Core: EGP and the Invention of Autonomous Systems

The early Internet did not decentralize by pretending that every network agreed. It learned to survive disagreement. The Exterior Gateway Protocol drew a boundary around what one routing administration could keep private and what it had to tell its neighbours. That boundary made autonomy practical, but EGP’s privileged core and thin evidence could not carry a meshed Internet. The machinery built around its omissions—and the AS path that followed—shows how a federation replaces a centre without replacing responsibility.

Mail Address That Outlived Its Server: How MX Records Separated Identity from Delivery

The Mail Address That Outlived Its Server: How MX Records Separated Identity from Delivery

An email address looks like a destination. In the early Internet, it often was: a mailer could take the domain after `@`, open SMTP to the machine with that name and hope the mailbox lived there. In January 1986, RFC 974 described why that assumption had stopped scaling—and how one small DNS record let the address remain while the receiving machine moved.

Clock Built from Disagreement: How NTP Made Internet Time Without Trusting One Server

The Clock Built from Disagreement: How NTP Made Internet Time Without Trusting One Server

In 1989, an Internet-wide experiment found clocks wrong by minutes, hours and, in a few cases, weeks. The problem was not a shortage of machines willing to state the time. It was deciding which statements deserved to move a local clock when packets, oscillators and operators could all be wrong.

Web CERN Chose Not to Own: How a Laboratory Designed Its Own Exit

The Web CERN Chose Not to Own: How a Laboratory Designed Its Own Exit

The World Wide Web did not become universal merely because it was invented at a famous laboratory. It became portable across institutions because its common machinery was kept small, its specifications were public, its clients escaped one workstation, and CERN eventually removed its intellectual-property claim over the executable seed. The decisive achievement was not permanent stewardship. It was an originator making its own permission unnecessary.

Network That Let Institutions Join Unequally: CSNET and the Architecture of Partial Access

The Network That Let Institutions Join Unequally: CSNET and the Architecture of Partial Access

CSNET widened the networked research community without pretending that every institution could afford or operate the same connection. By combining ARPANET access, full Internet service over commercial X.25, and dial-up PhoneNet mail, it showed that interoperability could begin with an honest minimum service—and that a lower-cost doorway mattered only if identities, messages and future upgrades could cross the boundary.

Map Made from Expired Packets: How Traceroute Turned Failure into Internet Evidence

The Map Made from Expired Packets: How Traceroute Turned Failure into Internet Evidence

In December 1988, Van Jacobson was not trying to draw the Internet. He was trying to find out where his packets had gone. The tool he assembled at Lawrence Berkeley Laboratory made the network answer indirectly: send a packet designed to expire, listen for the complaint, then let the next packet live one hop longer.

Day the Old Protocol Lost Its Network: The 1983 TCP/IP Cutover and the Limits of Technical Authority

The Day the Old Protocol Lost Its Network: The 1983 TCP/IP Cutover and the Limits of Technical Authority

On 1 January 1983, an ARPANET host that still depended on NCP faced a new fact: the network beneath it could stop servicing the old protocol. The famous cutover mattered not because a memo became universal law, but because a disclosed rule reached an execution boundary whose operator could enforce it—and whose sponsor had to absorb the consequences.

Where the Network Stopped: The IMP, the Host, and the First Price of Shared Correctness

ARPANET’s Interface Message Processor made packet switching operational by putting substantial machinery into a dedicated subnet. It also made a harder problem visible: infrastructure can carry, check, meter and protect communication without possessing the knowledge required to make communication correct. The Internet emerged when designers learned to preserve that distinction across networks—and to keep authority from expanding farther than the function actually delivered.

When One Router Announced Everyone’s Network: AS7007 and the Failure of Unchecked Trust

On 25 April 1997, one border router began presenting thousands of other networks as if they originated behind AS7007. The disruption exposed an Internet held together not by a central routing authority, but by a chain of local acceptance decisions whose limits had too often remained implicit.

When the First Network Became Replaceable: ARPANET’s Retirement and the Internet That Continued

ARPANET did not take the Internet with it when it was retired in 1990. That was not because the pioneering network had become unimportant. It was because its most important function—making unlike networks communicate—had already escaped the machinery and institution that first proved it.