Return-Path: <owner-ips@ece.cmu.edu>
X-Sieve: cmu-sieve 2.0
Return-Path: <owner-ips@ece.cmu.edu>
Received: (from majordom@localhost)
	by ece.cmu.edu (8.11.0/8.10.2) id h263Mrc09953
	for ips-outgoing; Wed, 5 Mar 2003 22:22:53 -0500 (EST)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from mail1irv.inside.istor.com (host28.istor.com [66.134.214.28])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h263MnM09941
	for <ips@ece.cmu.edu>; Wed, 5 Mar 2003 22:22:49 -0500 (EST)
Subject: Protocol errors during login.
From: Michael Morrison <mmorrison@istor.com>
To: iSCSI <ips@ece.cmu.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Organization: 
Message-Id: <1046920961.22424.22.camel@jackallnx.inside.istor.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 
Date: 05 Mar 2003 19:22:41 -0800
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

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