But it says it is ignored if ERL == 0
below:
10.15.3 Time2Wait
If the Logout response code is 0 and if the
operational
ErrorRecoveryLevel is 2,
this is the minimum amount of time, in
seconds,
to wait before attempting task reassignment. If the Logout
response
code is 0 and if the operational ErrorRecoveryLevel is less
than 2,
this field is to be ignored.
I can see a case where the target may not
have enough time to setup for another login unless the initiator delays for a
short time.
Eddy
-----Original Message-----
From: Julian Satran
[mailto:Julian_Satran@il.ibm.com]
Sent: Thursday, April 17, 2003 1:15 PM
To: Eddy Quicksall
Cc: Ips@Ece.Cmu.Edu
(ips@ece.cmu.edu); owner-ips@ece.cmu.edu
Subject: Re: delay before next
login
Eddy,
Time2Wait
implies it. It talks about reassignment because that is where time counts.
There
is also a typo in the last statement. Instead of:
...a
new Logout may be attempted
should
read
...a
new Login may be attempted
Julo
|
Eddy Quicksall
<eddy_quicksall@ivivity.com>
Sent
by: owner-ips@ece.cmu.edu
17/04/03
17:13
|
|
To
|
"Ips@Ece.Cmu.Edu (ips@ece.cmu.edu)"
<ips@ece.cmu.edu>
|
|
cc
|
|
|
Subject
|
delay before next login
|
|
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?
Eddy
EMAIL: Eddy_Quicksall@iVivity.com
