RE: smilint errors in RAQMON-MIB (resend)
Andy Bierman <[email protected]>
| Newsgroups | gmane.ietf.rmonmib |
|---|---|
| Message-ID | <[email protected]> |
At 01:11 PM 2/28/2005, Romascanu, Dan \(Dan\) wrote: >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]]On Behalf Of Andy Bierman >> Sent: 28 February, 2005 10:59 PM >> To: [email protected] >> Subject: [RMONMIB] smilint errors in RAQMON-MIB (resend) >> >> >> Hi, >> >> The raqmonParticipantDestPayloadType object is supposed to be >> Integer32 >> but it is SYNTAX Unsigned32 in the OBJECT-TYPE macro. Since the range >> includes -1, this is a fatal syntax error. > > >ooooops! It's half right (Integer32 in the SEQUENCE :-) >> >> I also get a warning that the index of row >> 'raqmonParticipantAddrEntry' can exceed OID size >> limit by 154 sub-identifiers. This should be fixed by adding >> ranges as needed. > >I believed that we said that text in the DESCRIPTION clause of the entry is sufficient: > >"Note that there is no concern about the indexation of this >table exceeding the limits defined by RFC 2578 Section 3.5. >According to [RAQMON-FRAMEWORK], Section 5.1, only IPv4 an > IPv6 addresses can be reported as participant addresses." okay, but why can't we put InetAddress (SIZE (4 | 16)) in the SYNTAX clause? Is this bad practice? It currently doesn't mention anything about IPv4 and IPv6 addresses only in the raqmonParticipantAddrType DESCRIPTION or SYNTAX clauses. The MIB should match the normative text in the Framework. >> >> thanks, >> Andy > >thank you! > >Dan Andy >>