Luis,
On 13/08/07, Luis EG Ontanon <luis.ontanon@xxxxxxxxx> wrote:
> I been thinking about the fact that Wireshark does not really need a
> MIB parser. It just needs to know OIDs, their name and their type.
>
> So I believe we should use a flat file that contains these three
> fields and provide the user with a separate program that actually
> reads the MIBs to maintain this file: like adding and removing
> modules.
There are other file formats than include OID definitions including:
* ASN.1 modules/RFCs (e.g.
http://www.itu.int/ITU-T/asn1/database/itu-t/x/x420/1999/IPMSObjectIdentifiers.html)
* LDAP/X.500 directory schemas (e.g. http://www.faqs.org/rfcs/rfc2798.html)
It would be useful if that program could handle those as well. Would
the use of libsmi (which I know nothing about) limit this?
> A file with basic oids should be provided to the user.
I have been using something like this in my private Wireshark for some
time. It allows me to add names to OIDs that Wireshark doesn't
natively know about, and also rename some of the in-built OID names.
I think it would be very useful to have this sort of functionality as
a mainstream feature.
Are you proposing a single file into which everything is compiled? In
which case will you program handle local, user-added, definitions
(e.g. not derived from a MIB).
Graeme
