by Darius Kazemi, April 10 2019
RFC-100 is titled “Categorization and Guide to NWG/RFCs”. It's by Peggy M. Karp of MITRE and dated February 26th, 1971.
The technical content
This document lists all RFCs to date, first by category, then in numerical order with cross references to the categories for the documents. It's similar to how card catalog systems used to organize documents at libraries, which if you are of a certain age you'll remember using. (I suspect I'm on the cusp and most people younger than me never used these.)
The document offers a “minimum subset of RFCs”, which are basically the must-read RFCs for anyone who wishes to be caught up to NWG discussions as of February 1971. And further, that the list is short enough that it “should dispel any fear of maintaining stacks of NWG/RFCs for quick reference.”
The subset is as follows (links to my own blog posts and their titles):
- RFC-5: DEL – the rich application layer that never was
- RFC-12: Flowcharts
- RFC-30: Adding Stanford and Carnegie Mellon
- RFC-31: Down with long boxes
- RFC-32: Crystals
- RFC-33: New concepts for the network
- RFC-41: Please provide timestamps
- RFC-47: Potential embarrassment
- RFC-48: Plateaus
- RFC-51: NIL
- RFC-53: Making things official
- RFC-54: A proffering
- RFC-55: Squishy amoebas
- RFC-56: A bit of a hit-and-run
- RFC-60: A simpler NCP
- RFC-62: A revision of another shot at interprocess communication
- RFC-66: Levels
- RFC-74: A working NCP
- RFC-76: A new kind of Host
- RFC-77: A three-day meeting
- RFC-78: Human factors
- RFC-80: Adaptive mechanisms
- RFC-81: Please send reading materials
- RFC-82: A fly on the wall
- RFC-83: A Language-Machine
- RFC-86: A simple drawing format
- RFC-87: A network graphics meeting
- RFC-88: Punch cards and printers
- RFC-89: Historic moments
- RFC-90: A resource to be shared
- RFC-91: Thinking about users
- RFC-94: Graphics suggestions
- RFC-95: Paper
- RFC-96: An experiment
- RFC-97: A Telnet protocol
- RFC-98: Logging in
- RFC-99: Atlantic City again
As well as this very RFC and the next two, 101 and 102.
The categories listed are, broadly:
- Host/IMP Protocol (Level 1)
- Host/Host Protocol (Level 2)
- Subsystem Level Protocol (Level 3)
- Measurement of Network
- Network Experience
- Site Documentation
Most categories have sub-categories that you can read in the original document.
This document is slated to become part of a separate, non-RFC series of documents, although I'm not sure if that series ever came to pass (there are many more of these catalogs in the RFC series itself over the years).
This document is RFC-100 but the author notes at the beginning that there are already 102 RFCs. And indeed, RFCs 101 and 102 are dated three days before this one. I don't know if they simply wanted RFC-100 to be used for this catalog, or if the RFC numbers were assigned prior to the final RFC being sent to the NWG members.
The list of categories is the first official confirmation of levels 1, 2, and 3.
The author notes that
reference to “#33, #66, #83, etc.” is a convenient shorthand (reminiscent of the old corny joke about joke #s) used extensively during meetings.
The joke referred goes something like this: a guy goes to prison. He becomes aware of a weird phenomenon where he'll hear someone yell a number like “71!” and people laugh. His bunk mate explains to him that the jokes here are so stale and repetetive that they've just numbered them all to save time. So the guy yells out a random number. At this point the punchline is either: everyone laughs and says “wow we've never heard that one before”, or nobody laughs and the bunkmate says “wow, some guys just are no good at telling jokes.”
I assume the implication here is that attending a Network Working Group meeting is more or less like being in prison.
How to follow this blog
You can subscribe to this blog's RSS feed or if you're on a federated ActivityPub social network like Mastodon or Pleroma you can search for the user “@firstname.lastname@example.org” and follow it there.