Subject: [eman] New Version Notification for draft-ietf-eman-energy-aware-mib-03.txt

From: Benoit Claise <[email-masked]>
Date: Tue, 01 Nov 2011 00:38:36 +0100

Dear all,

Here is a new version of the draft-ietf-eman-energy-aware-mib-03.txt. 
See http://tools.ietf.org/html/draft-ietf-eman-energy-aware-mib-03

 From the previous meeting minutes:

    - Open Issue: Should we seek to have these UUIDs put into the ENTITY MIB?
         - Special variables for EMAN?  Only need to implement just those variables

    - Some discussion occurred among [BC], [JS], and [WH].
       [BC] Some more objects might be referred to the ENTITY-MIB, with a minimum compliance
       statement for the ENTITY-MIB, specficically for EMAN. For example, the pmName,
       which refers to the entPhysicalName if the ENTITY-MIB is supported.

    - [DR]: Question about whether we need to update the Entity MIB with the UUID.
       His point is that we need to plan for this.  What is the preference?  [BC]
       makes the point that to do it right it goes in the ENTITY MIB; to do it quick
       it goes in the EMAN pmIndex.

    - Open issue: How to model multiple relationships, even in the same topology?

All points have been addressed
- the new table AUGMENTS the entPhysicalIndex
- reused the entPhysicalUris to store the UUID, as suggested by Juergen 
Schoenwaelder. This solves a big issue, discussed during the last 
meeting: we thought we needed an ENTITY-MIB v4 with a proper UUID
- this MIB module requires a minimum compliance to the ENTITY-MIB: 
entPhysicalindex, entPhysicalName ,entPhysicalUris.
-  the ability to report multiple parents (we actually report their 
UUIDs based on same principle as entPhysicalUris). For example, if an 
Energy Object has got multiple power sources.
- the ability to report different parent UUID per Energy Object 
Relationships.
- latest terminology from 
http://tools.ietf.org/html/draft-parello-eman-definitions-03 adopted

Please check UML for a high level overview.

The advantages of this design:
- simplified the index
- no redundant OIDs
- get the containment topology from the ENTITY-MIB, if the ENTITY MIB is 
fully implemented (i.e. battery contained in PC)

If this design is confirmed, the [EMAN-MON-MIB] and [EMAN-BATTERY-MIB] 
might have to be modified
For example, [EMAN-MON-MIB] doesn't refer to the entPhysicalIndex

Regards, John and Benoit (as a contributor)

-------- Original Message --------
Subject: 	New Version Notification for 
draft-ietf-eman-energy-aware-mib-03.txt
Date: 	Mon, 31 Oct 2011 12:50:26 -0700
From: 	[email-masked]
To: 	[email-masked]
CC: 	[email-masked], [email-masked]

A new version of I-D, draft-ietf-eman-energy-aware-mib-03.txt has been successfully submitted by Benoit Claise and posted to the IETF repository.

Filename:	 draft-ietf-eman-energy-aware-mib
Revision:	 03
Title:		 Energy-aware Networks and Devices MIB
Creation date:	 2011-10-31
WG ID:		 eman
Number of pages: 32

Abstract:
         This document defines a subset of a Management Information Base
         (MIB) for energy management of devices.  The module addresses
         device identification, context information, and the
         relationships between reporting devices, remote devices, and
         monitoring devices.

The IETF Secretariat