That's why we stop when we receive the second TCP RST.
It's just like dropping due to congestion, which is of course perfectly
safe in moderation.
> You would have to retry a connection with a new source port. How do
> you handle cases where the application explicitly bound the socket to
> a specific source port / source IP ?
Applications tend not to. Do we care about those that do?
> Caching whether the site is able to speak ECN or not is also
> suboptimal if the local site is opening lots of outgoing connections,
> like a proxy server. (Of course, memory has gotten cheap)
>
> _And_ it is solving the problem on the wrong end.
It would not solve the problem at all, if there's no incentive to switch
to ECN. But then, why force people to use ECN if there's no advantage
to it anyway?
Does ECN provide perceived benefits to the node using it?
-- Jamie
-
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/