RE: iSCSI: CmdSN checking and immediate

["Rod Harrison" <rod.harrison@windriver.com>]

	Immediate commands will carry a CmdSN == MaxCmdSN + 1 when the
command window is closed.

	- Rod

-----Original Message-----
From: owner-ips@ece.cmu.edu [mailto:owner-ips@ece.cmu.edu]On Behalf Of
pat_thaler@agilent.com
Sent: Monday, April 01, 2002 11:09 PM
To: Julian_Satran@il.ibm.com
Cc: ips@ece.cmu.edu; owner-ips@ece.cmu.edu
Subject: iSCSI: CmdSN checking and immediate


We have a question about CmdSN checking for immediate commands.
2.2.2.1 (near the top of page 31) says clearly that the target must
check CmdSN on non-immediate commands and reject those outside of
range. What it doesn't make clear is the intention for immediate
commands. Are they MUST NOT check or are they MAY check?

It probably should be MUST NOT check for immediate commands because
when commands arrive in order, they will arrive with a CmdSN less than
ExpCmdSN because they will have the same CmdSN as the preceeding
non-immediate command. Also, where there are multiple TCP connections
they may arrive out of order and have even eariler numbers. However, I
can't think of any reason that they would have a value higher than
MaxCmdSN.

Regards,
Pat