Hi!
Steve> I assume you mean "smidump -f xsd" on the rfc2863 mib (after running it Steve> through smistrip) and not really "smilint -f xsd".
Sorry for the confusion. Yes, I meant smidump. Note, that you don't have to strip MIBs from the RFC documents. All IETF Standard MIBs come with libsmi. So, if libsmi is installed, you can simply use `smidump -f xsd IF-MIB'.
Steve> I did this and the parses generated an error:
Steve> /IF-MIB:1134: index element `ifRcvAddressAddress' of row Steve> `ifRcvAddressEntry' must have a size restriction
Yes, there is a (minor) SMIv2 violation in the IF-MIB.
Steve> So I added a size restriction to the mib and ran smidump -f xsd again Steve> and there were no errors.
I'd suggest *not* to modify existing MIBs (this way). Usually supporting an existing (probably slightly invalid) Standard MIB is more important than supporting a correct `Non-Standard' MIB.
Steve> But, when I opened the xsd, there was no "ifTable" or Steve> "IfEntry", just the "ifEntry". If fact, the xsd output never Steve> seems to include tables, just the entries. Is this Steve> intentional?
Yes, it is intentional. We felt no need for the additional nesting of explicit table elements. E.g., addressing (the elements of) a table in XPath would be no easier (IF-MIB/ifTable/ifEntry vs. IF-MIB/ifEntry).
-frank