This Working Group did not meet
NOTE: This charter is a snapshot of the 59th IETF Meeting in Seoul, Korea. It may now be out-of-date.
Last Modified: 2004-01-29
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.
Done | Post Internet-Draft for Entity MIB. | |
Done | Post updated Entity MIB 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. | |
Done | Evaluate status of Entity MIB and collect implementation and interoperability reports | |
Done | Recommend to the IESG if Entity MIB can be elevated to Draft Standard. | |
Done | Post Internet-Draft for Sensor Entity MIB | |
Done | Determine if the Entity MIB should be modified to resolve any open issues | |
Done | Submit final version of Internet-Draft for Sensor Entity MIB for consideration as a Proposed Standard | |
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 | Post Internet-Draft for Sensor Entity MIB | |
Done | Determine if the Entity MIB should be modified to resolve any open issues | |
Done | Publish state/status extensions as a WG I-D | |
Done | Evaluate status of the Entity MIB and collect implementation and interoperability reports | |
Done | Evaluate status of the Entity MIB and collect implementation and interoperability reports | |
Done | Recommend to the IESG if the Entity MIB can be elevated to Draft Standard. | |
Feb 04 | Submit the Entity MIB to the IESG for Draft Standard | |
Mar 04 | Submit Entity State MIB to the IESG for Proposed Standard | |
Jun 04 | Re-charter or shut-down the WG |
RFC | Status | Title |
---|---|---|
RFC2037 | PS | Entity MIB |
RFC2737 | PS | Entity MIB (Version 2) |
RFC3433 | PS | Entity Sensor Management Information Base |