Re: time-out for R2T PDUs?

There could be a situation in which NOP-IN PDUs from the target are
sent successfully to the initiator, but some bug causes the initiator
not to send the data-out PDU. According to what you say, the target
may decide that it can't wait anymore and logout, right?

Thanks,
Erez

On Thu, Nov 6, 2008 at 3:09 PM, Julian Satran <[email protected]> wrote:
> Correct - there is no standard time-out. Regards, Julo
>
>
> From: "Deva Ranganathan" <[email protected]>
> To: "Erez Zilber" <[email protected]>
> Cc: [email protected]
> Date: 06/11/2008 04:20
> Subject: Re: [Ips] timeout for R2T PDUs?
> ________________________________
>
>
>
>
> On Thu, Nov 6, 2008 at 2:46 PM, Deva Ranganathan
> <[email protected]> wrote:
> Erez,
>
> I think that this s a target implementation issue wherein the implementation
> can choose the timeout  depending on the availability of resources  and the
> software architecture. A target also has a NOP-IN sent periodically and can
> use this to cleanup  the stale resources as well.
>
> thanks
>
> Deva
> HCL Technologies.
>
>
>
> On Thu, Nov 6, 2008 at 12:54 PM, Erez Zilber <[email protected]> wrote:
> Hi,
>
> I couldn't find an answer to the following question in iSCSI spec:
>
> During the execution of a WRITE command, an R2T PDU is sent from the
> target to the initiator. What should happen if a bug in the initiator
> causes it not to send the data-out PDU? Is there any timeout that will
> allow the target to abort this command?
>
> Thanks,
> Erez
> _______________________________________________
> Ips mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/ips
>
> _______________________________________________
> Ips mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/ips
>
>
>
_______________________________________________
Ips mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ips