Re: "Holes" in oid sequence.

On Wed, 14 Sep 2005 09:01:50 +0100 Dave wrote:
DS> On Tue, 2005-09-13 at 09:15 -0700, Tom Cumming wrote:
DS> > Is it "legal" to define a MIB with holes in the oid numbering
DS> 
DS> Yes.
DS> Relatively unusual, but perfectly legal.

Actually, I don't think that's right. per RFC 2578, Section 10.2:

Object Definitions

   An object definition may be revised in any of the following ways:

[...]

(7)  A conceptual row may be augmented by adding new columnar objects at
     the end of the row, and making the corresponding update to the
     SEQUENCE definition.


This says you can't go back and fill holes. I'm not sure they they considered
leaving holes, so this was written with the assumption that there wouldn't be
any. At any rate, it appears to rule out new object in the middle (though I
can't think of a good reason why).

-- 
NOTE: messages sent directly to me, instead of the lists, will be deleted
      unless they are requests for paid consulting services.

Robert Story; NET-SNMP Junkie
Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp>  
Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-users>

You are lost in a twisty maze of little standards, all different. 


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. 
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
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