Message-ID: <20030624141213.59998.qmail@web41409.mail.yahoo.com>
Date: Tue, 24 Jun 2003 07:12:13 -0700 (PDT)
From: Abhijit Lahiri <abhijit_lahiri@yahoo.com>
Subject: Clarification requested on iscsi-draft-20 w.r.t target behavior on error conditions
To: ips@ece.cmu.edu
Cc: abhijit_lahiri@yahoo.com, supriyo_p2003@yahoo.com
In-Reply-To: <OF1E0FF01D.15B2D61F-ONC2256D4F.0019F0D6-C2256D4F.003574B9@telaviv.ibm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

Hi All,

We are in the process of desigining an iscsi target
simulator as per draft-ietf-ips-iscsi-20.txt. 

The draft does not seem to be explicit about an ISCSI
target's behavior on encountering the following error
conditions.

1. Logout Request contains non zero DataSegmentLength

2. Write or Data-Out PDU contains data more than 
   MaxRecvDataSegmentLength

3. When pre-negotiated KeyValue pairs (like
InitialR2T, 
   ImmediateData, DataPDUInOrder etc) are not
   honoured in Full Feature Phase
   ("not honouring", also means violation of result 
    function rules)

4. When the sequence of PDUs (DataSN for Data-Out, 
   R2TSN for R2T, CmdSN for Command) are not in 
   increasing order

5. SNACK PDU sent for an iSCSI PDU already 
   acknowledged 

6. If NOP-Out ping request is sent in response to a 
   a NOP-In ping request

7. Renegotiating KeyValue pairs which are not 
   permitetd FFP,. (viz. MaxConnections)

Will such erors always result in a reject PDU with
appropriate error code ? In fact few of the above
cases does not map to an appropriate error code
listed.


It would be great if someone can help us out. 


Thanks in Advance,
-Abhijit Lahiri


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com