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

[sanjay kaniyar]

RST is sent out because the application does not care about the connection
anymore. For instance, say an application sent data, issued a Shutdown() to
close the connection gracefully - it waits for a duration of its choice but
the disconnect does not complete and it wants to abort the connection. The
Close() enables the application do exactly that.

But, this instance may be completely unrelated - let's see what Gouthatm's
test does.

Thanks,
Sanjay

-----Original Message-----
From: Joe Touch [mailto:touch at ISI.EDU] 
Sent: Tuesday, December 07, 2004 8:05 AM
To: sanjay kaniyar
Cc: 'Ted Faber'; end2end-interest at postel.org
Subject: Re: [e2e] Is this a bug with Windows TCP Stack ?



sanjay kaniyar wrote:
> Winsock API has subtle semantics, I am not totally sure but something like
> this could result in the observed trace:
> 
> - IIS does send
> - does Shutdown(SD_SEND) -> data and FIN go out.
> - setsockopt(Linger = OFF)
> - closesocket		-> RST goes out.

Why RST here? RST should be associated with an abort call. Closes that 
don't involve errors should not cause RSTs.

The issue, IMO, is 'what is the _error_ here_'? Lingering state is not 
an error.

Joe