Re: iscsi : DataPDULength can differ in each direction.

["Julian Satran" <Julian_Satran@il.ibm.com>]

If they cooperate they have to share goals. The parameters you quoted don't make sense per connection.
PDUlength makes a lot of sense.

Julo

Dave Sheehy <dbs@acropora.rose.agilent.com> Sent by: owner-ips@ece.cmu.edu 08-10-01 22:43 Please respond to Dave Sheehy

To:        ips@ece.cmu.edu (IETF IP SAN Reflector)         cc:                 Subject:        Re: iscsi : DataPDULength can differ in each direction.

Julian,

> Implementation is not a session parameter :-)

The implementation directly affects the values that a session acquire 
though. :-)

> What do you mean by an implementation specific parameter?  Is it that 
> every connection has a different implementation and they cooperate?

That is the scenario I'm addressing. There has been discussion of late 
which has indicated that initiators may have several different vendors 
products (i.e. implementations) installed at once and that it is expected 
that a session may span those multiple implementations. Each of those 
implementations will have its own constraints and limitations. So, you 
either have to adopt the greatest common denominator approach (i.e. limit 
connections to the intersection of all individual feature sets) or you allow 
each connection to conform to the implementation that it resides on.

Dave