RFC 1214 (rfc1214) - Page 2 of 83
OSI internet management: Management Information Base
Alternative Format: Original Text Document
RFC 1214 MIB-II-OIM April 1991 A1.5 Parameter Template........................................ 67 A1.6 Name Binding Template.................................... 67 A1.7 Attribute Template........................................ 70 A1.8 Notification Template.................................... 73 Appendix 2: New Objects: Internet SMI Object Type Macros....... 76 Appendix 3: Supporting Definitions............................. 81 Security Considerations........................................ 82 Author's Address............................................... 83 1. Introduction This memo defines the management information base (MIB) for use with the OSI network management protocol in TCP/IP based internets. It formats the Management Information Base (MIB-II) in OSI templates and adds variables necessary for use with the OSI management protocol. Together with internet memos that define agreements for using the OSI management protocol to manage TCP/IP internets (RFC 1189) [3], the management information base: MIB-II, and OSI standards defining the structure of management information (ISO/IEC DIS 10165) [4,5,6], these documents provide an OSI compatible architecture and system for managing TCP/IP based internets and in particular the Internet community. This OSI version of the MIB specification is an incremental refinement of MIB-II. It has been designed according to the following policy: first, maintain compatibility with MIB-II by including objects in MIB-II without changes to their registered identifiers, syntax, and behaviour; second, format the MIB-II using the OSI structure of information defined templates; third, add attributes necessary for identification using the OSI management protocol; fourth, identify object instances in a manner which is compatible with development of a common application programming interface for both CMIP and SNMP; and finally, define notifications (events), including those defined by SNMP (RFC 1157) [14], deemed necessary for management. It is expected that the MIB will grow over time to accommodate the changing needs of the Internet. As reported in RFC 1109, Report of the Second Ad Hoc Network Management Review Group [13], the requirements for SNMP and OSI frameworks were more different than anticipated. Therefore, the requirement for compatibility between the SMI/MIB for both frameworks was suspended. This action allowed both frameworks to independently define the MIB according to their SMI requirements and views of management. The SNMP response included development of MIB-II. The OSI response is this document which builds on the excellent work done in MIB-II, and adds to it attributes necessary to map into the OSI OIM Working Group
