[panorama photo]
[site name]

The April Fools' Day RFC's

RFC 1149 - A Standard for the Transmission of IP Datagrams on Avian Carriers
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. (1 April 1990)
RFC 2322 - Management of IP numbers by peg-dhcp
This RFC describes a protocol to dynamically hand out ip-numbers on field networks and small events that don't necessarily have a clear organisational body. (1 April 1998)
RFC 2549 - IP over Avian Carriers with Quality of Service
This memo amends RFC 1149 with Quality of Service information. (1 April 1999)
RFC 2550 - Y10K and Beyond
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). (1 April 1999)
RFC 2551 - The Roman Standards Process -- Revision III
This document specifies a Roman Worst Current Practices for the Roman Community, and requests discussion and suggestions for improvements. (1 April MCMXCIX)
RFC 2795 - The Infinite Monkey Protocol Suite
This memo describes 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. The suite includes communications and control protocols for monkeys and the organizations that interact with them. (1 April 2000)
RFC 3514 - The Security Flag in the IPv4 Header
Firewalls, packet filters, intrusion detection systems, and the like often have difficulty distinguishing between packets that have malicious intent and those that are merely unusual. We define a security flag in the IPv4 header as a means of distinguishing the two cases. (1 April 2003)
RFC 4041 - Requirements for Morality Sections in Routing Area Drafts
It has often been the case that morality has not been given proper consideration in the design and specification of protocols produced within the Routing Area. This has led to a decline in the moral values within the Internet and attempts to retrofit a suitable moral code to implemented and deployed protocols has been shown to be sub-optimal. (1 April 2005)
RFC 4042 - UTF-9 and UTF-18: Efficient Transformation Formats of Unicode
ISO-10646 defines a large character set called the Universal Character Set (UCS), which encompasses most of the world's writing systems. The current representation formats for Unicode (UTF-7, UTF-8, UTF-16) are not storage and computation efficient on platforms that utilize the 9 bit nonet as a natural storage unit instead of the 8 bit octet. (1 April 2005)