April Fools Day RFC's are a grand tradition. My favorite is "The Extension of MIME Content Types to a New Medium", RFC 1437... complete with extremely dated Dan Quayle joke. IP over Avian Carriers, RFC 2549, is a close second.
Whenever someone says "...but why don't we just implement a security feature which denies access to clients that try to do X?" where X is something extremely vague like "steal money" that is really hard to translate into an algorithm that could conceivably be implemented, I reply by noting that unfortunately their idea won't work since malware authors have such a low rate of RFC 3514 adoption.
Comments
April Fools Day RFC's are a grand tradition. My favorite is "The Extension of MIME Content Types to a New Medium", RFC 1437... complete with extremely dated Dan Quayle joke. IP over Avian Carriers, RFC 2549, is a close second.
Yes, but RFC 2549 was actually implemented in Norway, successfully sending a ping and receiving responses: https://en.wikipedia.org/wiki/IP_over_Avian_Carriers#Real-li...
HTTP error response code 418 (RFC2324) is my favorite because many servers have actually implemented it. The recent RFC7168 extends it.
I loved the IP Avian Carriers too. My favorite is "Hyper Text Coffee Pot Control Protocol" or RFC 2324, defining the HTTP error 418 "I'm a teapot".
Whenever someone says "...but why don't we just implement a security feature which denies access to clients that try to do X?" where X is something extremely vague like "steal money" that is really hard to translate into an algorithm that could conceivably be implemented, I reply by noting that unfortunately their idea won't work since malware authors have such a low rate of RFC 3514 adoption.