Re: draft-ietf-ospf-mib-update-04

[Spencer.Giacalone@predictive.com]

Ken, 

Thanks. The first might be a fat finger on my part, but SMIC didnt pick 
the rest up. Let me take a look and get back to you. Imports might be a 
legacy thing. 

Spence






"Chapman, Ken" <KChapman@unispherenetworks.com>
10/19/00 11:41 AM

 
        To:     "'ospf@discuss.microsoft.com'" <ospf@discuss.microsoft.com>
        cc:     "'spencer.giacalone@predictive.com'" <spencer.giacalone@predictive.com>, 
"'djoyal@quantumbridge.com'" <djoyal@quantumbridge.com>, 'Rob Coltun' 
<rcoltun@redback.com>, "'fred@cisco.com'" <fred@cisco.com>, 
"'mibs@ops.ietf.org'" <mibs@ops.ietf.org>
        Subject:        draft-ietf-ospf-mib-update-04


Hi,
I'm not a regular on this list and don't know a whole lot about OSPF; I'm
just an SNMP geek.
But I found some bugs in the MIBs, and I didn't see any issues raised in 
the
archives.

There is a bug in OSPF-TRAP-MIB: 
The last object imported from OSPF-MIB is 
"ospfAreaExtNssaTranslatorStatus";
it should be "ospfAreaNssaTranslatorState".

There are some minor "conformace" issues with the MIBs as presented:

The "00" year part of the dates in the LAST_UPDATED and REVISION clauses
need to be "2000"
(ref: RFC2578 clause 2 (top of page 5).

ospfAuthType is not included in any OBJECT-GROUP definition. 

None of the notifications in OSPF-TRAP-MIB are included in a
NOTIFICATION-GROUP. 
(note: don't forget to import NOTIFICATION-GROUP from SMIv2-CONF.)

While the last two are not violations per se (as far as I can tell from
reading RFC2580),
it makes it difficult to include these items in an AGENT-CAPABILITIES
definition.

I hope this is helpful.
Cheers.
                 Ken