RE: iSCSI: NopIn in ping mode can contain data?

["Martin, Nick" <Nick.Martin@compaq.com>]

Aryan,

I believe you are reading too much into "data".  A [NOP-Out or] NOP-In
may contain a payload called "ping data", the format of which is not
specified.  That payload, if present is not iSCSI Data-IN "data" nor
Text Response "data".  If this NOP-In is a response to a NOP-Out then it
is a copy (a.k.a. an echo) of the payload contained in the NOP-Out which
solicited this response.  

This was intended as a way for an Initiator to verify that packets of a
certain length can currently be successfully transmitted over this
connection.

The question being asked is whether a Target, which may send a NOP-In
that is not a response to a NOP-Out, should be allowed to include a
payload to be echoed by the Initiator.  This would allow the Target to
similarly test the connection with various packet lengths.

The answer, now clarified in draft 10 is no, the Target may not send a
NOP-In containing "ping data" except in response to a NOP-Out containing
"ping data".

Thanks,
Nick

Ajit Aryan wrote: 
> 
> 
> Julo,
> By this we should be able to say one thing, NOPIn in ping mode can 
> contain data. What every care has to be taken about the data. 
> Now, what
> should be the solicited data? In sense, the data which the initiator
> could use for tuning, negotiation etc...??
> 
> Aryan
> 
> Julian Satran wrote:
> 
> > 
> > Rod,
> > 
> > Initiators are usually build under the assumption that they are "in 
> > control" - e.g., no unsolicited data.
> > Having them prepare for unsolicited data without good cause 
> does not 
> > seem a good idea.
> > 
> > Julo
> > 
> > 
> > "Rod Harrison" <rod.harrison@windriver.com>
> > 
> > 21-01-02 17:31
> > 
> >        
> >         To:        Julian Satran/Haifa/IBM@IBMIL, <ips@ece.cmu.edu>
> >         cc:        
> >         Subject:        RE: iSCSI: NopIn in ping mode can 
> contain data?
> > 
> >        
> > 
> > 
> > 
> > Julian,
> > 
> >                 What's the reason behind preventing the 
> target sending 
> > ping data? I
> > would have thought it would be just as much use for a 
> target as it is
> > for an initiator.
> > 
> >                 - Rod
> > 
> > -----Original Message-----
> > From: owner-ips@ece.cmu.edu 
> [mailto:owner-ips@ece.cmu.edu]On Behalf Of
> > Julian Satran
> > Sent: Saturday, January 19, 2002 3:23 PM
> > To: ips@ece.cmu.edu
> > Subject: Re: iSCSI: NopIn in ping mode can contain data?
> > 
> > 
> > 
> > No  data - will indicate this in 10 - Julo
> > 
> > 
> > Tow Wang <Tow_Wang@adaptec.com>
> > Sent by: owner-ips@ece.cmu.edu
> > 16-01-02 01:10
> > 
> >        To:        ips@ece.cmu.edu
> >        cc:
> >        Subject:        iSCSI: NopIn in ping mode can contain data?
> > 
> > 
> > 
> > 
> > Hello everybody.
> > 
> > 1) When a target sends out a NopIn as a ping, is it allowed 
> to contain
> > a
> > data segment?
> > 2) If yes,
> >   a) why would anyone send data along?
> >   b) must the initiator echo back the data?
> > 
> > I haven't found a clear answer in draft 9. Thanks for any
> > clarifications.
> > --
> > Tow Wang
> > Adaptec Software Engineer
> > 
> > 
> > 
> 
> 
>