Developers and techies in general are not usually viewed as the most interesting people on the planet.
Popular culture portrays a caricature of a shy man who is comfortable only when spitting out code to a terminal interface.
This is of cos wholly misguided in fact a very important part of the process of writing an Internet Engineering Task Force (IETF) standard is the submission of a Request For Comment (RFC).
The submission process is informal by design and in addition to standards, survey results and philosophical basis for future RFCs are routinely submitted.
More interesting however is an April 1st culture of a joke RFC. While RFCs normally need to go through several stages including starting out their life as Internet-Drafts, joke RFCs don’t have to go through any of that and become instant published RFCs.
This tradition has come up with quite some gems including:
A Standard for the Transmission of IP Datagrams on Avian Carriers RFC 1149
This memo describes an experimental method for the encapsulation of IP datagrams in avian carriers. This specification is primarily useful in Metropolitan Area Networks. This is an experimental, not recommended standard. Distribution of this memo is unlimited.
Hyper Text Coffee Pot Control Protocol RFC 2324
This document describes HTCPCP, a protocol for controlling, monitoring, and diagnosing coffee pots.
Scenic Routing for IPv6 RFC 7511
This document specifies a new routing scheme for the current version of the Internet Protocol version 6 (IPv6) in the spirit of "Green IT", whereby packets will be routed to get as much fresh-air time as possible.
You can find this and the complete catalog of RFC jokes here https://en.wikipedia.org/wiki/April_Fools%27_Day_Request_for_Comments
Do you have any other RFCs or geek culture you find interesting? Share it with us on the comment section below.