|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: Proposal into smaller documents> -----Original Message----- > From: Douglas Otis [mailto:dotis@sanlight.net] > Sent: Friday, October 06, 2000 11:47 AM > To: Ips > Subject: Proposal into smaller documents > > > All, > > As a means to prevent new name servers being required together will > real-time authentication, third-party commands should be > restricted to SCSI > address space. A SCSI address may be transparently bridged > across IP space, > but such bridging information will not be included within the SCSI > transport. This IP configuration is within the domain of the > provider and > real-time configuration would be prohibitive. If dynamic > routes must be > used, these routes will be created in table form at time of > authentication > with an authentication database. > This raises a profound issue since there's no such thing as "SCSI Address space". i.e.: An address space that's independent of the transport layer. If such an address space were to be defined, there'd be a number of corollary issues, such as: a) How to translate from SCSI address space to transport address space. b) How to enforce the implicit assumption that the copy manager always has the same view of the network as the initiator. i.e.. Ensuring that the copy manager resolves the address of the SCSI device passed in the copy command to the device intended by the initiator. Charles
Home Last updated: Tue Sep 04 01:06:46 2001 6315 messages in chronological order |