Re: Asynchronous Message: Session Termination

[Mark Bakke <mbakke@cisco.com>]

Matt-

I think that you can get the functionality you want by sending the other
Async message type (3) on each of the connections that you want the
initiator to clean up and drop.  This seems sufficient.
 
      3    Target indicates it will/has dropped the connection - the 
      Parameter1 field will indicate on what CID while the Parameter2 
      field indicates, in seconds, the minimum time to reconnect and 
      Parameter3 the maximum time to reconnect. 

I still think that the intent of (4) was to drop the whole session; at
any rate, this is a necessary feature to allow a target to reboot or
fail over reasonably cleanly.

I think if we word (3) and (4) right, we will be able to support both
types of intent.

--
Mark

Matt Wakeley wrote:
> 
> Mark Bakke wrote:
> >
> > Matthew-
> >
> > The intent of these was not to connect and re-establish the same
> > session after a set amount of time; it was to inform the initiator
> > not to try to establish a new session until the time passes, which
> > is I think what you want.
> 
> Mark,
> 
> I don't think that was the intent of this feature.  Just because a target
> drops all it's connections, does not mean that the session is closed. In fact,
> the "maximum" time seems to indicate that if a connection is not tried within
> that amount of time, then the session will be aborted, or some other action
> taken.
> 
> Obviously, clarification on the intent is required, and then clarification in
> the text.
> 
> -Matt

-- 
Mark A. Bakke
Cisco Systems
mbakke@cisco.com
763.398.1054