The internet protocol designed to transmit data using homing pigeons
On April Fools' Day in 1990, network engineer David Waitzman published RFC 1149, an official specification for transmitting Internet Protocol packets using homing pigeons. Eleven years later, the Bergen Linux User Group actually tested it in Norway. They released pigeons carrying tiny memory cards with data packets over five kilometers. While it suffered 55 percent packet loss and took 73 minutes, the avian network successfully transmitted four complete response packets.
The Origin of an Unusual Protocol
In the early days of computer networking, the engineers drafting the technical architecture of the internet codified their work through documents called Requests for Comments, or RFCs. Published under the auspices of what became the Internet Engineering Task Force, RFCs established standard specifications for protocols like TCP, IP, and DNS. Alongside serious engineering proposals, a tradition emerged of publishing humorous or satirical RFCs on April Fools' Day. These joke documents were not mere nonsense; they were carefully composed parodies that strictly adhered to the formal formatting, rigid taxonomy, and architectural logic of authentic networking standards.
On April 1, 1990, network engineer David Waitzman submitted RFC 1149, titled "Standard for the Transmission of IP Datagrams on Avian Carriers." The document set out to specify how the Internet Protocol could operate across a transmission medium consisting entirely of homing pigeons. Written with a straight technical face, RFC 1149 treated the biological habits of pigeons as lower-layer physical constraints, proposing an encapsulation format where an IP datagram is printed onto a small slip of paper, rolled into a cylinder, and attached to the leg of a bird for physical transport.
Waitzman's paper was designed as technical satire, but it also functioned as a demonstration of the core philosophy of the internet protocol suite. By defining an interface between the network layer and a biological carrier, the specification illustrated the deliberate agnosticism of IP: the protocol does not care whether bits move across copper wires, optical fibers, radio waves, or feathered couriers.