bugMibble MIB Parser - Bugs: bug #16827, Symbols ccitt(0) and...


bug #16827: Symbols ccitt(0) and joint-iso-ccitt(2) are missing

Submitted by:  Bernd Sorgenfrei <berndsorgenfrei>
Submitted on:  Mon 12 Jun 2006 07:02:25 AM UTC  
Severity:  5 - Major Item Group:  Future Improvement
Status:  Fixed Privacy:  Public
Assigned to:  Per Cederberg <cederberg> Open/Closed:  Closed

Add a New Comment (Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


Wed 10 Jan 2007 05:52:05 PM UTC, comment #4:

Version 2.8, including a fix for this issue, has been released.

Per Cederberg <cederberg>
Project AdministratorIn charge of this item.
Sun 17 Sep 2006 05:53:53 PM UTC, comment #3:

The remaining issue of zeroDotZero has now been fixed in the repository. It will be released in the next alpha or beta build of Mibble 2.8.

Per Cederberg <cederberg>
Project AdministratorIn charge of this item.
Wed 28 Jun 2006 07:39:58 AM UTC, comment #2:

Unlike the other suggestions I don't have tested this one. As you have written, for symbol zeroDotZero in SNMPv2-SMI it does not work. If zeroDotZero would be defined with "::= {ccitt 0}" it would work but its "::= {0 0}".

So my further suggestion is that for the well known symbols ccitt(0), iso(1), joint-iso-ccitt(2) Mibble should use the ones defined in DefaultContext, independently if one uses e.g. "::= {ccitt 0}", "::= {ccitt(0) 0}" or "::= {0 0}". All this ways of writing should lead to the same result: "::= {ccitt 0}". For iso and joint-iso-ccitt the appropriate rule should apply.

Importantly the symbols from DefaultContext should have the correct childs. If I load SNMPv2-SMI and ask the child's of ccitt from DefaultContext it does not have one. But it should have zeroDotZero as child. With the above suggestion this should function.

One possiblility is that you provide an additional method in MibLoader. E.g. MibLoader.getRootOid(int rootSymbol), where rootSymbol is one of ccitt, iso and joint-iso-ccitt.

Bernd Sorgenfrei <berndsorgenfrei>
Sun 25 Jun 2006 01:14:44 PM UTC, comment #1:

Thanks for the suggestion. I've now added both these values to the default context. Please download version 2.8.alpha1 and try it out.

Regarding the zeroDotZero symbol, I'm unsure it will really be sufficient to just modify the default context. I don't recall that Mibble does any OID merging if an OID value is specified explicitly (vs by reference).

Also, with this addition of these symbols, I guess the API for MibLoader.getRootOid() is not really that great any more. I'm leaving this bug as open while pondering these issues. Please feel free to comment on what you see as the ideal behavior and/or API.

Per Cederberg <cederberg>
Project AdministratorIn charge of this item.
Mon 12 Jun 2006 07:02:25 AM UTC, original submission:

In RFC 1155 Section 3.1 are the symbols ccitt(0), iso(1) and joint-iso-ccitt(2) listed. The symbol iso(1) is defined in DefaultContext, the symbols ccitt(0) and joint-iso-ccitt(2) should be added to DefaultContext.

With this addition the symbol zeroDotZero(0.0) (e.g. in RFC 2578) has parent ccitt(0).

Bernd Sorgenfrei <berndsorgenfrei>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by cederberg (Posted a comment)

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.




    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2007-01-10 cederberg Open/ClosedOpen => Closed
    2006-09-17 cederberg StatusNone => Fixed
    2006-06-25 cederberg Assigned toNone => cederberg

    Back to the top

    Powered by Savane 3.4