Current Meeting Report
Slides


2.3.5 Entity MIB (entmib)

NOTE: This charter is a snapshot of the 53rd IETF Meeting in Minneapolis, MN USA. It may now be out-of-date. Last Modified: 18-Feb-02
Chair(s):
Margaret Wasserman <mrw@windriver.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@ietf.org
To Subscribe: http://www.ietf.org/mailman/listinfo/entmib
Archive: www.ietf.org/mail-archive/working-groups/entmib/current/maillist.htm
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 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.

Goals and Milestones:
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
Jan 02   Determine if the Entity MIB should be modified to resolve any open issues
Feb 02   Re-cycle the updated Entity MIB at proposed standard, if necessary
Apr 02   Submit final version of Internet-Draft for Sensor Entity MIB for consideration as a Proposed Standard
Jul 02   Evaluate status of the Entity MIB and collect implementation and interoperability reports
Sep 02   Recommend to the IESG if the Entity MIB can be elevated to Draft Standard.
Oct 02   Evaluate status of the Sensor Entity MIB and collect implementation and interoperability reports
Dec 02   Recommend to the IESG if the Sensor Entity MIB can be elevated to Draft Standard
Jan 03   Re-charter or shut-down the WG
Internet-Drafts:
Request For Comments:
RFCStatusTitle
RFC2737PSEntity MIB (Version 2)

Current Meeting Report

Entity MIB Minutes -- IETF 53, Minneapolis -- March 19, 2002

AGENDA BASHING:

Agenda:
Agenda Bashing (5 min)

Proposed RFC 2737 Updates (20 min)
- PhysicalIndexOrZero TC (Juergen)
- PhysicalClass CPU enumeration (Andy)
- Other proposed changes?
- Decision Point: Do we update RFC 2737 and recycle at PS?

Entity Sensor MIB (20 min)
- Presentation of Draft Status (Andy)
- Decision Point: Are we ready for WG last call for PS?

Wrap-up and Action Items (10 min)

No agenda changes were made.

PROPOSED RFC2737 UPDATES

Proposed 2737 Updates:
Margaret proposed Juergen's PhysicalIndexOrZero TC.
Some discussion about whether a zero value should indicate no entPhysicalTable entry, or whether the meaning of zero should be usage-specific. Text has changed since last discussed -- should ask Juergen to clarify reasons.

Physical Class CPU Enumeration:
Andy has received several requests for this enumeration.

We discussed whether or not to re-cycle RFC2737 at PS for these changes, given that we still don't have sufficient implementation experience to advance to DS.

Consensus of room was to recycle RFC2737 for these changes.
Margaret will check consensus on the list.

ENTITY SENSOR MIB

Andy presented current MIB status. No changes since previous draft.

Some discussion regarding whether the timestamp field should be a relative timestamp or a real date and time. Consensus was that a relative timestamp is acceptable for this limited situation.

Consensus in room was to proceed to WG last call for PS.
Margaret to initiate last call on list.

ACTION ITEMS:

Margaret Meeting minutes and confirm results with list

Andy Communicate with Juergent about meaning of zero value in PhysicalIndexOrZero TC

Andy Update RFC2737 and send to list

Margaret Initiate WG last call for Entity Sensor MIB

Slides

Agenda