by Darius Kazemi, June 24 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.

Socket length concerns

RFC-175 is titled “Comments on “Socket Conventions Reconsidered”“. It's authored by Harslem and Heafner of RAND, and dated June 11th 1971.

The technical content

In this RFC the authors comment on RFC-167, with one important exception: they think that, due to memory restritctions on the TIP (terminal IMP, the new IMP produced by BBN), sockets should be 16 bits long and not 32 bits long.

They also state that at least for programs in development at RAND, they won't need repeatable socket names except for the Initial Connection Protocol (ICP) sockets, since the ICP can broker all new socket assignments.

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.