lkml.org 
[lkml]   [2000]   [Nov]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] document ECN in 2.4 Configure.help
David S. Miller wrote:
> Any workaround which ignores TCP resets is broken from the start and
> is not to be implemented.

Hmm, what actual consequences (besides being non-conformant to RFC793)
would you expect ? I can see mainly two of them:

- non-ECN but otherwise healthy sites get an extra SYN packet for each
RST they send to an ECN-capable host using this recovery scheme
(strikes me as relatively harmless; note that any retry mechanism at
a higher protocol layer would have the same characteristics)
- if such a host receives a RST due to an ECN-unfriendly firewall, and
this RST was duplicated in the network, the duplicated RST will
probably reach the sender before the non-RST response reaches it, so
the connection fails unnecessarily.

The second scenario suggests that perhaps TCP should pick a new ISN in
this case. But I'm not sure the scenario would happen all that often in
real life ...

I'm much more worried about the "fall back immediately after single
failure" problem.

- Werner

--
_________________________________________________________________________
/ Werner Almesberger, ICA, EPFL, CH Werner.Almesberger@epfl.ch /
/_IN_N_032__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:45    [W:0.102 / U:1.152 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site