1. This MIB module does not compile! The following points will deal with some errors revealed by smilint. For example:
rtcp-xr.mib.txt:10: [1] {other} parse error, unexpected UPPERCASE_IDENTIFIER, expecting QUOTED_STRING
rtcp-xr.mib.txt:21: [5] {} warning: flushing recent incorrect declaration, see previous error(s)
rtcp-xr.mib.txt:26: [1] {} unknown object identifier label `rtcpXrMIB'
These errors are generated because of the LAST-UPDATED clause being left TBD, which is not accepted by the compiler. Actually this is NOT the first version of the MIB, as far as I know, so I see no reason for not filling this in.
2.
rtcp-xr.mib.txt:35: [1] {other} parse error, unexpected LOWERCASE_IDENTIFIER, expecting UPPERCASE_IDENTIFIER
rtcp-xr.mib.txt:45: [5] {} warning: flushing recent incorrect declaration, see previous error(s)
To fix this replace in line 35
SYNTAX SEQUENCE OF rtcpXrVoipEntry
by
SYNTAX SEQUENCE OF RtcpXrVoipEntry
3.
rtcp-xr.mib.txt:48: [1] {other} parse error, unexpected LOWERCASE_IDENTIFIER
rtcp-xr.mib.txt:54: [5] {} warning: flushing recent incorrect declaration, see previous error(s)
rtcp-xr.mib.txt:55: [1] {other} parse error, unexpected COLON_COLON_EQUAL
rtcp-xr.mib.txt:55: [5] {} warning: flushing recent incorrect declaration, see previous error(s)
To fix this replace in line 48
SYNTAX rtcpXrVoipEntry
by
SYNTAX RtcpXrVoipEntry
4.
rtcp-xr.mib.txt:57: [1] {other} parse error, unexpected COLON_COLON_EQUAL, expecting OBJECT
rtcp-xr.mib.txt:84: [5] {} warning: flushing recent incorrect declaration, see previous error(s)
To fix this replace in line 57
rtcpXrVoipEntry ::= SEQUENCE {
by
RtcpXrVoipEntry ::= SEQUENCE {
5. rtcp-xr.mib.txt:87: [5] {integer-misuse} warning: use Integer32 instead of INTEGER in SMIv2
That's quite of self-explanatory - related to rtcpXrVoipIndex
6.
rtcp-xr.mib.txt:88: [2] {} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead
rtcp-xr.mib.txt:89: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB
These errors and warnings and many other are the result of using SMIv1 constructs, which is no longer a practice in the IETF for about ten years.
7.
rtcp-xr.mib.txt:104: [2] {basetype-not-imported} SMIv2 base type `IpAddress' must be imported from SNMPv2-SMI
This is making use of a deprecated TC, and is not IPv6 friendly
Regards,
Dan
_______________________________________________ Audio/Video Transport Working Group avt at ietf.org https://www1.ietf.org/mailman/listinfo/avt