From: Eric Dumazet <eduma...@google.com> Date: Tue, 30 Jun 2020 13:39:27 -0700
> The (C) & (B) case are certainly doable. > > A) case is more complex, I have no idea of breakages of various TCP > stacks if a flow got SACK > at some point (in 3WHS) but suddenly becomes Reno. I agree that C and B are the easiest to implement without having to add complicated code to handle various negotiated TCP option scenerios. It does seem to be that some entities do A, or did I misread your behavioral analysis of various implementations Mathieu? Thanks.
