Re: iSCSI : Login Response PDU Issues.

[Matt Wakeley <matt_wakeley@agilent.com>]

Santosh Rao wrote:
> 
> Julian,
> 
> Some concerns regarding the Login Response PDU section of the latest
> iSCSI draft :
> 
> Section 2.11.3. Login Response Status
> ======================================
> 1) Should targets use a REJECT PDU or Login Response PDU with a status
> of "reject login" to indicate Login Reject ? Section 2.11.3 and 4.4
> contradict each other on this subject.
> 
> A standard REJECT PDU used to reject ALL non-scsi PDUs
> [and ONLY non-scsi PDUs] would be desirable and would provide
> the following benefits :

There already is one.  Check out section 2.19 "Reject".

> o       Allows more specific error information to be conveyed
>         within SCSI Task Mgmt response PDUs and SCSI Response
>         PDUs, on a reject of SCSI Task Mgmt Cmd or SCSI Command.
>         (thru the Response Data for Scsi Response PDU and
>          Response field for SCSI Task Mgmt response PDU).
> 
> o       Consistent with Fibre Channel semantics for the standard
>          LS_RJT for all ELS'. This also allows for easy mapping
>          from iSCSI Response PDUs to FC ELS responses and vice versa
>          in iSCSI-FC bridges.
>          (since an iSCSI-FC bridge would be mapping certain types of
>          operations and their responses from one protocol to another
> like
>           Login. Logout, NOP-OUT, etc.)
> 
> o        REJECT field in the Login Response PDU can be made reserved.
> 
> 2) Whatever the mechanism that will be finally used for login rejection
> [be it the REJECT PDU or "reject login" in login response PDU], it
> should
> make provisions for detailed reason codes and reason explanations that
> allow
> the initiator to determine the cause of the rejection. This does not
> currently exist in the draft.

Perhaps you should provide a detailed list of reason codes and reason
explanations you would like to see.

-Matt Wakeley
Agilent Technologies

> Thanks,
> Santosh