RFC-248
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.