[iSCSI][Q+RFC] login response, tsid

[Luben Tuikov <luben@splentec.com>]

From an implementation point of view:

1. TSID is implicitly defined to be an unsigned 16-bit integer.

TSID is only mentioned to be a ``tag'', ``null'', ``0'',
``1'', ``2'', ``entity'' and ``component''.

[NDT] defines ISID, but not TSID.

There need to be a definition of what kind of object TSID
is. _That_ will define the operations which can be performed
on it, not the other way around.

iSCSIv10, 9.1.2 talks only about TSID namespace segregation,
while a TSID object's definition is implicit.

A word on TSID generation MAY be mentioned as well.


2. Login response PDU, status-class, status-detail.

Wouldn't it be better to use one 16-bit unsigned integer
for this information, call it ``status''

Then this ``status'' can be _logically_ split into 
``class'' (8 MSb) and ``detail'' (8 LSb).

But an implementation (HBA, software, etc) will use
it as a 16-bit unsigned integer.

Comments?

-- 
Luben