No Subject

["Wijnen, Bert (Bert)" <bwijnen@lucent.com>]

forwarding a bounced posting.
Frank, are you not subscribed?

Bert 

-----Original Message-----
From: Frank Strauss <strauss@ibr.cs.tu-bs.de>
To: Joan Cucchiara <jcucchia@CrescentNetworks.com>
Cc: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
Cc: mibs@ops.ietf.org
Subject: Re: Question on BITS from SNMPv2-SMI
Date: 30 Aug 2001 23:58:07 +0200

Hi!

Joan> Does the BITS type needs to be IMPORTED
Joan> from SNMPv2-SMI?

Joan> I do not see this imported in some of the standard MIBs
Joan> (e.g. RFC2665 (EtherLike-MIB) and RFC2558 (SONET-MIB))
Joan> but one of the MIB compilers I'm using is flagging this
Joan> as an error, but seems to pass through a different
Joan> MIB compiler with no problem.

That one complaining MIB compiler is wrong.

RFC 2578 gives the definitve answer in Section 3.2.:

3.2.  IMPORTing Symbols

   [...]
   Finally, if any of the ASN.1 named types and macros defined in this
   document, specifically:

        Counter32, Counter64, Gauge32, Integer32, IpAddress, MODULE-
        IDENTITY, NOTIFICATION-TYPE, Opaque, OBJECT-TYPE, OBJECT-
        IDENTITY, TimeTicks, Unsigned32,

   or any of those defined in [2] or [3], are used in an information
   module, then they must be imported using the IMPORTS statement.
   However, the following must not be included in an IMPORTS statement:

      - named types defined by ASN.1 itself, specifically: INTEGER,
        OCTET STRING, OBJECT IDENTIFIER, SEQUENCE, SEQUENCE OF type,
      - the BITS construct.



 -frank