Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
NT
apps
dfs
dns
domain
dsmnfpnw
embedded
fsft
mail
misc
oemdsp.preinstall
personalfax
print
protocol.ipx
protocol.misc
protocol.ras
protocol.routing
protocol.tcpip
registry
setup
terminalserv.app.
terminalserv.client
terminalserv.connectivity
terminalserv.domain
terminalserv.misc
terminalserv.prot.rdp
terminalserv.prot.tcpip
terminalserv.setup
terminalserv.user
windowsnt.wntsee
  
 
date: Thu, 3 Apr 2008 00:47:02 +0200,    group: microsoft.public.windowsnt.protocol.tcpip        back       


LAST ACK in Threeway handshake   
Hi,
Does anyone know if it is legal to have data in the last ACK in the 
Three-way handshake or should the last ACK in the Three-way handshake always 
be empty?
Best Regards
ITO
date: Thu, 3 Apr 2008 00:47:02 +0200   author:   ITO

Re: LAST ACK in Threeway handshake   
On 2008-04-02 18:47:02 -0400, "ITO"  said:

> Hi,
> Does anyone know if it is legal to have data in the last ACK in the 
> Three-way handshake or should the last ACK in the Three-way handshake 
> always be empty?
> Best Regards
> ITO

ITO, IMHO, I don't think there is a specification in RFC792 or 
subsequent that specifies whether or not the "last ACK" in the 3-way 
handshake needs to be empty or not, if there is data to send, there is 
data to send, however, a lot of these 
"not-really-a-standard-but-common" behaviors unfortunately get included 
as security filters in firewall products.


-- 

 __| |_ __  / _| |_     01100100 01101101
/ _` | '  \|  _| ' \    01100110 01101000
\__,_|_|_|_|_| |_||_|    dmfh(-2)dmfh.cx
date: Mon, 7 Apr 2008 15:29:33 -0400   author:   Digital Mercenary For Honor dmfh(-2-)nospamr3m0v3th1s.dmfh.cx

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us