History of the Internet

Unknown Attachment Was Not Text: RFC 2049’s Minimum Promise

The Unknown Attachment Was Not Text: RFC 2049’s Minimum Promise

MIME conformance did not mean that a mail program understood every format. In 1996 it meant something smaller and more useful: decode the common transfer forms, preserve the distinction between text and opaque bytes, and retreat predictably when a type was unknown.

Packet Knew Its Place. It Did Not Prove the Picture: RFC 2035’s Reconstruction Boundary

The Packet Knew Its Place. It Did Not Prove the Picture: RFC 2035’s Reconstruction Boundary

RFC 2035 made Motion-JPEG economical on RTP by omitting stable JPEG syntax and repeating only the context needed to rebuild it. Fragment offsets and restart boundaries made damaged frames more tractable, but their evidence ended before decoded integrity, timely playout or a viewer’s experience.

Susan Estrada and the Network That Had to Account for Its Customers

An early Internet provider could prove that packets moved and still leave its customer unable to judge the service. Susan Estrada's work at CERFnet shows why commercial acceptance required another layer: reports, monitoring, support and a shared language for responsibility.

Server Said Why. It Did Not Prove It: RFC 2034 and SMTP’s Diagnostic Boundary

The Server Said Why. It Did Not Prove It: RFC 2034 and SMTP’s Diagnostic Boundary

RFC 2034 gave mail systems a finer vocabulary without asking them to surrender human explanation. Its three-part status token made replies easier to classify across software and languages, but the evidence still stopped at what one server declared during one exchange.

Laura Breeden and the Work Between a Connection and Adoption

An early federal evaluation found Internet projects that had acquired technology before asking what a community needed, leaving systems unused or badly underused. Laura Breeden's career explains why that failure belongs inside Internet history: a network becomes public infrastructure only when institutions can turn availability into sustained, useful access.

Bytes Kept Their Delimiters. Meaning Still Needed Another Contract: RFC 2044

The Bytes Kept Their Delimiters. Meaning Still Needed Another Contract: RFC 2044

UTF-8's first Internet-era promise was not that software had learned every language. It was that multilingual characters could enter systems built around ASCII without hiding an ASCII delimiter inside a multibyte character. RFC 2044 made that promise inspectable at the byte level—and stopped well before collation, normalization, display, identity, security or deployment.

Demi Getschko and the Country Code That Arrived Before Brazil Spoke TCP/IP

On 18 April 1989, `.br` entered the DNS root while Brazilian academic networks were still speaking BITNET, HEPnet and other protocols. Demi Getschko's part in that sequence reveals a neglected infrastructure skill: securing a durable name, accepting responsibility for it and designing its succession before the network it would identify had fully arrived.

One PPP Link, Two SNA Permissions: What RFC 2043's Open State Could Not Prove

A line can be up while the thing an operator cares about is still down. RFC 2043 made that distinction unusually concrete: on one PPP link, SNA with LLC 802.2 and HPR SNA without LLC were admitted by different control protocols. Each could open without speaking for the other, and neither could testify to the fate of an application session.

Next Macroblock Could Start Cleanly. The Picture Was Still Damaged: RFC 2032

The Next Macroblock Could Start Cleanly. The Picture Was Still Damaged: RFC 2032

RFC 2032 gave an H.261 receiver a deliberate place to resume after packet loss and a compact way to ask for corrective action. Neither mechanism certified that the missing picture returned, that prediction state was right, or that a viewer saw an uninterrupted frame.

255 Was a Workshop Tag, Not a Private BGP Namespace: RFC 2042

Two unfinished BGP attributes could both wear the number 255 and still mean entirely different things. That was the point. In RFC 2042, the value marked work under development; public identity began only when an attribute was documented and IANA assigned it a unique code.

Ginny Strazisar and the Gateway Code That Traveled Before the Packets Did

The celebrated packet path began with a less cinematic journey: an engineer arriving at a site where the machine for her software was not yet ready. Virginia “Ginny” Strazisar Travers helped turn internetworking from a protocol idea into installed boundary equipment at BBN, London and Norway. Her record shows that networks become interoperable only when code can meet unfamiliar hardware, expose its failures and survive outside the laboratory that produced it.

Clock at the Edge: RFC 2030 and the Evidence Lost When One Reply Becomes Time

The Clock at the Edge: RFC 2030 and the Evidence Lost When One Reply Becomes Time

RFC 2030 made Internet time small enough for simple devices by preserving the NTP packet while discarding most of the machinery around it. Its warning was architectural: an SNTP client belonged at a leaf, not in the middle of a dependency chain, because one usable reply could set a clock without proving that the source, path or next reply would remain trustworthy.

Server Was Up. The Website Was Not: RFC 2039’s Missing Layer

The Server Was Up. The Website Was Not: RFC 2039’s Missing Layer

In 1996, one short RFC identified a management error that survives every change of tooling: a machine can be measurable, orderly and alive while the service it is meant to provide is failing somewhere else.

Karen Sollins and the Delayed ACK That Made Every Packet Appear Twice

TFTP could deliver a file correctly and still damage the network carrying it. In the failure later called the Sorcerer’s Apprentice syndrome, one delayed acknowledgement could start a feedback loop in which every remaining data block and acknowledgement travelled twice. Karen Sollins’s successive TFTP specifications preserve a sharper lesson than “retransmit when uncertain”: recovery must be designed so that an old message cannot manufacture new work.

Eight Bytes Drew a Recovery Boundary: RFC 2029 and CellB After Packet Loss

RFC 2029 gave every CellB packet its own spatial address: the first 4×4 cell’s coordinates and the image dimensions. That small repeated header let a receiver resume at a known place after loss, but it did not replace the missing cells or prove that the resulting frame was complete, correct or ever displayed.

One Agent, Many Machines: RFC 2037 Put the Scope Back into the Name

RFC 2037 treated an index as a local coordinate, not a universal identity: the agent, naming scope and mapping path had to travel with the number.

Elise Gerich and the Backbone Shutdown That Needed a Dress Rehearsal

The NSFNET backbone did not disappear when someone threw a master switch. Its retirement was a year-long exercise in proving that exchange points, commercial providers, route servers, databases and regional networks could stand without the system they were replacing. Elise Gerich’s role makes the episode a study in how infrastructure leaders turn a public deadline into a sequence of reversible tests and, only then, irreversible decisions.

Mary Ann Horton and the Dial-Up Network That Had to Publish Its Own Map

Before an email address became a name, it could look like a set of directions. Every exclamation mark told a queued message which machine to visit next — and every omitted or stale hop could leave it stranded.

One Class A Subnet Could Defeat the Default: RFC 2036’s Compatibility Test

Opening unused Class A space in 1996 was not just a registry decision. It changed what every provider, customer domain and peer had to mean by a route: once a small component of an old classful parent appeared, inherited assumptions could send the rest of that parent away from an otherwise valid default.

Jean Armour Polly and the Internet Connection That Still Needed a Librarian

In 1992, “going online” at a public library did not begin with a browser. It began with a desk computer, communications software, a modem, a telephone line — and somebody who could turn that fragile stack into a public service.