3 ms·
Audio streaming not including voice calls I assume, because those are absolutely latency sensitive. Are your terminals going to include TCP Performance Enhanci
by jandrese 9y ago
Audio streaming not including voice calls I assume, because those are absolutely latency sensitive.
Are your terminals going to include TCP Performance Enhancing Proxies (PEPs)? The TCP three way handshake followed by the TLS handshake makes it kind of painful to browse on an unaccelerated network with a GEO hop. And this is before you get to the latency from the ground station to the website. The problem gets even worse in Web2.0 world where everything is running off of tiny queries that the web app developers assume will be back in 50ms or so.
TCP PEPs can only do so much too (cutting down on the roundtrips and ramping up the window size more quickly), eventually you hit the hard limits of physics.
- dfox 9y agoFrom my experience it is not so hard to build completely terrestrial links that have latency that is large enough such that TCP works (althought it should not), but TLS handshake will timeout. For GEO links you will get exactly this behavior by using BGAN terminal over Bluetooth DUN profile (BT adds enough latency for this to happen).
- jandrese 9y agoThe only time I've seen a terrestrial link with a latency so bad that TCP couldn't be established it also required you to install a poorly behaved app that reduced Window's TCP retransmit limit to 1 (from 3). TLS setups however as you note are a whole new ball of wax, especially if the link has a bit of loss to go along with the latency.