1. There are no conformance clauses, which leads to another solid bunch of errors
2. Some other warnings refer to un-used IMPORTS
rtcp-xr.mib.txt:3: [5] {import-unused} warning: identifier `Counter32' imported from module `SNMPv2-SMI' is never used
rtcp-xr.mib.txt:3: [5] {import-unused} warning: identifier `Counter64' imported from module `SNMPv2-SMI' is never used
rtcp-xr.mib.txt:3: [5] {import-unused} warning: identifier `Gauge32' imported from module `SNMPv2-SMI' is never used
rtcp-xr.mib.txt:3: [5] {import-unused} warning: identifier `mib-2' imported from module `SNMPv2-SMI' is never used
rtcp-xr.mib.txt:3: [5] {import-unused} warning: identifier `Integer32' imported from module `SNMPv2-SMI' is never used
rtcp-xr.mib.txt:5: [5] {import-unused} warning: identifier `Unsigned32' imported from module `SNMPv2-SMI' is never used
rtcp-xr.mib.txt:6: [5] {import-unused} warning: identifier `OBJECT-GROUP' imported from module `SNMPv2-CONF' is never used
rtcp-xr.mib.txt:6: [5] {import-unused} warning: identifier `MODULE-COMPLIANCE' imported from module `SNMPv2-CONF' is never used
rtcp-xr.mib.txt:7: [5] {import-unused} warning: identifier `InterfaceIndex' imported from module `IF-MIB' is never used
3. The following text in the 'Security Considerations' section is not appropriate:
In most cases, MIBs are not themselves security risks; if SNMP
security is operating as intended, the use of a MIB to view
information about a system, or to change some parameter at the
system, is a tool, not a threat.
This is not considered enough by the SNMP use practice. This is why a Security Consideration section must include a list of all writeable objects, together with the associated security threats. Also, if there are MIB objects that contain information that may be considered security-sensitive in some environments, this should be mentioned explicitly. See http://www.ops.ietf.org/mib-security.html for the guidelines for a security section.
4. The Reference Section include some non-updated references, including references to SNMPv1. They are also not separated into Normative and Informative References, as recommended. See again http://www.ops.ietf.org/mib-boilerplate.html.
Regards,
Dan
_______________________________________________ Audio/Video Transport Working Group avt at ietf.org https://www1.ietf.org/mailman/listinfo/avt