SES-1 v. SES-2 clarification

Rich Ramos t10 at RichRamos.com
Tue Jul 6 11:22:10 PDT 2004


* From the T10 Reflector (t10 at t10.org), posted by:
* Rich Ramos <t10 at RichRamos.com>
*

I'm trying to figure out if some wording change between SES-1 and 
SES-2 was a change in function or just a clarification.  In section 
4.1.2 in SES-1, which is section 4.1.3 in SES-2, it more or less says 
all the same thing except the following sentence:

SES-1:
SCSI device servers set the enclosure services bit (ENCSERV) in the 
standard INQUIRY data (see ANSI X3.301) to indicate that they are 
capable of transporting enclosure services information if an 
enclosure services process is connected to the device.

SES-2:
SCSI device servers set the ENCSERV (enclosure services) bit in the 
standard  INQUIRY data (see SPC-3) to indicate that they are capable 
of transporting enclosure services information to an  attached 
enclosure services process.


The wording in SES-1 would seem to allow implementations of devices 
that are capable of Enclosure Services but that if they don't 
actually have an encserv process attached that they won't set the 
EncServ bit.  The wording in SES-2 seems to remove this allowance. 
Do people agree that the wording in SES-1 allows for such a case or 
not?  If so, then this would be a functional change between 1 and 2, 
correct?

-Rich
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org




More information about the T10 mailing list