RE: ISCSI: Unsolicited data in draft v12

[Paul Koning <ni1d@arrl.net>]

Excerpt of message (sent 8 April 2002) by John Hufferd:
> 
> Matthew,
> I would have thought that if there is some special buffer space set aside
> for the session, whether physical set aside or as a high/low water mark, it
> would still be available for other tasks in the session, even if some tasks
> do not use it, so I fail to see the true impact.

That doesn't sound right.  Either it's reserved, or it's available for
others.  If it's available for others, then others may use it, and
when they do, it won't be there anymore when its original intended
user calls on it.

You can't have it both ways in resource management: either you reserve
resources to guarantee they will be there, in which case they sit
unused if not called on, or you share resource pools and hope you
don't run out.

I don't have a strong opinion on allowing the omission of unsolicited
data if it was negotiated, but I see the sense of the argument.

      paul