Vint Cerf's Christmas networking RFC ends with an off-by-one index
The December 1985 document puts an ARPANET hacker inside holiday verse, with protocol names where the reindeer usually go.
The network is down, the engineers are miserable and the salesmen are asleep. Vint Cerf’s Christmas poem knew exactly which part of the organization would be enjoying the holiday.
RFC 968, dated December 1985, is titled ’Twas the Night Before Start-up. It borrows the familiar holiday-verse structure and populates it with packets, diagnostics and a visiting ARPANET hacker. The result is an official-looking document with remarkably little interest in being a configuration manual.
Its status paragraph says it discusses network startup problems and debugging techniques. The verse delivers those themes through a rescue story: a silent network, a competent visitor, one suspect line and a patch that gets traffic moving.
The protocol roll call supplies the seasonal joke. LAPB, OSI and X.25 appear alongside TCP, SNA and V.35. Anyone expecting hooves on the roof instead gets another reminder that the network room has no comfortable chairs.
The closing culprit is “an off-by-one index,” in Cerf’s own words. That is the payoff within the poem. RFC 968 does not identify a real company’s outage, document an affected product or provide a reproducible incident timeline. Turning its story into a historical postmortem would give the verse a job it never applied for.
That distinction makes this a good small piece of internet history to pass along. The artifact itself is the evidence. Readers can open the short text, see the date and attribution, and follow the joke without relying on somebody’s recollection of what a standards document is supposed to sound like.
It is also a reminder to read a technical document’s purpose before treating its number as authority for a claim. An RFC number tells you where the text is filed. The text still has to tell you what it is doing. Here, the meter is a rather strong clue.
For someone sharing it with a team, the funny part survives better with that context attached. Calling it a networking poem sets expectations. Calling it proof that one famous bug took down a particular network adds a story the source never supplies.
The indexing joke works because the repair is small compared with the anxiety around it. The engineers have cards and dumps; the visitor finds one suspect line. Anyone who has stared at a failure caused by a tiny boundary error can recognize the emotional shape without pretending this is an engineering report.
The salesmen remain an especially efficient bit of characterization. Their pleasant dreams sit beside the people handling the actual startup. Cerf gives the reader the organizational tension in a few rhyming lines, which is more than some incident documents manage in an entire executive overview.
The document can be enjoyed as it stands. There is no missing implementation to install, and no benchmark to improve. A holiday reading in the network room would be a perfectly defensible use of it, provided somebody checks whether the live network is still running.
Even the punchline has a boundary.