IETF RFC 4363 PDF

The MIB modules defined in this document include a comprehensive set of managed objects that attempts to match the set defined in IEEE 802.1D and IEEE 802.1Q. However, to be consistent with the spirit of the SNMP Framework, a subjective judgement was made to omit the objects from those standards most 'costly' to implement in an agent and least 'essential' for fault and configuration management. The omissions are described in Section 3 below.

Historical note:

The original BRIDGE-MIB [RFC1493] used the following principles for determining inclusion of an object in the BRIDGE-MIB module:

(1) Start with a small set of essential objects and add only as further objects are needed.

(2) Require that objects be essential for either fault or configuration management.

(3) Consider evidence of current use and/or utility.

(4) Limit the total number of objects.

(5) Exclude objects that are simply derivable from others in this or other MIBs.

(6) Avoid causing critical sections to be heavily instrumented. The guideline that was followed is one counter per critical section per layer.