[e2e] Is this a bug with Windows TCP Stack ?

[Rick Jones]

On Monday, December 06, 2004, at 09:18AM, Ted Faber <faber at ISI.EDU> wrote:

>On Sun, Dec 05, 2004 at 11:59:45AM -0800, sanjay kaniyar wrote:
>> In this case, Windows TCP is not sending the RST on its own from FIN_WAIT_2 
>> - IIS must have closed the connection.
>
>The close is what put the connection into FIN_WAIT_1, and getting an ACK
>after close put it into FIN_WAIT_2.  IIS can't close it again.  I hope.

Isn't there is a chance, however small, that IIS called shutdown() or its WSA equivalent before calling close() or its WSA equivalent?

I have seen that on a stack nearer and dearer to my heart, customers insist on a timeout to kill FIN_WAIT_2 connections - above and beyond the existing (in that stack anyway) mechanism that starts keepalive probes after an interval in a detached state.  That timer is arbitrary.  Perhaps Windows has one as well.

Is there progress afoot to update the TCP specs with a standardized mechanism to deal with the possibility of infinite time in FIN_WAIT_2?

rick jones