Re: iSCSI: 2.2.6. Naming & mapping

["John Hufferd/San Jose/IBM" <hufferd@us.ibm.com>]

Pierre, You said
"Yes, it is not a transport issue, but why not request that now before
people
start building iSCSI controllers if it simplifies the life of everybody?
I don't know how FC managed to have their WWN but why could not we do the
same thing?"

Again, you mixed concepts, that is a "port" attribute (WWN) which is a
Transport item, and LUs specific names which is a SCSI issue.

However, there are still things associated with iSCSI which may address
some of the things you are interested in.  Specifically, there are reasons
for a Connection to be "bound" to a specific set of LUs   We are defining a
concept of a LU view, that will permit, the storage controller to know what
LU Views to give to any specific connection.   This is of value to the
Storage Controller as an entity, and the names and associations will
probably be saved in the Discovery Database (LDAP). However, this is my
hallucination, and has not been defined by the Workgroup.

The Workgroup has already agreed to work on the items that are needed for
Discovery, etc. in one of the next work assignments following the
definition of the iSCSI protocol.  There will also be the need to have a
process that defines Names and View Mapping (see section 2.2.6).  There
will need to be, of course a way for the setting and naming the LU View
maps.  All of that is beyond the iSCSI protocol specification.  The iSCSI
protocol (2.2.6 & 3.17), however, has specified the protocol needed to
carry the View information.

Now, please lets focus on the iSCSI Transport Protocol Draft and take on
these LU naming issues at the approprate time.

.
.
.
John L. Hufferd