Today is my last day in the office. I'm being forced to work at home from now on.

[csziggy]

48. If he moves to the wilderness, he can use RFC 1149 - Standard for the transmission of IP datagrams o

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.

More: http://www.faqs.org/rfcs/rfc1149.html

Although the standard was first described in 1990, it was not implemented until 2001 when the Bergen Linux User group successfully did a 7 1/2 minute interval between the ping packets - https://www.cnet.com/news/pigeon-powered-internet-takes-flight/ and https://www.blug.linux.no/rfc1149/writeup/

But now there's a practical use for pigeon-based communications: photographers working for the white-water rafting company Rocky Mountain Adventures send memory sticks full of digital photos via homing pigeon so the photos will be ready when the rafters finish up. The company has details on how the pigeons are trained and equipped. It may not be a full implementation of the Pigeon Protocol, but it works in narrow canyons far off the beaten path — and just as David Waitzman presciently predicted, they occasionally suffer packet loss due to hawks and ospreys."
https://entertainment.slashdot.org/story/09/08/29/1934251/pigeon-protocol-finds-a-practical-purpose

https://vimeo.com/5558263

So rather than Morse Code, use Pigeon Express!