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 h084fvg08537
	for ips-outgoing; Tue, 7 Jan 2003 23:41:57 -0500 (EST)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from procsys.com (203-195-197-22.now-india.net.in [203.195.197.22] (may be forged))
	by ece.cmu.edu (8.11.0/8.10.2) with SMTP id h084fpW08531;
	Tue, 7 Jan 2003 23:41:52 -0500 (EST)
Received: from procsys.com ([192.168.1.71]) by procsys.com with SMTP; Wed, 08 Jan 2003 10:19:42 -0530
Message-ID: <3E1BABE6.688824F6@procsys.com>
Date: Wed, 08 Jan 2003 10:11:10 +0530
From: "Eshanye.K.P" <esha@procsys.com>
X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: owner-ips@ece.cmu.edu, ips@ece.cmu.edu
Subject: need info regarding checksum algorithm
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

Hello,

Need some information. FC data traffic contains the checksum before SOF.
Can anybody tell me which is the algorithm generally used by the FC
world for this. Is it Fletcher Checksum - RFC 905 or Nakassis for
optimized computation of checksum - RFC 1008.  Does any standard (like
FC-FS or any scsi standard) talk about this ?

Regards
Esha

