https://bugzilla.mindrot.org/show_bug.cgi?id=3578
Damien Miller <d...@mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |d...@mindrot.org
--- Comment #1 from Damien Miller <d...@mindrot.org> ---
This would be nice, but the features that you're asking for are really
at the TCP level - protocols that use TCP have very little control over
timeouts and retransmits that happen in TCP. Similarly, SSH sending
FEC'd data over a TCP channel would do little, since the bad behaviour
in the presence of packet loss is a TCP phenomenom.
Other protocols such as QUIC avoid this by switching the transport from
TCP to UDP, but this comes at the price of the protocol having to
manage packet loss detection, in-order delivery, retransmission, etc. I
don't think there is much appetite to take on this burden in SSH.
Given that SSH is likely to remain on TCP for now, the best you can do
is get TCP to behave better in environments with high packet loss. Some
platforms (e.g. Linux) do offer a menu of TCP packet scheduling
algorithms, and some of these are designed to do better in these cases.
https://linuxgazette.net/135/pfeiffer.html has some details.
--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs
