RE: SCSI URL scheme [WAS: Re: iSCSI: 2.2.6. Naming & mapping]

["Douglas Otis" <dotis@sanlight.net>]

Costa,

Why should a transport protocol carry device abstractions?  This a function
best left to an LDAP server.  You could use LDAP as a means to discover
devices, for authentication, and any number of binary representations to
text abstractions.  By keeping this function independent of the transport
layer, you allow flexibility in actual management to be either focused at
the client or at the provider or perhaps a combination of the two.

You should not attempt to solve everything with one specification.

Doug



> -----Original Message-----
> From: owner-ips@ece.cmu.edu [mailto:owner-ips@ece.cmu.edu]On Behalf Of
> csapuntz@cisco.com
> Sent: Sunday, September 17, 2000 11:11 PM
> To: IP Storage
> Cc: csapuntz@cisco.com
> Subject: SCSI URL scheme [WAS: Re: iSCSI: 2.2.6. Naming & mapping]
>
>
>
> Here is a proposal to extend the iSCSI URL scheme to support LUNs and
> WWNs. It was originally proposed by Daniel Smith of IBM Almaden. This
> extension is not required for the iSCSI transport protocol, but may be
> useful for discovery and management.
>
> A URL for the target has the following form:
>
> scsi://hostname/path/with/
>
> A URL referring to a specific LU has the following form:
>
> scsi://hostname/path/with/?LUN=lunnumber?WWN=wwnnumber
>
> If no LUN= term appears in the URL, then LUN 0 is assumed.
>
> The WWN= term is optional. If present, the party should
> verify that the WWN in the LU's Device Identification Inquiry
> Page correspojnds to the WWN.
>
> Note, the following URL:
>
> scsi://gsg.cisco.com/tape/?WWN=0a050a4bcdefa
>
> refers to LUN 0 of target scsi://gsg.cisco.com/tape/. After
> connecting, the initiator should verify that the WWN
> of the LU is 0a050a4bcdefa.
>
> -Costa
>