This article does not apply to TCP over SSH, as in SSH port forwarding (not openssh's VPN feature), in that case the timers are tied together and you don't get the crappy cascading behavior.
That sounds very interesting. Do you have any technical sources that I could delve deeper into? I've always thought that SSH tunneling / port forwarding suffers from the exact problems outlined in TFA.
As I understand it, ssh "unwraps" the TCP stream back into a regular byte stream, then sends that, and reconstitutes it back into TCP packets on the other end.
Thanks. That sounds like a reasonable explanation, and anecdotally I don't remember ever having major performance problems with SSH, even on mobile networks, so it makes sense that there ia something preventing this particular error mode.