The RFC Family

Three decades of avian infrastructure standards

1990Experimental

RFC 1149

A Standard for the Transmission of IP Datagrams on Avian Carriers

D. Waitzman

The foundational document. Defines IP transmission over homing pigeons, including segment size (256 milligrams), maximum transmission unit, and error detection via examining the carrier.

1999Experimental

RFC 2549

IP over Avian Carriers with Quality of Service

D. Waitzman

Extends RFC 1149 with QoS markings. Defines differentiated services for avian transport: priority traffic may be carried by faster birds (swifts); low-priority traffic by slower species.

2001Historical

Bergen, Norway

Real-world implementation

BLUG (Bergen Linux User Group)

The Bergen Linux User Group implemented RFC 1149 in practice. Nine packets were sent. Ping response time: 3,000–6,000 seconds. Packet loss: 55%. The surviving pigeons beat the local ADSL connection in effective throughput.

2011Informational

RFC 6214

Adaptation of RFC 1149 for IPv6

B. Carpenter, R. Hinden

Updates RFC 1149 for IPv6. Notes that the increased address space (128 bits) requires larger leg bands. Recommends using longer-lived bird species for addresses with low TTL.

2026Internet-Draft

DoAC

DNS over Avian Carriers

C. E. Cruz González

The missing piece: how does a host on an avian-carrier network resolve a hostname? Defines the AA resource record, the Pigeon of Last Resort (PoLR), and retransmission behavior. Threat model includes Hawk-in-the-Middle (HitM) attacks and the Hungry Cat as a physical layer threat.

Read the draftdraft-cruzgonzalez-ipoac-dns