Re: [Ips] iSCSI: Correct value for ExpDataSN for bidirectional commands

Not sure why the initiator needs to be reported on the
total # of R2Ts in the final response....I presume
any mismatch in R2Ts is already factored into the status.

_If_ we indeed want to include R2Ts, I think it would be
necessary to make changes (10.4.8, E.2.2, and perhaps 6)
because I believe the current spec semantics are clear
that R2Ts are not included.
-- 
Mallikarjun

Mallikarjun Chadalapaka
Networked Storage Architecture
Network Storage Solutions
Hewlett-Packard MS 5668
Roseville CA 95747
cbm [at] rose.hp.com

Julian Satran wrote:

> It is in fact the Data-In + R2T - Julo
> 
> 
> 
> "Ken Sandars" <ksandars@elipsan.com> 
> Sent by: ips-admin@ietf.org
> 27/01/2004 11:48
> 
> To
> <ips@ietf.org>
> cc
> 
> Subject
> [Ips] iSCSI: Correct value for ExpDataSN for bidirectional commands
> 
> 
> 
> 
> 
> 
> Hi people,
> 
> Does section 10.4.8 which clearly states that ExpDataSN is "the number
> of Data-In (read) PDUs the target has sent for the command" hold for
> bidirectional commands?
> 
> i.e. It's not the number of Data-In and R2T PDUs sent for the command is
> it?
> 
> 
> Thanks again,
> Ken Sandars
> Elipsan UK
> 
> 
> 
> _______________________________________________
> Ips mailing list
> Ips@ietf.org
> https://www1.ietf.org/mailman/listinfo/ips
> 
> 
> 
> _______________________________________________
> Ips mailing list
> Ips@ietf.org
> https://www1.ietf.org/mailman/listinfo/ips

_______________________________________________
Ips mailing list
Ips@ietf.org
https://www1.ietf.org/mailman/listinfo/ips