On Wed, 2015-01-07 at 20:37 +0000, Erik Grinaker wrote:
I agree. I have contacted Amazon about this, but am not too hopeful
for a quick fix; they have been promising SACK-support on their
loadbalancers since 2006, for example.
That said, since this change breaks a service as popular as S3, it
might be worth reconsidering.
Which change are you talking about ? Have you done a bisection to
clearly identify the patch exposing this sender bug ?
We are not going to stick TCP stack to 20th century and buggy peers or
middleboxes, sorry.