Re: iSCSI : More problems with Status SNACK !

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

julian_satran@il.ibm.com wrote:

> 
> IF StatSN is going to become optional a negative response to SNACK while
> keeping up counters for compliance
> could be a good enough solution for a good enough target.
> 
> But I am still not sure that this is the way to go.

Do we agree that Data & Status SNACK capability must be optional ?

If so, these capabilities must be negotiated at login time to optimize
against initiators attempting SNACK and getting rejects on each attempt. 

When both initiator and target know that SNACK is unsupported, what is
the value add in continuing to generate StatSN and ExpStatSN for such an
I-T nexus ? It only adds extra overheads.

- Santosh
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