Discussion
RE: https://mastodon.online/@rfceditor/116653935307843868
Seeing the SSH protocols formalized and standardized is nice, but I also note that after 57 years of Internet RFCs, we're closing in on needing a fifth digit for numbering them.
Hopefully this epoch will require less preparation than Y2K did.
@mattblaze "Is YOUR system RFC10k compliant[tm]? Find out with this expensive piece of software that..."
@mattblaze @rfceditor RFC 1 is from April 1969. RFC 100 is February 1971. RFC 1000 is August 1987. But hey, the metadata is all machine-readable (https://www.rfc-editor.org/rfc-index.xml); let's fit a curve…
@mattblaze I've got a couple of 4-digit RFCs. Is there a marketplace where I can sell the numbers? Steve Crocker really going to clean up on this one!
@carlmalamud Number of digits in your first published RFC is like Erdos numbers for networking people.
@mattblaze @carlmalamud
The gulf between RFC9000 and RFC1436 is so great, I think we should just say specifically log10(id) is the metric. I assume mathematicians would approve.
@mattblaze @carlmalamud This has big "I have a six-digit ICQ account number" vibes
@mattblaze @carlmalamud When I was on the IAB, we were writing an RFC on cryptographic technology and the Internet. Looking at where we were in the numbering, I emailed Jon Postel and asked if it could be RFC 1984. Jon replied, "We never reserve RFC numbers—but coincidences can happen". Guess what happened…
@SteveBellovin
When we revised the JSON RFC7159 its successor was 8259, not by accident.
There are conversations in progress about whether there should be an RFC Ten Thousand and if so what it should be.
Install bonfire.cafe
Get the full app experience
