 |
Fake
| | RFCs - Internet, Computers 3,143
 Joke RFCsJoke RFCs
 Index of RFCs created for humorous purposes.
|
RFC 3252: Binary Lexical Octet Ad-hoc TransportRFC 3252: Binary Lexical Octet Ad-hoc Transport
 A reformulation of IP and two transport layer protocols (TCP and UDP) as XML applications (April 1, 2002)
|
RFC 3251: Mostly Pointless Lamp SwitchingRFC 3251: Mostly Pointless Lamp Switching
 A description of an architecture for carrying electricity over IP. (April 1, 2002)
|
RFC 2795: The Infinite Monkey Protocol Suite (IMPS)RFC 2795: The Infinite Monkey Protocol Suite (IMPS)
 A protocol suite which supports an infinite number of monkeys that sit at an infinite number of typewriters in order to determine when they have either produced the entire works of William Shakespeare or a good television show. (April 1, 2000)
|
RFC 2549: IP over Avian Carriers with Quality of Service (FTP)RFC 2549: IP over Avian Carriers with Quality of Service (FTP)
 "This memo amends RFC 1149, 'A Standard for the Transmission of IP Datagrams on Avian Carriers', with Quality of Service information. This is an experimental, not recommended standard." (April 1, 1999)
|
RFC 2551: The Roman Standards Process -- Revision III (FTP)RFC 2551: The Roman Standards Process -- Revision III (FTP)
 "This memo documents the process used by the Roman community for the standardization of protocols and procedures. It defines the stages in the standardization process, the requirements for moving a document between stages and the types of documents used during this process. It also addresses the intellectual property rights and copyright issues associated with the standards process." (April 1, 1999)
|
RFC 2550: Y10K and Beyond (FTP)RFC 2550: Y10K and Beyond (FTP)
 "As we approach the end of the millennium, much attention has been paid to the so-called "Y2K" problem. Nearly everyone now regrets the short-sightedness of the programmers of yore who wrote programs designed to fail in the year 2000. Unfortunately, the current fixes for Y2K lead inevitably to a crisis in the year 10,000 when the programs are again designed to fail. This specification provides a solution to the "Y10K" problem which has also been called the "YAK" problem (hex) and the "YXK" problem (Roman numerals)." (April 1, 1999)
|
RFC 2325: Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2 (FTP)RFC 2325: Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2 (FTP)
 This RFC "defines objects for the management of coffee-brewing and maintenance devices." (April 1, 1998)
|
RFC 2324: Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0) (FTP)RFC 2324: Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0) (FTP)
 "This document describes HTCPCP, a protocol for controlling, monitoring, and diagnosing coffee pots." (April 1, 1998)
|
RFC 2323: IETF Identification and Security Guidelines (FTP)RFC 2323: IETF Identification and Security Guidelines (FTP)
 "This RFC is meant to represent a guideline by which the IETF conferences may run more efficiently with regards to identification and security protocols, with specific attention paid to a particular sub-group within the IETF: "facial hairius extremis". This document will shed further illumination on these problems and provide some possible solutions. This memo provides entertainment for the Internet community. It does not specify an Internet standard of any kind, but is rather unstandard, actually. Please laugh loud and hard." (April 1, 1998)
|
RFC 2321: RITA -- The Reliable Internetwork Troubleshooting Agent (FTP)RFC 2321: RITA -- The Reliable Internetwork Troubleshooting Agent (FTP)
 "A Description of the usage of Nondeterministic Troubleshooting and Diagnostic Methodologies as applied to today's complex nondeterministic networks and environments." (April 1, 1998)
|
RFC 1924: A Compact Representation of IPv6 Addresses (FTP)RFC 1924: A Compact Representation of IPv6 Addresses (FTP)
 "IPv6 addresses, being 128 bits long, need 32 characters to write in the general case, if standard hex representation, is used, plus more for any punctuation inserted (typically about another 7 characters, or 39 characters total). This document specifies a more compact representation of IPv6 addresses, which permits encoding in a mere 20 bytes." (April 1, 1996)
|
RFC 1925: The Twelve Networking Truths (FTP)RFC 1925: The Twelve Networking Truths (FTP)
 "This memo documents the fundamental truths of networking for the Internet community. This memo does not specify a standard, except in the sense that all standards must implicitly follow the fundamental truths." (April 1, 1996)
|
RFC 1882: The 12-Days of Technology Before Christmas (FTP)RFC 1882: The 12-Days of Technology Before Christmas (FTP)
 Parody of "The 12 Days of Christmas." (December 21, 1995)
|
RFC 1605: SONET to Sonnet Translation (FTP)RFC 1605: SONET to Sonnet Translation (FTP)
 "Because Synchronous Optical Network (SONET) transmits data in frames of bytes, it is fairly easy to envision ways to compress SONET frames to yield higher bandwidth over a given fiber optic link. This memo describes a particular method, SONET Over Novel English Translation (SONNET)." Written by W. Shakespeare of Globe Communications. (April 1, 1994)
|
RFC 1149: A Standard for the Transmission of IP Datagrams on Avian Carriers (FTP)RFC 1149: A Standard for the Transmission of IP Datagrams on Avian Carriers (FTP)
 "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." (April 1, 1990)
|
RFC 527: ARPAWOCKY (FTP)RFC 527: ARPAWOCKY (FTP)
 A song about the ARPANET. (June 22, 1973)
|
|
|
|
|
|
