Message-ID: <3E66DC79.46D00A51@npd.hcltech.com>
Date: Thu, 06 Mar 2003 10:58:25 +0530
From: Subrahmanya Sastry K V <skotra@npd.hcltech.com>
Organization: HCLT-NTL
MIME-Version: 1.0
To: Michael Morrison <mmorrison@istor.com>
CC: ips@ece.cmu.edu
Subject: Re: Protocol errors during login.
References: <1046920961.22424.22.camel@jackallnx.inside.istor.com>
Content-Type: multipart/alternative;
 boundary="------------C11D1E5F66768138AB1FC3CA"
Sender: owner-ips@ece.cmu.edu
Precedence: bulk


--------------C11D1E5F66768138AB1FC3CA
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi Mike,

To my understanding of the protocol, when a text parameter which is not
allowed in a particular stage of login phase is sent to the target, it
should
respond back with the status class 0x02 and status detail 0x00 (indicating
the
miscellaneous initiator errors, which may include protocol errors also).
This applies to both the cases mentioned in sections 5.2 and 5.3.

- Sastry


Michael Morrison wrote:

> Howdy folks,
>
> The following paragraphs both mention 'protocol errors' while doing text
> negotiations.
>
> Section 5.2 states:
> The constants "None", "Reject", "Irrelevant", and "NotUnderstood" are
> reserved and MUST ONLY be used as described here. Violation of this rule
> is a protocol error (in particular the use of "Reject", "Irrelevant",
> and "NotUnderstood" as proposed values).
>
> Section 5.3 states:
> "Any given Login request or response belongs to a specific stage; this
> determines the negotiation keys allowed with the request or response. It
> is considered to be a protocol error to send a key not allowed in the
> current stage."
>
> It's not clear to me how "protocol error" status is communicated back to
> the initiator. What Status-Class and Status-Detail values are
> appropriate for a Login Response PDU to indicate "protocol error"?
>
> Thanks
>
> Mike

--
Subrahmanya Sastry K V
HCL Tech, Chennai, INDIA
Ph: +91-44-3728366  Xtn-1146
http://www.hcltech.com/san



--------------C11D1E5F66768138AB1FC3CA
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hi Mike,
<p>To my understanding of the protocol, when a text parameter which is
not
<br>allowed in a particular stage of login phase is sent to the target,
it should
<br>respond back with the status class 0x02 and status detail 0x00 (indicating
the
<br>miscellaneous initiator errors, which may include protocol errors also).
<br>This applies to both the cases mentioned in sections 5.2 and 5.3.
<p>- Sastry
<br>&nbsp;
<p>Michael Morrison wrote:
<blockquote TYPE=CITE>Howdy folks,
<p>The following paragraphs both mention 'protocol errors' while doing
text
<br>negotiations.
<p>Section 5.2 states:
<br>The constants "None", "Reject", "Irrelevant", and "NotUnderstood" are
<br>reserved and MUST ONLY be used as described here. Violation of this
rule
<br>is a protocol error (in particular the use of "Reject", "Irrelevant",
<br>and "NotUnderstood" as proposed values).
<p>Section 5.3 states:
<br>"Any given Login request or response belongs to a specific stage; this
<br>determines the negotiation keys allowed with the request or response.
It
<br>is considered to be a protocol error to send a key not allowed in the
<br>current stage."
<p>It's not clear to me how "protocol error" status is communicated back
to
<br>the initiator. What Status-Class and Status-Detail values are
<br>appropriate for a Login Response PDU to indicate "protocol error"?
<p>Thanks
<p>Mike</blockquote>

<pre>--&nbsp;
Subrahmanya Sastry K V
HCL Tech, Chennai, INDIA
Ph: +91-44-3728366&nbsp; Xtn-1146
<A HREF="http://www.hcltech.com/san">http://www.hcltech.com/san</A></pre>
&nbsp;</html>

--------------C11D1E5F66768138AB1FC3CA--