History of the Internet

Borrowed Bytes: How DHCP Reused Its Boot Fields

A thirteen-byte filename could be too large—not for a DHCP message, and not for an option, but for the space left in one field. Reusing old boot fields solved one shortage. Reassembling the pieces in an agreed order solved another. The distinction made a small extension into a lasting parser obligation.

Two Queries, Two Servers: Why DNS Needed NSID

A service address can stay the same while the machine answering changes. DNS needed a way to identify the instance behind a particular reply, not merely whichever instance answered the next question. The resulting standard made the association precise while leaving the identity deliberately opaque.

Random Bit That Congestion Erased: The ECN Nonce Experiment

The Random Bit That Congestion Erased: The ECN Nonce Experiment

An experiment can work and still lose its claim on shared protocol space. ECN Nonce made a receiver's congestion report testable by exploiting information a router had destroyed. Its withdrawal illuminates both the limits of that test and the cost of keeping an experiment alive on paper.

Name That Entered Through Port One: TCPMUX and the Scope of Coordination

The Name That Entered Through Port One: TCPMUX and the Scope of Coordination

A two-page proposal from 1988 let a new service borrow a common entrance instead of acquiring its own official TCP port. The interesting question was not whether numbers disappeared, but which decisions could now remain inside the host.

Bit That Could Not Keep a Service Running: Why DNS WKS Never Became a Live Directory

The Bit That Could Not Keep a Service Running: Why DNS WKS Never Became a Live Directory

Before opening a connection, an early Internet mailer could inspect one bit in DNS and decide whether a server existed. The bit was exact. The world behind it was not.

Answer That Could Only Name What One Server Knew: Why DNS Retired IQUERY

The Answer That Could Only Name What One Server Knew: Why DNS Retired IQUERY

A DNS request once arrived with no question at all. Instead, it placed a resource record in the Answer section and asked the server to supply every name that matched it. The reversal looked elegant on paper: if an ordinary query mapped a name to a value, an inverse query would map the value back to names. But DNS had distributed its authority by names, not by every possible value stored beneath them. IQUERY could search one server’s memory; it could never establish that the server was the right place to ask or that its list was complete.

Reply That Could Not Say Which Packet Arrived: How Karn’s Algorithm Taught TCP to Refuse a Measurement

The Reply That Could Not Say Which Packet Arrived: How Karn’s Algorithm Taught TCP to Refuse a Measurement

A sender transmits one TCP segment, waits, and sends the same sequence space again after its timer expires. An acknowledgment then advances. Delivery has become visible, but causation has not: the ACK carries no label saying whether the first transmission was merely slow or the second one succeeded quickly. Karn’s algorithm turned that missing label into a discipline. TCP would rather lose a timing sample than let an unprovable sample teach its retransmission clock.

Mask That Silence Guessed Wrong: How ICMP Bootstrapped a Subnet

The Mask That Silence Guessed Wrong: How ICMP Bootstrapped a Subnet

A host wakes with an IPv4 address but no rule for deciding which destinations are on its own wire. It broadcasts a question: what mask divides this address into network, subnet and host? Nothing answers. The old specification permits a conservative guess—the unsubnetted mask implied by the address class—but warns that the mask may be wrong because every agent could merely be down. The repair arrives later as an unsolicited broadcast from an explicitly authorized agent. This nearly forgotten exchange made a sharp distinction that remains useful: silence can justify a reversible operating choice, while authority to publish configuration must come from somewhere else.

Label a Firewall Could Not Safely Erase: IPv4's Security Option in Closed Networks

The Label a Firewall Could Not Safely Erase: IPv4's Security Option in Closed Networks

A firewall sees an unfamiliar security option and removes it. The packet now looks simpler, but it may be less safe. In a network that uses IPv4 sensitivity labels, the receiver can reject the unlabelled packet—or attach an implicit label that is too high or too low. Type 130 survived not because the public Internet embraced classified traffic, but because a device cannot infer from four header bits whether it stands on the open Internet or inside a closed multi-level-secure system. Sometimes the safest default is to preserve a label one does not understand.

Token That Proved a Reply Had a Path Back: DNS Cookies Without Identity

The Token That Proved a Reply Had a Path Back: DNS Cookies Without Identity

A small EDNS option changed what a DNS server could reasonably infer from a UDP source address. It did not identify the sender. It showed, more narrowly and more usefully, that someone at that apparent address had received an earlier reply and returned a server-made token.

Test That Succeeded by Saying Nothing: What Discard Could Actually Prove

The Test That Succeeded by Saying Nothing: What Discard Could Actually Prove

An engineer sends a known stream to port 9 and waits for confirmation. None arrives. That is not an omitted feature: RFC 863 requires the Discard service to throw the data away and send no response. The test can still be useful, but only if its operator names which layer produced the evidence—and refuses to turn correct silence into a receipt the protocol never issued.

Clock Answer with No Grammar: Why Daytime Was for People, Not Programs

The Clock Answer with No Grammar: Why Daytime Was for People, Not Programs

A client connects to port 13 and receives a perfectly valid answer. Another host returns the same moment in a different order, with a different year width and another kind of timezone label. Both exchanges succeeded. RFC 867 promised a readable clock line, not a grammar that software could safely turn back into time.

One-for-One Replies That Never Stopped: How Echo and Chargen Formed a Network Loop

The One-for-One Replies That Never Stopped: How Echo and Chargen Formed a Network Loop

The sender can vanish after the first datagram. One machine receives a packet and generates characters for the address named as its source. A second receives those characters and echoes them back. From then on, each reply is the other service's request. Nothing in either one-for-one rule says when the pair must stop.

Null Byte That Made Return Unambiguous: How Telnet Distinguished a New Line from a Carriage Return

The Null Byte That Made Return Unambiguous: How Telnet Distinguished a New Line from a Carriage Return

A print head has reached column forty when the network sends carriage return. Should it move to the left edge of the same line, or is a line feed about to move it down as well? Telnet refused to make the receiver guess. The next byte carried the distinction: `LF` meant new line; `NUL` meant carriage return alone.

Server That Changed Jobs Mid-Connection: How NNTP Made Roles Explicit

The Server That Changed Jobs Mid-Connection: How NNTP Made Roles Explicit

One NNTP connection can begin by offering peer-to-peer article transfer and, after two words from the client, present itself as a reading service. The socket has not moved. The server’s authority has. `MODE READER` made that change visible—and made stale assumptions dangerous.

Retraction That Had to Travel as News: How Usenet Made Cancellation a Local Decision

The Retraction That Had to Travel as News: How Usenet Made Cancellation a Local Decision

One cancel article reaches three news servers. The first already holds the named post and withdraws it. The second rejects the request under local policy. The third has not yet seen the post, so it remembers the Message-ID and refuses the late arrival. Nothing in that sequence resembles a central recall button. Usenet carried a request; each site supplied the authority.

Delete That Waited for Goodbye: How POP3 Separated a Mark from an Irreversible Removal

The Delete That Waited for Goodbye: How POP3 Separated a Mark from an Irreversible Removal

The server answers `+OK message 4 deleted`. Then the cable comes out before the client says `QUIT`. On the next connection, message 4 is back. POP3 did not contradict itself: the positive reply had accepted a reversible mark inside one session, while actual removal belonged to a later state that the broken connection never reached.

Bytes That Had to Wait for Permission: How IMAP Literals Traded a Round Trip for a Resource Boundary

The Bytes That Had to Wait for Permission: How IMAP Literals Traded a Round Trip for a Resource Boundary

An IMAP client could finish a line with `{11}`, announce exactly how much data came next—and then stop. The eleven octets were not late, lost or flow-controlled by TCP. They were waiting for a one-character reply from the server: `+`. That pause turned a count into a permission boundary. When LITERAL+ removed the pause, it saved a network turn but also changed who paid for bytes the server might not want.

Checkpoint That Was Not a Byte Number: How FTP Learned to Resume a File

The Checkpoint That Was Not a Byte Number: How FTP Learned to Resume a File

Midway through an FTP transfer, a reply could appear on the control connection: `110 MARK ssss = rrrr`. It did not say that a certain number of bytes had arrived. It joined one position understood by the sending system to another position understood by the receiving system—and the data was not supposed to stop while the reply travelled. Long before “resume download” became a button, FTP treated recovery as a problem of preserving two local meanings at one committed boundary.

Empty Query That Listed Everyone: How Finger Made Human Presence a Network Reply

The Empty Query That Listed Everyone: How Finger Made Human Presence a Network Reply

Send no name, no password and no command word—only a carriage return and line feed—to a remote service on port 79. In the original Finger protocol, that empty line asked the host to list everyone currently using it. The exchange was tiny. The disclosure could include a room, terminal, idle time, phone number or a message written by the user. Finger's later history is the story of learning that a shared place to ask was not a shared right to know.