control protocol using SMIv2 RFC 2013: SNMPv2 management information base for the user datagram protocol using SMIv2. d. Application MIBs RFC 2789: Mail monitoring MIB RFC 1611: DNS server MIB extensions Remote monitoring MIBs: This category is mainly to group MIBs used for defining remote network monitoring (RMON). RFC 2819 is the main stan- dard in this category. Other RFCs associated with remote monitoring include: - RFC 2021: RMON version 2 - RFC 1513: Token ring extension to RFC - RFC 2613: RMON MIB extensions for switched networks version 1.0 Hardware specific MIBs: Data management for equipment like a printer, modem, and UPS is done using hardware specific MIBs. There are separate RFCs to define the objects that are associated and need to be managed in hardware. Some of the RFC documents that fall in this category are: - RFC 1696: Modem management information base using SMIv2 - RFC 1759: This document details printer MIB Fundamentals of EMS, NMS and OSS/BSS - RFC 1660: It has definitions of managed objects for parallel printer-like hardware devices using SMIv2 - RFC 1659: Definitions of managed objects for RS-232-like hardware devices using SMIv2 - RFC1628: UPS management information base Distributed management MIBs: Data about events, notifications, trace, and scheduling operations in a distributed environment are handled using the distributed management MIBs. Some of the RFC documents that fall in this category are: - RFC 2981: This is event MIB and handles four areas associated with event. They are trigger, object, event, and notification. Trigger is what causes the event on an object that could lead to a notification - RFC 2925: Definitions of managed objects for remote ping, trace route, and lookup operations RFC 2591: Definitions of managed objects for scheduling management operations Vendor specific MIBs: There would be scenarios when the standard and experimental MIBS provided by IETF does not provide access to all statisti- cal, state, configurations, and control information of the managed object 