RFC 1149

RFC 1149: A Standard for the Transmission of IP Datagrams on Avian Carriers 🐦💖

• Network Working Group 🌸
• Request for Comments: 1149
• Author: D. Waitzman (David Waitzman), BBN STC 🎀
• Date: 1 April 1990 📅
• Status: experimental, not recommended standard 🧪
• Obsoletes / Updates: none listed in the header 🙈

Status of This Memo ✨

okay so this memo describes an experimental method for wrapping IP datagrams up in avian carriers 🐦 (birds, bestie). it's mainly useful in Metropolitan Area Networks 🏙️. it's an experiment, NOT a recommended standard, so don't treat it like one 💅. distribution of this memo is unlimited 🫶.

Overview and Rational 🕊️

ngl, avian carriers are giving high delay, low throughput, and low altitude service 💀. the connection topology is limited to a single point-to-point path for each carrier, used with standard carriers 🦋. but you can run lots of carriers without much interference between them, except in early spring 🌸. that's because they get 3D ether space to fly around in, unlike the 1D ether IEEE802.3 is stuck with 😤. the carriers also have an intrinsic collision avoidance system, which boosts availability 👑.

unlike some network technologies, like packet radio, you're not limited to line-of-sight distance 🧚. and connection oriented service is available in some cities, usually based on a central hub topology 🌈.

Frame Format 🎀

the IP datagram gets printed on a small scroll of paper in hexadecimal 📜. each octet is separated by whitestuff and blackstuff 🖤🤍. the scroll is wrapped around one leg of the avian carrier 🦵. then a band of duct tape holds the datagram's edges down 🩹. the bandwidth is limited to the leg length, so it is what it is 💅. the MTU is variable, and paradoxically, it generally goes UP as the carrier gets older 🍓. a typical MTU is 256 milligrams ⚖️. some datagram padding may be needed ✨.

upon receipt, the duct tape comes off 😭, and the paper copy of the datagram gets optically scanned into an electronically transmittable form 💜.

Discussion 🧚‍♀️

multiple types of service can be provided with a prioritized pecking order 👑. there's also built-in worm detection and eradication, which is honestly iconic 🔥. because IP only guarantees best effort delivery, losing a carrier can be tolerated 🫠. over time, the carriers are self-regenerating 🌱. broadcasting is not specified, and storms can cause data loss ⛈️. there is persistent delivery retry, until the carrier drops 🦋. audit trails are automatically generated, and you can often find them on logs and cable trays 🙈.

Security Considerations 🔐

security is not generally a problem in normal operation 💖, but special measures must be taken (such as data encryption) when avian carriers are used in a tactical environment 🚨. no cap, don't skip this part 😭.

Author's Address 💌

David Waitzman BBN Systems and Technologies Corporation BBN Labs Division 10 Moulton Street Cambridge, MA 02238

Phone: (617) 873-4323 📞

EMail: dwaitzman@BBN.COM 💜