WYAE - Joke-RfCs
While a "normal" RfC (Request for Comments) usually defines internet
standards and protocols, there are a number of RfCs and HowTos published
on 1st of April -
or for a similar purpose. Well, some (RfC 1149 and 2322) in fact were
implemented or are in practical use. Read and have fun...
- Russian Tea HowTo V3.0
- Caffeine is essential for keeping the brain active during nightly
hacking sessions. There are, however, many ways to satisfy a hacker's
need for caffeine. Drinking Canned Capitalism (Coke) contradicts the
very principles of the open source movement, for it is a closed
source product, manufactured by a huge, evil corporation.
(additionally: Version 2.0)
- RfC 527 (1973)
- ARPAWOCKY
- RfC 748 (1978)
- Telnet Randomly-lose option
- RfC 1097 (1989)
- Telnet subliminal-message option
- RfC 1149 (1990)
- Standard for the transmission of IP datagrams on avian carriers
- The first implementation was B2P (back to Pigeons) April 2001 in Bergen, Norway.
A later implementation (FiFly, March 2004, Israel)
reached 2,27Mbit/s data transfer rate (very high latency, though) - and a later one (September 2009) about 4 Mbit/s
http://pigeonrace2009.co.za/ (also extremely high latency).
In April 2005 an
even higher throughput was achieved with adhesive surface-mounted
carriers (SNAP = SNAil-based data transfer Protocol, 37 Mbit/s).
- RfC 1216 (1991)
- Gigabit network economics and paradigm shifts
- RfC 1217 (1991)
- Memo from the Consortium for Slow Commotion Research
- RfC 1313 (1992)
- Today's Programming for KRFC AM 1313 Internet Talk Radio
- RfC 1437 (1993)
- The Extension of MIME Content-Types to a New Medium
- RfC 1438 (1993)
- Internet Engineering Task Force Statements Of Boredom (SOBs)
- RfC 1605 (1994)
- SONET to Sonnet Translation
- RfC 1606 (1994)
- A Historical Perspective On The Usage Of IP Version 9
- RfC 1607 (1994)
- A view from the 21st century
- RfC 1776 (1995)
- The Address is the Message
- RfC 1882 (1995)
- The 12-Days of Technology Before Christmas
- RfC 1924 (1996)
- A Compact Representation of IPv6 Addresses
- RfC 1925 (1996)
- The Twelve Networking Truths
- RfC 1926 (1996)
- An Experimental Encapsulation of IP Datagrams on Top of ATM
- RfC 1927 (1996)
- Suggested Additional MIME Types for Associating Documents
- RfC 2100 (1997)
- The Naming of Hosts
- RfC 2321 (1998)
- RITA -- The Reliable Internetwork Troubleshooting Agent
- RfC 2322 (1998)
- Management of IP numbers by peg-dhcp
- RfC 2322 actually is being used successfully at hacking camps like HIP
(Hacking in Progress) or the CCCamp. In a different area it is widely
(and successfully) used: to handle frequency usage at clubs for RC
model planes (cars, ships, ...)
- RfC 2323 (1998)
- IETF Identification and Security Guidelines
- RfC 2324 (1998)
- Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)
- RfC 2325 (1998)
- Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2
- RfC 2549 (1999)
- IP over Avian Carriers with Quality of Service
- RfC 2550 (1999)
- Y10K and Beyond
- RfC 2551 (1999)
- The Roman Standards Process -- Revision III
- RfC 2795 (2000)
- The Infinite Monkey Protocol Suite (IMPS)
- RfC 3091 (2001)
- Pi Digit Generation Protocol
- RfC 3092 (2001)
- Etymology of 'Foo'
- RfC 3093 (2001)
- Firewall Enhancement Protocol (FEP)
- RfC 3251 (2002)
- Electricity over IP - Mostly Pointless Lamp Switching (MPLampS)
- RfC 3252 (2002)
- Binary Lexical Octet Ad-hoc Transport (BLOAT)
- RfC 3514 (2003)
- The Security Flag in the IPv4 Header
- There even was a patch submitted to the Linux kernel by Hugo Mills <hugo@carfax.org.uk>
(Thu, 1 Apr 2004 13:06:38 +0100, to linux-kernel@vger.kernel.org, netfilter-devel@lists.netfilter.org)
which implements definition, handling and filtering of the "Evil" bit defined in this RfC.
(http://linux.derkeiler.com/Mailing-Lists/Kernel/2004-04/0168.html)
- RfC 3751 (2004)
- Omniscience Protocol Requirements
- RfC 4041 (2005)
- Requirements for Morality Sections in Routing Area Drafts
- RfC 4042 (2005)
- UTF-9 and UTF-18
- RfC 4144 (2005)
-
How to Gain Prominence and Influence in Standards Organizations
(not sure about this one - real, valid content but not feeling RfC-ish)
- RfC 4824 (2007)
-
The Transmission of IP Datagrams over the Semaphore Flag Signaling System (SFSS)
- RfC 5241 (2008)
-
Naming Rights in IETF Protocols
- RfC 5242 (2008)
-
A Generalized Unified Character Code: Western European and CJK Sections
- RfC 5513 (2009)
-
IANA Considerations for Three Letter Acronyms
- RfC 5514 (2009)
-
IPv6 over Social Networks
- RfC 5841 (2010)
-
TCP Option to Denote Packet Mood
- RfC 5984 (2011)
-
Increasing Throughput in IP Networks with ESP-Based Forwarding: ESPBasedForwarding
- RfC 6214 (2011)
-
Adaptation of RFC 1149 (IP over avian carriers) for IPv6
- RfC 6217 (2011)
-
Regional Broadcast Using an Atmospheric Link Layer
- RfC (draft) (2012)
-
An M-party, N-state Game of Rochambeau
a formalization of playing Rock-Paper-Scissors-Spock and variants
- RfC 6919 (2013)
-
Further Key Words for Use in RFCs to Indicate Requirement Levels (extending RFC 2119)
For Joke-RfCs after 2012 please see the Wikipedia page.
