Ctrl+Alt+Route

I though we should start this series with an absolute classic, one of most famous or at least well known RFCs, however despite its comedic origin, it has since inspired real-world implementations and continues to be a legendary piece of internet history.

Overview

RFC Published: April 1, 1990 | Author: David Waitzman

RFC 1149 defines a method for delivering IP datagrams using avian carriers, specifically, birds like pigeons.

This standard describes how to encapsulate IP packets, attach them to birds, send them across a metropolitan area, and recover the data upon arrival. It highlights the benefits and technical specifics of bird-based packet transfer.

The method involves printing IP packets on paper, attaching them to a bird’s leg with duct tape, and scanning them back into digital form upon delivery. The RFC even provides commentary on collision avoidance, Quality of Service (“pecking order”), and security considerations.

Key Points from RFC 1149

• Transmission Medium: Avian carriers (pigeons) serve as the physical layer for IP delivery.
• Performance Characteristics: Extremely high latency, very low throughput, and natural collision avoidance in the 3D “ether.”
• Frame Format:
  • IP datagrams printed in hexadecimal on scrolls of paper
  • Wrapped around the bird’s leg and secured with duct tape
  • MTU ~256 mg but increases with bird age
• Service Behavior:
  • Prioritized “pecking order” for delivery
  • Built-in worm detection (literal)
  • Automatic audit trails (left as logs)
  • Persistent retries—carrier keeps trying until it “drops”
• Security: Generally safe, but encryption recommended in tactical environments.
• Intended Audience: Experimental use; not a recommended standard.

Additional information

And here’s the best part: someone actually tried this. In 2001, a Linux user group in Norway implemented RFC 1149 exactly as written, using homing pigeons to transport real IP data. The packets were printed, taped to the birds’ legs, and delivered just like the RFC describes.

Was it fast? Not even close. Latency was measured in tens of minutes, throughput in single packets per bird. But it worked — proving that even a joke RFC can be technically valid if you’re determined enough.

It’s one of those great reminders that networking has a long history of experimentation, curiosity, and the occasional bit of chaos engineering… even if it involves pigeons.

You can read more here:

• Bergen Linux User Group: https://blug.linux.no/rfc1149/writeup/

What’s an RFC?

A Request for Comment (RFC) is a formal document created by the IETF and other standards bodies that defines everything from internet protocols, networking architectures and best practices.

RFCs are how the internet evolves. Many of the protocols you use every day — TCP/IP, DNS, HTTP, BGP, SMTP — all originated as RFCs.

They’re publicly available, versioned, and archived for anyone to study.

If you’re new to RFCs, these are excellent starting points:

• How to Read an RFC: https://www.ietf.org/blog/how-read-rfc/
• RFC Availability & Use: https://www.ietf.org/process/rfcs/#availability-and-use