Re: Vista TCP/IP Stack not RFC 1624 compliant
- From: "Volodymyr M. Shcherbyna" <v_scherbina@xxxxxxxxxxxxxxx>
- Date: Thu, 8 May 2008 09:46:24 +0200
Well, the best case is to report it at connect for WNDP team:
https://connect.microsoft.com/WNDP/Feedback
--
V.
This posting is provided "AS IS" with no warranties, and confers no
rights.
"pdhooper" <pdhooper@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:45642010-4873-4004-9C8B-6A088D56C68D@xxxxxxxxxxxxxxxx
Thanks, is there anyway I can escalate this? What is the best way to raise
an
incident report with Microsoft over this issue?
"Volodymyr M. Shcherbyna" wrote:
Will try to inform WNDP team about this.
--
V.
This posting is provided "AS IS" with no warranties, and confers no
rights.
"pdhooper" <pdhooper@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2B65E0C7-D103-4972-B017-A5DCF5DE8BFD@xxxxxxxxxxxxxxxx
RE: TCP checksum failure with offloading disabled (0xFFFF)
I have confirmed that the same application software and hardware has
the
following behaviour under Vista...
* With checksum offloading the connection is fine
* Without checksum offloading the Vista TCP/IP stack can generate
packets
with a checksum of 0xFFFF (minus zero)
RFC 1624 implies that a stack should only generate 0x0000 (plus zero)
as a
checksum and never minus zero. However it should accept both to ensure
greatest compatibility.
Please someone correct me if I am wrong
.
- References:
- Re: Vista TCP/IP Stack not RFC 1624 compliant
- From: Volodymyr M. Shcherbyna
- Re: Vista TCP/IP Stack not RFC 1624 compliant
- From: pdhooper
- Re: Vista TCP/IP Stack not RFC 1624 compliant
- Prev by Date: IOCP question
- Next by Date: Re: Able to detect disconnect, except one weird case...
- Previous by thread: Re: Vista TCP/IP Stack not RFC 1624 compliant
- Next by thread: Re: 'Netsh firewall reset' but from a program.
- Index(es):
Relevant Pages
|
|