RE: smilint errors in RAQMON-MIB (resend)
"Romascanu, Dan \(Dan\)" <[email protected]>
| Newsgroups | gmane.ietf.rmonmib |
|---|---|
| Message-ID | <AAB4B3D3CF0F454F98272CBE187FDE2F07F67A43@IS0004AVEXU1.global.avaya.com> |
> >> 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. > InetAddress (SIZE (4 | 16)) should be OK. According to RFC 2579, the sub-typing rules defined in RFC 2578, Section 11 also apply to TCs. Any advice from MIB Doctors? I'm copying mreview for some more feedback. Thanks, Dan