Having worked with QUIC extensively lately I must say that having protocol entirely in userspace is truly liberating. It also helps that almost everything, including headers is encrypted, as a result middle boxes can't interfere and "optimise" your flow.
For high latency and high packet loss links, like one described in the article, you'll probably need pre-emptive retransmits and I am not sure that simply tuning parameters will get there. Retransmitting before loss is detected cuts bandwidth, but I suspect will improve end to end latency.
Aren’t fec codes already used in satellite transmissions? I recall reading the patents around fec codes had something to do with the satellite industry.
definitely. that's the only reason I know about them. usually you have to do a little more, because the errors are very bursty, so you have to use very wide windows or interleave in order to spread the errors out so that the redundancy can cover them.
if you're saying 'thats a link layer problem' then I agree, but it would be better to change your link level encoding strategy than to just start sending multiple copies at the transport layer.
For high latency and high packet loss links, like one described in the article, you'll probably need pre-emptive retransmits and I am not sure that simply tuning parameters will get there. Retransmitting before loss is detected cuts bandwidth, but I suspect will improve end to end latency.