Re: iSCSI Naming and Discovery

[julian_satran@il.ibm.com]

Ralph,

You are correct. The draft proposes only mapping target-names (the part
assumed to be transport dependent but limited by SPC to 8 bytes!) into SPC
required form.

LUN stays as they are.

Julo

Ralph Weber <ralphoweber@compuserve.com> on 04/10/2000 18:48:36

Please respond to ENDL_TX@computer.org

To:   ips@ece.cmu.edu
cc:    (bcc: Julian Satran/Haifa/IBM)
Subject:  Re: iSCSI Naming and Discovery




I've looked at the source messages and believe that these
comments are not repeats.

Black_David@emc.com wrote:
<snip>

>
> [5] SCSI 3rd party commands need to name LUNs, including
> iSCSI LUNs [Daniel i)]

The EXTENDED COPY command provides fields for the LUN values
so target naming (addressing) is the only issue for 3rd
party commands and T10 has a work in progress to deal with
that ftp://ftp.t10.org/t10/document.00/00-279r0.pdf .  Since
the T10 work in this area is not yet complete, expeditious
input from IPS would be helpful.

<remainder snipped>