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 h3HKcvn05455
	for ips-outgoing; Thu, 17 Apr 2003 16:38:57 -0400 (EDT)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from firegate.attotech.com (firegate.attotech.com [12.32.232.50])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h3HKcq305439
	for <ips@ece.cmu.edu>; Thu, 17 Apr 2003 16:38:52 -0400 (EDT)
Received: from [172.16.1.2] by firegate.attotech.com
	for eddy_quicksall@ivivity.com
	id QAA08401; Thu Apr 17 16:18:01 2003
Subject: Re: delay before next login
Message-ID: <OF09C0988E.85522AC5-ON85256D0B.006F54CC@attotech.com>
Date: Thu, 17 Apr 2003 16:18:01 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
To: eddy_quicksall@ivivity.com
From: AClarke@attotech.com
Cc: ips@ece.cmu.edu
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

>I can see a reason to need a delay after a logout but before the next
login. Time2Wait does not seem to cover that. Is there a way to tell the
initiator to wait before logging in again?
>

In what situation do you expect a delay between logins?  Isn't this a
matter for your TCP stack and target implementation queing and accepting
new connections.  If your target must support multiple initiators (and
connections), expecting a delay does not seem reasonable.

