Re: login response for non-login request.
"Sukanta Ganguly" <sganguly@opulentsystems.com> Sat, 28 September 2002 16:33 UTC
Received: from ece.cmu.edu (ECE.CMU.EDU [128.2.136.200]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07249 for <ips-archive@lists.ietf.org>; Sat, 28 Sep 2002 12:33:32 -0400 (EDT)
Received: (from majordom@localhost) by ece.cmu.edu (8.11.0/8.10.2) id g8SFvN227978 for ips-outgoing; Sat, 28 Sep 2002 11:57:23 -0400 (EDT)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from mtiwmhc13.worldnet.att.net (mtiwmhc13.worldnet.att.net [204.127.131.117]) by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id g8SFvMo27973 for <ips@ece.cmu.edu>; Sat, 28 Sep 2002 11:57:22 -0400 (EDT)
Received: from sahara ([12.81.6.184]) by mtiwmhc13.worldnet.att.net (InterMail vM.5.01.05.12 201-253-122-126-112-20020820) with ESMTP id <20020928155716.DCQO8019.mtiwmhc13.worldnet.att.net@sahara>; Sat, 28 Sep 2002 15:57:16 +0000
Message-ID: <200209280900240925.03C74F31@mailhost.worldnet.att.net>
In-Reply-To: <1032978132.20055.7.camel@jackallnx.engasic.istor.com>
References: <1032978132.20055.7.camel@jackallnx.engasic.istor.com>
X-Mailer: Calypso Version 3.30.00.00 (4)
Date: Sat, 28 Sep 2002 09:00:24 -0700
Reply-To: sganguly@opulentsystems.com
From: Sukanta Ganguly <sganguly@opulentsystems.com>
To: Michael Morrison <mmorrison@istor.com>, IPS <ips@ece.cmu.edu>
Subject: Re: login response for non-login request.
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ece.cmu.edu id g8SFvMo27974
Sender: owner-ips@ece.cmu.edu
Precedence: bulk
Content-Transfer-Encoding: 8bit
Hi Michael,
It makes perfect sense. In case of processing the Login request the Target is in the Login processing state machine, if you will. Hence sending a Login reject is the most appropriate response.
The development process also stays simple in that manner.
Regards
Sukanta Ganguly
Opulent Systems
*********** REPLY SEPARATOR ***********
On 9/25/2002 at 11:22 AM Michael Morrison wrote:
>In the last paragraph of section 2.2.3 of draft 17
>
>"Once the Login phase has started, if the target
>receives any PDU except a Login request, it MUST send a Login reject
>(with Status "invalid during login") and then disconnect. If the
>initiator receives any PDU except a Login response, it MUST
>immediately terminate the connection."
>
>Shouldn't the target send back a Reject PDU with PROTOCOL ERROR in this
>case?
>
>why would the target send a Login Response to a non-login request?
>
>Thanks
>
>
>--
>Michael Morrison
>mmorrison@istor.com
>ISTOR Networks
>7585 Irvine Center Dr. Ste 250
>Irvine Ca. 92618
>PGP Key ID:
>http://pgp.mit.edu:11371/pks/lookup?search=0x74C30155&op=index
- Re: login response for non-login request. Bill Studenmund
- Re: login response for non-login request. Sukanta Ganguly
- login response for non-login request. Michael Morrison
- Re: login response for non-login request. Robert D. Russell