Peder> Hello, I have attempted to use scotty to test an implementation
Peder> of the workings of the IETF ATOMMIB group. The SNMP parser,
Peder> unfortunately, fails to parse the textual convention MIB of the
Peder> ATOMMIB suite, in the file draft-ietf-atommib-atm2TC-06.txt.
Peder> The problem is that this draft contains two ASN.1 OID values
Peder> with more than one numeric sub-identifier:
Peder> atmTCMIB MODULE-IDENTITY .... ::= { mib-2 37 3 } and
Peder> atmTrafficDescriptorTypes OBJECT IDENTIFIER ::= {mib-2 37 1 1}
[snip]
Peder> I am pretty certain that the construction used in the textual
Peder> convention ATOMMIB is valid. It *is* valid with respect to the
Peder> ASN.1 standard, and I cannot find anything in the SNMP SMI that
Peder> prohibits it's use.
Correct.
Peder> Unfortunately, I do not have a code fix for the problem; I can
Peder> see what causes the problem, but fixing it calls for detailed
Peder> knowledge of the data structures used during parsing.
This is one of the problems with the MIB parser. Unfortunately, this
is not only a parsing problem. To fix this problem, one has to change
the way the internal MIB tree is build. I am not going to fix this
problem until I have time to work on a real lex/yacc based parser.
This is not going to happen soon - for now, there is only the solution
you have described in your mail.
Juergen
-- Juergen Schoenwaelder schoenw@ibr.cs.tu-bs.de http://www.cs.tu-bs.de/~schoenw Technical University Braunschweig, Dept. Operating Systems & Computer Networks Bueltenweg 74/75, 38106 Braunschweig, Germany. (Tel. +49 531 / 391 3283)-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.