New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strict SMIv1 and SMIv2 parsing #4

Closed
cederberg opened this Issue Dec 8, 2011 · 2 comments

Comments

Projects
None yet
1 participant
@cederberg
Copy link
Owner

cederberg commented Dec 8, 2011

When parsing SMIv1 files, any usage of symbols or constructs from SMIv2 should trigger a warning.

The opposite goes for SMIv2 files.

@cederberg

This comment has been minimized.

Copy link
Owner

cederberg commented Dec 28, 2016

The simplest possible implementation should probably identify and categorize these three basic MIB imports. Warning could be issued when using "pre-SMIv1" or when mixing SMIv1 and SMIv2.

Macro definitions — OBJECT-TYPE (and more for SMIv2):

  • pre-SMIv1: RFC1065-SMI and RFC1155-SMI
  • SMIv1: RFC-1212
  • SMIv2: SNMPv2-SMI

SMI definitions — enterprises, IpAddress and others:

  • pre-SMIv1: RFC1065-SMI
  • SMIv1: RFC1155-SMI
  • SMIv2: SNMPv2-SMI

Textual conventions — DisplayString, PhysAddress and others:

  • pre-SMIv1: RFC1158-MIB
  • SMIv1: RFC1213-MIB
  • SMIv2: SNMPv2-TC

Warnings should probably also be issued when using a macro def without prior import.

@cederberg

This comment has been minimized.

Copy link
Owner

cederberg commented Dec 30, 2016

Closing. Fixed in 2.10.

@cederberg cederberg closed this Dec 30, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment