Current Meeting Report

2.3.7 Entity MIB (entmib)

NOTE: This charter is a snapshot of the 52nd IETF Meeting in Salt Lake City, Utah USA. It may now be out-of-date. Last Modified: 29-Oct-01
Margaret Wasserman <>
Operations and Management Area Director(s):
Randy Bush <>
Bert Wijnen <>
Operations and Management Area Advisor:
Bert Wijnen <>
Mailing Lists:
To Subscribe:
Description of Working Group:
This working group is chartered to standardize a set of managed objects representing logical and physical entities and the relationships between them. Logical entities can occur when a single agent supports multiple instances of one MIB, such as RFCs 1493, 1525, or 1850 where each instance represents a single (logical) device/entity. Physical entities are the actual physical components on which the logical entities operate; typically, the physical components exist in a hierarchy. The set of objects will be consistent with the SNMP framework and existing SNMP standards.

The scope of the defined managed objects should allow an NMS to interrogate a standard SNMP context and thereby discover what logical and physical entities exist, how to access the MIB information of each logical entity, and the relationships between the various entities. The MIB should support both a single agent or multiple agents in one physical entity. The Working Group should adopt a minimalist approach for the (initial) MIB so as to maximize the chance of success, e.g., read-only.

Goals and Milestones:
Done   Hold BOF at Stockholm IETF.
Done   Post Internet-Draft for Entity MIB.
Done   Meet at Dallas IETF to review Internet-Draft and the issues raised during mailing list discussion.
Done   Post updated Entity MIB Internet-Draft.
Done   Meet at IETF to reach consensus on updated Internet-Draft.
Done   Submit final version of Internet-Draft for consideration as a Proposed Standard.
Done   Finalize scope of changes/augmentations to RFC 2037
Done   Post updated/new Internet Drafts
Done   Reach agreement on changes/extensions to RFC 2037
Done   Evaluate status of RFC 2037 and report to the IESG if it should be recycled at Proposed or can be elevated to Draft Standard.
Done   Submit Internet Draft containing Entity MIB Extensions to IESG for consideration as a Proposed Standard.
Apr 01   Evaluate status of RFC 2737 and collect implementation and interoperability reports
Sep 01   Recommend to the IESG if RFC 2737 can be elevated to Draft Standard.
Oct 01   Shut down working group
Request For Comments:
RFC2737PSEntity MIB (Version 2)

Current Meeting Report

None received.


None received.