[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Status compliance check across SMIv1/SMIv2
>>>>> chintan sheth writes:
chintan> Hello,
chintan> what do we do if we want to check the status compliance for
chintan> two MIB objects where one is written using SMIv1 rules
chintan> (mandatory etc.) and the latter using SMIv2 rules (current,
chintan> obsolete etc.). Is "current" equivalent to "mandatory" in
chintan> this case? or is this kind of compliance check across
chintan> SMIv1/SMIv2 allowed?
The SMIv1 STATUS clauses mixes the status of the definition with
conformance requirements. SMIv2 separates them so that the STATUS
clause only defines whether a definitions is current, deprecated or
obsolete. Conformance statements are written in separate conformance
statements. See RFC 2580 for detail or consult Dave Perkin's book
"Understanding SNMP MIBs" for more background info and examples.
/js
--
Juergen Schoenwaelder Technical University Braunschweig
<schoenw@ibr.cs.tu-bs.de> Dept. Operating Systems & Computer Networks
Phone: +49 531 391 3289 Muehlenpfordtstr. 23, 38106 Braunschweig, Germany
Fax: +49 531 391 5936 <http://www.ibr.cs.tu-bs.de/~schoenw/>