Most RFCs specify a wire format, an algorithm, or an architectural principle. RFC 2235 specifies nothing. It is a chronological timeline of the Internet from 1957 through 1997, formally published as an Informational RFC. That alone makes it worth knowing about — the RFC series was flexible enough to absorb a historian's scrapbook alongside TCP and BGP.

What problem does it solve? By the mid-1990s, the Internet was exploding into public consciousness and journalists, policy-makers, and new engineers kept re-inventing the origin story badly. Zakon had been maintaining "Hobbes' Internet Timeline" as a web document at the Internet Society since 1993. Turning it into an RFC gave it a citeable, archived, permanent identifier — the same reason we cite RFC 793 for TCP. It became the canonical dated history you could point to when someone claimed Al Gore invented the Internet or that TCP/IP shipped in the 1980s.

What's actually in it? A dense, year-by-year (and often month-by-month) log of milestones organized into four rough eras:

• Genesis (1957–1968): Sputnik, the founding of ARPA, Licklider's "Galactic Network" memos, Baran and Davies independently inventing packet switching, the 1968 ARPANET contract to BBN.
• ARPANET (1969–1982): The first IMP at UCLA, the "LO" first message, Tomlinson's @-sign email in 1971, TCP replacing NCP on flag day (1 January 1983).
• Internet (1983–1989): DNS replacing HOSTS.TXT, NSFNET, the Morris Worm, the emergence of commercial ISPs.
• Web (1990–1997): Berners-Lee at CERN, Mosaic, the NSFNET decommissioning in 1995, the Netscape IPO, ICANN's precursors.

Interleaved with the technical milestones are growth statistics — host counts, domain counts, traffic on backbones — which is why the document is still cited today. If you need a defensible number for "hosts on the Internet in January 1993" (1,313,000), this is where it comes from.

Design decisions worth noting. Zakon chose to include social and cultural events alongside pure protocol history: the first spam (1978, Digital Equipment sales pitch to ARPANET users), the first emoticon (Fahlman, 1982), the first web-ordered pizza (Pizza Hut, 1994). This was deliberate — the timeline treats the Internet as a socio-technical system, not just a stack of protocols. That framing has aged extremely well; it's the same lens modern Internet governance scholarship uses.

Why it still matters. Three reasons. First, it's a reminder that the RFC series is a publication venue, not just a spec repository — the April 1st RFCs get the attention, but there's a whole tradition of Informational RFCs (poetry in RFC 1121, the Tao of IETF in RFC 4677) that keep institutional memory. Second, when you're debugging a legacy protocol and wondering "why on earth did they design it this way in 1985?", the timeline gives you the surrounding context: what hardware existed, what the host count was, what NSFNET's AUP forbade. Third, Zakon's timeline is still maintained at zakon.org, well past the RFC's 1997 freeze — but the RFC remains the authoritative snapshot of what "the story of the Internet" looked like from inside the community at the moment the web went mainstream.

Read it once. It takes twenty minutes and it will change how you interpret every other RFC.