Entity MIB (entmib) Concluded WG
Note: The data for concluded WGs is occasionally incorrect.
|Area||Operations and Management Area (ops)|
|Dependencies||Document dependency graph (SVG)|
Charter for 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 WG will also standardize a set of managed objects representing
sensor entities. Sensor entities are physical entities that report
a value based on external conditions, such as temperature sensors,
power monitors, etc. The Sensor Entity MIB will augment the basic
Entity MIB to allow an NMS to obtain the value reported by a sensor.
This MIB will not contain internal support for alarms or
thresholds, but should work with standard alarm and threshold MIBs,
such as RMON-2.
|Jun 2004||Re-charter or shut-down the WG|
|Done||Submit Entity State MIB to the IESG for Proposed Standard|
|Done||Submit the Entity MIB to the IESG for Draft Standard|
|Done||Recommend to the IESG if the Entity MIB can be elevated to Draft Standard.|
|Done||Evaluate status of the Entity MIB and collect implementation and interoperability reports|
|Done||Publish state/status extensions as a WG I-D|
|Done||Re-cycle the updated Entity MIB at proposed standard, if necessary|
|Done||Submit final version of Internet-Draft for Sensor Entity MIB for consideration as a Proposed Standard|
|Done||Determine if the Entity MIB should be modified to resolve any open issues|
|Done||Post Internet-Draft for Sensor Entity MIB|
|Done||Recommend to the IESG if Entity MIB can be elevated to Draft Standard.|
|Done||Evaluate status of Entity MIB and collect implementation and interoperability reports|
|Done||Submit Internet Draft containing Entity MIB Extensions to IESG for consideration as a Proposed Standard.|
|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||Reach agreement on changes/extensions to RFC 2037|
|Done||Post updated/new Internet Drafts|
|Done||Finalize scope of changes/augmentations to RFC 2037|
|Done||Submit final version of Internet-Draft for consideration as a Proposed Standard.|
|Done||Post updated Entity MIB Internet-Draft.|
|Done||Post Internet-Draft for Entity MIB.|