Standard for the transmission of IP datagrams on avian carriers
Ce document décrit une méthode expérimentale et humoristique pour transporter des données du protocole internet (IP) en utilisant des oiseaux plutôt que des câbles électroniques. Pour envoyer un message, les données sont imprimées sur un petit morceau de papier, fixées à la patte d'un oiseau, puis acheminées vers la destination. Une fois l'oiseau arrivé, le papier est retiré et numérisé. Bien que cette approche évite les interférences de signal traditionnelles et ne nécessite pas de connexion en ligne de vue, elle souffre d'une latence extrêmement élevée et d'un débit de données très faible. La quantité de données pouvant être envoyées est physiquement limitée par la longueur de la patte de l'oiseau. Les risques notables incluent la perte de données lors de tempêtes et la possibilité que les porteurs soient interceptés dans des environnements tactiques. En tant que plaisanterie du poisson d'avril, elle illustre la nature « best effort » (meilleur effort) de la livraison IP de la manière la plus littérale possible.
🇬🇧 Résumé (en anglais)
This document describes a humorous, experimental method for transporting internet protocol (IP) data using birds instead of electronic cables. To send a message, the data is printed on a small piece of paper, taped to a bird's leg, and flown to the destination. Once the bird arrives, the paper is removed and scanned back into a digital format. While this approach avoids traditional signal interference and doesn't require a line-of-sight connection, it suffers from extremely high latency and low data throughput. The amount of data that can be sent is physically limited by the length of the bird's leg. Notable risks include data loss during storms and the potential for carriers to be intercepted in tactical environments. As an April Fools' Day joke, it highlights the "best effort" nature of IP delivery in the most literal way possible.
Network Working Group D. Waitzman
Request for Comments: 1149 BBN STC
1 April 1990
A Standard for the Transmission of IP Datagrams on Avian Carriers
Status of this Memo
This memo describes an experimental method for the encapsulation of
IP datagrams in avian carriers. This specification is primarily
useful in Metropolitan Area Networks. This is an experimental, not
recommended standard. Distribution of this memo is unlimited.
Overview and Rational
Avian carriers can provide 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 many carriers can be used without significant interference with
each other, outside of early spring. This is because of the 3D ether
space available to the carriers, in contrast to the 1D ether used by
IEEE802.3. The carriers have an intrinsic collision avoidance
system, which increases availability. Unlike some network
technologies, such as packet radio, communication is not limited to
line-of-sight distance. Connection oriented service is available in
some cities, usually based upon a central hub topology.
Frame Format
The IP datagram is printed, on a small scroll of paper, in
hexadecimal, with each octet separated by whitestuff and blackstuff.
The scroll of paper is wrapped around one leg of the avian carrier.
A band of duct tape is used to secure the datagram's edges. The
bandwidth is limited to the leg length. The MTU is variable, and
paradoxically, generally increases with increased carrier age. A
typical MTU is 256 milligrams. Some datagram padding may be needed.
Upon receipt, the duct tape is removed and the paper copy of the
datagram is optically scanned into a electronically transmittable
form.
Discussion
Multiple types of service can be provided with a prioritized pecking
order. An additional property is built-in worm detection and
eradication. Because IP only guarantees best effort delivery, loss
of a carrier can be tolerated. With time, the carriers are self-
regenerating. While broadcasting is not specified, storms can cause
data loss. There is persistent delivery retry, until the carrier
drops. Audit trails are automatically generated, and can often be
found 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.
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