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 h3J3ZsO28026
	for ips-outgoing; Fri, 18 Apr 2003 23:35:54 -0400 (EDT)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from d12lmsgate-3.de.ibm.com (d12lmsgate-3.de.ibm.com [194.196.100.236])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id h3J3Zq328020
	for <ips@ece.cmu.edu>; Fri, 18 Apr 2003 23:35:52 -0400 (EDT)
Received: from d12relay02.de.ibm.com (d12relay02.de.ibm.com [9.165.215.23])
	by d12lmsgate-3.de.ibm.com (8.12.9/8.12.8) with ESMTP id h3J3ZjCi039074
	for <ips@ece.cmu.edu>; Sat, 19 Apr 2003 05:35:45 +0200
Received: from d10ml001.telaviv.ibm.com (d10ml001.telaviv.ibm.com [9.148.216.55])
	by d12relay02.de.ibm.com (8.12.8/NCO/VER6.5) with ESMTP id h3J3ZjHY230764
	for <ips@ece.cmu.edu>; Sat, 19 Apr 2003 05:35:45 +0200
In-Reply-To: <004901c305d8$f3896b10$766f030f@rose.hp.com>
To: ips@ece.cmu.edu
Subject: Re: delay before next login
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.0.1 February 07, 2003
From: "Julian Satran" <Julian_Satran@il.ibm.com>
Message-ID: <OF8DABEF65.C3615AFD-ONC2256D0D.0012FA15-C2256D0D.0013BFF7@telaviv.ibm.com>
Date: Sat, 19 Apr 2003 06:35:41 +0300
X-MIMETrack: Serialize by Router on D10ML001/10/M/IBM(Release 5.0.9a |January 7, 2002) at
 19/04/2003 06:35:45,
	Serialize complete at 19/04/2003 06:35:45
Content-Type: multipart/alternative; boundary="=_alternative 00139C8FC2256D0D_="
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

This is a multipart message in MIME format.
--=_alternative 00139C8FC2256D0D_=
Content-Type: text/plain; charset="US-ASCII"

Eddy, Mallikarjun & others,

I just reread the whole paragraph 10.15.3. I was mistaken in my previous 
note to the list. Time2Wait is the time to the next logout attempt when 
the logout fails.
The time to login (if any) is not specified. If you intend to use a new 
connection for recovery it is up to you to choose the time so that you 
will not let the tasks expire (Time2Retain) but all the rest is up to the 
implementer.

The text has not typos.

Julo
--=_alternative 00139C8FC2256D0D_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Eddy, Mallikarjun &amp; others,</font>
<br>
<br><font size=2 face="sans-serif">I just reread the whole paragraph 10.15.3.
I was mistaken in my previous note to the list. Time2Wait is the time to
the next logout attempt when the logout fails.</font>
<br><font size=2 face="sans-serif">The time to login (if any) is not specified.
If you intend to use a new connection for recovery it is up to you to choose
the time so that you will not let the tasks expire (Time2Retain) but all
the rest is up to the implementer.</font>
<br>
<br><font size=2 face="sans-serif">The text has not typos.</font>
<br>
<br><font size=2 face="sans-serif">Julo</font>
--=_alternative 00139C8FC2256D0D_=--
