Jokes From RFCs

一向是严肃的Internet标准制定者RFC也会开玩笑，事实上在数千的RFC文档里不缺乏恶搞式的幽默，似乎从1989年开始，每年的愚人节都会出台一个玩笑性质的RFC文档,而且有些玩笑（RFC 1149, 2322）事实上被人实现或者投入使用：

RfC 527 (1973)

ARPAWOCKY （看起来是一首诗？）

RfC 748 (1978)

Telnet Randomly-lose option （Telnet协议的随机丢失选项（估计作者是在抱怨当时网络丢包吧））

RfC 1097 (1989)

Telnet subliminal-message option （Telnet潜在信息选项？）

RfC 1149 (1990)

Standard for the transmission of IP datagrams on avian carriers

这个搞笑性很高：使用信鸽（或者其他鸟类）传输IP数据包的标准

而且这个RFC有好事者实现了，还不止一次：

The first implementation was B2P (back to Pigeons) April 2001 in Bergen, Norway. 用信鸽传递纸条，然后再OCR扫描进去的实现。

A later implementation (FiFly, March 2004, Israel) reached 2,27Mbit/s data transfer rate (very high latency, though) .用信鸽传递闪存芯片的实现

And a later one (April 2005) even higher throughput 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 传说中的IPv9就是这个啦～天朝的科学研究，有兴趣的Google

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 吧ipv6地址压缩成Base85编码

RfC 1925 (1996)

The Twelve Networking Truths

RfC 1926 (1996)

An Experimental Encapsulation of IP Datagrams on Top of ATM IP包通过声音传输，嗯，通讯基本靠吼就是这个了

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 （支持QOS的IP over 信鸽协议- -||）

RfC 2550 (1999)

Y10K and Beyond 有两千年问题，自然也有一万年问题

RfC 2551 (1999)

The Roman Standards Process -- Revision III

RfC 2795 (2000)

The Infinite Monkey Protocol Suite (IMPS)

   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.

描述了一个支持无限只猴子坐在无限台打字机前以测试他们能否打出整部莎士比亚的作品或者是肥皂剧本的协议

RfC 3091 (2001)

Pi Digit Generation Protocol（圆周率生成协议，他们还能想出更加没用的浪费电能的方式么？）

RfC 3092 (2001)

Etymology of 'Foo' Foobar的来源（不是那个音乐播放器啦）

RfC 3093 (2001)

Firewall Enhancement Protocol (FEP)

RfC 3251 (2002)

Electricity over IP - Mostly Pointless Lamp Switching (MPLampS)

通过IP协议传送电能

RfC 3252 (2002)

Binary Lexical Octet Ad-hoc Transport (BLOAT)

RfC 3514 (2003)

The Security Flag in the IPv4 Header

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

UTF-8不够用咯

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