|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] iSCSI: question and wording of RejectDoes a target need to send a Text Response after it has sent a Reject for the Text Request? The 2nd sentense in sec 6.2 says a Text Response PDU must be returned, but the 3rd sentense seems to be conflicting. Please clarify. on page 85 (draft 13): A target may reset an operational parameter negotiation by answering a Text request with a Reject. on page 105: 6.2 Usage Of Reject PDU in Recovery Targets MUST NOT implicitly terminate an active task by sending a Reject PDU for any PDU exchanged during the life of the task. If the target decides to terminate the task, a Response PDU (SCSI, Text, Task etc.) must be returned by the target to conclude the task. If the task had never been active before the Reject (i.e., the Reject is on the command PDU), targets should not send any further responses because the command itself is being discarded. In general, the word "Reject" is pretty overloaded, it would be more clear to explicitly say "Reject PDU" for all situations that refer to the Reject PDU. Here are some of those situations: "Reject" in 2nd paragraph on page 85; "Reject" in 3rd paragraph on page 85; "Reject" in sec 6.9 page 110; "Reject" in 2nd paragraph on page 160; "Reject" in 1st paragraph on page 172; "Login Reject" on page 79: there is no reason code called "Login Reject", maybe the word Reject should be changed to lower case, to be consistent with the other occurances of "Login reject". Thanks, Dennis
Home Last updated: Sat Jun 22 15:18:47 2002 10944 messages in chronological order |