This Working Group Did Not Meet.
NOTE: This charter is a snapshot of the 47th IETF Meeting in Adelaide, Australia. It may now be out-of-date. Last Modified: 29-Feb-00
Chair(s):
Keith McCloghrie <kzm@cisco.com>
Operations and Management Area Director(s):
Randy Bush <randy@psg.com>
Bert Wijnen <bwijnen@lucent.com>
Operations and Management Area Advisor:
Bert Wijnen <bwijnen@lucent.com>
Mailing Lists:
General Discussion:entmib@cisco.com
To Subscribe: majordomo@cisco.com
In Body: subscribe entmib your_email_address
Archive: ftp://ftp.cisco.com/entmib/entmib
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 1253, 1493, 1516 or 1525, 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. |
Apr 98 |
|
Finalize scope of changes/augmentations to RFC 2037 |
Apr 98 |
|
Post updated/new Internet Drafts |
Aug 98 |
|
Reach agreement on changes/extensions to RFC 2037 |
Oct 98 |
|
Evaluate status of RFC 2037 and report to the IESG if it should be recycled at Proposed or can be elevated to Draft Standard. |
Oct 98 |
|
Submit Internet Draft containing Entity MIB Extensions to IESG for consideration as a Proposed Standard. |
No Current Internet-Drafts
Request For Comments:
RFC |
Status |
Title |
RFC2737 |
PS |
Entity MIB (Version 2) |