@Vive_Levant @sng @ai6yr @futurebird those are two of my favourite RFCs! 😜
in seriousness though, #NASA has done a lot of work on delay-tolerant networking and there are several related RFCs including RFCs 4838 & 5050
https://www.rfc-editor.org/rfc/rfc4838
https://www.rfc-editor.org/rfc/rfc5050
#DTN
^ what??!? it’s totally normal to have favourite RFCs, shut up! 🤪
@itgrrl @sng @ai6yr @futurebird I’m sure you know, but is the rest of the fediverse aware that rfc 1149 was implemented in 2001 and a desastrously inefficient ping was successfully executed by a Norwegian LUG in Bergen ?
Desastrously inefficient success :
9 packets transmitted, 4 packets received, 55% packet loss
round-trip min/avg/max = 3211900.8/5222806.6/6388671.9 ms
@sng @ai6yr @futurebird LEO? no, it's fine
The moon? 1.3s, which isn't insurmountable but sure is annoying
@astraluma @sng @ai6yr @futurebird so long as you manage to sort out the “500-mile email” problem… 🙃
@itgrrl @astraluma @sng @futurebird Ha!
Funny story, I was attempting to figure out how to do some configuration of various Internet utilities over AREDN (ham radio mesh), and -- due to mesh and RF involved -- it pushes up against a lot of these same timeout errors. It was extremely annoying... i.e. you knew there was a node you could theoretically get to, but there was no MODERN protocol able to communicate because of those latency timeouts. I was looking to see if anyone still supported UUCP to get around the problem!! (but then got distracted, and never figured it out).