Return-Path: <owner-ips@ece.cmu.edu>
X-Sieve: cmu-sieve 2.0
Return-Path: <owner-ips@ece.cmu.edu>
Received: (from majordom@localhost)
	by ece.cmu.edu (8.11.0/8.10.2) id h0O3jLv11858
	for ips-outgoing; Thu, 23 Jan 2003 22:45:21 -0500 (EST)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from marantinetworks.com (66-147-154-67.focaldata.net [66.147.154.67] (may be forged))
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h0O3jAW11850
	for <ips@ece.cmu.edu>; Thu, 23 Jan 2003 22:45:11 -0500 (EST)
Received: from Pverma (Sonic.marantinetworks.com [66.147.154.66])
	by marantinetworks.com (8.11.2/8.11.2) with SMTP id h0O3gRt19820;
	Thu, 23 Jan 2003 19:42:48 -0800
Reply-To: <pverma@marantinetworks.com>
From: "Preetam Verma" <pverma@marantinetworks.com>
To: "'bill'" <bill@strahm.net>
Cc: <ips@ece.cmu.edu>
Subject: RE: How to handle CRC errors?
Date: Thu, 23 Jan 2003 19:41:11 -0800
Message-ID: <006301c2c35a$70a994b0$b6000a0a@maranti.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
In-Reply-To: <011f01c2c355$8ebe2e20$6501a8c0@mobilebill>
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

I meant the PDU has CRC error........not the TCP packet as such.

Preetam

-----Original Message-----
From: bill [mailto:bill@strahm.net]
Sent: Thursday, January 23, 2003 7:06 PM
To: Preetam Verma
Subject: RE: How to handle CRC errors?


Silly question... If the TCP CRC is incorrect, wouldn't the TOE discard
it, NAK the package and get a retransmit ?

Bill

-----Original Message-----
From: owner-ips@ece.cmu.edu [mailto:owner-ips@ece.cmu.edu] On Behalf Of
Preetam Verma
Sent: Thursday, January 23, 2003 3:32 PM
To: ips@ece.cmu.edu
Subject: How to handle CRC errors?


I have a situation like this:

                                            CPU
                                               |
                                               |
<---------------->port<---------->TCP offload engine
<------------->Logic<----------------->Application processing

The logic is going to assemble PDUs and pass them on to the application.
If a PDU that came in has CRC errors, will the application need to
signal the initiator to terminate the session? Say a PDU header from the
TCP offload engine was corrupted, how would the "logic" need to handle
the data that comes later. How do I ensure that the application receives
packets in order? How can I ensure that in such an event the PDU
processing logic does not go out of sync?

Regards

Preetam





