by Darius Kazemi, December 24 2019
RFC-358 was never issued, even though its existence was promised in RFC-357. I think what happened was: 357 referenced 358, but they never got around to writing it. But because 358 was already referenced, the NIC couldn't just assign that number to the next available RFC, because the reference was in place and it would be confusing to go look up 358 thinking you'd get satellite uplink discussions and instead see something totally unrelated.
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 “@email@example.com” and follow it there.
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.