SCSI MIB: Open Issues

["Michele Hallak - Stamler" <michele@sanrad.com>]

Hi,
I compiled and made all the changes that were suggested/commented in the different emails.
However, I have some open issues and I would like help from the group regarding them.
See my questions preceded by MHS>>>>>>

**************************************************************************************************************
From Robert Elliott email:
subject: RE: draft-ietf-ips-scsi-mib-04 comments.
Sent: Monday, December 09, 2002 22:28


"   scsiLuOutQueueFullStatus   OBJECT-TYPE 
     SYNTAX         Counter32 
     MAX-ACCESS     read-only 
     STATUS         current 
     DESCRIPTION 
          " This object represents the number of queue full statuses 
          received by this logical unit." 
     ::= { scsiLuEntry 14 }  "

COMMENT: There is no QUEUE FULL in SCSI-3; that's a SCSI-2 term.  Use
"TASK SET FULL".

MHS>>>>>>>>>> Knowing that we are SCSI-2 compliant and not SCSI-3, how should we call this
MIB object?

****************************************************************************************************************
From Marjorie Krueger's email:
subject: Comments on draft-ietf-ips-scsi-mib-04
Sent: Wednesday, December 11, 2002 21:40

6)scsiInstAlias, scsiDeviceAlias, etc -why are these admin strings 
limited to 79 characters?  IMO, these SYNTAX should just be SnmpAdminString
w/no additional size limitation.

MHS>>>>>>>>>> I would like to hear other opinions.

8) scsiDscLunLun - the discovered LUN number is a natural index for this
table, there is no need for another artificial index.  So this table 
should look like: ......

MHS>>>>>>>>>>> LUN is generally an 8-bytes integer that can be 0:
1. To have it as an index looks heavy from my point of view.
2. It is generally not recommended to have 0 as an index.
I would like to get other opinions before doing the changes.


*********************************************************************************
Thanks a lot,

	Michele