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 Standard That Required Two Answers: TCP-AO's Cryptographic Baseline record
Historical coverageOriginal: HistoryPublished 5 Sept 2026

Standard That Required Two Answers: TCP-AO's Cryptographic Baseline

The Standard That Required Two Answers: TCP-AO's Cryptographic Baseline

Algorithm agility sounds like freedom of choice. For TCP-AO, RFC 5926 exposed the harder half of that promise: two endpoints could each support sound cryptography and still fail to authenticate a single segment unless they shared one precise MAC-and-key-derivation pair.

Read Record
Open Translator That Changed the Authenticated Connection: TCP-AO and NAT record
Historical coverageOriginal: HistoryPublished 5 Sept 2026

Translator That Changed the Authenticated Connection: TCP-AO and NAT

The Translator That Changed the Authenticated Connection: TCP-AO and NAT

A middlebox can change a packet without changing its route. TCP-AO made the consequences depend on what changed: rewriting a TCP option could be accommodated by authenticating fewer fields, but rewriting an address or port changed the identity of the protected connection itself.

Read Record
Open Reset That Could Not Be Trusted: TCP-AO After a Peer Reboot record
Historical coverageOriginal: HistoryPublished 5 Sept 2026

Reset That Could Not Be Trusted: TCP-AO After a Peer Reboot

The Reset That Could Not Be Trusted: TCP-AO After a Peer Reboot

TCP normally has a blunt way to tell a peer that an old connection no longer exists: send a reset. TCP-AO makes that answer harder to trust on purpose. When a protected peer reboots and forgets its connection state, the reset it can still send may be precisely the reset the surviving peer must reject.

Read Record
Open Header Described an Archive. It Did Not Authorize the Decoder to Run It: RFC 1505 record
Historical coverageOriginal: HistoryPublished 5 Sept 2026

Header Described an Archive. It Did Not Authorize the Decoder to Run It: RFC 1505

The Header Described an Archive. It Did Not Authorize the Decoder to Run It: RFC 1505

The line counts agree. The archive expands. The checksum closes. A shell command now waits in a directory created from an email message. In 1993, RFC 1505 drew the most important boundary at exactly this point: successful decoding was not permission to execute.

Read Record
Open Router Saw a New Network. It Was a Shadow of Its Own Mapping: RFC 1504 record
Historical coverageOriginal: HistoryPublished 5 Sept 2026

Router Saw a New Network. It Was a Shadow of Its Own Mapping: RFC 1504

The Router Saw a New Network. It Was a Shadow of Its Own Mapping: RFC 1504

The route looked newly learned and the number was locally valid. The awkward fact was that no second network had appeared. A number invented at one translation boundary had travelled around a redundant path, lost its lineage and returned as if it belonged to a stranger.

Read Record
Open Key That Could Change Mid-Connection: TCP-AO's Rollover Signal record
Historical coverageOriginal: HistoryPublished 5 Sept 2026

Key That Could Change Mid-Connection: TCP-AO's Rollover Signal

The Key That Could Change Mid-Connection: TCP-AO's Rollover Signal

Long-lived routing sessions made a simple operational question unusually dangerous: how can two endpoints replace an authentication key without dropping the TCP connection or guessing the same switching instant? TCP-AO answered with visible key identifiers and directional rollover state, while deliberately leaving key distribution outside TCP.

Read Record
Open RFC Published a Straw Poll. It Did Not Create a Constituency: RFC 1501 record
Historical coverageOriginal: HistoryPublished 5 Sept 2026

RFC Published a Straw Poll. It Did Not Create a Constituency: RFC 1501

The RFC Published a Straw Poll. It Did Not Create a Constituency: RFC 1501

Two electronic addresses at the end of a two-page RFC offered individual OS/2 users a way to be counted. They were doors into a proposed organisation, not proof that the people behind those doors had already become members, chosen representatives or moved IBM.

Read Record
Open Gateway Kept the Message. It Could Not Preserve Every Meaning: RFC 1496 record
Historical coverageOriginal: HistoryPublished 5 Sept 2026

Gateway Kept the Message. It Could Not Preserve Every Meaning: RFC 1496

The Gateway Kept the Message. It Could Not Preserve Every Meaning: RFC 1496

RFC 1496 gave an X.400(84)–MIME gateway an admirably stubborn rule: convert what it can, encapsulate what it cannot, and never discard an entire message merely because one body part is unfamiliar. That discipline protected the carrier. It did not make every heading survive, every recipient understand the content, every reverse conversion exact or every helper safe to run.

Read Record
Open Table Moved the Service. It Did Not Rename It: RFC 1498 record
Historical coverageOriginal: HistoryPublished 5 Sept 2026

Table Moved the Service. It Did Not Rename It: RFC 1498

The Table Moved the Service. It Did Not Rename It: RFC 1498

A 1993 RFC recovered an older lesson: a table can change where a service runs while its name survives. Reaching it still requires separate evidence for the node, attachment point and path—and none of those bindings alone proves identity, authority or delivery.

Read Record
Open Code Was Available. The Original Specification Was Not: RFC 1492 record
Historical coverageOriginal: HistoryPublished 5 Sept 2026

Code Was Available. The Original Specification Was Not: RFC 1492

The Code Was Available. The Original Specification Was Not: RFC 1492

The original TACACS specification existed, and the author of RFC 1492 could not obtain it because of copyright issues. What reached the public record in July 1993 was therefore an Informational reconstruction, constrained by running code and candid about the possibility that the missing document might one day prove it wrong.

Read Record
Open Damaged Text Became Readable Latin. It Did Not Become the Russian Original: RFC 1489 record
Historical coverageOriginal: HistoryPublished 5 Sept 2026

Damaged Text Became Readable Latin. It Did Not Become the Russian Original: RFC 1489

The Damaged Text Became Readable Latin. It Did Not Become the Russian Original: RFC 1489

When the eighth bit disappeared from a KOI8-R message, Russian letters could fall into a strange, case-reversed Latin shadow. A reader might still guess the words. That humane failure mode did not restore the erased bits, certify the charset or turn recognition into proof of the original text.

Read Record
Open MX Record Found a Gateway. It Did Not Prove the Fax Machine Existed: RFC 1486 record
Historical coverageOriginal: HistoryPublished 5 Sept 2026

MX Record Found a Gateway. It Did Not Prove the Fax Machine Existed: RFC 1486

The MX Record Found a Gateway. It Did Not Prove the Fax Machine Existed: RFC 1486

A wildcard in the Domain Name System could announce that a mail gateway was willing to serve thousands of telephone numbers. It could not say whether any one of those numbers existed, answered, belonged to a fax machine or put a page into the intended person's hands. RFC 1486 built a useful bridge by refusing to confuse those claims.

Read Record
Open String Carried the Distinguished Name. It Did Not Become the Directory Entry: RFC 1485 record
Historical coverageOriginal: HistoryPublished 5 Sept 2026

String Carried the Distinguished Name. It Did Not Become the Directory Entry: RFC 1485

The String Carried the Distinguished Name. It Did Not Become the Directory Entry: RFC 1485

RFC 1485 let an ASN.1 directory name leave the directory protocol and travel on a business card, in a mail message or through ordinary prose. The achievement was portability with structure. It did not make one typography canonical, preserve every encoding choice, or turn a reference to an entry into proof about the person, permission or outcome behind it.

Read Record
Open String Could Be Parsed Without Ambiguity. It Still Was Not the Directory Entry: RFC 1485 record
Historical coverageOriginal: HistoryPublished 5 Sept 2026

String Could Be Parsed Without Ambiguity. It Still Was Not the Directory Entry: RFC 1485

The String Could Be Parsed Without Ambiguity. It Still Was Not the Directory Entry: RFC 1485

A Distinguished Name could leave ASN.1, cross a business card or mail message, and return as the same ordered structure. That was an important interoperability result. It did not make the printed line canonical, summon a current directory entry, or prove who stood behind the name.

Read Record
Open Name Was Easy to Type. Its Identity Still Depended on the Directory Around It: RFC 1484 record
Historical coverageOriginal: HistoryPublished 5 Sept 2026

Name Was Easy to Type. Its Identity Still Depended on the Directory Around It: RFC 1484

The Name Was Easy to Type. Its Identity Still Depended on the Directory Around It: RFC 1484

A person could say a short, natural name and let the directory fill in types, hierarchy and spelling. The convenience was real because the omitted context still existed: inside the local environment, current entries, matching rules and the user’s final choice.

Read Record
Open PDU Arrived. Its Protocol May Still Have Been Agreed Elsewhere: RFC 1483 record
Historical coverageOriginal: HistoryPublished 5 Sept 2026

PDU Arrived. Its Protocol May Still Have Been Agreed Elsewhere: RFC 1483

The PDU Arrived. Its Protocol May Still Have Been Agreed Elsewhere: RFC 1483

RFC 1483 offered two ways to tell an ATM receiver what it had received. One put a protocol label in every AAL5 PDU. The other removed that label and made the virtual circuit carry its meaning. The bytes grew leaner, but the missing fact did not vanish; it moved into provisioning and call setup.

Read Record
Open IAB Endorsed CIDR. Four Different Actors Still Had to Make It Real: RFC 1481 record
Historical coverageOriginal: HistoryPublished 5 Sept 2026

IAB Endorsed CIDR. Four Different Actors Still Had to Make It Real: RFC 1481

The IAB Endorsed CIDR. Four Different Actors Still Had to Make It Real: RFC 1481

In July 1993, the Internet Architecture Board used a sentence that sounds like a finish line: it “endorses the CIDR architecture and its implementation.” The sentence mattered. It still did not allocate an address block, add classless code to a router, install that code in a network or produce a single aggregate in a global routing table. RFC 1481 was a coordination signal whose success depended on several actors retaining their own power to act.

Read Record
Open Aggregate Had a Home AS. That Did Not Mean Every Announcement Came From Home: RFC 1482 record
Historical coverageOriginal: HistoryPublished 5 Sept 2026

Aggregate Had a Home AS. That Did Not Mean Every Announcement Came From Home: RFC 1482

The Aggregate Had a Home AS. That Did Not Mean Every Announcement Came From Home: RFC 1482

RFC 1482 gave one aggregate a Home AS, then listed other ASs that would announce the same prefix to different neighbors. The table did not contradict itself. It recorded a chain of intended propagation in which origin, onward announcement, acceptance, installation and delivery remained separate facts.

Read Record
Open Name Existed in .US. That Did Not Mean the Zone Had Been Delegated: RFC 1480 record
Historical coverageOriginal: HistoryPublished 4 Sept 2026

Name Existed in .US. That Did Not Mean the Zone Had Been Delegated: RFC 1480

The Name Existed in .US. That Did Not Mean the Zone Had Been Delegated: RFC 1480

Two names could appear equally real beneath `.US` in 1993. One might be a direct MX entry for a UUCP host; another might sit inside a branch whose manager ran its own name servers. The resolver made both names visible. RFC 1480 did not give them the same authority, network attachment or operating obligations.

Read Record