Re: iSCSI-related conclusions from Orlando interim Meeting

[Santosh Rao <santoshr@cup.hp.com>]

I assume the below is referring to targets using NOP-IN as a NOP request in
order to test a connection (?)

If so, I don't see how this can result in a loop. A NOP-IN is sent with an
Initiator Task Tag of 0xFFFFFFFF (assuming the errant usage of 0 as a reserved
value were to be fixed in the spec). An initiator on seeing a NOP-IN with an
I.T.T. of 0xFFFFFFFF will respond by sending NOP-OUT with I.T.T. of 0xFFFFFFFF.
When a target receives a NOP-OUT with an I.T.T. of 0xFFFFFFFF, it is aware that
this is a response to a NOP-IN it had originated earlier with a T.T.T that it
specifies.

How is a loop caused in the above scenario ?

However, there is the other issue of the convoluted and non-intuitive logic in
the above approach. There exist benefits of simplicity of understanding by the
usage of NOP-OUT [or NOP Command] for the request and NOP-IN [or NOP response]
for the response.

Regards,
Santosh


Black_David@emc.com wrote:

>
> - Ping/NOP issues
> - NOP responses are not permitted to request responses to avoid
> loops
>
begin:vcard 
n:Rao;Santosh 
tel;work:408-447-3751
x-mozilla-html:FALSE
org:Hewlett Packard, Cupertino.;SISL
adr:;;19420, Homestead Road, M\S 43LN,	;Cupertino.;CA.;95014.;USA.
version:2.1
email;internet:santoshr@cup.hp.com
title:Software Design Engineer
x-mozilla-cpt:;21088
fn:Santosh Rao
end:vcard