All RFCs containing MIBs have been checked through rfc3055. This is as of
02/20/2001.

Here is the list of MIBs that were not included in the makefile:

rfc1065     Obsoleted by rfc1155.
rfc1066     Obsoleted by rfc1156.
rfc1067     Obsoleted by rfc1098 then rfc1157.
rfc1085     Appears to be ASN.1 formatted example.
rfc1095     Uses "CHOICE" in one MIB. Obsoleted by rfc1189 (HISTORIC) which
            does not have a replacement MIB.
rfc1098     Uses "CHOICE". Appears to be ASN.1 formatted example.
rfc1142     Not a complete MIB.
rfc1155     Uses "CHOICE". Appears to be ASN.1 formatted example.
rfc1157     Uses "CHOICE". Appears to be ASN.1 formatted example.
rfc1165     Uses "CHOICE". Appears to be ASN.1 formatted example.
rfc1212     An ASN.1 formatted example.
rfc1214     Uses "CHOICE". Appears to be ASN.1 formatted example.
rfc1218     Informational.
rfc1224     Experimental MIB. Definition.
rfc1227     Uses "CHOICE". Appears to be ASN.1 formatted example.
rfc1248     Errors in this MIB are fixed in rfc1252.
rfc1303     ASN.1 style description. Not a MIB.
rfc1442     Uses "CHOICE". Appears to be ASN.1 formatted example.
rfc1443     Attempts to redefine SNMPv2-TC which Emissary doesn't allow.
rfc1444     Attempts to redefine SNMPv2-CONF which Emissary doesn't allow.
rfc1448     Uses "CHOICE". Appears to be ASN.1 formatted example.
rfc1449     Attempts to redefine SNMPv2-TM which Emissary doesn't allow.
rfc1487     Uses "CHOICE". Appears to be ASN.1 formatted example.
rfc1494     Does not appear to be a complete MIB. 
rfc1495     Does not appear to be a complete MIB. 
rfc1507     Uses "CHOICE". Appears to be ASN.1 formatted example.
rfc1508     ASN.1 style description. Not a MIB.
rfc1596     Fatal error. Obsoleted by rfc1604. 
rfc1801     Uses "CHOICE". Appears to be ASN.1 formatted example.
rfc1901     ASN.1 style description. Not a MIB.
rfc1902     Uses "CHOICE". Appears to be ASN.1 formatted example.
rfc1903     Attempts to redefine SNMPv2-TC which Emissary doesn't allow.
rfc1904     Attempts to redefine SNMPv2-CONF which Emissary doesn't allow.
rfc1905     Uses "CHOICE". Appears to be ASN.1 formatted example.
rfc1906     Attempts to redefine SNMPv2-TM which Emissary doesn't allow.
rfc2078     ASN.1 style description. Not a MIB.
rfc2157     MIB is there for OID assignments. "mixer" is not "{ mail 1 }".
rfc2160     Requires rfc2157, which is not a "good" MIB.
rfc2479     ASN.1 style description. Not a MIB. 
rfc2524     Does not appear to be a complete MIB. 
rfc2578     Redefinition of SNMPv2-SMI. 
rfc2579     Redefinition of SNMPv2-TC. 
rfc2580     Redefinition of SNMPv2-CONF. 
rfc2649     Does not appear to be a complete MIB. 
rfc2898     This does not appear to be a correctly formed MIB.
rfc3159     ASN.1 style description. Not a MIB. 
rfc3416     Definition of SNMPv2-PDU, not a complete MIB.
rfc3417     Redefinition of SNMPv2-TM.

Below is the list of files that could be changed to make them compile:

iftype      The line with mfSigLink has a comma after the "(167)", it
            shouldn't.

rfc1156     Got a number of 'rfc1156.mib:nnn: the row object "xxxxxx" must
            have an INDEX clause.' errors. To fix these I added index clauses
            that seemed to make the most sense.

            Also got 'rfc1156.mib:571: expected a string, got }' because of an
            extra comma after the last item in a list.

            The changes are shown below:

               84a63 
               >                           INDEX   { ifIndex }
               301a281
               >                           INDEX   { atIfIndex }
               461a442
               >                           INDEX   { ipAdEntIfIndex }
               510a492
               >                           INDEX   { ipRouteIfIndex }
               588c570
               <                             remote(4),     -- host/network/sub-network
               ---
               >                             remote(4)      -- host/network/sub-network
               878a861
               >                           INDEX   { tcpConnLocalPort }
               999a983
               >                           INDEX   { egpNeighAddr }

rfc1158     DisplayString was not IMPORTed from SNMPv2-TC.

            Got a number of 'rfc1158.mib:nnn: the row object "xxxxxx" must
            have an INDEX clause.' errors. To fix these I added index clauses
            that seemed to make the most sense.

            Got 'rfc1158.mib:671: expected right-brace, got bgp' because of a
            missing comma in a list declaration.

            Got 'rfc1158.mib:510: sequence type "IpAddrEntry" references
            undefined columnar object "ipAdEntReasmMaxSize".' The final 'e'
            was missing from the OBJECT-TYPE definition. Also got
            'rfc1158.mib:711: sequence type "IpNetToMediaEntry" references
            undefined columnar object "ipNetoToMediaType".' where an
            extraneous 'o' had been added to the object name.

            The changes are shown below:

               35c8
               <                            FROM RFC1155-SMI;
               ---
               >                            FROM RFC1155-SMI
               36a10,12
               >                        DisplayString
               >                            FROM SNMPv2-TC;
               > 
               120a97
               >                        INDEX   { ifIndex }
               356a334
               >                        INDEX   { atIfIndex }
               519a498
               >                        INDEX   { ipAdEntIfIndex }
               559c538
               <                ipAdEntReasmMaxSiz OBJECT-TYPE
               ---
               >                ipAdEntReasmMaxSize OBJECT-TYPE
               576a556
               >                        INDEX   { ipRouteIfIndex }
               690c670
               <                                    ospf(13)
               ---
               >                                    ospf(13),
               720a701
               >                        INDEX   { ipNetToMediaIfIndex }
               730c711
               <                    ipNetoToMediaType
               ---
               >                    ipNetToMediaType
               1016a998
               >                        INDEX   { tcpConnLocalPort }
               1126a1109
               >                        INDEX   { udpLocalPort }
               1185a1169
               >                        INDEX   { egpNeighAddr }

rfc1162     For some reason a line containing '[APPLICATION 5]' was inside an
            object definition. This same defintion also included the word
            'IMPLICIT' which mibcomp did not like.

            Got 4 occurrences of the 'rfc1162.mib:nnn: the row object "xxxxxx"
            must have an INDEX clause.' error where the INDEX clause had been
            commented out. Uncommented them.

            The changes are shown below:

               34,35c10
               <                    [APPLICATION 5]
               <                        IMPLICIT OCTET STRING (SIZE (1..21))
               ---
               >                        OCTET STRING (SIZE (1..21))
               197c172
               <                --      INDEX   { clnpAdEntAddr }
               ---
               >                        INDEX   { clnpAdEntAddr }
               239c214
               <                --      INDEX   { clnpRouteDest }
               ---
               >                        INDEX   { clnpRouteDest }
               374,375c349,350
               <                --      INDEX   { clnpNetToMediaIfIndex,
               <                --                clnpNetToMediaNetAddress }
               ---
               >                        INDEX   { clnpNetToMediaIfIndex,
               >                                  clnpNetToMediaNetAddress }
               446,447c421,422
               <                --      INDEX   { clnpMediaToNetIfIndex,
               <                --                clnpMediaToNetPhysAddress }
               ---
               >                        INDEX   { clnpMediaToNetIfIndex,
               >                                  clnpMediaToNetPhysAddress }

rfc1230     The MIB did not IMPORT 'Counter' from RFC1155-SMI. 

rfc1232     Tried to IMPORT DisplayString from RFC1158-MIB, when it should be
            IMPORTed from SNMPv2-TC. This was changed.

rfc1233     Tried to IMPORT DisplayString from RFC1158-MIB, when it should be
            IMPORTed from SNMPv2-TC. This was changed.

rfc1238     Got 'rfc1238.mib:8: IMPORTS clause references unknown module
            "RFC-1213".' and 'rfc1238.mib:732: sequence type
            "ClnpMediaToNetEntry" references undefined columnar object
            "clnpMediaToNetNetAddress".'. These were fixed with the following
            changes:

               7c7
               <                           FROM RFC-1213
               ---
               >                           FROM RFC1213-MIB
               732c732
               <                   clnpMediaToNetNetAddress
               ---
               >                   clnpMediaToNetAddress

rfc1252     Got 'rfc1252.mib:46: INTEGER value must be less than or equal to
            2147483647.' because the top end of an integer range was defined
            as 'FFFFFFFF'h. This was changed to '7FFFFFFF'h.

            Got 'rfc1252.mib:238: sequence type "OspfAreaEntry" references
            undefined columnar object "ospfLSACount".' It appears that the
            ospfLSACount in this definition should have been ospfAreaLSACount.

            Got 'rfc1252.mib:221: INDEX clause for "ospfAreaEntry" references
            undefined object "ospfAreaID".' It appears that ospfAreaID in this
            line should be ospfAreaId.

            The changes to this MIB are shown below:

               46c46
               <              PositiveInteger ::= INTEGER (1..'FFFFFFFF'h)
               ---
               >              PositiveInteger ::= INTEGER (1..'7FFFFFFF'h)
               221c221
               <          INDEX { ospfAreaID }
               ---
               >          INDEX { ospfAreaId }
               238c238
               <              ospfLSACount
               ---
               >              ospfAreaLSACount

rfc1269     Below is a list of the non-cosmetic differences between the MIB in
            the RFC and the installed MIB. The MIB in the RFC does not
            compile. The installed MIB has not been updated to match the code
            from the RFC. The additional import of NetworkAddress would not
            cause an error, just a warning because it is never used.

               4c4
               <                     NetworkAddress, IpAddress, Counter
               ---
               >                     IpAddress, Counter
               346c346
               <                     SYNTAX IpAddress
               ---
               >                     SYNTAX INTEGER
               356c356
               <                     ENTERPRISE { bgp }
               ---
               >                     ENTERPRISE   bgp
               366c365
               <                     ENTERPRISE { bgp }
               ---
               >                     ENTERPRISE   bgp

rfc1289     Got 'rfc1289.mib:720: expected SYNTAX, got SYNTAXINTEGER'. Added a
            space between the two words.

            There were a large number of cases where the compile an error like
            this: 'rfc1289.mib:nnnn: SYNTAX for column object "fooObject"
            conflicts with type in sequence "FooEntry". Mostly the conflict
            were between PhivAddr or PhivCounter types and INTEGERs. PhivAddr
            is defined as OCTET STRING (SIZE (2)) and PhivCounter is defined
            as INTEGER. In cases where the types don't match, the Phiv* side
            of the conflict was arbitrarily selected.

            All of the changes are shown below:

               718c720
               <            SYNTAXINTEGER {
               ---
               >            SYNTAX INTEGER {
               1204c1206
               <            SYNTAX PhivCounter
               ---
               >            SYNTAX PhivCounter (0..65535)
               1305c1307
               <            SYNTAX PhivCounter
               ---
               >            SYNTAX PhivCounter (0..65535)
               1382c1384
               <                    INTEGER (0..65535),
               ---
               >                    PhivAddr,
               1509c1511
               <            SYNTAX INTEGER (0..255)
               ---
               >            SYNTAX PhivCounter (0..255)
               2113c2115
               <            SYNTAX INTEGER ( 0..65535 )
               ---
               >            SYNTAX PhivCounter
               2121c2123
               <            SYNTAX INTEGER ( 0..65535 )
               ---
               >            SYNTAX PhivCounter ( 0..65535 )
               2130c2132
               <            SYNTAX INTEGER ( 0..65535 )
               ---
               >            SYNTAX PhivCounter ( 0..65535 )
               2138c2140
               <            SYNTAX INTEGER ( 0..65535 )
               ---
               >            SYNTAX PhivCounter ( 0..65535 )
               2147c2149
               <            SYNTAX INTEGER ( 0..65535 )
               ---
               >            SYNTAX PhivCounter ( 0..65535 )
               2155c2157
               <            SYNTAX INTEGER ( 0..65535 )
               ---
               >            SYNTAX PhivCounter ( 0..65535 )
               2163c2165
               <            SYNTAX INTEGER ( 0..65535 )
               ---
               >            SYNTAX PhivCounter ( 0..65535 )

rfc1353     A number of changes needed to be made to the IMPORT section:

               4,5c4,6
               <                   system, mib, private, internet    FROM RFC1155-SMI
               <                   OBJECT-TYPE                       FROM RFC-1212;
               ---
               >                   private, internet     FROM RFC1155-SMI
               >                   OBJECT-TYPE           FROM RFC-1212
               >                   mib-2                 FROM SNMPv2-SMI;

rfc1414     Below is a list of the differences between the MIB in the RFC and
            the installed MIB. The MIB in the RFC does not compile. The
            installed MIB has not been updated to match the code from the RFC.

               7c7,8
               <               tcpConnRemAddress, tcpConnRemPort
               ---
               >               tcpConnRemAddress, tcpConnRemPort,
               >               mib-2

rfc1447     Got the following error when trying to compile: "rfc1447.mib:7:
            SNMPv2-SMI doesn't define UInteger32". Changed lines 7 and 78 to
            use Integer32 for now so that the file would compile.

rfc1471     Below is a list of the differences between the MIB in the RFC and
            the installed MIB. The MIB in the RFC does not compile. The
            installed MIB has not been updated to match the code from the RFC.

               194c194
               <                SYNTAX    INTEGER(1..2147483648)
               ---
               >                SYNTAX    INTEGER(1..2147483647)
               208c208
               <                SYNTAX    INTEGER(1..2147483648)
               ---
               >                SYNTAX    INTEGER(1..2147483647)
               564c564
               <                SYNTAX    INTEGER(1..2147483648)
               ---
               >                SYNTAX    INTEGER(1..2147483647)
               578c578
               <                SYNTAX    INTEGER(1..2147483648)
               ---
               >                SYNTAX    INTEGER(1..2147483647)

rfc1472     Below is the only difference between the MIB in the RFC and the
            installed MIB. The MIB in the RFC _does_ compile, but with a
            warning. Because the additional IMPORT is not used, the installed
            MIB has not been updated to match the code from the RFC.

               4,5d3
               <                Counter
               <                     FROM RFC1155-SMI

rfc1473     Below is the only difference between the MIB in the RFC and the
            installed MIB. The MIB in the RFC _does_ compile, but with a
            warning. Because the additional IMPORT is not used, the installed
            MIB has not been updated to match the code from the RFC.

               4,5d3
               <                Counter
               <                     FROM RFC1155-SMI

rfc1474     Below is the only difference between the MIB in the RFC and the
            installed MIB. The MIB in the RFC _does_ compile, but with a
            warning. Because the additional IMPORT is not used, the installed
            MIB has not been updated to match the code from the RFC.

               4,5d3
               <                Counter
               <                     FROM RFC1155-SMI

rfc1512     Below is a list of the differences between the MIB in the RFC and
            the installed MIB. The MIB in the RFC does not compile. The
            installed MIB has not been updated to match the code from the RFC.

               7c7,9
               <                       FROM RFC-1212;
               ---
               >                       FROM RFC-1212
               >                   transmission
               >                       FROM RFC1213-MIB;

rfc1514     Below is a list of the differences between the MIB in the RFC and
            the installed MIB. The MIB in the RFC does not compile. The
            installed MIB has not been updated to match the code from the RFC.

               4a5
               >        mib-2,

rfc1515     Below is a list of the differences between the MIB in the RFC and
            the installed MIB. The MIB in the RFC does not compile. The
            installed MIB has not been updated to match the code from the RFC.

               6a7
               >             mib-2                               FROM RFC1213-MIB

rfc1559     Below is a list of the differences between the MIB in the RFC and
            the installed MIB. The MIB in the RFC does not compile. The
            installed MIB has not been updated to match the code from the RFC.

               1005c1005
               <                 INTEGER,
               ---
               >                 InterfaceIndex,
               1432c1432
               <                 INTEGER,
               ---
               >                 PhivAddr,
               1500c1500
               <                 PhivCounter
               ---
               >                 INTEGER (0..255)
               2165c2165
               <         SYNTAX INTEGER (0..65535)
               ---
               >         SYNTAX PhivCounter (0..65535)
               2173c2173
               <         SYNTAX INTEGER (0..65535)
               ---
               >         SYNTAX PhivCounter (0..65535)
               2182c2182
               <         SYNTAX INTEGER (0..65535)
               ---
               >         SYNTAX PhivCounter (0..65535)
               2190c2190
               <         SYNTAX INTEGER (0..65535)
               ---
               >         SYNTAX PhivCounter (0..65535)
               2199c2199
               <         SYNTAX INTEGER (0..65535)
               ---
               >         SYNTAX PhivCounter (0..65535)
               2207c2207
               <         SYNTAX INTEGER (0..65535)
               ---
               >         SYNTAX PhivCounter (0..65535)
               2215c2215
               <         SYNTAX INTEGER (0..65535)
               ---
               >         SYNTAX PhivCounter (0..65535)

rfc1592     Got error 'rfc1592.mib:9: expected comma or FROM, got OBJECT'.
            Replaced missing semicolon at end of IMPORTS.

            Got errors 'rfc1592.mib:31: The SNMPv2 OBJECT-TYPE macro requires
            a MAX-ACCESS clause, not an ACCESS clause.' and 'rfc1592.mib:40:
            The SNMPv2 OBJECT-TYPE macro requires a MAX-ACCESS clause, not an
            ACCESS clause.'. Changed clauses to MAX-ACCESS.

            Got errors 'rfc1592.mib:32: SNMPv2 objects may not have STATUS
            mandatory or optional.' and 'rfc1592.mib:41: SNMPv2 objects may
            not have STATUS mandatory or optional.'. Changed STATUSes to
            "current".

rfc1604     Below is a list of the differences between the MIB in the RFC and
            the installed MIB. The MIB in the RFC does not compile. The
            installed MIB has not been updated to match the code from the
            RFC. This list does not include the changes to the MAX-ACCESS,
            listed at the bottom of this file, which were required to get the
            file to compile.

               5,8c5,7
               <     Counter32, Integer32,
               <     TimeTicks                                FROM SNMPv2-SMI
               <     DisplayString, PhysAddress,
               <     TimeStamp, RowStatus                     FROM SNMPv2-TC
               ---
               >     Counter32, Integer32                     FROM SNMPv2-SMI
               >     DisplayString, TimeStamp,
               >     RowStatus, TEXTUAL-CONVENTION            FROM SNMPv2-TC

rfc1611     For some reason the following line was not included in the
            installed version of the MIB. It does not generate any compile
            errors.

               157d156
               <        DISPLAY-HINT "4d"

rfc1612     The MIB below had a number of changes due to problems with
            MAX-ACCESS. These are listed at the bottom of this file. In
            addition to that, there was also the difference shown
            below. Because the additional IMPORT is not used, the installed
            MIB has not been updated to match the code from the RFC.

               6c6
               <        TEXTUAL-CONVENTION, RowStatus, DisplayString
               ---
               >        RowStatus, DisplayString

rfc1623     Got 'rfc1623.mib:35: The columnar object "dot3StatsEtherChipSet"
            is not an element of the row sequence type "Dot3StatsEntry".'
            This appears to have been caused by the dot3StatsEtherChipSet
            OBJECT not being included at the end of the Dot3StatsEntry
            SEQUENCE. It has been added.

            Got 'rfc1623.mib:362: INDEX clause for "dot3CollEntry" references
            undefined object "ifIndex".' Later there is a comment saying '-- {
            dot3CollEntry 1 } is no longer in use'. I believe that this might
            have been the original entry for the ifIndex OBJECT. Since it does
            not exist in the MIB and appears to have been removed, the entry
            will be removed from the INDEX clause.

rfc1658     Below is a list of the differences between the MIB in the RFC and
            the installed MIB. The MIB in the RFC does not compile. The
            installed MIB has not been updated to match the code from the RFC.

               4c4
               <        MODULE-IDENTITY, OBJECT-TYPE,
               ---
               >        MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
               7c7
               <        AutonomousType, InstancePointer, TEXTUAL-CONVENTION
               ---
               >        AutonomousType, InstancePointer
               11c11
               <        mib-2, DisplayString
               ---
               >        transmission, mib-2

rfc1659     The MIB in the RFC compiles, but with an additional warning that
            the object is imported but never used. This MIB has been updated
            to match the contents of the RFC.

               4c4
               <        MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
               ---
               >        MODULE-IDENTITY, OBJECT-TYPE,

rfc1660     Below is a list of the differences between the MIB in the RFC and
            the installed MIB. The MIB in the RFC compiles, but with an
            additional warning that the object is imported but never
            used. This MIB has been updated to match the contents of the RFC.

               4c4
               <        MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
               ---
               >        MODULE-IDENTITY, OBJECT-TYPE,

rfc1696     Compile failed with 'rfc1696.mib:26: Circular definition for
            "mdmMIB".' Within the MIB is the following code:

               mdmMIB MODULE-IDENTITY
                    [...]
                   ::= { mdmMIB 1 }

               mdmMib OBJECT IDENTIFIER ::= { mib-2 38 }

            To get the code to compile this was changed to:
 
               mdmMIB MODULE-IDENTITY
                    [...]
                   ::= { mib-2 38 }

rfc1697     Below is a list of the differences between the MIB in the RFC and
            the installed MIB. The MIB in the RFC does not compile. The
            installed MIB has not been updated to match the code from the RFC.

               4,5c4,5
               <      MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
               <       Counter32, Gauge32, Integer32
               ---
               >      MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, OBJECT-IDENTITY, 
               >       Counter32, Gauge32
               8a9,10
               >       MODULE-COMPLIANCE, OBJECT-GROUP
               >           FROM SNMPv2-CONF
               12c14,16
               <           FROM RFC1213-MIB;
               ---
               >           FROM RFC1213-MIB
               >       hrSystem
               >           FROM HOST-RESOURCES-MIB;
               1276c1280
               <       MODULE RDBMS-MIB
               ---
               >       MODULE -- RDBMS-MIB


rfc1743     Got 'rfc1743.mib:822: Conflicting registrations "dot5TimerIfIndex"
            and "dot5StateGroup".' It turns out that, slightly higher up the
            tree, '{ dot5 5 }' was used twice. Assuming the second use is the
            wrong one and changing it to '{ dot5 6 }'. It is unknown if this
            is correct, but it does get the file to compile.

rfc1757     Below is a list of the differences between the MIB in the RFC and
            the installed MIB. The MIB in the RFC does not compile. The
            installed MIB has not been updated to match the code from the RFC.

               4,6c4,5
               <                   Counter                FROM RFC1155-SMI
               <                   DisplayString          FROM RFC1158-MIB
               <                   mib-2                  FROM RFC1213-MIB
               ---
               >                   Counter, TimeTicks     FROM RFC1155-SMI
               >                   DisplayString, mib-2   FROM RFC1213-MIB

rfc1759     Below is a list of the differences between the MIB in the RFC and
            the installed MIB. The MIB in the RFC does not compile. The
            installed MIB has not been updated to match the code from the
            RFC. This list does not include the change to the MAX-ACCESS,
            listed at the bottom of this file, which was required to get the
            file to compile.

               4c4
               <     MODULE-IDENTITY, OBJECT-TYPE, experimental, Counter32, Integer32,
               ---
               >     MODULE-IDENTITY, OBJECT-TYPE, Counter32, Integer32,
               8c8,9
               <     hrDeviceIndex, hrStorageIndex FROM HOST-RESOURCES-MIB;
               ---
               >     hrDeviceIndex, hrStorageIndex FROM HOST-RESOURCES-MIB
               >     mib-2 FROM RFC1213-MIB;

rfc1792     Got error 'rfc1792.mib:13: expected SIZE, got size'. Fixed.

            Got error 'rfc1792.mib:63: expected right-brace, got
            tcpIpxConnLocalPort'. Replaced missing comma in previous line.

            Got error 'rfc1792.mib:180: expected right-brace, got
            udpIpxLocalPort'. Replaced missing comma in previous line.

            Got error 'rfc1792.mib:218: the table object "tcpIpxConnTable"
            already has the SYNTAX "SEQUENCE OF TcpIpxConnEntry".' This was
            caused by an error while block copying the defintion. The syntax
            apparently should have been "SEQUENCE OF TcpUnspecConnEntry".

            Got error 'rfc1792.mib:249: expected a descriptor, got }'. Removed
            extraneous comma at the end of the last definition of the
            sequence.

            Got error 'rfc1792.mib:17: Unresolved forward valuereference
            "enterprises".' Added IMPORT.

rfc1850t    For some reason ospfIfStateChange was moved from one place to
            another in the MIB. It appears that this was done to try to remove
            some warnings, but the same warnings were given for the new last
            item defined. The definition was put back into the same place as
            in the RFC to remove future diff output.

rfc2006     In order to get the MIB to compile, the following changes had to
            be made:

               4c4
               <         Counter32, Gauge32, Integer32, IpAddress, experimental,
               ---
               >         Counter32, Gauge32, Integer32, IpAddress, Unsigned32,
               10,11c10,12
               <         MODULE-COMPLIANCE, OBJECT-GROUP
               <                                         FROM SNMPv2-CONF;
               ---
               >         MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
               >                                         FROM SNMPv2-CONF
               >         mib-2                           FROM RFC1213-MIB;

rfc2024     In a number of cases comments that are started with "--" have "--"
            later in the comment. This terminates the comment.

            These changes are listed with the others in the diff below. The
            MAX-ACCESS errors have been removed for readability and are noted
            in that section later.

               13c13,14
               <         sdlcLSAddress                     FROM SNA-SDLC-MIB;
               ---
               >         sdlcLSAddress                     FROM SNA-SDLC-MIB
               >         mib-2                             FROM RFC1213-MIB;
               152,157c153,158
               < -- (1) dlswNode      -- information about this DLSw
               < -- (2) dlswTConn     -- about adjacent DLSw partners
               < -- (3) dlswInterface -- about which interfaces DLSw is active on
               < -- (4) dlswDirectory -- about any directory of local/remote resources
               < -- (5) dlswCircuit   -- about established circuits.
               < -- (6) dlswSdlc      -- about SDLC data link switched devices
               ---
               > -- (1) dlswNode      - information about this DLSw
               > -- (2) dlswTConn     - about adjacent DLSw partners
               > -- (3) dlswInterface - about which interfaces DLSw is active on
               > -- (4) dlswDirectory - about any directory of local/remote resources
               > -- (5) dlswCircuit   - about established circuits.
               > -- (6) dlswSdlc      - about SDLC data link switched devices
               170c171
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               172c173,174
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               > 
               213c215
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               215c217
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               240c242
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               242c244
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               341c343
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               343c345
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               376c378
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               378c380
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               650c652
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               652c654
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               658c660
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               1258c1262
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               1260c1264
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               1265c1269
               < -- TCP Transport Connection Specific -- Configuration
               ---
               > -- TCP Transport Connection Specific - Configuration
               1332c1336
               < -- TCP Transport Connection Specific -- Operation
               ---
               > -- TCP Transport Connection Specific - Operation
               1478c1482
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               1480c1484
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               1562c1566
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               1564c1568
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               1924c1928
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               1926c1930
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               2063c2067
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               2065c2069
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               2087c2091
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               2098c2102
               < --         entries in the    |--------------------------------------
               ---
               > --         entries in the    |======================================
               2100c2104
               < --    -----------------------|--------------------------------------
               ---
               > --    =======================|======================================
               2114c2118
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               2828c2836
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               2840c2848
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               2915c2923
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               2917c2925
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               3262c3270
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************
               3264c3272
               < -- -------------------------------------------------------------------
               ---
               > -- *******************************************************************

rfc2096     Below is a list of the differences between the MIB in the RFC and
            the installed MIB. The MIB in the RFC _does_ compile, but does not
            contain these comments. They have been removed.

               1c1
               < IP-FORWARD-MIB DEFINITIONS ::= BEGIN
               ---
               > IP-FORWARD-MIB 
               2a3,8
               > -- from RFC 1354, now marked as obsolete
               > --EXCLUDE ipForwardNumber
               > --EXCLUDE ipForwardTable
               > 
               > DEFINITIONS ::= BEGIN
               > 

rfc2206     The upper limits of the following OCTET STRINGs was set to 65536
            (the maximum allowed is 65535):

                rsvpSenderPolicy (line 588)
                rsvpResvScope (line 1387)
                rsvpResvPolicy (line 1452)
                rsvpResvFwdScope (line 1846)
                rsvpResvFwdPolicy (line 1907)

rfc2213     The IMPORT of TestAndIncr from SNMPv2-TC is missing.

rfc2238     In HprRtpEntry SEQUENCE definition, one of the comments wrapped to
            the next line causing an error. The specific changes are shown
            below:

               516,517c516
               <      hprRtpSmRdTripDelay     Gauge32,            -- smooth rnd trip
               <                                                     delay
               ---
               >      hprRtpSmRdTripDelay     Gauge32,            -- smooth rnd trip delay

rfc2263     The SNMP-TARGET-MIB incorrectly tried to IMPORT TEXTUAL-CONVENTION
            from SNMPv2-SMI when it should have been IMPORTed from
            SNMPv2-TC. This has been fixed.

            The SNMP-TARGET-MIB also neglected to IMPORT Counter32.

            There was an extraneous comma in the IMPORTs for the
            SNMP-PROXY-MIB.

            Here are the actual changes:

               4d3
               <        TEXTUAL-CONVENTION,
               8c7,8
               <        Integer32
               ---
               >        Integer32,
               >        Counter32
               10a11
               >        TEXTUAL-CONVENTION,
               1194c1195
               <        SnmpTagValue,
               ---
               >        SnmpTagValue

rfc2325     TimeStamp and TimeInterval were incorrectly IMPORTed from
            SNMPv2-SMI when they should have been IMPORTed from
            SNMPv2-TC. Also DisplayString was not IMPORTed from RFC1213-MIB.

            Fixed a number of syntax errors. These fixes are shown below:

               5d4
               <        TimeStamp, TimeInterval,
               7a7,8
               >        TimeStamp, TimeInterval
               >            FROM SNMPv2-TC
               10c11
               <        transmission
               ---
               >        transmission, DisplayString
               56c57
               <            espresso(4),
               ---
               >            espresso(4)
               64c65
               <    potLocation OBJECT-TYPE {
               ---
               >    potLocation OBJECT-TYPE
               76,77c77,78
               <    potOperStatus
               <         SYNTAX     Integer {
               ---
               >    potOperStatus OBJECT-TYPE
               >         SYNTAX     INTEGER {
               102c103
               <         SYNTAX     Integer {
               ---
               >         SYNTAX     INTEGER {
               117c118
               <        SYNTAX     Integer64
               ---
               >        SYNTAX     Integer32

rfc2417     In order to get the MIB to compile "mib-2" had to be explicitly
            IMPORTed from SNMPv2-SMI as shown below:

               7c7,8
               <            Integer32, Unsigned32, OBJECT-TYPE, IpAddress
               ---
               >            Integer32, Unsigned32, OBJECT-TYPE, IpAddress,
               >            mib-2

rfc2558     Got 'rfc2558.mib:322: named number "Bellcore1991" must begin with
            a lower-case letter'. The first character was changed to lower
            case in order to get the file to compile.

rfc2662     Got 'rfc2662.mib:3483: Invalid MIN-ACCESS read-wr'. The MIN-ACCESS
            line was duplicated in the RFC. The second one was correctly
            formed. Deleted the incorrect line.

rfc2754     A page break got past the compiler by hiding in the CONTACT-INFO
            string. It has been removed.

rfc2925     Added to makefile. Needed to fix a number of occurrences of the
            following error: 'rfc2925.mib:nnnn: A named number list may be
            applied only to the INTEGER type itself, and not to a type derived
            from the INTEGER type.'. This occurred on lines: 1028, 1061,
            2282, 2337, 2349, and 2360.

<        SYNTAX  InetAddressType { unknown(0), ipv4(1), ipv6(2) }

            The line was commented out and a copy was added with the number
            list removed. It appears that the author wanted to limit the
            selections to not include the "dns(16)" InetAddressType.

rfc2982     Encountered error "rfc2982.mib:1041: The upper bound of an OCTET
            STRING size constraint may not exceed 65535." It was 65536. Fixed.

rfc3176     On lines 362 and 367 the original version of this file got the
            error "A named number list may be applied only to the INTEGER type
            itself, and not to a type derived from the INTEGER type." The
            incorrect line was commented out and replaced.

                <         SYNTAX     InetAddressType { ipv4(1) }
                ---
                >         SYNTAX     INTEGER { ipv4(1) }

rfc3202     On line 1465 the original version of this file had the error "A
            named number list may be applied only to the INTEGER type itself,
            and not to a type derived from the INTEGER type." The incorrect
            line was commented out and replaced.

                <         SYNTAX      RowStatus { active(1) }
                ---
                >         SYNTAX      INTEGER { active(1) }

rfc3289     33 lines in the original version of this file had the error "A
            named number list may be applied only to the INTEGER type itself,
            and not to a type derived from the INTEGER type." The incorrect
            lines were commented out and replaced. These fixes are shown
            below:

                2741,2744c2741,2742
                < --    SYNTAX RowStatus { active(1) }
                <     SYNTAX INTEGER { active(1) }
                < --    WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
                <     WRITE-SYNTAX INTEGER { createAndGo(4), destroy(6) }
                ---
                >     SYNTAX RowStatus { active(1) }
                >     WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
                2749,2752c2747,2748
                < --    SYNTAX RowStatus { active(1) }
                <     SYNTAX INTEGER { active(1) }
                < --    WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
                <     WRITE-SYNTAX INTEGER { createAndGo(4), destroy(6) }
                ---
                >     SYNTAX RowStatus { active(1) }
                >     WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
                2757,2760c2753,2754
                < --    SYNTAX RowStatus { active(1) }
                <     SYNTAX INTEGER { active(1) }
                < --    WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
                <     WRITE-SYNTAX INTEGER { createAndGo(4), destroy(6) }
                ---
                >     SYNTAX RowStatus { active(1) }
                >     WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
                2766,2767c2760
                < --    SYNTAX  InetAddressType { unknown(0), ipv4(1), ipv6(2) }
                <     SYNTAX  INTEGER { unknown(0), ipv4(1), ipv6(2) }
                ---
                >     SYNTAX  InetAddressType { unknown(0), ipv4(1), ipv6(2) }
                2779,2782c2772,2773
                < --    SYNTAX RowStatus { active(1) }
                <     SYNTAX INTEGER { active(1) }
                < --    WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
                <     WRITE-SYNTAX INTEGER { createAndGo(4), destroy(6) }
                ---
                >     SYNTAX RowStatus { active(1) }
                >     WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
                2787,2790c2778,2779
                < --    SYNTAX RowStatus { active(1) }
                <     SYNTAX INTEGER { active(1) }
                < --    WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
                <     WRITE-SYNTAX INTEGER { createAndGo(4), destroy(6) }
                ---
                >     SYNTAX RowStatus { active(1) }
                >     WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
                2795,2798c2784,2785
                < --    SYNTAX RowStatus { active(1) }
                <     SYNTAX INTEGER { active(1) }
                < --    WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
                <     WRITE-SYNTAX INTEGER { createAndGo(4), destroy(6) }
                ---
                >     SYNTAX RowStatus { active(1) }
                >     WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
                2803,2806c2790,2791
                < --    SYNTAX RowStatus { active(1) }
                <     SYNTAX INTEGER { active(1) }
                < --    WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
                <     WRITE-SYNTAX INTEGER { createAndGo(4), destroy(6) }
                ---
                >     SYNTAX RowStatus { active(1) }
                >     WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
                2811,2814c2796,2797
                < --    SYNTAX RowStatus { active(1) }
                <     SYNTAX INTEGER { active(1) }
                < --    WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
                <     WRITE-SYNTAX INTEGER { createAndGo(4), destroy(6) }
                ---
                >     SYNTAX RowStatus { active(1) }
                >     WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
                2819,2822c2802,2803
                < --    SYNTAX RowStatus { active(1) }
                <     SYNTAX INTEGER { active(1) }
                < --    WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
                <     WRITE-SYNTAX INTEGER { createAndGo(4), destroy(6) }
                ---
                >     SYNTAX RowStatus { active(1) }
                >     WRITE-SYNTAX RowStatus { createAndGo(4), destroy(6) }
                2887,2888c2868
                < --    SYNTAX       RowStatus { active(1) }
                <     SYNTAX       INTEGER { active(1) }
                ---
                >     SYNTAX       RowStatus { active(1) }
                2906,2907c2886
                < --    SYNTAX       RowStatus { active(1) }
                <     SYNTAX       INTEGER { active(1) }
                ---
                >     SYNTAX       RowStatus { active(1) }
                2940,2941c2919
                < --    SYNTAX       RowStatus { active(1) }
                <     SYNTAX       INTEGER { active(1) }
                ---
                >     SYNTAX       RowStatus { active(1) }
                2954,2955c2932
                < --    SYNTAX       InetAddressType { unknown(0), ipv4(1), ipv6(2) }
                <     SYNTAX       INTEGER { unknown(0), ipv4(1), ipv6(2) }
                ---
                >     SYNTAX       InetAddressType { unknown(0), ipv4(1), ipv6(2) }
                3056,3057c3033
                < --    SYNTAX       RowStatus { active(1) }
                <     SYNTAX       INTEGER { active(1) }
                ---
                >     SYNTAX       RowStatus { active(1) }
                3094,3095c3070
                < --    SYNTAX       RowStatus { active(1) }
                <     SYNTAX       INTEGER { active(1) }
                ---
                >     SYNTAX       RowStatus { active(1) }
                3127,3128c3102
                < --    SYNTAX       RowStatus { active(1) }
                <     SYNTAX       INTEGER { active(1) }
                ---
                >     SYNTAX       RowStatus { active(1) }
                3146,3147c3120
                < --    SYNTAX       RowStatus { active(1) }
                <     SYNTAX       INTEGER { active(1) }
                ---
                >     SYNTAX       RowStatus { active(1) }
                3190,3191c3163
                < --    SYNTAX       RowStatus { active(1) }
                <     SYNTAX       INTEGER { active(1) }
                ---
                >     SYNTAX       RowStatus { active(1) }
                3244,3245c3216
                < --    SYNTAX       RowStatus { active(1) }
                <     SYNTAX       INTEGER { active(1) }
                ---
                >     SYNTAX       RowStatus { active(1) }
                3278,3279c3249
                < --    SYNTAX       RowStatus { active(1) }
                <     SYNTAX       INTEGER { active(1) }
                ---
                >     SYNTAX       RowStatus { active(1) }
                3317,3318c3287
                < --    SYNTAX       RowStatus { active(1) }
                <     SYNTAX       INTEGER { active(1) }
                ---
                >     SYNTAX       RowStatus { active(1) }
                3351,3352c3320
                < --    SYNTAX       RowStatus { active(1) }
                <     SYNTAX       INTEGER { active(1) }
                ---
                >     SYNTAX       RowStatus { active(1) }
                3384,3385c3352
                < --    SYNTAX       RowStatus { active(1) }
                <     SYNTAX       INTEGER { active(1) }
                ---
                >     SYNTAX       RowStatus { active(1) }

rfc3295     On line 1418 the original version of this file got the error "A
            named number list may be applied only to the INTEGER type itself,
            and not to a type derived from the INTEGER type." The incorrect
            line was commented out and replaced.

                <        SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2),
                ---
                >        SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2),

not-accessible errors: Errors of this type have the form 'OBJECTS clause for
                       "fooGroup" references object "bar" with MAX-ACCESS
                       "not-accessible".' These errors were temporarily worked
                       around by changing the MAX-ACCESS to read-only.

    rfc1447     partyMIBGroup                   aclTarget
                partyMIBGroup                   aclSubject
    rfc1604     frPVCConnectStatusChange        frPVCConnectIndex
                frPVCConnectStatusChange        frPVCConnectLowIfIndex
                frPVCConnectStatusChange        frPVCConnectLowDLCIIndex
                frPVCConnectStatusChange        frPVCConnectHighIfIndex
                frPVCConnectStatusChange        frPVCConnectHighDLCIIndex
    rfc1611     dnsServCounterGroup             dnsServCounterOpCode
                dnsServCounterGroup             dnsServCounterQClass
                dnsServCounterGroup             dnsServCounterQType
                dnsServCounterGroup             dnsServCounterTransport
                dnsServZoneGroup                dnsServZoneName
                dnsServZoneGroup                dnsServZoneClass
                dnsServZoneGroup                dnsServZoneSrcName
                dnsServZoneGroup                dnsServZoneSrcClass
                dnsServZoneGroup                dnsServZoneSrcAddr
    rfc1612     dnsResConfigGroup               dnsResConfigSbeltAddr
                dnsResConfigGroup               dnsResConfigSbeltSubTree
                dnsResConfigGroup               dnsResConfigSbeltClass
                dnsResCounterGroup              dnsResCounterByOpcodeCode
                dnsResCounterGroup              dnsResCounterByRcodeCode
                dnsResLameDelegationGroup       dnsResLameDelegationSource
                dnsResLameDelegationGroup       dnsResLameDelegationName
                dnsResLameDelegationGroup       dnsResLameDelegationClass
                dnsResCacheGroup                dnsResCacheRRName
                dnsResCacheGroup                dnsResCacheRRClass
                dnsResCacheGroup                dnsResCacheRRType
                dnsResCacheGroup                dnsResCacheRRIndex
                dnsResNCacheGroup               dnsResNCacheErrQName
                dnsResNCacheGroup               dnsResNCacheErrQClass
                dnsResNCacheGroup               dnsResNCacheErrQType
    rfc1628     upsTrapAlarmEntryAdded          upsAlarmId
    rfc1650     etherCollisionTableGroup        dot3CollCount
    rfc1665     snaNodeGroup                    snaNodeAdminIndex
                snaNodeGroup                    snaNodeLinkAdminIndex
                snaLuGroup                      snaLuAdminLuIndex
                snaMgtToolsRtmGroup             snaLuRtmPuIndex
                snaMgtToolsRtmGroup             snaLuRtmLuIndex
    rfc1759     printerV2Alert                  prtAlertIndex
    rfc2024     dlswTrapTConnPartnerReject      dlswTConnOperTDomain
                dlswTrapTConnPartnerReject      dlswTConnOperRemoteTAddr
                dlswTrapCircuitUp               dlswCircuitS1Mac
                dlswTrapCircuitUp               dlswCircuitS1Sap
                dlswTrapCircuitUp               dlswCircuitS2Mac
                dlswTrapCircuitUp               dlswCircuitS2Sap
    rfc2954     frPVCConnectStatusChange        frPVCConnectIndex
                frPVCConnectStatusChange        frPVCConnectLowIfIndex
                frPVCConnectStatusChange        frPVCConnectLowDLCIIndex
                frPVCConnectStatusChange        frPVCConnectHighIfIndex
                frPVCConnectStatusChange        frPVCConnectHighDLCIIndex
