Re: Importing items used in MODULE-COMPLIANCE and AGENT-CAPABILITIES

["C. M. Heard" <heard@pobox.com>]

On Sun, 8 Dec 2002, David T. Perkins wrote:
> On this issue, I suggest that those with strong opinions write
> some example MIB modules containing the MODULE-COMPILANCE and
> AGENT-CAPABILITIES constructs.
> 
> I did this many years ago, and for me having the redundant IMPORTS
> seemed a little silly.
> 
> Try it, and provide a URL to your example MIB modules.
> Here is my example that contains two MIB modules. The first
> has no imports and the second has imports.
> http://www.snmpinfo.com/EX-MIB.txt

OK, here is an Internet Draft with a real-life example, with every
externally-defined symbol imported, including the ones used only
in the conformance statement:

http://www.ietf.org/internet-drafts/draft-ietf-hubmib-wis-mib-04.txt

Since I don't have facilities for putting stuff on the web, I'll
have to settle for telling people what might be left out:

(a) if object groups are imported but object names appearing only
in OBJECT clauses are not, then sonetMediumType, sonetMediumLineCoding,
sonetMediumLineType, sonetMediumCircuitIdentifier, sonetMediumLoopbackConfig,
sonetSESthresholdSet, and sonetPathCurrentWidth could be omitted;

(b) if we don't import any externally-defined descriptors that are
used only in the conformance statement, then we'd import nothing at
all from the SONET-MIB.

Note that option (a) would be legal but option (b) would not, if we
stick to RFC 2578 and RFC 2580 as actually written.

//cmh