RE: [tcpm] TCP Secure

Hi Toby,

Please see inline.

________________________________

	From: toby.moncaster@bt.com [mailto:toby.moncaster@bt.com] 
	Sent: Friday, May 18, 2007 7:00 AM
	To: tcpm@ietf.org
	Subject: [tcpm] TCP Secure

	Hi, 

	I was just wanting a couple of bits of clarification about TCP
Secure: 

	Top of page 10: It isn't clear what happens to other segments
after you drop the RST? Are they just processed as normal? This is what
is implied but it would be useful if it were made explicitly clear. 

	Mitesh: yes, they are processed as normal as if the RST didnt
arrive. 

	What happens if there is any re-ordering before a valid RST or
SYN is sent? Can you clarify how your mitigations react to this. From my
understanding, the reason for originally accepting any RST or SYN in the
valid receive window was to allow for data reordering (as explicitly
stated in RFC793) 

	Mitesh: you mean the other side send bunch of data followed by a
RST, however we received the RST followed by the data ?

	In that case, we send an ACK for the RST and process the
following data and hopefully when we get the RST for the ACK that

	we had send, we will flush the connection.  

	Finally: spotted three typos: 

	Page 5 para 3) "...before succeeding in his mischieve." --> "...
before succeeding in his mischief." 
	Page 11 3rd para up from bottom "...would not have a TCB..." -->
"...would not have a TCP..." 
	Page 19, para 2. Initial "i" not capitalized  

	Thanks. We will get them in.

	Mitesh 