RFCs

RFCs (Requests For Comments) are the documents that define how the Internet works.

Since 1969 the IETF and its forerunners have used them to publish protocols, conventions, and ideas, one numbered memo at a time.

Most RFCs are dry technical specifications. But a small subset of those are something entirely different: they describe the Internet's culture - how to behave on it, how it governs and remembers itself, and the jokes it tells about itself.

This site

This site will list a couple of those cultural RFCs, converting original plain text into HTML + some additions. That said, while RFCs are authoritative historical documents - this site is merely a fan site. The text will be as true to original, but some things will be different. Every RFC page links back to the authoritative text at the RFC Editor.

  • Most of this information is decades old. Some of it might be irrelevant nowadays.
  • Some links are dead. Some - will be replaced for active ones.
  • Some things will have additional links, just for fun.

At its core it will be the FYI subseries on etiquette, history, and security written for people, plus a a few documents on how the IETF works and the long-running April Fools' tradition.

Random links

  • Internet Top Ten Lists (https://www.savetz.com/topten/), an unpublished book of Internet history, statistics, trivia, and culture, circa 1994
  • A first access internet tutorial (/docs/firstaccess.pdf). "Results show that a 59 percent improvement occurred in student ability as a result of using the tutorial"

Etiquette

How to conduct yourself online - electronic mail, mailing lists and newsgroups, and the fine art of not becoming a nuisance.

  • RFC 1855 - Netiquette Guidelines (FYI 28)
    The canonical guide to behaving online. Mail, chat, mailing lists, newsgroups.
  • RFC 2635 - DON'T SPEW: Guidelines for Mass Unsolicited Mailings and Postings (FYI 35)
    The anti-spam etiquette followup. Why flooding the network makes enemies.
  • RFC 3098 - How to Advertise Responsibly Using E-Mail and Newsgroups (FYI 38)
    If you must market on the net, how not to be a pest about it.

Culture

The network as a human place - naming your machine, art on the wires, and where the word "foo" actually came from.

  • RFC 1178 - Choosing a Name for Your Computer (FYI 5)
    Short, fun, and still correct. Don't name your machine after something you'll regret.
  • RFC 3092 - Etymology of "Foo"
    Where foo, bar, and foobar actually come from. Yes, there is a real answer.

Reference

The Internet explaining itself - glossaries, a timeline of milestones, and the people who built it.

  • RFC 1336 - Who's Who in the Internet: Biographies of IAB, IESG and IRSG Members
    Faces and names of the early architects. A who-was-who.
  • RFC 1983 - Internet Users' Glossary (FYI 18)
    What all the words meant, back when they still needed explaining.
  • RFC 2235 - Hobbes' Internet Timeline (FYI 32)
    The history of the net up to 1997, in milestone form. A snapshot of a snapshot.

Governance

How the IETF actually works, and the rare moments it takes a stand.

  • RFC 7258 - Pervasive Monitoring Is an Attack
    The closest the IETF comes to a political statement. Mass surveillance is a threat to be engineered against.

Humor

The April Fools' tradition - IP over carrier pigeon, a coffee-pot protocol, the evil bit, and faster-than-light delivery.

  • RFC 1149 - A Standard for the Transmission of IP Datagrams on Avian Carriers
    IP over carrier pigeon. Yes, someone implemented it. Yes, it worked.
  • RFC 2324 - Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)
    The origin of HTTP status code 418 "I'm a teapot."
  • RFC 3514 - The Security Flag in the IPv4 Header
    The evil bit. Packets with malicious intent are now clearly labeled, as required.
I survived Y2K!Best viewed with EYESNeoCities - Your Home On the Web - Free Web PagesThis site is made with zedfoobar2000. Plays music.Don't feed the fish!Lynx Now!Proudly zero-javascript!