Re: Fast multi-task abort model

On Dec 6, 2005, at 5:13 AM, Ken Sandars wrote:

> Hi Bill,
>
> I'm thinking a sequence reception timeout for the outstanding TTT's 
> will
> come into effect for your scenario. However, there's always the fun of
> determining how long that timeout needs to be...
>
> Also, the target might use Nop-In ping PDUs to detect path loss - dead
> initiators send no responses. This would lead to connection transport
> failure, another timeout and then more clearing effects. Again, how 
> quickly
> this happens with respect to boiling HCT test scenarios is another 
> matter.

You're right, and that's why I was talking about timeouts earlier in 
this thread. Like a month or two ago.

The problem I see with this is that we have, until now, left timeouts 
to the implementors. But now for this all to work, we have to pay 
attention to them. And, to how _other_ initiators have timeouts 
configured. Since to perform the abort, I have to wait for someone 
else's TTTs to clear.

Also, as an administrator, I would really object to having to wait for 
the TTT timeouts. I'm _aborting_ the task, why do I have to wait for it 
to time out? :-)

Take care,

Bill

_______________________________________________
Ips mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ips