Re: iscsi : DataPDULength can differ in each direction.

[Dave Sheehy <dbs@acropora.rose.agilent.com>]

> Having now accepted that DataPDULength is a "maximum receive pdu length"
> limitation that each end point is allowed to express, this key needs to
> be on a per connection basis, and not a per session basis.
> 
> The reason for this being that limitations on DataPDULength (more aptly,
> max receive pdu length) stem from implementation specific quirks. (One
> of the reasons for allowing this feature, in the first place.). 

Following this same line of reasoning the keys:

	MaxBurstSize
	FirstBurstSize
	MaxOutstandingR2T
	DataPDUInOrder
	DataSequenceInOrder
	ErrorRecoveryLevel

are all potentially implementation specific and should not be categorized
as LO.

Dave