Re: Section 4.1 (Login Phase)

["Santosh Rao" <santo_rao@hotmail.com>]

Julian,

Are you saying the Reject is NOT meant to be used for all format errors (?)

How then is the following description of Reject PDU (Section 2.19) to be interpreted :

"It may happen that a target receives a message with a format error
   (inconsistent fields, reserved fields not 0, inexistent LUN etc.) or
   a digest error (invalid payload or header). The target returns the
   header of the message in error as the data of the response.
   
2.20 Reason
   
   The reject Reason is coded as follows:
   
      1 - Format Error
      2 - Header Digest Error
      3 - Payload Digest Error ""

Why are 2 mechanisms required to indicate format errors ? The one in Login response (reject with F=0) seems redundant.

- Santosh

>From: julian_satran@il.ibm.com

>To: ips@ece.cmu.edu

>Subject: Re: Section 4.1 (Login Phase)

>Date: Sun, 4 Feb 2001 11:52:00 +0200

>

>

>

>wrong. Julo

>

>Santosh Rao

on 02/02/2001 18:46:20

>

>Please respond to Santosh Rao

>

>To: Julian Satran/Haifa/IBM@IBMIL

>cc: santoshr@hpcuhe.cup.hp.com (Santosh Rao)

>Subject: Section 4.1 (Login Phase)

>

>

>

>

>Julian,

>

>The following sentence :

>

>"Login reject with Final bit 0 is a format error."

>

>needs to be removed from the draft. I believe the

>Reject PDU is intended to communicate all format

>errors on any PDU (?)

>

>Regards,

>Santosh

>

>--

>#################################

>Santosh Rao

>Software Design Engineer,

>HP, Cupertino.

>email : santoshr@cup.hp.com

>Phone : 408-447-3751

>#################################

>

>

>

---

Get your FREE download of MSN Explorer at http://explorer.msn.com