iSCSI: response to second login (with same ISID)

["Jim Hafner" <hafner@almaden.ibm.com>]

Folks,

Santosh has requested a response to this question and I don't think I've
noticed an answer.  It's one of those "dot the i" things that we need to
complete.

The current thinking is that an iSCSI initiator must use a different ISID
for each session it opens with a specific iSCSI target.

We need to decide on the iSCSI target's response when the iSCSI initiator
attempts to break this rule.  The choices are:
1) REJECT the login with some error code (that the iSCSI initiator can
understand or infer to mean "ISID in use") and leave the pre-existing
session alone
2) CLOSE the pre-existing session (and abort all it's tasks) and then
process the new login fresh.

Personally, I have no strong feeling either way, but lean towards option
(1).  It's simple, clean and doesn't involve any interruption.

Anybody else got any opinions?

Jim Hafner