64 bytes from 10.0.3.1: icmp_seq=0 ttl=255 time=6165731.1 ms
"If 16 homing pigeons are given eight 512 GB SD cards each, and take an hour to reach their destination, the throughput of the transfer would be 145.6 Gbit/s, excluding transfer to and from the SD cards."
Today we have 1TB microSD cards, they only weight an 8th of an SD card.
If the capacity of a pigeon is 8 SD cards (1290,24cm³) then it can carry 64 microSD cards (1049,6cm³).
This means the capacity is now 64TB instead of 4TB. and the throughput would be 18,6 Tbit/s.
> Inspired by RFC 2549, on 9 September 2009, the marketing team of The Unlimited, a regional company in South Africa, decided to host a tongue-in-cheek "Pigeon Race" between their pet pigeon "Winston" and local telecom company Telkom SA. The race was to send 4 gigabytes of data from Howick to Hillcrest, approximately 60 km apart. The pigeon carried a microSD card and competed against a Telkom ADSL line. Winston beat the data transfer over Telkom's ADSL line, with a total time of two hours, six minutes and 57 seconds from uploading data on the microSD card to completion of download from card. At the time of Winston's victory, the ADSL transfer was just under 4% complete.
> Each Snowmobile is a secured data truck with up to 100PB storage capacity that can be dispatched to your site and connected directly to your network backbone to perform high-speed data migration
A Wired article  calculated the San Francisco to New York bandwidth of a full Snowmobile as just under 5 Tbps which is pretty damn impressive, although the offload network connection on the truck is (only) a 1 Tbps connection. And it gets quite pricey, a fully loaded Snowmobile is USD 500K per month, plus the 350 kW of electricity it needs.
According to the FAQ, if you need more bandwidth, you can operate the Snowmobile trucks in parallel to get multi Exabyte scale data transfers, but I have difficulty imagining any of the use cases that would require that as a solution...?!?
ACM DL: https://dl.acm.org/citation.cfm?id=2212785
Open PDF: http://stuartgeiger.com/papers/ipoxp-archive.pdf
HTTP Status 418: I'm a teapot - https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/418
Wasn't there also a protocol for checking vending machines for cold drinks?
Trivia: It was (I was told) using experimental 3Mbps Ethernet, the predecessor to the 10Mbps Ethernet that has grown to 10Gpbs+ now.
Implementing tea making device remote management would probably be a good candidate for a GSoC project or even a startup if you can find a VC gullible enough to fund you!
npm implemented it in their server last year!
Still remember the day 30+years ago using my 2400 baud to connect to internet and discovered FYI articles and the zen of internet.
Much better than reading ICL and IBM manual (red book ok but no fun) I supposed and debug 370 assembler Abend code etc.
A talk I attended by Heino Falcke stated that each site is now recording data at 64Gbps. Astounding metrics.
Today, or course, it would be a Chevy Spark stuffed with micro-SD cards... >smile<
Cop: I clocked you at 532 Mbps, this is a 400Mbps zone.
EvanAnderson: Oh I didn't see the sign.
Cop: License and registration.
> Never underestimate the bandwidth of a station wagon full of tapes hurtling down the highway.
— Tanenbaum, Andrew S. (1989). Computer Networks. New Jersey: Prentice-Hall. p. 57. ISBN 0-13-166836-6.
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
author rfc1149 and rfc2549
The same was noted 6 years ago: https://news.ycombinator.com/item?id=5999813
A store and forward network could be implemented on that.
Internationalizing IPv6 Using 128-Bit Unicode
> This new 128-bit Unicode code point space can be leveraged by the
IETF to address one of the lingering issues with IPv6: there's not
much left to standardize. With the changes described in this
document, the IETF will be kept busy for decades to come. It also
enables new features and market opportunities, to help the global
economy. This in turn will increase tax revenues for governments,
which eventually may lead to increased funds for combating global
warming. Therefore, the ultimate goal of this document is to reduce
Also, combining the two into a "birds and bees" protocol might be idea for some kinds of traffic.
Doom on bees. NetBSD on bees. Linux on bees. TensorFlow on bees. Software as a hive. Bees as a service.
All of that would be... the bee's knees.