Live data from Hacker News

IP over Avian Carriers RFC 1149 event (2001)

blug.linux.no

21–30 of 38 posts

Re: IP over Avian Carriers RFC 1149 event (2001)

#21
post #18
post #3

When I read that RFC, I imagined that a barcode would be more reliable to read in and process than printing the hex characters.

Typical 1D barcode has a size limit, and the RFC is from 1990. Nowadays you could just use a QR code, which would be comfortable enough to have a 1500 MTU in a single QR code. It probably warrants an additional layer so multiple QR codes can be transmitted by a single carrier.

Looked into using paper as an archival for small amounts of data as a long-term backup of very important data, and found this[1], which would allow encoding ~200kB of data per A4 page. Should be applicable for avian IP as well.

[1]: https://blog.za3k.com/paper-archival/

Re: IP over Avian Carriers RFC 1149 event (2001)

#22

Not so funny at times: an article from 2009, "In Africa, A Pigeon Transfers Data Faster Than The Internet": * https://www.wired.com/2009/09/in-africa-a-pigeon-transfers-d... * https://spectrum.ieee.org/carrier-pigeon-beats-internet-

Strap the pigeon with 100 1TB microSD cards (~250 mg per card) and the bandwidth will approach the transfer speed of the microSD card itself — nearly gigabit speed for UHS-III cards.

Re: IP over Avian Carriers RFC 1149 event (2001)

#24

> with ping times varying from 3211 to 6389 seconds. I guess this is a new record for ping times… Hmm, T-mobile's network comes close, but not quite that high, I think. /s Somewhat more seriously, I have seen ping times approaching 20,000 ms on their network. Given the light-distance to the moon is ~1.3 seconds, this ping clearly went significantly further than the moon's orbit, and back; very clearly some routes nee…

More likely than moving far or moving slow the ping spent a long time being buffered at a radio lower layer retransmit where, much like Wi-Fi, having an issue sending the packet can result in multiple retries instead of an immediate drop.

Re: IP over Avian Carriers RFC 1149 event (2001)

#26

Not so funny at times: an article from 2009, "In Africa, A Pigeon Transfers Data Faster Than The Internet": * https://www.wired.com/2009/09/in-africa-a-pigeon-transfers-d... * https://spectrum.ieee.org/carrier-pigeon-beats-internet-

A truck full of storage volumes can have a higher bandwidth than fiber. Just really bad latency.

Interesting how the analogy progressed over the years from "a station wagon filled with tapes" to "a truck full of storage volumes".

An A380 filled with micro SD cards would likely beat any conceivable fiber network in bandwidth, if not latency.

Re: IP over Avian Carriers RFC 1149 event (2001)

#27
post #18

Earlier quoted context omitted.

Typical 1D barcode has a size limit, and the RFC is from 1990. Nowadays you could just use a QR code, which would be comfortable enough to have a 1500 MTU in a single QR code. It probably warrants an additional layer so multiple QR codes can be transmitted by a single carrier.

Looked into using paper as an archival for small amounts of data as a long-term backup of very important data, and found this[1], which would allow encoding ~200kB of data per A4 page. Should be applicable for avian IP as well. [1]: https://blog.za3k.com/paper-archival/

Interesting, many thanks. Currently enjoying the fall down the Golay code rabbit hole.

https://en.m.wikipedia.org/wiki/Binary_Golay_code

Re: IP over Avian Carriers RFC 1149 event (2001)

#28

RFC 1149 was updated in RFC 6214 [1] to support IPv6 but adoption has been painstakingly slow among avian ISPs. [1]: https://datatracker.ietf.org/doc/html/rfc6214

Hey! We'll have none of that anti-pigeon bigotry here :-P

                             ---
        \                  /   @ )
          \             _/_   |~ \)
            \     ( ( (     \ \
             ( ( ( ( (       | \
    _ _=(_(_(_(_(_(_(_  _ _ /  )
                    -  _ _ _  /
                          _\___
                         `    "'
Post reply on HN