RE: [tcpm] TCP Secure

"Mitesh Dalal \(mdalal\)" <> Wed, 23 May 2007 17:46 UTC

Return-path: <>
Received: from [] ( by with esmtp (Exim 4.43) id 1Hquuu-00063i-Sw; Wed, 23 May 2007 13:46:32 -0400
Received: from [] ( by with esmtp (Exim 4.43) id 1Hquut-00063d-Jb for; Wed, 23 May 2007 13:46:31 -0400
Received: from ([] by with esmtp (Exim 4.43) id 1Hquut-0000z7-1J for; Wed, 23 May 2007 13:46:31 -0400
Received: from ([]) by with ESMTP; 23 May 2007 10:46:30 -0700
X-IronPort-AV: i="4.14,570,1170662400"; d="scan'208,217"; a="487979213:sNHT295208744"
Received: from ( []) by (8.12.11/8.12.11) with ESMTP id l4NHkUYq006264; Wed, 23 May 2007 10:46:30 -0700
Received: from ( []) by (8.12.10/8.12.6) with ESMTP id l4NHkB2Y020512; Wed, 23 May 2007 17:46:30 GMT
Received: from ([]) by with Microsoft SMTPSVC(6.0.3790.1830); Wed, 23 May 2007 10:46:26 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: RE: [tcpm] TCP Secure
Date: Wed, 23 May 2007 10:46:26 -0700
Message-ID: <>
In-Reply-To: <>
Thread-Topic: [tcpm] TCP Secure
Thread-Index: AceZVNkemAiLQ7iLRQKC0/WDRCqdNgEDQeRw
From: "Mitesh Dalal (mdalal)" <>
X-OriginalArrivalTime: 23 May 2007 17:46:26.0662 (UTC) FILETIME=[495E4860:01C79D62]
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=5998; t=1179942390; x=1180806390; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;;; z=From:=20=22Mitesh=20Dalal=20\(mdalal\)=22=20<> |Subject:=20RE=3A=20[tcpm]=20TCP=20Secure |Sender:=20; bh=+pJfYyZCKtzkaGRBU7ecQq1hZr0uJIQ0bZALGiNXWLk=; b=aUtKZsjwgdB4Lbwn1vAmZqPVW973qRNsH1KpMiy2FSH2i/Nt4Kunm23KESf3QsMHW2lV522f vVH+r08zHenQdxzYNEwkstXI8TtRb/LwU2ql+obF0kNMxrpNUyzk5vCY;
Authentication-Results: sj-dkim-4;; dkim=pass ( sig from verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3971661e40967acfc35f708dd5f33760
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <>
List-Unsubscribe: <>, <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
Content-Type: multipart/mixed; boundary="===============0716728146=="

Hi Toby,
Please see inline.


	From: [] 
	Sent: Friday, May 18, 2007 7:00 AM
	Subject: [tcpm] TCP Secure


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

	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

	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.


tcpm mailing list