365 RFCs

Commenting on one RFC a day in honor of the 50th anniversary of the first RFC.

by Darius Kazemi, September 12 2019

In 2019 I'm reading one RFC a day in chronological order starting from the very first one. More on this project here. There is a table of contents for all my RFC posts.

An improvement

RFC-255 is titled “Status of Network Hosts”. It's authored by Ellen Westheimer of BBN and dated October 26, 1971.

The technical content

This is another report from BBN on the status of various ARPANET hosts in the same series as RFC-252, RFC-235, and RFC-240.

The numbers this time:

  • 47 dead
  • 41 open
  • 13 timed out
  • 6 half open
  • 1 refused

Analysis

The percentage of open connections has gone up to 38% from about 25%, so that's an improvement. In the intervening 20 days since RFC-252, we see the following changes:

  • Both of UCLA's hosts are completely online instead of intermittently offline
  • Utah has gone from completely dead to sometimes-timed-out
  • Harvard has gone from completely dead to sometimes-timed-out
  • SRI NIC is online more often

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 “@365-rfcs@write.as” and follow it there.

About me

I'm Darius Kazemi. I'm an independent technologist and artist. I do a lot of work on the decentralized web with ActivityPub, including a Node.js reference implementation, an RSS-to-ActivityPub converter, and a fork of Mastodon, called Hometown. You can support my work via my Patreon.

by Darius Kazemi, September 11 2019

In 2019 I'm reading one RFC a day in chronological order starting from the very first one. More on this project here. There is a table of contents for all my RFC posts.

A handbook (and a time machine)

RFC-254 (PDF) is titled “Scenarios for Using ARPANET Computers”. It's authored by Abhay Bhushan of MIT Project MAC and dated October 29, 1971.

The technical content

This is a massive RFC, and I think it's massively important for readers of this blog.

If you've ever wanted to know what it was like to connect to the ARPANET, and what a typical user might actually be doing while logged into remote computers, this is basically your Rosetta Stone.

This RFC is an example of the kind of handbook that an ARPANET host site user would have on hand, probably sitting on their desk as they accessed their terminal to connect to the network. Since this is from MIT Project MAC, this is their handbook, and it shows us what typical sessions of a user of their Dynamic Modeling Computer Graphics PDP-10 would look like.

The document is broken up into different sections illustrating typical interactions on each of 22 different ARPANET hosts. Each section lists the quirks of the particular system, like whether to engage in full or half duplex, what characters it considers valid, and whether it is line-at-a-time versus character-at-a-time.

I really recommend at least skimming the entire original scan to get a sense of the scope of what could be done on the network in 1971, but I'll include some of the more exciting highlights here.

The Network Information Center: chat and a forum

When a user logs in to the NIC there is normal sequence where you enter your site name as a login followed by the ARPA password as described in RFC-223. Once you're logged in you can enter a SYSTAT command to get a list of other people using the NIC system. With this information you can “link” your console to another user's console, and then type a message prepended with a semicolon, like so:

;hello are you there?

Followed by a carriage return, this will display on the console of the person you've “linked” to!

This chat service is actually provided by TENEX, the operating system that BBN wrote for the PDP-10, so other systems that use TENEX also have this chat functionality.

One bit of functionality that is not native to TENEX but rather custom to the NIC is their “NIC Journal” system, which is kind of a bulletin board or forum for posting messages for people to read!

You can type the command NLS to enter the NIC text editing system, TNLS. This opens up a new prompt for the TNLS program, at which point you can type the following to get access to the NIC Journal:

*execute journal
submit message
This is a test message.<EOT>

By typing <EOT> (“end of text”, I believe) the system knows that you've done typing your message content. Then it prompts you for a title (subject line) and id numbers of people known to the system. Then it posts your message.

Many of the records of this forum, known also as the SRI ARC Journal, are available on the Computer History Museum website as scans. If you'd like a taste of what was being posted to this forum, there's plenty at that link, though for a quick look you can see this PDF of forum posts from June and July 1971, just a few months before this booklet was published as an RFC. Yes there are big computer science papers posted in the forum but also more pedestrian stuff like IT requests for file access. See this one from page 111 of the linked PDF:

Ken..I guess I must have mis-understood what was to happen with respect to the group stuff. I am no longer in NLS' group (or whichever way it is supposed to be), which is innconvenient. [sic] Could things be fixed so I can write NLS' files again???
Thanks...Bill

“Bill” in this message is Bill Duvall, who received the first message on the ARPANET in 1969, writing to Kenneth E. Victor.

Utah: a paragon of security

The PDP-10 at the University of Utah features the password:

THISISANINTENTIONALLYLONGPASSWORD

This is the only known information about their system, as MIT has been unable to log in.

BBN: games of note

When connected to TENEX on the PDP-10 at BBN you have access to some games and toys. LIFE lets you play “game of life”, which I am assuming is Conway's Game of Life, invented just the year prior.

You can also type DOCTOR to speak to a pretend psychiatrist (sardonically noted in the booklet as “psychiatrist service--self-explanatory”)! You can read the full source code for a version of this program if you want to get a sense of what a chat with the doctor is like. I'll note that this program I've linked is probably a version that is far more developed than the 1971 edition but you get the idea!

I am glad that games are highlighted on the BBN PDP-10 because a few years after this, BBN's Will Crowther would write ADVENTURE for this very computer system, arguably the first interactive fiction computer game ever written.

Multics: customer service

If you're logged into MIT's Multics system, you can prefix a message with an apostrophe and it will go directly to a live “network consultant”! Their example of the kind of message you might want to send to start talking to the consultant is:

'Please help me on-line

There's also a local mail system between users on the system, editors, and all sorts of other Multics goodies.

Harvard: hello world

The Harvard section includes a simple FORTRAN “hello world” type program. In the following listing, . is the prompt for the operating system and * is the prompt for TECO, a text editor. The $ is apparently something that prints out if you type the <ALT> key. There are also carriage returns at the end of each line that I've omitted since they're obvious to a 2019 reader.

.R TECO
*| <TAB> TYPE 100
100 <TAB> FORMAT('HELLO THERE.')
<TAB>     END
<ESC>

*EWDSK:TEST.FOR$$$$
*PWEF$$$$
*<Ctrl+C>
.EXECUTE TEST.FOR

HELLO THERE

(A user could take this documentation and replace the one-line command to print “HELLO THERE” with any complex FORTRAN program they want.)

Lincoln Lab: contact Joel

Lincoln Lab's computer comes with the suggestion that people directly message Joel Winett with the message “HELP” if they panic!

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 “@365-rfcs@write.as” and follow it there.

About me

I'm Darius Kazemi. I'm an independent technologist and artist. I do a lot of work on the decentralized web with ActivityPub, including a Node.js reference implementation, an RSS-to-ActivityPub converter, and a fork of Mastodon, called Hometown. You can support my work via my Patreon.

by Darius Kazemi, September 10 2019

In 2019 I'm reading one RFC a day in chronological order starting from the very first one. More on this project here. There is a table of contents for all my RFC posts.

Golden Pavillion

RFC-253 is titled “Second Network Graphics Meeting Details”. It's authored by James A. Moorer of the Stanford AI Laboratory and dated October 19, 1971.

The technical content

This is the meeting formally announced in RFC-246. It gives the usual information about location, lodgings, and a Chinese food banquet at the Golden Pavillion in Los Altos.

Analysis

This RFC features an incredibly curious turn of phrase:

Attendees will be stored in the Flamingo Motel in Palo Alto at $8.25 a night.

Stored. Okay!

Here's the Golden Pavillion Restaurant and Motor Inn in all its 1960s glory, as found on various antique postcard websites:

A very retro building in mustard yellow without the usual exotic trappings of an American Chinese restaurant, though notably a big circular gate.

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 “@365-rfcs@write.as” and follow it there.

About me

I'm Darius Kazemi. I'm an independent technologist and artist. I do a lot of work on the decentralized web with ActivityPub, including a Node.js reference implementation, an RSS-to-ActivityPub converter, and a fork of Mastodon, called Hometown. You can support my work via my Patreon.

by Darius Kazemi, September 9 2019

In 2019 I'm reading one RFC a day in chronological order starting from the very first one. More on this project here. There is a table of contents for all my RFC posts.

New week, same numbers

RFC-252 is titled “Network Host Status”. It's authored by Ellen Westheimer of BBN and dated October 8, 1971.

The technical content

This is another report from BBN on the status of various ARPANET hosts in the same series as RFC-235 and RFC-240.

The numbers this time

  • 40 dead
  • 22 open
  • 17 timed out
  • 5 half open
  • none refused

These are essentially the same results network-wide as the last time these measurement were taken, though the pool of measurements is smaller because this report covers only seven days instead of ten.

Analysis

Wow the 1990s transcription of this report is bad. It gets Westheimer's last name wrong in the title page, and on subsequent headers her name is listed as... Wnetheimer.

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 “@365-rfcs@write.as” and follow it there.

About me

I'm Darius Kazemi. I'm an independent technologist and artist. I do a lot of work on the decentralized web with ActivityPub, including a Node.js reference implementation, an RSS-to-ActivityPub converter, and a fork of Mastodon, called Hometown. You can support my work via my Patreon.

by Darius Kazemi, September 8 2019

In 2019 I'm reading one RFC a day in chronological order starting from the very first one. More on this project here. There is a table of contents for all my RFC posts.

Weather data

RFC-251 is titled “Weather Data”. It's authored by Dale H. Stern of Computer Corporation of America, and dated October 13, 1971.

The technical content

This RFC informs the Network Working Group that the Datacomputer at Computer Corporation of America will be providing weather data from the United States Air Force Environmental Technical Applications Center. It's ten years of detailed surface and upper atmosphere weather data from around the world. It seems like this is going to be the first large, real-world data set provided to the network by the Datacomputer.

Further reading

The author, Dale Stern, was one of the principles behind the Datacomputer project at Computer Corporation of America. Here's a 1975 report authored by CCA on the Datacomputer which includes a paper by Stern and Thomas Marill in Appendix 1.

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 “@365-rfcs@write.as” and follow it there.

About me

I'm Darius Kazemi. I'm an independent technologist and artist. I do a lot of work on the decentralized web with ActivityPub, including a Node.js reference implementation, an RSS-to-ActivityPub converter, and a fork of Mastodon, called Hometown. You can support my work via my Patreon.

by Darius Kazemi, September 7 2019

In 2019 I'm reading one RFC a day in chronological order starting from the very first one. More on this project here. There is a table of contents for all my RFC posts.

Colliding ideas

RFC-250 is titled “Some Thoughts on File Transfer”. It's authored by Howard R. Brodie of UCLA and dated October 7, 1971.

The technical content

This RFC talks about some concerns the author has with RFC-171 and RFC-172, which respectively describe the Data Transfer Protocol and the File Transfer Protocol.

The concerns listed in this RFC are almost identical to Bob Braden's concerns in RFc-238, though the concern about sequence number is somewhat different than Braden's. Brodie is concerned that message sequence number in DTP is sometimes referenced as 8-bit and sometimes referenced as 16-bit.

Analysis

Seeing as Brodie and Braden are both based at UCLA I wonder if they had a conversation about these topics and independently filed RFCs about the same topic. The dates are close enough together that Brodie might not have seen Braden's RFC until after he submitted this one.

Also, Brodie argues for an 8-bit sequence number as “sufficient” compared to a 16-bit sequence number. This makes me cringe as I can easily imagine a sequence of more than 256 messages making up some kind of large file transfer!

Further reading

The only reference I can find to Howard Brodie is in the acknolwedgements section of Bob Metcalfe's Harvard Ph.D. dissertation, “Packet Communication”. This dissertation represents a huge chunk of the work that more or less led him to invent Ethernet and co-invent TCP/IP with Vint Cerf.

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 “@365-rfcs@write.as” and follow it there.

About me

I'm Darius Kazemi. I'm an independent technologist and artist. I do a lot of work on the decentralized web with ActivityPub, including a Node.js reference implementation, an RSS-to-ActivityPub converter, and a fork of Mastodon, called Hometown. You can support my work via my Patreon.

by Darius Kazemi, September 6 2019

In 2019 I'm reading one RFC a day in chronological order starting from the very first one. More on this project here. There is a table of contents for all my RFC posts.

Group discounts

RFC-249 is titled “Coordination of Equipment and Supplies Purchase”. It's authored by Raymond F. Borelli of the University of Illinois Center for Advanced Computation and dated October 8, 1971.

The technical content

It appears that the author and Steve Crocker and cooking up a scheme to coordinate the purchase of equipment network-wide to take advantage of group discounts. For example, if everyone on the network bought the same model terminal, then they could submit a purchase order to a company for a large order, split the costs, and enjoy the discount.

The author acknowledges that there might not be enough overlapping demand for equipment for a group rate to be feasible, and that some organizations require competitive bidding on large purchases which means they wouldn't fit into this scheme.

At any rate, they want to test the feasibility and include a sample form for sites to reply with their equipment needs so they can see if this makes sense as an idea.

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 “@365-rfcs@write.as” and follow it there.

About me

I'm Darius Kazemi. I'm an independent technologist and artist. I do a lot of work on the decentralized web with ActivityPub, including a Node.js reference implementation, an RSS-to-ActivityPub converter, and a fork of Mastodon, called Hometown. You can support my work via my Patreon.

by Darius Kazemi, September 5 2019

In 2019 I'm reading one RFC a day in chronological order starting from the very first one. More on this project here. There is a table of contents for all my RFC posts.

Not issued

RFC-248 was never issued.

Someone asked me recently why there are some RFC numbers that are not issued, rather than just filling in the RFC number with a new document.

My understanding is that RFC numbers were sometimes “reserved” with the Network Information Center for forthcoming papers. I believe that sometimes these papers never materialized, hence the RFC number without a document to go with it. I could be totally wrong on this.

In terms of today's RFC series and why nobody's ever gone back to fill these in, there are documents out there that state things like “RFC-248 was never issued”. If this were to change then those documents would go out of date. But... more on this in a future post about a long-lost RFC that I uncovered earlier this year.

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 “@365-rfcs@write.as” and follow it there.

About me

I'm Darius Kazemi. I'm an independent technologist and artist. I do a lot of work on the decentralized web with ActivityPub, including a Node.js reference implementation, an RSS-to-ActivityPub converter, and a fork of Mastodon, called Hometown. You can support my work via my Patreon.

by Darius Kazemi, September 4 2019

In 2019 I'm reading one RFC a day in chronological order starting from the very first one. More on this project here. There is a table of contents for all my RFC posts.

Actual comments

RFC-247 is titled “Proferred Set of Standard Host Names”. It's authored by Peggy Karp of MITRE and dated October 12, 1971.

The technical content

This RFC is the first one to make me laugh out loud since the early days of RFCs. The document opens:

In RFC #226, BBN's TENEX list of Host names was set up as a strawman set of standard Host names.  Comments received since then (an RFC actually generated comments!!!) have influenced me to propose the following general rules for forming Host names.

You'll recall that her RFC-226 garnered at least five responses in RFC form as well as one or two others that were written at least partially in response.

She takes feedback into account and proposes a different host site naming scheme. She gives an algorithm for choosing the name! She proposes a name be of the form <site>-<machine>.

If a site name is shorter than 5 characters, use the full name. If not, use the standard acronym, if that is shorter than 5 characters. If not, use the standard abbreviation, if shorter than 5 characters. Failing that, use the first four letters (for example, MITRE is always MITRE, so she would suggest “MITR” for the site name). Failing that, the site itself should pick something appropriate shorter than 5 characters.

The machine is a designation for the computer being connected to and uses similar rules for picking the name.

The RFC ends with a potential 2-byte implementation where the first byte maps to a site from some kind of known table, and the same goes for the machines.

Analysis

I'd argue that the word “proferred” in the title was very intentionally chosen to invoke Steve Crocker's seminal RFCs, RFC-54 and RFC-123. These RFCs were the foundations of protocols that went on to define the early ARPANET and I think this was a smart rhetorical move by Karp in response to the rather intense response she got to her RFC-226. I believe her making light with her “an RFC actually generated comments!!!” is another classic move used to defuse a tense situation.

I think the other authors in conversation with Karp had a good point that machines will change often so it might not make sense to name a host after its machine. Also maintaining two tables, one for site-to-integer mapping and one for machine-to-integer mapping, seems like a lot of work and highly error-prone! So I'm not a fan of what is being proposed here.

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 “@365-rfcs@write.as” and follow it there.

About me

I'm Darius Kazemi. I'm an independent technologist and artist. I do a lot of work on the decentralized web with ActivityPub, including a Node.js reference implementation, an RSS-to-ActivityPub converter, and a fork of Mastodon, called Hometown. You can support my work via my Patreon.

by Darius Kazemi, September 3 2019

In 2019 I'm reading one RFC a day in chronological order starting from the very first one. More on this project here. There is a table of contents for all my RFC posts.

New dates

RFC-246 is titled “Network Graphics Meeting”. It's authored by Al Vezza of MIT and dated October 5, 1971.

The technical content

RFC-232 let everyone know that the Network Graphics Meeting was going to be postponed to November or December and would still be held somewhere near San Francisco. This RFC lets everyone know that the new dates are November 21-23, 1971 and the meeting will be held at the Stanford Artificial Intelligence Project.

Analysis

According to the latest stats from RFC-240, the Stanford AI group's ARPANET connection has been fully dead. I'm wondering if hosting this meeting will spur them to get back online. It's happened before with other meeting hosts who were seemingly shamed into fixing their network implementations!

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 “@365-rfcs@write.as” and follow it there.

About me

I'm Darius Kazemi. I'm an independent technologist and artist. I do a lot of work on the decentralized web with ActivityPub, including a Node.js reference implementation, an RSS-to-ActivityPub converter, and a fork of Mastodon, called Hometown. You can support my work via my Patreon.

Enter your email to subscribe to updates.