Re: TCP NewReno and single retransmit
From: Neal Cardwell <ncardwell@google.com>
Date: 2014-11-04 14:38:48
From: Neal Cardwell <ncardwell@google.com>
Date: 2014-11-04 14:38:48
On Tue, Nov 4, 2014 at 2:59 AM, Yuchung Cheng [off-list ref] wrote:
Thanks for checking. So my suggested fix of removing the hold state is the "less careful variant" that RFC does not recommend. I would rather have the proposed 2-liner fix than implementing the section 6 heuristics to detect spurious retransmit. It's not worth the effort. Everyone should use SACK.
Agreed. The simple 2-liner seems like the simplest and lowest-risk fix. And given that >95% of public Internet flows and an even higher proportion of datacenter flows use SACK, it's not worth spending time optimizing NewReno. neal