[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: some IETF SMIv2 MIB metrics

To: heard@pobox.com
Subject: Re: some IETF SMIv2 MIB metrics
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
Date: Tue, 17 Dec 2002 22:41:13 +0100
Cc: mreview@ops.ietf.org
In-reply-to: <Pine.LNX.4.10.10212171315060.14104-100000@shell4.bayarea.net>(heard@pobox.com)
References: <Pine.LNX.4.10.10212171315060.14104-100000@shell4.bayarea.net>

>>>>> C M Heard writes:

Mike> I'm curious as to why Integer32 and Unsigned32 are missing from
Mike> this table.  (It might also be useful to include predefined
Mike> ASN.1 types such as INTEGER, OCTET STRING, and OBJECT IDENTIFIER
Mike> also.)

The libsmi uses the SMIng data type model internally which means that
Integer32 and Unsigned32 are base types while Counter32 and Gauge32
are derived types. I did not count the usage of (libsmi) base types
and I did not spend efforts to exclude the (SMIv2) base types and this
is why things look a bit surprising from the outside.

Perhaps I should also count base type usage, but then the references
to SNMPv2-SMI would probably go up somewhere into the 90% region.

/js

-- 
Juergen Schoenwaelder    <http://www.informatik.uni-osnabrueck.de/schoenw/>

References:
- Re: some IETF SMIv2 MIB metrics
  - From: "C. M. Heard" <heard@pobox.com>

Prev by Date: Re: some IETF SMIv2 MIB metrics
Next by Date: RE: Issue with MIB compilation requirement in "AD Review of I-Ds" (http://www.ietf.org/ID-nits.html)
Previous by thread: Re: some IETF SMIv2 MIB metrics
Index(es):
- Date
- Thread