[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Some additional obscure questions...



> At 2/7/2003:01:46 AM, David T. Perkins wrote:
> 

> >then you cannot support
> >the following valid MIB module that must use a forward reference:
> >
> >MY-MIB DEFINITIONS ::=
> >BEGIN
> >  IMPORTS
> >      x FROM ...
> >     ;
> >  myMIB MODULE-IDENTITY
> >     ....
> >     ::= { y 1 } -- this is { x 1 1 }
> >
> >  y OBJECT IDENTIFIER ::= { x 1 }
> >END
> 


See RFC 2108 or RFC 2668 for real life, standards track
examples of what Dave referred to above.  A MIB compiler
that cannot handle a forward reference will not be able
to parse either of these modules.

Note that these were both originally SMIv1 modules, and
therefore had no MODULE-IDENTITY.  When converted to
SMIv2,and the MODULE-IDENTITY clauses were defined, the
WG chose to register the MODULE-IDENTITY under the original
OID for the module.  Probably not the best practice, but
an entirely legal one.  Note that SMIv2 does not allow any
definitions between the IMPORTS and MODULE-IDENTITY, so putting
y before myMIB is not possible.

John