Multiple compilation problems in subnet-mgmt-agent-mib-05

Hi -

First compilation check using [email protected] on
 http://www.ietf.org/internet-drafts/draft-ietf-ipoib-subnet-mgmt-agent-mib-05.txt
found several problems.

1) the Gauge32 type is used, but is missing from the IMPORTS.

2) in the SEQUENCE IbSmaSmInfoEntry, it claims the type of ibSmaSmGuid doesn't
match what appears in the OBJECT-TYPE.  The underlying type of the TC is indeed
OCTET STRING, so one might wonder why the tool complains.  I think it may be
unhappy because fixed-length octet strings (like this one) get special treatment
when used as indexes.  Anyway, the complaint can be eliminated by simply using
the TC's name in the SEQUENCE.

3) The tool doesn't like the name chosen for ibGuidInfoEntry in the ibSmaGuidInfoTable.
It (and picky reviewers) would be happy if the entry were called "ibSmaGuidInfoEntry".
Another possibility would ibSmaGuidTable and ibSmaGuidEntry, since "Info" isn't
terribly descriptive.

4) for the notifications, "ibSmaNotificationPrefix" must have been intended
where "ibSmaNotifications" is currently used.  As currently writtem,
ibSmaPortLinkStateChan, ibSmaLinkIntegrityThresReached,
ibSmaExcessBuffOverrunThres, ibSmaFlowCntrlUpdateTimerExpire
ibSmaCapabilityMaskModified, ibSmaSysImageGuidModified,
ibSmaBadManagementKey, ibSmaBadPartitionKey,
ibSmaBadQueueKey, and ibSmaBadPKeyAtSwitchPort don't
have the right OID structure to permit mapping back and for
to SNMPv1.

5) the module IMPORTS "experimental", "TEXTUAL-CONVENTION",
"SnmpAdminString", and InterfaceIndex, but doesn't use them.  These
should be removed.

 Randy