|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: iSCSI Naming: WWUIs, URNs, and namespaces> >Are "initiators" being connected to actively by "targets"? > >Via some call back or something? > > Not that I know of. The target has to map each initiator that is logging > in to a particular SCSI resource (or set of resources), which may be > different for each initiator. For example, suppose you have an iSCSI > target node with disk space carved up evenly between two users. When you > log in to that target, you want to be given access to your disk space > allocation, not mine. The initiator identifies itself to the target via > the InitiatorWWUI text key of the Login. The current spec declares that > InitiatorWWUI is globally unique, which makes this mapping easy. If > InitiatorWWUI is unique only within the initiator node, multiple initiator > nodes can choose the same name (e.g., "WindowsLaptop"). We'll have to > qualify it with something else to make it unique, at least to a target that > uses that name to look up the mapping. > As previously discussed in this thread, your terminology is obsolete - the IESG axed the use of "WWUI" and you should be referring to "initiator name" and "target name" or genericly "storage node name". You have not made a case for a need for these names to be globally unique. In any case, fully qualified host names *are* globally unique, are already a part of the IP protocols, and can be used as part of a URL syntax to identify storage node objects. You keep referring to "WindowsLaptop" as the hostname, but that's only part of the hostname. Are you familiar with IP hostname constructs?
Home Last updated: Tue Sep 04 01:05:06 2001 6315 messages in chronological order |