This category is for joke RFCs (Request For Comments).
More information
More information
Subcategories 1
Related categories 1
Sites 9
A description of an architecture for carrying electricity over IP.
(April 01, 2002)
A reformulation of IP and two transport layer protocols (TCP and UDP) as XML applications
(April 01, 2002)
"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 01, 1999)
"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 01, 1999)
"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 01, 1998)
This RFC "defines objects for the management of coffee-brewing and maintenance devices."
(April 01, 1998)
"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 01, 1996)
"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 01, 1994)
"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 01, 1990)
A description of an architecture for carrying electricity over IP.
(April 01, 2002)
A reformulation of IP and two transport layer protocols (TCP and UDP) as XML applications
(April 01, 2002)
"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 01, 1999)
"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 01, 1999)
This RFC "defines objects for the management of coffee-brewing and maintenance devices."
(April 01, 1998)
"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 01, 1998)
"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 01, 1996)
"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 01, 1994)
"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 01, 1990)
