"Holes" in oid sequence.

Is it "legal" to define a MIB with holes in the oid numbering to 
allow for features that are unknown today to be added at a later date??? 
I.e., a table with oids:

   .1.3.6.1.....23.1.1
   .1.3.6.1.....23.1.2
   .1.3.6.1.....23.1.3                 <- 4,5,6,7,8,9 skipped.
   .1.3.6.1.....23.1.10
   .1.3.6.1.....23.1.11

    I tried it for kicks, and I got the following in snmpd.log.

unknown column 4 in _RaidControllerTable_get_column
unknown column 5 in _RaidControllerTable_get_column
unknown column 6 in _RaidControllerTable_get_column...

    I understand that just because I got the above message doesn't mean 
it's illegal, but it did make me take notice. I tried to read up on it, 
and I couldn't find anywhere that it wasn't ok. Does anyone know? If 
it's not ok, what is the proper way to future-proof your MIB?

    Thanx, tom.c
--------------------------------------------------------

CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and contains information that is confidential and proprietary to Applied Micro Circuits Corporation or its subsidiaries. It is to be used solely for the purpose of furthering the parties' business relationship. All unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users