The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED BUT REPULSIVE", "WRONG BUT WROMANTIC", "FREQUENTLY MISUNDERSTOOD", "NOBODY BOTHERS WITH THIS BIT", "SHOULDN'T REALLY BUT WE WON'T JUDGE", "REQUIRED IN ORDER TO WORK AROUND EVERYONE ELSE'S BUGS", "YOU DO YOU", and "OBVIOUSLY ABSURD BUT VERY COMMON FOR SOME REASON" in this document are to be interpreted as described in RFC 2119.
@simontatham Plus the ever popular "WE DON'T KNOW WHAT WE WERE THINKING, IT WAS 3AM WE WERE EXTREMELY DRUNK AND THERE WAS ALSO A DONKEY WHICH WE SHALL NEVER SPEAK OF AGAIN"
@wordshaper a certain piece of software I regularly use, which shall remain nameless unless anyone else in this thread recognises it, currently has the official version number "wtf 11pm pub"
@simontatham The key words "MUST (BUT WE KNOW YOU WON'T)", "SHOULD CONSIDER", "REALLY SHOULD NOT", "OUGHT TO", "WOULD PROBABLY", "MAY WISH TO", "COULD", "POSSIBLE", and "MIGHT" in this document are to be interpreted as described in RFC 6919.
@anticomposite @simontatham tfw the IETF thought of your shitpost even before you did.
@can @anticomposite shitpost it may have been, but it's been a pretty popular one so far. Guess nobody else had seen RFC 6919 either!
@simontatham just now realising those instructions explain how to interpret "must", "should", etc but not "are to" :) :) :)
The key words "WHAT", "DAMNIT", "GOOD GRIEF", "FOR HEAVEN'S SAKE", "RIDICULOUS", "BLOODY HELL", and "DIE IN A GREAT BIG CHEMICAL FIRE" in this memo are to be interpreted as described in [RFC2119].
https://fanf2.user.srcf.net/hermes/doc/qsmtp/draft-fanf-wtf8.html#anchor2
@simontatham @can @anticomposite
You've got some good ones that are still missing. Please submit a new rfc.
@simontatham@hachyderm.io the lack of these terms in RFC 2119 should be submitted as an erratum (to RFC 2119)
@amyipdev @simontatham Mentioned up-thread is an RFC that adds to 2119; though it doesn't define these terms it does define MUST BUT WE KNOW YOU WON'T, among others: https://datatracker.ietf.org/doc/html/rfc6919
@Two9A@hachyderm.io @simontatham@hachyderm.io this actually got designated as an experimental protocol? lolllll
What I've always liked about RFC6919 is that for *every* so called "key word" it "standardises" it provides an actual example from an actual non-humorous RFC which uses that exact phrase.
Making fun of yourself the right way.
@anticomposite @simontatham
- replies
- 1
- announces
- 4
- likes
- 11
@simontatham I'm stealing "wromantic". It gels nicely with "scareoused".
@tryst alas, I can't claim credit for actually inventing that word. That's lifted from Sellar & Yeatman's "1066 And All That", in its description of the English Civil War: the Cavalier side was described as "Wrong but Wromantic", and the Roundheads were "Right but Repulsive".
@anticomposite @EdG @simontatham Is there any form of humor more absolutely niche than IETF RFC jokes? Like these are for an audience of dozens…luckily we are all on Fedi.
I was actually online on the morning of April 1, 1990 when the canonical example, “RFC 1149 - A Standard for the Transmission of IP Datagrams on Avian Carriers” dropped*, and it is deeply embedded in my headcanon Internet Timeline of Important Events. But I run into supposed industry professionals (even network and security admins!) who are completely unaware of this seminal document with alarming frequency.
(*) the standard has since updated twice, once to add Quality of Service and once to add IPv6 support. A real world implementation was only partially successful, as latency and packet loss were substantial. The whole protocol is nerdvana and the commitment to the bit is exemplary…
@
@dwenius @anticomposite @EdG avian carriers are all very well, but I think 418 I'm A Teapot is more iconic.
I proposed a 1st April RFC myself once, but it wasn't accepted. At the time SSH-2 was still considering a "none" cipher, for countries outlawing encryption: you wouldn't encrypt, but would still MAC, so the spooks could read but not hijack your session. I proposed adding the "rot13" cipher instead, to protect network-monitoring sysadmins from movie spoilers and distractingly juicy gossip.
@simontatham @can @anticomposite I did not notice this at first. 🤣
@simontatham @anticomposite definitely funny! The fact that there's an actual RFC for it makes it even funnier imo
@wouter I had only read the abstract, but thanks to your note I had to read the whole thing. It's brilliant.
My favorite reference:
The phrase "MIGHT" conveys a requirement in an intentionally stealthy fashion, to facilitate product differentiation (cf. "COULD" above).For example: "In the case of audio and different "m" lines for different codecs, an implementation might decide to act as a mixer with the different incoming RTP sessions, which is the correct behavior."
I just adore that passive aggressive "... which is the correct behavior" and would love to hear the anecdote for why the editor snuck that in there and how many chairs were thrown during the meeting.