Skip to main content

BTW Media Editorial Collection

History of the Internet

The internet was not born as a finished system. It was built across decades by researchers, engineers, operators, institutions, and communities who chose openness, interoperability, and shared stewardship before the world knew what the network would become.

History of the Internet is BTW Media's editorial archive of the people, protocols, institutions, and turning points that shaped the global network.

1969ARPANETFirst message
1983TCP/IPOperational flag day
1983/84DNSNames become infrastructure
1989/91WWWThe network becomes readable
1998ICANNGlobal identifier stewardship
TodayShared stewardshipOpen network memory

People who built the network

Researchers, engineers, operators, and community leaders whose choices shaped the internet's open architecture.

Protocols that became infrastructure

TCP/IP, DNS, routing, email, the Web, number resources, and standards processes made global interoperability possible.

Memory for the next generation

Interviews, profiles, and records preserve how the internet was imagined, governed, expanded, and defended.

This collection brings together interviews, profiles, source-backed reporting, and historical analysis about the builders and witnesses of the internet age.

This page follows how individual decisions, technical principles, public institutions, and regional communities became civilization-scale infrastructure.

For the people recorded here, this is a record of contribution. For readers, it is a map of how the internet became one of humanity's shared systems.

Series

People Who Built the Internet

From packet-switching theory to the World Wide Web, this map connects the people, protocol decisions, and governance transitions that shaped the global network.

Leonard Kleinrock profile portrait

1961

Leonard Kleinrock

Recorded contribution

Leonard Kleinrock (1961): Published the earliest packet-switching and information-flow work that provided mathematical foundations for breaking messages into packets.

J.C.R. Licklider profile portrait

1962 / 1963

J.C.R. Licklider

Recorded contribution

J.C.R. Licklider (1962 / 1963): Articulated the "Intergalactic Computer Network" vision that inspired ARPA's networking goals and the idea of a globally-connected computing commons.

Paul Baran profile portrait

1964

Paul Baran

Recorded contribution

Paul Baran (1964): RAND memorandum On Distributed Communications laid out distributed network designs intended to be survivable — a key conceptual precursor to later packet networks.

Donald Davies profile portrait

1965

Donald Davies

Recorded contribution

Donald Davies (1965): Coined the term "packet" and advanced practical packet-switching architecture at the UK National Physical Laboratory.

Douglas Engelbart profile portrait

1968

Douglas Engelbart

Recorded contribution

Douglas Engelbart (1968): Demonstrated the oN-Line System (NLS) at the "Mother of All Demos" — showing hypertext, shared editing, the mouse and other interactive concepts that shaped future online tools.

Lawrence (Larry) Roberts profile portrait

1969

Lawrence (Larry) Roberts

Recorded contribution

Lawrence (Larry) Roberts (1969): As ARPA program manager he designed and led the ARPANET construction, turning packet-switching proposals into the first operational research network.

Jon Postel profile portrait

1969

Jon Postel

Recorded contribution

Jon Postel (1969): Became central to the RFC series and began his long stewardship of protocol documentation and numbering — the Internet's numbering authority.

Steve Crocker profile portrait

1969

Steve Crocker

Recorded contribution

Steve Crocker (1969): Instigated the ARPANET "Network Working Group" and created the Request for Comments (RFC) series — the primary open documentation mechanism for Internet protocols.

Vint Cerf & Bob Kahn profile portrait

1972–1973

Vint Cerf & Bob Kahn

Recorded contribution

Vint Cerf & Bob Kahn (1972–1973): Co-designed the Transmission Control Protocol (TCP) and later TCP/IP, enabling communication across multiple networks — the birth of internetworking.

Robert Metcalfe profile portrait

1973

Robert Metcalfe

Recorded contribution

Robert Metcalfe (1973): Invented Ethernet at Xerox PARC, making local networking fast and scalable for office and campus environments.

Louis Pouzin profile portrait

1973–1975

Louis Pouzin

Recorded contribution

Louis Pouzin (1973–1975): Developed CYCLADES in France, a datagram-based packet network that directly influenced TCP/IP's design.

Danny Cohen profile portrait

1973

Danny Cohen

Recorded contribution

Danny Cohen (1973): Pioneered early packet voice transmission and endianness concepts, key to interoperability in TCP/IP systems.

Yngvar G. Lundh profile portrait

1975

Yngvar G. Lundh

Recorded contribution

Yngvar G. Lundh (1975): Promoted and implemented early packet networking in Scandinavia, connecting European research networks.

Elizabeth "Jake" Feinler profile portrait

1976

Elizabeth "Jake" Feinler

Recorded contribution

Elizabeth "Jake" Feinler (1976): Managed the ARPANET Network Information Center (NIC) at SRI, maintaining the official host name directory before DNS.

Pål Spilling profile portrait

1977

Pål Spilling

Recorded contribution

Pål Spilling (1977): Helped establish early ARPANET links in Europe and co-authored the first Internet (TCP/IP) experiments between continents.

Bob Kahn, Vint Cerf & Jon Postel profile portrait

1977

Bob Kahn, Vint Cerf & Jon Postel

Recorded contribution

Bob Kahn, Vint Cerf & Jon Postel (1977): Conducted the first three-network TCP/IP test (ARPANET, SATNET, PRNET), proving the architecture's viability.

Steve Crocker, Jon Postel & Joyce Reynolds profile portrait

1978

Steve Crocker, Jon Postel & Joyce Reynolds

Recorded contribution

Steve Crocker, Jon Postel & Joyce Reynolds (1978): Led early IETF-like protocol coordination and RFC series continuity — the core of today's open standards process.

Radia Perlman profile portrait

1979

Radia Perlman

Recorded contribution

Radia Perlman (1979): Developed early routing algorithms that evolved into the Spanning Tree Protocol (finalized 1985).

Paul Mockapetris profile portrait

1981–1983

Paul Mockapetris

Recorded contribution

Paul Mockapetris (1981–1983): Invented the Domain Name System (DNS) to replace the central HOSTS.TXT file. Introduced hierarchical, distributed naming via RFC 882/883.

Danny Cohen profile portrait

1981

Danny Cohen

Recorded contribution

Danny Cohen (1981): Published "On Holy Wars and a Plea for Peace," formalizing the concept of byte ordering ("endianness").

Daniel Karrenberg profile portrait

1982

Daniel Karrenberg

Recorded contribution

Daniel Karrenberg (1982): Helped build EUnet, the first pan-European Internet Service Provider (ISP) and in 1989 was one of the founders of RIPE.

Vint Cerf, Bob Kahn, Jon Postel & Steve Crocker profile portrait

1982–1983

Vint Cerf, Bob Kahn, Jon Postel & Steve Crocker

Recorded contribution

Vint Cerf, Bob Kahn, Jon Postel & Steve Crocker (1982–1983): Oversaw the January 1, 1983 "flag day" switchover from NCP to TCP/IP — the operational birth of the modern Internet.

Radia Perlman profile portrait

1983–1984

Radia Perlman

Recorded contribution

Radia Perlman (1983–1984): Developed the Spanning Tree Protocol (STP), which made Ethernet networks reliable and loop-free.

Mike Muuss profile portrait

1984

Mike Muuss

Recorded contribution

Mike Muuss (1984): Created ping, one of the simplest and most enduring diagnostic tools in networking.

Eric Allman profile portrait

1984–1986

Eric Allman

Recorded contribution

Eric Allman (1984–1986): Wrote Sendmail, the first general-purpose Internet email transport system, crucial for global email interoperability.

Brian Carpenter profile portrait

1985

Brian Carpenter

Recorded contribution

Brian Carpenter (1985): Led development of key Internet standards and chaired IETF working groups, promoting IPv6 and architectural consistency.

John Klensin profile portrait

1986

John Klensin

Recorded contribution

John Klensin (1986): Significant early work on SMTP, FTP, and internationalization of Internet protocols.

Joyce K. Reynolds & Bob Braden profile portrait

1987

Joyce K. Reynolds & Bob Braden

Recorded contribution

Joyce K. Reynolds & Bob Braden (1987): Contributed to RFC editing, TCP/IP documentation, and Internet research group coordination.

Alan Emtage profile portrait

1989

Alan Emtage

Recorded contribution

Alan Emtage (1989): Developed Archie, the first Internet search engine, enabling users to find files across FTP servers.

Tim Berners-Lee profile portrait

1990 / 1991

Tim Berners-Lee

Recorded contribution

Tim Berners-Lee (1990 / 1991): Invented the World Wide Web at CERN — creating HTTP, HTML, and the first web server and browser, converting network infrastructure into a global publishing and information system.

Linus Torvalds profile portrait

1991

Linus Torvalds

Recorded contribution

Linus Torvalds (1991): Created the Linux kernel, which became a cornerstone of Internet infrastructure, web servers, and open-source computing.

Jianping Wu profile portrait

1991

Jianping Wu

Recorded contribution

Jianping Wu (1991): Led the development of CERNET, China's first academic Internet network, linking universities across the country.

Scott Bradner profile portrait

1991

Scott Bradner

Recorded contribution

Scott Bradner (1991): Key figure in IETF standardization and Internet governance; helped define early Internet policy and protocol stewardship.

Kilnam Chon profile portrait

1992

Kilnam Chon

Recorded contribution

Kilnam Chon (1992): Built KREONET, the Korean Research Network, pioneering Internet connectivity in Asia.

Marc Andreessen profile portrait

1993

Marc Andreessen

Recorded contribution

Marc Andreessen (1993): Co-developed Mosaic, the first mainstream graphical web browser, which popularized the Web and inspired Netscape.

Robert Cailliau profile portrait

1993

Robert Cailliau

Recorded contribution

Robert Cailliau (1993): Collaborated with Berners-Lee at CERN to promote and refine the World Wide Web and its first browser/server setup.

Mitchell Baker profile portrait

1994

Mitchell Baker

Recorded contribution

Mitchell Baker (1994): Led the Mozilla project, defending open web standards and community-driven browser development.

Xing Li profile portrait

1994

Xing Li

Recorded contribution

Xing Li (1994): Architect of CERNET, China's first academic network (1994), and early IPv6 advocate for Asia-Pacific.

Paul Vixie profile portrait

1995

Paul Vixie

Recorded contribution

Paul Vixie (1995): Principal developer of BIND, the most widely used DNS server software; improved DNS reliability and security.

Larry Landweber profile portrait

1996

Larry Landweber

Recorded contribution

Larry Landweber (1996): Created CSNET and helped connect over 25 countries to the early Internet, bridging academia and policy.

Radia Perlman profile portrait

1997

Radia Perlman

Recorded contribution

Radia Perlman (1997): Authored Interconnections, formalizing network protocol design principles and influencing Internet routing education.

Jon Postel profile portrait

1998

Jon Postel

Recorded contribution

Jon Postel (1998): Demonstrated control over the DNS root servers and led the IANA transition, symbolizing his lifelong role.

Vint Cerf & Bob Kahn profile portrait

1998

Vint Cerf & Bob Kahn

Recorded contribution

Vint Cerf & Bob Kahn (1998): Helped found ICANN and promoted the institutional frameworks for managing Internet naming and numbering globally.

Al Gore profile portrait

1999

Al Gore

Recorded contribution

Al Gore (1999): Sponsored the 1991 High Performance Computing and Communications Act, which funded Internet expansion — earning the nickname "the Information Superhighway."

Explore the Wider Lineage44 names and milestones

Foundations: 1960s

  1. 1961Leonard Kleinrock

    Leonard Kleinrock (1961): Published the earliest packet-switching and information-flow work that provided mathematical foundations for breaking messages into packets.

  2. 1962 / 1963J.C.R. Licklider

    J.C.R. Licklider (1962 / 1963): Articulated the "Intergalactic Computer Network" vision that inspired ARPA's networking goals and the idea of a globally-connected computing commons.

  3. 1964Paul Baran

    Paul Baran (1964): RAND memorandum On Distributed Communications laid out distributed network designs intended to be survivable — a key conceptual precursor to later packet networks.

  4. 1965Donald Davies

    Donald Davies (1965): Coined the term "packet" and advanced practical packet-switching architecture at the UK National Physical Laboratory.

  5. 1968Douglas Engelbart

    Douglas Engelbart (1968): Demonstrated the oN-Line System (NLS) at the "Mother of All Demos" — showing hypertext, shared editing, the mouse and other interactive concepts that shaped future online tools.

  6. 1969Lawrence (Larry) Roberts

    Lawrence (Larry) Roberts (1969): As ARPA program manager he designed and led the ARPANET construction, turning packet-switching proposals into the first operational research network.

  7. 1969Jon Postel

    Jon Postel (1969): Became central to the RFC series and began his long stewardship of protocol documentation and numbering — the Internet's numbering authority.

  8. 1969Steve Crocker

    Steve Crocker (1969): Instigated the ARPANET "Network Working Group" and created the Request for Comments (RFC) series — the primary open documentation mechanism for Internet protocols.

Protocols & Internetworking: 1970s

  1. 1972–1973Vint Cerf & Bob Kahn

    Vint Cerf & Bob Kahn (1972–1973): Co-designed the Transmission Control Protocol (TCP) and later TCP/IP, enabling communication across multiple networks — the birth of internetworking.

  2. 1973Robert Metcalfe

    Robert Metcalfe (1973): Invented Ethernet at Xerox PARC, making local networking fast and scalable for office and campus environments.

  3. 1973–1975Louis Pouzin

    Louis Pouzin (1973–1975): Developed CYCLADES in France, a datagram-based packet network that directly influenced TCP/IP's design.

  4. 1973Danny Cohen

    Danny Cohen (1973): Pioneered early packet voice transmission and endianness concepts, key to interoperability in TCP/IP systems.

  5. 1975Yngvar G. Lundh

    Yngvar G. Lundh (1975): Promoted and implemented early packet networking in Scandinavia, connecting European research networks.

  6. 1976Elizabeth "Jake" Feinler

    Elizabeth "Jake" Feinler (1976): Managed the ARPANET Network Information Center (NIC) at SRI, maintaining the official host name directory before DNS.

  7. 1977Pål Spilling

    Pål Spilling (1977): Helped establish early ARPANET links in Europe and co-authored the first Internet (TCP/IP) experiments between continents.

  8. 1977Bob Kahn, Vint Cerf & Jon Postel

    Bob Kahn, Vint Cerf & Jon Postel (1977): Conducted the first three-network TCP/IP test (ARPANET, SATNET, PRNET), proving the architecture's viability.

  9. 1978Steve Crocker, Jon Postel & Joyce Reynolds

    Steve Crocker, Jon Postel & Joyce Reynolds (1978): Led early IETF-like protocol coordination and RFC series continuity — the core of today's open standards process.

  10. 1979Radia Perlman

    Radia Perlman (1979): Developed early routing algorithms that evolved into the Spanning Tree Protocol (finalized 1985).

Naming, Routing & Standards: 1980s

  1. 1981–1983Paul Mockapetris

    Paul Mockapetris (1981–1983): Invented the Domain Name System (DNS) to replace the central HOSTS.TXT file. Introduced hierarchical, distributed naming via RFC 882/883.

  2. 1981Danny Cohen

    Danny Cohen (1981): Published "On Holy Wars and a Plea for Peace," formalizing the concept of byte ordering ("endianness").

  3. 1982–1983Vint Cerf, Bob Kahn, Jon Postel & Steve Crocker

    Vint Cerf, Bob Kahn, Jon Postel & Steve Crocker (1982–1983): Oversaw the January 1, 1983 "flag day" switchover from NCP to TCP/IP — the operational birth of the modern Internet.

  4. 1983–1984Radia Perlman

    Radia Perlman (1983–1984): Developed the Spanning Tree Protocol (STP), which made Ethernet networks reliable and loop-free.

  5. 1984Mike Muuss

    Mike Muuss (1984): Created ping, one of the simplest and most enduring diagnostic tools in networking.

  6. 1984–1986Eric Allman

    Eric Allman (1984–1986): Wrote Sendmail, the first general-purpose Internet email transport system, crucial for global email interoperability.

  7. 1985Brian Carpenter

    Brian Carpenter (1985): Led development of key Internet standards and chaired IETF working groups, promoting IPv6 and architectural consistency.

  8. 1986John Klensin

    John Klensin (1986): Significant early work on SMTP, FTP, and internationalization of Internet protocols.

  9. 1987Joyce K. Reynolds & Bob Braden

    Joyce K. Reynolds & Bob Braden (1987): Contributed to RFC editing, TCP/IP documentation, and Internet research group coordination.

  10. 1989Alan Emtage

    Alan Emtage (1989): Developed Archie, the first Internet search engine, enabling users to find files across FTP servers.

Web, Search & Governance: 1990s

  1. 1990 / 1991Tim Berners-Lee

    Tim Berners-Lee (1990 / 1991): Invented the World Wide Web at CERN — creating HTTP, HTML, and the first web server and browser, converting network infrastructure into a global publishing and information system.

  2. 1991Linus Torvalds

    Linus Torvalds (1991): Created the Linux kernel, which became a cornerstone of Internet infrastructure, web servers, and open-source computing.

  3. 1991Scott Bradner

    Scott Bradner (1991): Key figure in IETF standardization and Internet governance; helped define early Internet policy and protocol stewardship.

  4. 1993Marc Andreessen

    Marc Andreessen (1993): Co-developed Mosaic, the first mainstream graphical web browser, which popularized the Web and inspired Netscape.

  5. 1993Robert Cailliau

    Robert Cailliau (1993): Collaborated with Berners-Lee at CERN to promote and refine the World Wide Web and its first browser/server setup.

  6. 1994Mitchell Baker

    Mitchell Baker (1994): Led the Mozilla project, defending open web standards and community-driven browser development.

  7. 1995Paul Vixie

    Paul Vixie (1995): Principal developer of BIND, the most widely used DNS server software; improved DNS reliability and security.

  8. 1996Larry Landweber

    Larry Landweber (1996): Created CSNET and helped connect over 25 countries to the early Internet, bridging academia and policy.

  9. 1997Radia Perlman

    Radia Perlman (1997): Authored Interconnections, formalizing network protocol design principles and influencing Internet routing education.

  10. 1998Jon Postel

    Jon Postel (1998): Demonstrated control over the DNS root servers and led the IANA transition, symbolizing his lifelong role.

  11. 1998Vint Cerf & Bob Kahn

    Vint Cerf & Bob Kahn (1998): Helped found ICANN and promoted the institutional frameworks for managing Internet naming and numbering globally.

  12. 1999Al Gore

    Al Gore (1999): Sponsored the 1991 High Performance Computing and Communications Act, which funded Internet expansion — earning the nickname "the Information Superhighway."

Regional Internet Builders

  1. 1982Daniel Karrenberg

    Daniel Karrenberg (1982): Helped build EUnet, the first pan-European Internet Service Provider (ISP) and in 1989 was one of the founders of RIPE.

  2. 1991Jianping Wu

    Jianping Wu (1991): Led the development of CERNET, China's first academic Internet network, linking universities across the country.

  3. 1992Kilnam Chon

    Kilnam Chon (1992): Built KREONET, the Korean Research Network, pioneering Internet connectivity in Asia.

  4. 1994Xing Li

    Xing Li (1994): Architect of CERNET, China's first academic network (1994), and early IPv6 advocate for Asia-Pacific.

Internet Milestones

Milestones in the Making of the Internet

A decade-by-decade guide to the experiments, protocols, standards, networks, and institutions that turned internetworking into shared global infrastructure.

1960s — Experimental Packet Networks

  • 1962-1965

    Packet switching becomes a practical networking idea

    Paul Baran and Donald Davies separately formalize packet-switched communication, giving later research networks a way to move data without relying on circuit-switched telephony.

    Paul Baran, Donald Davies

    RAND, National Physical Laboratory

  • 1969

    ARPANET sends its first message

    The first host-to-host ARPANET message travels between UCLA and SRI, turning packet networking from research architecture into an operating experiment.

    Leonard Kleinrock, Charley Kline, Bill Duvall

    UCLA, SRI, ARPA

1970s — Protocols & Internetworking

  • 1971

    Email becomes the first durable social application of the network

    Ray Tomlinson adapts network mail between machines, making person-to-person communication one of the internet's earliest reasons to exist.

    Ray Tomlinson

    BBN, ARPANET

  • 1974

    TCP paper defines internetworking as an open architecture

    Vint Cerf and Bob Kahn publish the TCP paper and give the network a protocol model for connecting heterogeneous networks into an internet.

    Vint Cerf, Bob Kahn

    DARPA

  • 1977

    Three-network TCP/IP test proves internetworking across media

    Packet radio, satellite, and ARPANET paths carry traffic through a common protocol design, showing that an internet can survive different physical networks.

    Vint Cerf, Jon Postel, Bob Kahn

    DARPA research community

1980s — Naming, Routing & Standards

  • 1983

    TCP/IP flag day makes the modern internet operational

    ARPANET hosts move from NCP to TCP/IP on January 1, 1983, making the protocol suite an operational foundation rather than a research proposal.

    Vint Cerf, Bob Kahn, Jon Postel, Steve Crocker

    DARPA, ARPANET community

  • 1983-1984

    DNS turns names into distributed internet infrastructure

    Paul Mockapetris and the early naming community replace host tables with the Domain Name System, giving the expanding network a scalable naming layer.

    Paul Mockapetris, Jon Postel

    USC/ISI, IANA

  • 1986

    NSFNET expands academic networking into a backbone

    The NSFNET programme links supercomputing centres and research institutions, creating a backbone that helps move the internet beyond its original defence research context.

    National Science Foundation, regional academic networks

  • Late 1980s

    Routing growth forces inter-domain coordination

    As networks multiply, operators move toward scalable inter-domain routing practices that later make BGP and routing security central to internet operations.

    Network operators and routing researchers

    IETF, operator community

  • 1989 / 1990

    Archie makes distributed network resources discoverable

    Alan Emtage creates Archie, showing that the internet also needs discovery systems, not only transport and addressing.

    Alan Emtage

    McGill University

1990s — Web, RIRs & Governance

  • 1989 / 1991

    The World Wide Web opens the internet to publishing and navigation

    Tim Berners-Lee proposes and implements HTTP, HTML, URLs, and early browser/server software, turning the network into a global information space.

    Tim Berners-Lee, Robert Cailliau

    CERN

  • 1992

    Regional number coordination takes institutional form

    Regional internet growth creates the need for durable address allocation institutions, with APNIC emerging in the Asia-Pacific coordination context.

    Regional operators and registry builders

    APNIC, RIR community

  • 1993

    El Salvador joins the global internet story

    Local builders connect national academic and technical communities into the global network, showing how internet history is made outside the original centres of research funding.

    Lito Ibarra

    El Salvador internet community

  • 1998

    ICANN is formed to coordinate global identifiers

    ICANN becomes the institutional home for DNS and identifier coordination debates, moving internet governance into a more formal multi-stakeholder structure.

    Jon Postel, Vint Cerf, global governance community

    ICANN, IANA community

  • 1998

    IPv6 is specified in RFC 2460

    The IETF publishes RFC 2460, preserving the internet's ability to scale addressing beyond IPv4 exhaustion and making protocol stewardship a generational task.

    Brian Carpenter, IETF IPv6 community

    IETF

2000s — Regional Builders & Operational Memory

  • 1986 / 1992

    Latin American academic networks become regional infrastructure

    Builders in Chile, Venezuela, Argentina, and neighbouring communities turn research connectivity into lasting regional internet capacity.

    Florencio Utreras, Ermanno Pietrosemoli, Olga Cavalli

    Latin American academic and governance communities

  • 2000s

    African technical communities expand capacity and participation

    Training, software communities, and advocacy broaden who can build, operate, and govern internet infrastructure.

    Dorcas Muthoni

    African technology and internet communities

  • 2000s

    Operational analysis becomes part of internet stewardship

    Routing, addressing, measurement, and security analysis become essential to explaining where the global network is resilient and where it is fragile.

    Geoff Huston

    APNIC Labs, operator community

2010s — Stewardship, Security & Continuity

  • 2016

    IANA stewardship transition completes

    The transition marks a major governance shift from US government oversight toward the global multi-stakeholder community.

    ICANN, IANA community, global internet governance community

  • 2010s / 2020s

    Routing security becomes a core public-interest issue

    RPKI, MANRS, and operator coordination make routing security part of the internet's institutional memory and daily operational discipline.

    Routing security researchers and operators

    IETF, RIRs, operator community

  • 2024

    Internet history becomes a source-backed archive

    Measurement archives, oral histories, and editorial collections make internet history itself a field of stewardship for the next generation.

    Jim Cowie and internet history researchers

    Internet History Initiative

Published Records

BTW Internet History Archive

Published interviews, profiles, and historical reporting from BTW Media's History of the Internet collection.

Open Fallback Was Written Down. Running Servers Still Broke the Session: RFC 1425 record
Historical coverage2 Sept 2026Original: HistoryPublished 2 Sept 2026

Fallback Was Written Down. Running Servers Still Broke the Session: RFC 1425

The Fallback Was Written Down. Running Servers Still Broke the Session: RFC 1425

The old server was supposed to say that it did not understand `EHLO`, remain connected and let the client try `HELO`. That was the elegant transition drawn in RFC 1425. Seventeen months later, its successor had to record what running systems actually did: some dropped the connection at the new word; others rejected the old greeting after rejecting the new one. The fallback existed in the document before it reliably existed on the wire.

Read Record
Open Shortcut Was for Display. The Stored Address Had to Outlive It: RFC 1278 record
Historical coverage1991Original: HistoryPublished 2 Sept 2026

Shortcut Was for Display. The Stored Address Had to Outlive It: RFC 1278

The Shortcut Was for Display. The Stored Address Had to Outlive It: RFC 1278

The sharpest sentence in RFC 1278 comes after the convenient machinery. Macros could shorten a long presentation address, nest inside one another and choose the longest available substitution for display. Then the memo drew the line: no macro should ever be relied on. In 1991, human readability was already being treated as a surface—not as permission to store the shortcut as the network fact.

Read Record
Open Mail Stayed Readable. Every Rewrite Became the Verifier's Problem: RFC 1421 record
Historical coverage2 Sept 2026Original: HistoryPublished 2 Sept 2026

Mail Stayed Readable. Every Rewrite Became the Verifier's Problem: RFC 1421

The Mail Stayed Readable. Every Rewrite Became the Verifier's Problem: RFC 1421

The words were already on the screen. A recipient could read the paragraphs, understand the request and even act on them. Yet the machine still had a different question: were these the same canonical lines that the sender had signed? In RFC 1421's `MIC-CLEAR` format, human access arrived before cryptographic certainty. That was not an accident. It was a compatibility bargain with the mail system that already existed.

Read Record
Open Plan Was Published Before the Result. The Announcement Could Change the Sample: RFC 1273 record
Historical coverage2 Sept 2026Original: HistoryPublished 2 Sept 2026

Plan Was Published Before the Result. The Announcement Could Change the Sample: RFC 1273

The Plan Was Published Before the Result. The Announcement Could Change the Sample: RFC 1273

The awkward number in RFC 1273 was not 73,760 connection attempts. It was the cost of explaining them. In the study’s initial tests, messages intended to notify remote administrators generated more network and administrative load than the measurement itself, while roughly half came back undeliverable. The attempt to make observation legible had become a second intervention—and one capable of changing the sample.

Read Record
Open Name Service Failed. The Agent Could Still Answer: RFC 1419 record
Historical coverage2 Sept 2026Original: HistoryPublished 2 Sept 2026

Name Service Failed. The Agent Could Still Answer: RFC 1419

The Name Service Failed. The Agent Could Still Answer: RFC 1419

The management station remembered an agent's name and yesterday's address. Today the name service could not resolve it. The direct datagram path might nevertheless still work—and that old address might still reach the intended box. Or a new box might have acquired it. RFC 1419 designed for both truths at once: caches could preserve manageability during discovery failure, but a cached route could never be promoted into device identity.

Read Record
Open Session Died. Route Memory Became an Explicit Exception: RFC 1267 record
Historical coverage2 Sept 2026Original: HistoryPublished 2 Sept 2026

Session Died. Route Memory Became an Explicit Exception: RFC 1267

The Session Died. Route Memory Became an Explicit Exception: RFC 1267

An incremental protocol carries an unspoken dependency: both sides must remember the same beginning. RFC 1267 sent a complete routing table once, then only the changes, and required each BGP speaker to retain its peer’s current table for the life of the connection. Later BGP specifications did not quietly abolish that boundary. They turned survival beyond it into a negotiated, labelled and expiring exception.

Read Record
Open Specification Called Zero VAR. Running Code Called It VALUE: RFC 1408 record
Historical coverage2 Sept 2026Original: HistoryPublished 2 Sept 2026

Specification Called Zero VAR. Running Code Called It VALUE: RFC 1408

The Specification Called Zero VAR. Running Code Called It VALUE: RFC 1408

One octet crossed a Telnet connection. The new specification said zero introduced a variable name. A family of existing programs read the same zero as the beginning of a value. Nothing in the packet announced which dictionary had produced it. RFC 1408 had given the exchange a public grammar, but publication could not rewrite the parsers already running. The repair would require more than correcting a table: first infer the past, then give the future a new number.

Read Record
Open Report Counted 56 Routers. It Refused to Call the Stress Case Normal: RFC 1266 record
Historical coverage2 Sept 2026Original: HistoryPublished 2 Sept 2026

Report Counted 56 Routers. It Refused to Call the Stress Case Normal: RFC 1266

The Report Counted 56 Routers. It Refused to Call the Stress Case Normal: RFC 1266

Fifty-six was not the number of production routers. RFC 1266 first counted 56 BGP border routers in seven autonomous systems, then removed the seven-router T3 NSFNET Test Network from the operational denominator: 49 routers, six systems. That correction is the most important line in the report. It shows an early Internet standards record preserving the boundary between everything observed and what could honestly be called operational.

Read Record
Open Graph Could Travel. Its Measurement History Had to Travel With It: RFC 1404 record
Historical coverage1993Original: HistoryPublished 2 Sept 2026

Graph Could Travel. Its Measurement History Had to Travel With It: RFC 1404

The Graph Could Travel. Its Measurement History Had to Travel With It: RFC 1404

A line on a screen looks self-contained. In 1993, RFC 1404 treated it as the end of a chain: a named interface had been polled at an actual interval, its counter had been turned into a delta, the result had been mapped to a continuing network resource, and older samples may already have been compressed into an average or a peak. If another operations centre received only the line, it received a picture without the conditions that made the picture comparable.

Read Record
Open Checklist Was Retired. The Evidence Question Moved: RFC 1264 record
Historical coverage1991Original: HistoryPublished 2 Sept 2026

Checklist Was Retired. The Evidence Question Moved: RFC 1264

The Checklist Was Retired. The Evidence Question Moved: RFC 1264

In 1991, a routing protocol did not advance merely because its specification looked complete. RFC 1264 asked for separate receipts: independently written code, tests for every feature, security demonstrations, operational history, and an account of where the design would break. Fifteen years later, the IETF retired that universal routing checklist. It did not turn publication into deployment. It moved the authority to demand evidence.

Read Record
Open Route Tag Could Admit It Had Forgotten the Path: RFC 1403 record
Historical coverage1993Original: HistoryPublished 2 Sept 2026

Route Tag Could Admit It Had Forgotten the Path: RFC 1403

The Route Tag Could Admit It Had Forgotten the Path: RFC 1403

A border router in 1993 could squeeze a route’s history into thirty-two bits only by throwing most of that history away. RFC 1403 made the loss visible: its OSPF tag could say whether path knowledge was complete and roughly how long the path had been. When the missing detail was needed to make a new BGP claim, the tag was not allowed to improvise. The route stayed inside.

Read Record
Open Relay Changed the Message. It Had to Call Itself a Gateway: RFC 1344 record
Historical coverage1992Original: HistoryPublished 2 Sept 2026

Relay Changed the Message. It Had to Call Itself a Gateway: RFC 1344

The Relay Changed the Message. It Had to Call Itself a Gateway: RFC 1344

A carrier can claim neutrality while the object in its custody remains untouched. The claim becomes harder after it changes an image, replaces a reference with a copy or divides one message into several. RFC 1344 gave that moment a name in 1992: the intermediary was no longer merely transporting mail. It had become a gateway, and its decision needed a trace separate from delivery, fidelity and consent.

Read Record
Open Test Bed Could Demonstrate a Future. It Could Not Decide the Public Network: RFC 1259 record
Historical coverage2 Sept 2026Original: HistoryPublished 2 Sept 2026

Test Bed Could Demonstrate a Future. It Could Not Decide the Public Network: RFC 1259

The Test Bed Could Demonstrate a Future. It Could Not Decide the Public Network: RFC 1259

RFC 1259 imagined the NREN as a new subdivision built before the surrounding city. Its mistakes could teach later builders, but its streets, prices and residents could not decide the whole metropolis. The crucial Internet-history lesson was not prediction. It was the design of a place where technology, access, competition and rights could be tested without mistaking the experiment for public consent.

Read Record
Open Network Did Not Have to Keep the Beat. The Receiver Rebuilt It: RFC 1257 record
Historical coverage1991Original: HistoryPublished 2 Sept 2026

Network Did Not Have to Keep the Beat. The Receiver Rebuilt It: RFC 1257

The Network Did Not Have to Keep the Beat. The Receiver Rebuilt It: RFC 1257

In 1991, a voice sample could arrive early, the next one late, and the listener could still hear a regular cadence—if the receiver knew the deadline, kept enough memory and woke at the right time. RFC 1257 used that construction to move a costly promise out of every subnetwork without pretending that bandwidth, delay, clocks, buffers and final playback were the same fact.

Read Record
Open Packet Got a New Lifetime at Every Border: RFC 1326 record
Historical coverage2 Sept 2026Original: HistoryPublished 2 Sept 2026

Packet Got a New Lifetime at Every Border: RFC 1326

The Packet Got a New Lifetime at Every Border: RFC 1326

A tunnel is often described as a clean bargain: put one protocol inside another, cross a network that understands the outer wrapper, then recover the original packet at the exit. RFC 1326 asked what happens when two such bargains face each other and routing sends the packet back before either tunnel has finished. Every gateway can make a locally sensible move while the packet grows, fragments and keeps returning. The missing object is not another wrapper. It is one lifetime that every wrapper must consume.

Read Record
Open Analysis Could Not Stand In for the Test Network: RFC 1245 and RFC 1246 record
Historical coverage1991Original: HistoryPublished 2 Sept 2026

Analysis Could Not Stand In for the Test Network: RFC 1245 and RFC 1246

The Analysis Could Not Stand In for the Test Network: RFC 1245 and RFC 1246

In July 1991, OSPF arrived with more than a protocol specification. Its supporting case was deliberately divided into an analysis and an experience report. That division preserved a distinction Internet engineering still needs: a model can bound expected behaviour, but only implementations, test configurations and operating networks can reveal which assumptions survive contact with each other.

Read Record
Open NIC Owned the Question. It Did Not Own the Network: RFC 1302 record
Historical coverage1992Original: HistoryPublished 2 Sept 2026

NIC Owned the Question. It Did Not Own the Network: RFC 1302

The NIC Owned the Question. It Did Not Own the Network: RFC 1302

A help desk can keep faith with a user without pretending to control every system behind the problem. RFC 1302 made that distinction unusually clear in 1992. A Network Information Center was expected to take responsibility for an inquiry until it was resolved in some way. Yet resolution could mean an answer, a referral, or coordination with a Network Operations Center. The duty stayed with the question; authority and evidence remained distributed.

Read Record
Open MIB Had to Redraw Who Could Change AppleTalk: RFC 1243 and RFC 1742 record
Historical coverage1991Original: HistoryPublished 2 Sept 2026

MIB Had to Redraw Who Could Change AppleTalk: RFC 1243 and RFC 1742

The MIB Had to Redraw Who Could Change AppleTalk: RFC 1243 and RFC 1742

A management model is also a map of responsibility. In 1991, the first AppleTalk MIB let an SNMP manager write route fields and zone mappings while reporting how port settings had been obtained. Four years later, its replacement moved several of those lines. The revision matters because a value's presence, origin, mutability and effect were never the same fact.

Read Record
Open Box Dropped No Frames. It Had Not Passed the Other Tests: RFC 1242 record
Historical coverage2 Sept 2026Original: HistoryPublished 2 Sept 2026

Box Dropped No Frames. It Had Not Passed the Other Tests: RFC 1242

The Box Dropped No Frames. It Had Not Passed the Other Tests: RFC 1242

A clean throughput trial is seductive because it ends in one number. RFC 1242 gave that number a strict meaning, then surrounded it with other terms that refused to disappear. Zero loss at one offered rate did not answer latency, burst tolerance, overload, restart, filtering or single-frame behavior. The vocabulary was an early attempt to keep the conditions attached to the claim.

Read Record
Open Counter Was Total. Subscription Discards Were Somewhere Else: RFC 1304 record
Historical coverage1992Original: HistoryPublished 2 Sept 2026

Counter Was Total. Subscription Discards Were Somewhere Else: RFC 1304

The Counter Was Total. Subscription Discards Were Somewhere Else: RFC 1304

A number labelled total looks like the end of an investigation. In RFC 1304, it was the beginning of one. The 1992 MIB could count SIP packets discarded for protocol or bit errors, list other address-related failures and remember the latest disagreement of each syntactic type. Yet it expressly sent subscription-screening violations to another management module. “Total” meant complete inside a declared accounting boundary—not every packet the network refused, and certainly not the result experienced by an application.

Read Record