
From chrisv@cyberswitching.com  Mon Nov  1 05:39:49 2010
Return-Path: <chrisv@cyberswitching.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F7F53A69AA for <eman@core3.amsl.com>; Mon,  1 Nov 2010 05:39:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o-U9RHg5cxRQ for <eman@core3.amsl.com>; Mon,  1 Nov 2010 05:39:32 -0700 (PDT)
Received: from p01c12o147.mxlogic.net (p01c12o147.mxlogic.net [208.65.145.70]) by core3.amsl.com (Postfix) with ESMTP id CED403A69B4 for <eman@ietf.org>; Mon,  1 Nov 2010 05:39:30 -0700 (PDT)
Received: from unknown [64.81.28.110] (EHLO mail03.cyberswitching.local) by p01c12o147.mxlogic.net(mxl_mta-6.7.0-2) with ESMTP id 305becc4.0.1377.00-380.3219.p01c12o147.mxlogic.net (envelope-from <chrisv@cyberswitching.com>);  Mon, 01 Nov 2010 06:39:32 -0600 (MDT)
X-MXL-Hash: 4cceb50407406d3d-857875821a63972f782bb04f706d793424363cfb
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB79C1.CDDAB197"
Date: Mon, 1 Nov 2010 05:39:23 -0700
Message-ID: <68FBE0F3CE97264395875AC1C468F22C514765@mail03.cyberswitching.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [eman] Entity identification method
Thread-Index: Act5cqHsDhmfAmy/STet1I+75V6LWwATbYMA
References: <C8EFF4A6.163CA%quittek@neclab.eu> <4CCE3065.6050705@nteczone.com>
From: "Chris Verges" <chrisv@cyberswitching.com>
To: "Christian Groves" <Christian.Groves@nteczone.com>, <eman@ietf.org>
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010073001)]
X-MAIL-FROM: <chrisv@cyberswitching.com>
X-SOURCE-IP: [64.81.28.110]
X-AnalysisOut: [v=1.0 c=1 a=aPxnrr7mnCkA:10 a=BLceEmwcHowA:10 a=4zsJQXJisS]
X-AnalysisOut: [Y22NXBO5KRuA==:17 a=48vgC7mUAAAA:8 a=r3s3_62XAAAA:8 a=wzgq]
X-AnalysisOut: [fsuUAAAA:8 a=AUd_NHdVAAAA:8 a=oBUWs83Srh6Q5gb-M04A:9 a=zsu]
X-AnalysisOut: [1_Ljcez07bt0VcscA:7 a=dt6pBVLn0XsYqdbX_t82qYV6OYsA:4 a=Cju]
X-AnalysisOut: [IK1q_8ugA:10 a=lZB815dzVvQA:10 a=3wXEbymkWtoA:10 a=yvfu_RG]
X-AnalysisOut: [Vus0A:10 a=JfD0Fch1gWkA:10 a=k39n37jPGg6u_oG2:21 a=QpmRQdU]
X-AnalysisOut: [X81T2P5lL:21 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=sbdoQi21f]
X-AnalysisOut: [xKO7Yv6x3IA:9 a=o2f4d_6fe6gvTU74nBwA:7 a=xkzHSaadGwKltBk9R]
X-AnalysisOut: [9mkq1Iv2TcA:4 a=gqkT6wR1tgRuwOjx:21 a=ejbnQF0o4mzN7jfV:21]
Subject: Re: [eman] Entity identification method
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the creation of an Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Nov 2010 12:39:49 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB79C1.CDDAB197
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Christian,

=20

Are you looking to allocate actual energy usage by a virtual entity,
like the amount of energy used by a virtual machine running on a shared
server?  Certainly an interesting problem ... gives a lot of room for
innovation for different vendors to find solutions.

=20

>From a MIB standpoint, it seems like the requirement is to have a
flexible power-related MIB that can either map to physical or logical
entities.  One question is, "where do you want those entities
enumerated?"

=20

Are virtual entities that need to be mapped to power usage normally
enumerated in ENTITY-MIB in the "logical" table?

=20

If so, perhaps something like this would fit the bill:

=20

POWER-ENTITY-MIB:

  pwrEntityTable

   pwrEntityEntry

      pwrEntityIndex

      pwrEntityName

      pwrEntityType

      pwrEntityParent

      pwrEntityPhysical

      pwrEntityLogical

=20

The pwrEntity[Physical|Logical] objects would point to the appropriate
index in ENTITY-MIB.

=20

However, if the virtual entities are not enumerated in ENTITY-MIB, the
pwrEntityLogical column is probably overkill.  The virtual entities can
be enumerated in pwrEntityTable and linked to the Physical meter using
the pwrEntityParent column, much like how ENTITY-MIB currently manages
references between parent and component entities.  It would just involve
a new pwrEntityType being added for "virtual" or something similar.

=20

So what's the typical use case as these virtual entities relate to
ENTITY-MIB?

=20

Chris

=20

=20

-----Original Message-----
From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of
Christian Groves
Sent: Sunday, October 31, 2010 8:14 PM
To: eman@ietf.org
Subject: Re: [eman] Entity identification method

=20

Hello Juergen,

=20

I think distinguishing the two cases is the correct way to go.

=20

I agree that reporting energy consumption for logical entities is a
challenge and not straight forward. I guess there are a number of ways
to look at this problem and how address the problem depends on the
ambition level.

=20

As you rightly mention where there is partial use of a physical resource
by a logical entity it is very difficult to have an exact figure. =20

However I think the "grain size" of the measurement comes into play. For
example if we have a large gateway implementing several virtual gateways
if we take an overall measurement then we have the problem determining a
figure. If the however the virtual gateways were each assigned a
physical rack and the measurements were taken at a rack level then we
have a more precise estimate of contribution of each virtual gateway to
the overall picture.

=20

For me logical entities ultimately will be realised by physical
hardware. The key is understanding the relationship between these
entities. Thus I think virtualization can in some way be supported by
allowing energy consumption reports for physical entities to indicate
if/what logical entities they relate to. As they say information is
power (pardon the pun :-) ).

=20

Regards, Christian

=20

On 29/10/2010 12:48 PM, Juergen Quittek wrote:

> Hi Christian,

>=20

> Thank you for this interesting comment.

>=20

> It looks like we have to distinguish two cases: power state monitoring


> and energy consumption monitoring.

>=20

> For a logical entity and a virtual machine it may be well possible to=20

> report on their power state. However, reporting their energy=20

> consumption seems to be a tough challenge at least if be base it on
real measurements.

>=20

> It is well feasible to measure energy consumption of physical=20

> entities, but if you have a logical entity that consumes only partial=20

> resources of a physical entity, then precise measurement of the energy


> consumption will be hardly possible. Estimations may be possible based


> on a model of the logical entity, but I don't know how good such
models can be.

>=20

> Thanks,

>=20

>      Juergen

>=20

>=20

> On 29.10.10 03:25  "Christian Groves"<Christian.Groves@nteczone.com
<mailto:Christian.Groves@nteczone.com> >  wrote:

>=20

>> Hello

>>=20

>> I've just started to digest the various drafts of the eman wg and I=20

>> see the comment below on logical entities. It's not clear to me=20

>> how/if network virtualization is intended on being handled in the
eman work.

>>=20

>> In networks there's now a trend towards network virtualization and=20

>> cloud computing with the different "X" as a service models (i.e.=20

>> Amazon EC2 "platform as a service" running different server=20

>> instances). Even in today's networks we have physical gateways that=20

>> are virtualized into different logical gateways. For example:=20

>> H.248/Megaco virtual MG (VMG) concept.

>>=20

>> I think it would be advantageous to be able to assess the energy=20

>> consumption of the VMGs or instances (which are logical entities)=20

>> independent of the physical gateway so that a customers energy use=20

>> may be recording. Will this sort of functionality be allowed?

>>=20

>> Regards, Christian

>>=20

>> On 29/10/2010 1:22 AM, Juergen Quittek wrote:

>>> Hi Chris,

>>>=20

>>> I think it may become very difficult if we want to assess energy=20

>>> consumption of logical entities. It seems to be reasonable and=20

>>> practical to limit energy consumption measurements to physical=20

>>> entities. The ENERGY AWARE MIB module

>>> (draft-parello-eman-energy-aware-mib) and the POWER MIB

>>> (draft-quittek-power-mib-02) went this way.

>>>=20

>>> Just using entPhysicalIndex solves some of the problem you
mentioned.

>>> Particularly, you don't need a mapping table to entities if you=20

>>> restrict Yourself to entPhysicalIndex.

>>>=20

>>> Thanks,

>>>=20

>>>       Juergen

>>>=20

>>> On 28.10.10 13:34  "Chris Verges"<chrisv@cyberswitching.com
<mailto:chrisv@cyberswitching.com> >   wrote:

>>>=20

>>>> Hi Jurgen and all,

>>>>=20

>>>> The more I've been thinking about these scenarios, the more=20

>>>> something doesn't seem quite right.  I'll try to explain my thought


>>>> process behind this and see if my concerns/confusions get captured.

>>>>=20

>>>> ENTITY-MIB provides enumerated lists of physical and logical=20

>>>> entities on the system.  The indices in both lists are maintained=20

>>>> separately, so there is not a single, unique identifier provided. =20

>>>> Because of this, the MIBs being discussed by the EMAN WG must only=20

>>>> reference to one type (physical or logical) and are limited to that
without additional work.

>>>> At some point in my mind, I'm asking myself the question, "What's=20

>>>> the point of linking to ENTITY-MIB?"

>>>>=20

>>>> More on that question in later scenarios below ...

>>>>=20

>>>> One possibility would be to create a separate mapping table that=20

>>>> gives a guaranteed unique index based on all entities, regardless=20

>>>> of type.  The physical vs. logical extensions would then become=20

>>>> sparse tables that augment this.  For example:

>>>>=20

>>>>     ENTITY-MIB : entityGeneral.entGeneralTable.entGeneralEntry

>>>>     +-----------------+-----------------+-----+

>>>>     | entGeneralIndex | entGeneralDescr | ... |

>>>>     +-----------------+-----------------+-----+

>>>>     |        1        | PDU Chassis     |     |

>>>>     +-----------------+-----------------+-----+

>>>>     |        2        | Meter #1        |     |

>>>>     +-----------------+-----------------+-----+

>>>>     |        3        | Meter #2        |     |

>>>>     +-----------------+-----------------+-----+

>>>>     |        4        | Remote Meter #1 |     |

>>>>     +-----------------+-----------------+-----+

>>>>=20

>>>>     ENTITY-MIB : entityPhysical.entPhysicalTable.entPhysicalEntry

>>>>     +-----------------+-----------------+-----+

>>>>     | entGeneralIndex | entVendorType   | ... |

>>>>     +-----------------+-----------------+-----+

>>>>     |        1        | enterprises.foo |     |

>>>>     +-----------------+-----------------+-----+

>>>>     |        2        | enterprises.foo |     |

>>>>     +-----------------+-----------------+-----+

>>>>     |        3        | enterprises.foo |     |

>>>>     +-----------------+-----------------+-----+

>>>>=20

>>>>     ENTITY-MIB : entityLogical.entLogicalTable.entLogicalEntry

>>>>     +-----------------+----------------------+-----+

>>>>     | entGeneralIndex | entLogicalCommunity  | ... |

>>>>     +-----------------+----------------------+-----+

>>>>     |        4        | remote-power-group-1 |     |

>>>>     +-----------------+----------------------+-----+

>>>>=20

>>>> It seems like this 'entGeneralIndex' concept is what's missing from


>>>> the current ENTITY-MIB, and is causing problems when thinking about


>>>> local and remote power data being reported by the same agent.

>>>>=20

>>>> Another possibility would be to choose one -- entLogicalIndex, most


>>>> likely -- and require that anyone who wants to implement the EMAN=20

>>>> WG MIBs to always create an entLogicalEntry for the power data.  In


>>>> this context, the entLogicalTable fills the role of entGeneralTable


>>>> as described above.  For all entPhysicalTable entries, there would=20

>>>> need to be a corresponding entry in entLogicalTable with a 1:1=20

>>>> mapping between them.  For all remote entries, there would be a=20

>>>> unique entry in entLogicalTable.  Of course, this would add some=20

>>>> additional overhead on the part of the implementer, but isn't too
overburdening.

>>>>=20

>>>> A third possibility is that ENTITY-MIB just doesn't do what we need


>>>> in its present form and we need to think about enumerating power=20

>>>> sensors separately from other components/sensors on the system.  It


>>>> seems like entPhysicalTable gives a good starting template for a=20

>>>> new 'POWER-ENTITY-MIB', but can be extended to include support for=20

>>>> remote agents.  The difference would be a clean break from the=20

>>>> legacy ENTITY-MIB structure.

>>>>=20

>>>> And with that, I look forward to others' feedback and ideas on=20

>>>> solving this problem!

>>>>=20

>>>> Thanks,

>>>> Chris

>>>>=20

>>>> -----Original Message-----

>>>> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On=20

>>>> Behalf Of Chris Verges

>>>> Sent: Tuesday, October 26, 2010 9:26 PM

>>>> To: Juergen Quittek; Benoit Claise; eman mailing list

>>>> Subject: Re: [eman] Entity identification method (was: EMAN=20

>>>> chartered itemsversus drafts)

>>>>=20

>>>> Hi Juergen and all,

>>>>=20

>>>> Agreed that a common ID method makes sense, and ENTITY-MIB seems to


>>>> be a good choice.  In case (c) from your list, wouldn't the remote=20

>>>> agent condition be handled by ENTITY-MIB supporting a logical=20

>>>> entity that is the remote agent iself?  Since the logical entity is


>>>> in the ENTITY-MIB table, it would be given a unique ID mixed=20

>>>> amongst the other logical and physical entities.

>>>>=20

>>>> At that point, should all of the MIBs being discussed in the EMAN=20

>>>> WG be sparse table augmentations of ENTITY-MIB?

>>>>=20

>>>> Thanks,

>>>> Chris

>>>>=20

>>>> -----Original Message-----

>>>> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On=20

>>>> Behalf Of Juergen Quittek

>>>> Sent: Tuesday, October 26, 2010 6:01 AM

>>>> To: Benoit Claise; eman mailing list

>>>> Subject: [eman] Entity identification method (was: EMAN chartered=20

>>>> items versus drafts)

>>>>=20

>>>> Hi Benoit and all,

>>>>=20

>>>> I agree that we should find a common identification method for=20

>>>> entities used by all MIB modules. This does not apply to the POWER=20

>>>> MIB only, but to all MIB modules in the eman WG.

>>>> The modules will use an entity ID as index for their tables.

>>>> Which entity is identified by the index can be resolved by other=20

>>>> MIB modules, such as the POWER AWARE MIB module

>>>> (draft-parello-eman-energy-aware-mib) or the ENTITY MIB module (RFC


>>>> 4133).

>>>>=20

>>>> I see three basic scenarios for the entity identification:

>>>>=20

>>>>     a) a device just reports on its own power state and energy

>>>>        consumption and it reports on its own as a single unit.

>>>>=20

>>>>        Then we have a single index only stating "it's me".

>>>>        Such a device usually does not need further identification

>>>>        of itself, because typically there are sufficient other

>>>>        MIB modules for this purpose running in the same SNMP
engine,

>>>>        that provide information about the device's IP address,

>>>>        manufacturer, operating system, etc. In such a case a

>>>>        'trivial' index, such as '0' should be used in order to

>>>>        keep it simple in this most simple case.

>>>>=20

>>>>     b) a device reports on its own but not just as a single unit

>>>>        but it reports power states and energy consumption for its

>>>>        individual components, for example it may report separately

>>>>        on contained hard drives, line cards, back planes,

>>>>        processor boards, etc.

>>>>=20

>>>>        In such a case, identification of these components as

>>>>        individual entities would be required. The ENTITY MIB

>>>>        module was designed for this purpose and would be a good

>>>>        choice here. Also the POWER AWARE MIB module would be

>>>>        useful in this case.

>>>>=20

>>>>     c) a device reports on energy consumption of other, remote

>>>>        devices. Then remote devices (and potentially also their

>>>>        contained components need to be identified. For

>>>>        identifying remote components there is the POWER AWARE MIB

>>>>        module that has been designed for this purpose. As far as

>>>>        I understand, the ENTITY MIB module is not applicable to

>>>>        remote devices.

>>>>=20

>>>> In summary,

>>>>     - if you need to report on remote entities (case c)),

>>>>       you need the POWER AWARE MIB module,

>>>>     - if you report only on entities locally contained

>>>>       in the reporting device (case b)), you can use

>>>>       the POWER AWARE MIB or the ENTITY MIB

>>>>     - if you report just on your own as a single device

>>>>       (case a)), identification is trivial

>>>>=20

>>>> Hence, my recommendation (stated for POWER-STATE MIB and ENERGY MIB


>>>> in

>>>> draft-quittek-power-mib-02) would be:

>>>>=20

>>>> If there is an implementation of the POWER AWARE MIB module=20

>>>> instantiated in the local SNMP engine, then you SHOULD (or MUST?)=20

>>>> use it for indexing (pmIndex).

>>>> If this is not the case but there is an ENTITY MIB instance=20

>>>> available, then you SHOULD use this one (entPhysicalIndex).

>>>> If neither of this MIB modules is available you should use index 0=20

>>>> only and be limited to report on the local device as a single
entity only.

>>>>=20

>>>> That's just my view. Certainly, there are more ways of entity=20

>>>> identification. I look forward to discussing them.

>>>>=20

>>>> Thanks,

>>>>=20

>>>>       Juergen

>>>>=20

>>>>=20

>>>> On 26.10.10 11:44  "Benoit Claise"<bclaise@cisco.com
<mailto:bclaise@cisco.com> >   wrote:

>>>>=20

>>>>> Hi Juergen,

>>>>>=20

>>>>> Thanks for the clarification.

>>>>>=20

>>>>> Something key is to agree on the Power Monitor index for all MIB=20

>>>>> modules, which IMHO should be part of the Energy-aware Networks=20

>>>>> and Devices MIB module, but reuse in the other MIB modules.

>>>>>=20

>>>>> Regards, Benoit.

>>>>>> Hi Benoit,

>>>>>>=20

>>>>>> Thanks for checking all drafts.

>>>>>>=20

>>>>>> I don't think that draft-quittek-power-mib-02 makes significant=20

>>>>>> contributions to the Energy-aware Networks and Devices MIB.

>>>>>> It just covers the Power and Energy Monitoring MIB and the=20

>>>>>> Battery

>>>> MIB.

>>>>>> Thanks,

>>>>>>        Juergen

>>>>>>=20

>>>>>>=20

>>>>>> On 26.10.10 08:22  "Benoit Claise"<bclaise@cisco.com
<mailto:bclaise@cisco.com> >    wrote:

>>>>>>=20

>>>>>>> Dear all,

>>>>>>>=20

>>>>>>> I went through the exercise of mapping the existing six=20

>>>>>>> chartered items with the existing draft content.

>>>>>>>=20

>>>>>>> _Energy Management Requirements_=20

>>>>>>> http://tools.ietf.org/html/draft-quittek-power-monitoring-requir
<http://tools.ietf.org/html/draft-quittek-power-monitoring-requir>=20

>>>>>>> emen

>>>>>>> ts-02=20

>>>>>>> https://datatracker.ietf.org/doc/draft-norwin-energy-consider/
<https://datatracker.ietf.org/doc/draft-norwin-energy-consider/>=20

>>>>>>> _

>>>>>>> Energy Management Framework_

>>>>>>> http://tools.ietf.org/html/draft-claise-power-management-arch-02
<http://tools.ietf.org/html/draft-claise-power-management-arch-02>=20

>>>>>>>=20

>>>>>>> _Energy-aware Networks and Devices MIB_

>>>>>>> http://tools.ietf.org/html/draft-parello-eman-energy-aware-mib-0
<http://tools.ietf.org/html/draft-parello-eman-energy-aware-mib-0>=20

>>>>>>> 0

>>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
<http://tools.ietf.org/html/draft-quittek-power-mib-02>=20

>>>>>>>=20

>>>>>>> _Power and Energy Monitoring MIB_

>>>>>>> http://tools.ietf.org/html/draft-claise-energy-monitoring-mib-06
<http://tools.ietf.org/html/draft-claise-energy-monitoring-mib-06>=20

>>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
<http://tools.ietf.org/html/draft-quittek-power-mib-02>=20

>>>>>>>=20

>>>>>>> _Battery MIB_

>>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
<http://tools.ietf.org/html/draft-quittek-power-mib-02>=20

>>>>>>>=20

>>>>>>> _Energy Management Applicability_=20

>>>>>>> http://datatracker.ietf.org/doc/draft-tychon-eman-applicability-
<http://datatracker.ietf.org/doc/draft-tychon-eman-applicability->=20

>>>>>>> stat

>>>>>>> ement/

>>>>>>>=20

>>>>>>> Please let me know if I made any mistakes or if I missed any
draft?

>>>>>>>=20

>>>>>>> Regards, Benoit.

>>>>>>> _______________________________________________

>>>>>>> eman mailing list

>>>>>>> eman@ietf.org <mailto:eman@ietf.org>=20

>>>>>>> https://www.ietf.org/mailman/listinfo/eman
<https://www.ietf.org/mailman/listinfo/eman>=20

>>>> _______________________________________________

>>>> eman mailing list

>>>> eman@ietf.org <mailto:eman@ietf.org>=20

>>>> https://www.ietf.org/mailman/listinfo/eman
<https://www.ietf.org/mailman/listinfo/eman>=20

>>>=20

>>> _______________________________________________

>>> eman mailing list

>>> eman@ietf.org <mailto:eman@ietf.org>=20

>>> https://www.ietf.org/mailman/listinfo/eman
<https://www.ietf.org/mailman/listinfo/eman>=20

>> _______________________________________________

>> eman mailing list

>> eman@ietf.org <mailto:eman@ietf.org>=20

>> https://www.ietf.org/mailman/listinfo/eman
<https://www.ietf.org/mailman/listinfo/eman>=20

>=20

>=20

> _______________________________________________

> eman mailing list

> eman@ietf.org <mailto:eman@ietf.org>=20

> https://www.ietf.org/mailman/listinfo/eman
<https://www.ietf.org/mailman/listinfo/eman>=20

_______________________________________________

eman mailing list

eman@ietf.org <mailto:eman@ietf.org>=20

https://www.ietf.org/mailman/listinfo/eman
<https://www.ietf.org/mailman/listinfo/eman>=20


------_=_NextPart_001_01CB79C1.CDDAB197
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1638025773;
	mso-list-type:hybrid;
	mso-list-template-ids:-1152120844 67698689 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoPlainText>Hi =
Christian,<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Are you looking to allocate actual energy usage by =
a virtual entity, like the amount of energy used by a virtual machine =
running on a shared server?&nbsp; Certainly an interesting problem ... =
gives a lot of room for innovation for different vendors to find =
solutions.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>From a MIB standpoint, it seems like the =
requirement is to have a flexible power-related MIB that can either map =
to physical or logical entities.&nbsp; One question is, &#8220;where do =
you want those entities enumerated?&#8221;<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Are =
virtual entities that need to be mapped to power usage normally =
enumerated in ENTITY-MIB in the &#8220;logical&#8221; =
table?<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>If so, perhaps something like this would fit the =
bill:<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>POWER-ENTITY-MIB:<o:p></o:p></p><p =
class=3DMsoPlainText>&nbsp; pwrEntityTable<o:p></o:p></p><p =
class=3DMsoPlainText> &nbsp;&nbsp;&nbsp;pwrEntityEntry<o:p></o:p></p><p =
class=3DMsoPlainText>&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;pwrEntityIndex<o:p></o:p></p><p =
class=3DMsoPlainText>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
pwrEntityName<o:p></o:p></p><p =
class=3DMsoPlainText>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
pwrEntityType<o:p></o:p></p><p =
class=3DMsoPlainText>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
pwrEntityParent<o:p></o:p></p><p =
class=3DMsoPlainText>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
pwrEntityPhysical<o:p></o:p></p><p =
class=3DMsoPlainText>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
pwrEntityLogical<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>The =
pwrEntity[Physical|Logical] objects would point to the appropriate index =
in ENTITY-MIB.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>However, if the virtual entities are not enumerated =
in ENTITY-MIB, the pwrEntityLogical column is probably overkill.&nbsp; =
The virtual entities can be enumerated in pwrEntityTable and linked to =
the Physical meter using the pwrEntityParent column, much like how =
ENTITY-MIB currently manages references between parent and component =
entities.&nbsp; It would just involve a new pwrEntityType being added =
for &#8220;virtual&#8221; or something similar.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>So =
what&#8217;s the typical use case as these virtual entities relate to =
ENTITY-MIB?<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Chris<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>-----Original Message-----<br>From: =
eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of =
Christian Groves<br>Sent: Sunday, October 31, 2010 8:14 PM<br>To: =
eman@ietf.org<br>Subject: Re: [eman] Entity identification method</p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Hello =
Juergen,<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>I think distinguishing the two cases is the correct =
way to go.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>I agree that reporting energy consumption for =
logical entities is a challenge and not straight forward. I guess there =
are a number of ways to look at this problem and how address the problem =
depends on the ambition level.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>As you =
rightly mention where there is partial use of a physical resource by a =
logical entity it is very difficult to have an exact figure.&nbsp; =
<o:p></o:p></p><p class=3DMsoPlainText>However I think the &quot;grain =
size&quot; of the measurement comes into play. For example if we have a =
large gateway implementing several virtual gateways if we take an =
overall measurement then we have the problem determining a figure. If =
the however the virtual gateways were each assigned a physical rack and =
the measurements were taken at a rack level then we have a more precise =
estimate of contribution of each virtual gateway to the overall =
picture.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>For me logical entities ultimately will be realised =
by physical hardware. The key is understanding the relationship between =
these entities. Thus I think virtualization can in some way be supported =
by allowing energy consumption reports for physical entities to indicate =
if/what logical entities they relate to. As they say information is =
power (pardon the pun :-) ).<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Regards, Christian<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>On =
29/10/2010 12:48 PM, Juergen Quittek wrote:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; Hi Christian,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; Thank you for this interesting =
comment.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; It looks like we have to distinguish two =
cases: power state monitoring <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; and energy consumption =
monitoring.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; For a logical entity and a virtual machine it =
may be well possible to <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
report on their power state. However, reporting their energy =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; consumption seems to be a =
tough challenge at least if be base it on real =
measurements.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; It is well feasible to measure energy =
consumption of physical <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
entities, but if you have a logical entity that consumes only partial =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; resources of a physical =
entity, then precise measurement of the energy <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; consumption will be hardly possible. =
Estimations may be possible based <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; on a model of the logical entity, but I don't =
know how good such models can be.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; Thanks,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Juergen<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; On 29.10.10 03:25&nbsp; &quot;Christian =
Groves&quot;&lt;<a href=3D"mailto:Christian.Groves@nteczone.com"><span =
style=3D'color:windowtext;text-decoration:none'>Christian.Groves@nteczone=
.com</span></a>&gt;&nbsp; wrote:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; Hello<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; I've just started to digest the various =
drafts of the eman wg and I <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; see the comment below on logical entities. =
It's not clear to me <o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
how/if network virtualization is intended on being handled in the eman =
work.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; In networks there's now a trend towards =
network virtualization and <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; cloud computing with the different =
&quot;X&quot; as a service models (i.e. <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; Amazon EC2 &quot;platform as a =
service&quot; running different server <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; instances). Even in today's networks we =
have physical gateways that <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; are virtualized into different logical =
gateways. For example: <o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
H.248/Megaco virtual MG (VMG) concept.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; I think it would be advantageous to be =
able to assess the energy <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; consumption of the VMGs or instances =
(which are logical entities) <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; independent of the physical gateway so =
that a customers energy use <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; may be recording. Will this sort of =
functionality be allowed?<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; Regards, Christian<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; On 29/10/2010 1:22 AM, Juergen Quittek =
wrote:<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt; Hi =
Chris,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; I think it may become very difficult =
if we want to assess energy <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; consumption of logical entities. It =
seems to be reasonable and <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; practical to limit energy consumption =
measurements to physical <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; entities. The ENERGY AWARE MIB =
module<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt; =
(draft-parello-eman-energy-aware-mib) and the POWER MIB<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; (draft-quittek-power-mib-02) went this =
way.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; Just using entPhysicalIndex solves =
some of the problem you mentioned.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; Particularly, you don't need a mapping =
table to entities if you <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; restrict Yourself to =
entPhysicalIndex.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; Thanks,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Juergen<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; On 28.10.10 13:34&nbsp; &quot;Chris =
Verges&quot;&lt;<a href=3D"mailto:chrisv@cyberswitching.com"><span =
style=3D'color:windowtext;text-decoration:none'>chrisv@cyberswitching.com=
</span></a>&gt;&nbsp;&nbsp; wrote:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; Hi Jurgen and =
all,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; The more I've been thinking about =
these scenarios, the more <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; something doesn't seem quite =
right.&nbsp; I'll try to explain my thought <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; process behind this and see if my =
concerns/confusions get captured.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; ENTITY-MIB provides enumerated =
lists of physical and logical <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; entities on the system.&nbsp; The =
indices in both lists are maintained <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; separately, so there is not a =
single, unique identifier provided.&nbsp; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; Because of this, the MIBs being =
discussed by the EMAN WG must only <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; reference to one type (physical or =
logical) and are limited to that without additional =
work.<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt; At some =
point in my mind, I'm asking myself the question, &quot;What's =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt; the point of =
linking to ENTITY-MIB?&quot;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; More on that question in later =
scenarios below ...<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; One possibility would be to create =
a separate mapping table that <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; gives a guaranteed unique index =
based on all entities, regardless <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; of type.&nbsp; The physical vs. =
logical extensions would then become <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; sparse tables that augment =
this.&nbsp; For example:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; ENTITY-MIB =
: entityGeneral.entGeneralTable.entGeneralEntry<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
+-----------------+-----------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; | =
entGeneralIndex | entGeneralDescr | ... |<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
+-----------------+-----------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | PDU =
Chassis&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; =
|<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
+-----------------+-----------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Meter =
#1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; =
|<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
+-----------------+-----------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Meter =
#2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp; =
|<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
+-----------------+-----------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Remote Meter #1 =
|&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
+-----------------+-----------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; ENTITY-MIB =
: entityPhysical.entPhysicalTable.entPhysicalEntry<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
+-----------------+-----------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; | =
entGeneralIndex | entVendorType&nbsp;&nbsp; | ... |<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
+-----------------+-----------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | enterprises.foo =
|&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
+-----------------+-----------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | enterprises.foo =
|&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
+-----------------+-----------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | enterprises.foo =
|&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
+-----------------+-----------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; ENTITY-MIB =
: entityLogical.entLogicalTable.entLogicalEntry<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
+-----------------+----------------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; | =
entGeneralIndex | entLogicalCommunity&nbsp; | ... |<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
+-----------------+----------------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | remote-power-group-1 =
|&nbsp;&nbsp;&nbsp;&nbsp; |<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; =
+-----------------+----------------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; It seems like this =
'entGeneralIndex' concept is what's missing from <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; the current ENTITY-MIB, and is =
causing problems when thinking about <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; local and remote power data being =
reported by the same agent.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; Another possibility would be to =
choose one -- entLogicalIndex, most <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; likely -- and require that anyone =
who wants to implement the EMAN <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; WG MIBs to always create an =
entLogicalEntry for the power data.&nbsp; In <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; this context, the entLogicalTable =
fills the role of entGeneralTable <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; as described above.&nbsp; For all =
entPhysicalTable entries, there would <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; need to be a corresponding entry =
in entLogicalTable with a 1:1 <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; mapping between them.&nbsp; For =
all remote entries, there would be a <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; unique entry in =
entLogicalTable.&nbsp; Of course, this would add some <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; additional overhead on the part of =
the implementer, but isn't too overburdening.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; A third possibility is that =
ENTITY-MIB just doesn't do what we need <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; in its present form and we need to =
think about enumerating power <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; sensors separately from other =
components/sensors on the system.&nbsp; It <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; seems like entPhysicalTable gives =
a good starting template for a <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; new 'POWER-ENTITY-MIB', but can be =
extended to include support for <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; remote agents.&nbsp; The =
difference would be a clean break from the <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; legacy ENTITY-MIB =
structure.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; And with that, I look forward to =
others' feedback and ideas on <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; solving this =
problem!<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; Thanks,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; Chris<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; -----Original =
Message-----<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt; =
From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt; Behalf Of Chris =
Verges<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt; Sent: =
Tuesday, October 26, 2010 9:26 PM<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; To: Juergen Quittek; Benoit =
Claise; eman mailing list<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; Subject: Re: [eman] Entity =
identification method (was: EMAN <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; chartered itemsversus =
drafts)<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; Hi Juergen and =
all,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; Agreed that a common ID method =
makes sense, and ENTITY-MIB seems to <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; be a good choice.&nbsp; In case =
(c) from your list, wouldn't the remote <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; agent condition be handled by =
ENTITY-MIB supporting a logical <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; entity that is the remote agent =
iself?&nbsp; Since the logical entity is <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; in the ENTITY-MIB table, it would =
be given a unique ID mixed <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; amongst the other logical and =
physical entities.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; At that point, should all of the =
MIBs being discussed in the EMAN <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; WG be sparse table augmentations =
of ENTITY-MIB?<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; Thanks,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; Chris<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; -----Original =
Message-----<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt; =
From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt; Behalf Of =
Juergen Quittek<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt; =
Sent: Tuesday, October 26, 2010 6:01 AM<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; To: Benoit Claise; eman mailing =
list<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt; Subject: =
[eman] Entity identification method (was: EMAN chartered =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt; items versus =
drafts)<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; Hi Benoit and =
all,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; I agree that we should find a =
common identification method for <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; entities used by all MIB modules. =
This does not apply to the POWER <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; MIB only, but to all MIB modules =
in the eman WG.<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt; =
The modules will use an entity ID as index for their =
tables.<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt; Which =
entity is identified by the index can be resolved by other =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt; MIB modules, =
such as the POWER AWARE MIB module<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; =
(draft-parello-eman-energy-aware-mib) or the ENTITY MIB module (RFC =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt; =
4133).<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; I see three basic scenarios for =
the entity identification:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; a) a =
device just reports on its own power state and energy<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; consumption and it reports on its own as a single =
unit.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; Then we have a single index only stating &quot;it's =
me&quot;.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; Such a device usually does not need further =
identification<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; of itself, because typically there are sufficient =
other<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; MIB modules for this purpose running in the same SNMP =
engine,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; that provide information about the device's IP =
address,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; manufacturer, operating system, etc. In such a case =
a<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; 'trivial' index, such as '0' should be used in order =
to<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; keep it simple in this most simple case.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; b) a =
device reports on its own but not just as a single unit<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; but it reports power states and energy consumption for =
its<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; individual components, for example it may report =
separately<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; on contained hard drives, line cards, back =
planes,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; processor boards, etc.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; In such a case, identification of these components =
as<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; individual entities would be required. The ENTITY =
MIB<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; module was designed for this purpose and would be a =
good<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; choice here. Also the POWER AWARE MIB module would =
be<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; useful in this case.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; c) a =
device reports on energy consumption of other, remote<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; devices. Then remote devices (and potentially also =
their<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; contained components need to be identified. For<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;identifying remote components there is the POWER AWARE =
MIB<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; module that has been designed for this purpose. As far =
as<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; I understand, the ENTITY MIB module is not applicable =
to<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; remote devices.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; In summary,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp; &nbsp;&nbsp;&nbsp;- if you =
need to report on remote entities (case c)),<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 you need the POWER AWARE MIB module,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; - if you =
report only on entities locally contained<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 in the reporting device (case b)), you can use<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 the POWER AWARE MIB or the ENTITY MIB<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp; - if you =
report just on your own as a single device<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 (case a)), identification is trivial<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; Hence, my recommendation (stated =
for POWER-STATE MIB and ENERGY MIB <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; in<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; draft-quittek-power-mib-02) would =
be:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; If there is an implementation of =
the POWER AWARE MIB module <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; instantiated in the local SNMP =
engine, then you SHOULD (or MUST?) <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; use it for indexing =
(pmIndex).<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt; If =
this is not the case but there is an ENTITY MIB instance =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt; available, then =
you SHOULD use this one (entPhysicalIndex).<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; If neither of this MIB modules is =
available you should use index 0 <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; only and be limited to report on =
the local device as a single entity only.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; That's just my view. Certainly, =
there are more ways of entity <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; identification. I look forward to =
discussing them.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; Thanks,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
 Juergen<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; On 26.10.10 11:44&nbsp; =
&quot;Benoit Claise&quot;&lt;<a href=3D"mailto:bclaise@cisco.com"><span =
style=3D'color:windowtext;text-decoration:none'>bclaise@cisco.com</span><=
/a>&gt;&nbsp;&nbsp; wrote:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; Hi Juergen,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; Thanks for the =
clarification.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; Something key is to agree on =
the Power Monitor index for all MIB <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; modules, which IMHO should be =
part of the Energy-aware Networks <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; and Devices MIB module, but =
reuse in the other MIB modules.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; Regards, =
Benoit.<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; =
Hi Benoit,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; Thanks for checking all =
drafts.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; I don't think that =
draft-quittek-power-mib-02 makes significant <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; contributions to the =
Energy-aware Networks and Devices MIB.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; It just covers the Power =
and Energy Monitoring MIB and the <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; Battery<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; MIB.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; Thanks,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp; Juergen<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; On 26.10.10 08:22&nbsp; =
&quot;Benoit Claise&quot;&lt;<a href=3D"mailto:bclaise@cisco.com"><span =
style=3D'color:windowtext;text-decoration:none'>bclaise@cisco.com</span><=
/a>&gt;&nbsp;&nbsp;&nbsp; wrote:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; Dear =
all,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; I went through the =
exercise of mapping the existing six <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; chartered items with =
the existing draft content.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; _Energy Management =
Requirements_ <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"http://tools.ietf.org/html/draft-quittek-power-monitoring-requir"=
><span =
style=3D'color:windowtext;text-decoration:none'>http://tools.ietf.org/htm=
l/draft-quittek-power-monitoring-requir</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; emen<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; ts-02 =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"https://datatracker.ietf.org/doc/draft-norwin-energy-consider/"><=
span =
style=3D'color:windowtext;text-decoration:none'>https://datatracker.ietf.=
org/doc/draft-norwin-energy-consider/</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; _<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; Energy Management =
Framework_<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"http://tools.ietf.org/html/draft-claise-power-management-arch-02"=
><span =
style=3D'color:windowtext;text-decoration:none'>http://tools.ietf.org/htm=
l/draft-claise-power-management-arch-02</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; _Energy-aware Networks =
and Devices MIB_<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"http://tools.ietf.org/html/draft-parello-eman-energy-aware-mib-0"=
><span =
style=3D'color:windowtext;text-decoration:none'>http://tools.ietf.org/htm=
l/draft-parello-eman-energy-aware-mib-0</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; 0<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"http://tools.ietf.org/html/draft-quittek-power-mib-02"><span =
style=3D'color:windowtext;text-decoration:none'>http://tools.ietf.org/htm=
l/draft-quittek-power-mib-02</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; _Power and Energy =
Monitoring MIB_<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"http://tools.ietf.org/html/draft-claise-energy-monitoring-mib-06"=
><span =
style=3D'color:windowtext;text-decoration:none'>http://tools.ietf.org/htm=
l/draft-claise-energy-monitoring-mib-06</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"http://tools.ietf.org/html/draft-quittek-power-mib-02"><span =
style=3D'color:windowtext;text-decoration:none'>http://tools.ietf.org/htm=
l/draft-quittek-power-mib-02</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; _Battery =
MIB_<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
<a href=3D"http://tools.ietf.org/html/draft-quittek-power-mib-02"><span =
style=3D'color:windowtext;text-decoration:none'>http://tools.ietf.org/htm=
l/draft-quittek-power-mib-02</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; _Energy Management =
Applicability_ <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"http://datatracker.ietf.org/doc/draft-tychon-eman-applicability-"=
><span =
style=3D'color:windowtext;text-decoration:none'>http://datatracker.ietf.o=
rg/doc/draft-tychon-eman-applicability-</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; stat<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
ement/<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; Please let me know if =
I made any mistakes or if I missed any draft?<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; Regards, =
Benoit.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
_______________________________________________<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; eman mailing =
list<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
<a href=3D"mailto:eman@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>eman@ietf.org</span></a><=
o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/eman"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/eman</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; =
_______________________________________________<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; eman mailing list<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; <a =
href=3D"mailto:eman@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>eman@ietf.org</span></a><=
o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/eman"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/eman</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; =
_______________________________________________<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; eman mailing list<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; <a href=3D"mailto:eman@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>eman@ietf.org</span></a><=
o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/eman"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/eman</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; =
_______________________________________________<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; eman mailing list<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <a href=3D"mailto:eman@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>eman@ietf.org</span></a><=
o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/eman"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/eman</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; =
_______________________________________________<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; eman mailing list<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; <a href=3D"mailto:eman@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>eman@ietf.org</span></a><=
o:p></o:p></p><p class=3DMsoPlainText>&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/eman"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/eman</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>_______________________________________________<o:p>=
</o:p></p><p class=3DMsoPlainText>eman mailing list<o:p></o:p></p><p =
class=3DMsoPlainText><a href=3D"mailto:eman@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>eman@ietf.org</span></a><=
o:p></o:p></p><p class=3DMsoPlainText><a =
href=3D"https://www.ietf.org/mailman/listinfo/eman"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/eman</span></a><o:p></o:p></p></div></body></html>
------_=_NextPart_001_01CB79C1.CDDAB197--

From moulchan@cisco.com  Mon Nov  1 23:38:52 2010
Return-Path: <moulchan@cisco.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 417633A67E2 for <eman@core3.amsl.com>; Mon,  1 Nov 2010 23:38:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pyeYECbUT8LE for <eman@core3.amsl.com>; Mon,  1 Nov 2010 23:38:50 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id A03933A680B for <eman@ietf.org>; Mon,  1 Nov 2010 23:38:00 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAONOz0ytJV2c/2dsb2JhbAChZXGiapwOgwQIgjkEhFeJCw
X-IronPort-AV: E=Sophos;i="4.58,279,1286150400"; d="scan'208";a="177605154"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rtp-iport-2.cisco.com with ESMTP; 02 Nov 2010 06:38:03 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core-5.cisco.com (8.14.3/8.14.3) with ESMTP id oA26c34a022373;  Tue, 2 Nov 2010 06:38:03 GMT
Received: from xmb-rcd-106.cisco.com ([72.163.62.148]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 2 Nov 2010 01:38:03 -0500
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 2 Nov 2010 01:37:59 -0500
Message-ID: <E9B25823FA871E4AA9EDA7B163E5D8A903443ECA@XMB-RCD-106.cisco.com>
In-Reply-To: <4CCE3065.6050705@nteczone.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [eman] Entity identification method
Thread-Index: Act5crT1GyAB1idORdWd/G16DWNmvAA4ypog
References: <C8EFF4A6.163CA%quittek@neclab.eu> <4CCE3065.6050705@nteczone.com>
From: "Mouli Chandramouli (moulchan)" <moulchan@cisco.com>
To: "Christian Groves" <Christian.Groves@nteczone.com>, <eman@ietf.org>
X-OriginalArrivalTime: 02 Nov 2010 06:38:03.0050 (UTC) FILETIME=[7FD3F8A0:01CB7A58]
Subject: Re: [eman] Entity identification method
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the creation of an Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Nov 2010 06:38:52 -0000

Hi Christian,=20

Presently, the power measurement technology and instrumentation (power
sensors) exist for physical entities.=20
While the MIBs in circulation attempt to provide power consumption by
physical components, cost of measurement sensors should be taken into
account.=20

Clearly, the power cost of software features or virtual machines
(logical entities) should be determined, the technology/methodology is
work in progress as given in the research paper.=20

Power measurement of virtual machines is still at research stage.

http://www.sigmetrics.org/sigmetrics2010/greenmetrics/greenMetrics10.Kri
shnan.pdf


On another point, it has been widely reported in several bench marking
studies that most of the power consumption is due to physical entities.
Clearly, this notion should be extended to logical entities as you have
pointed out.=20

Thanks
Mouli


-----Original Message-----
From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of
Christian Groves
Sent: Monday, November 01, 2010 8:44 AM
To: eman@ietf.org
Subject: Re: [eman] Entity identification method

Hello Juergen,

I think distinguishing the two cases is the correct way to go.

I agree that reporting energy consumption for logical entities is a=20
challenge and not straight forward. I guess there are a number of ways=20
to look at this problem and how address the problem depends on the=20
ambition level.

As you rightly mention where there is partial use of a physical resource

by a logical entity it is very difficult to have an exact figure. =20
However I think the "grain size" of the measurement comes into play. For

example if we have a large gateway implementing several virtual gateways

if we take an overall measurement then we have the problem determining a

figure. If the however the virtual gateways were each assigned a=20
physical rack and the measurements were taken at a rack level then we=20
have a more precise estimate of contribution of each virtual gateway to=20
the overall picture.

For me logical entities ultimately will be realised by physical=20
hardware. The key is understanding the relationship between these=20
entities. Thus I think virtualization can in some way be supported by=20
allowing energy consumption reports for physical entities to indicate=20
if/what logical entities they relate to. As they say information is=20
power (pardon the pun :-) ).

Regards, Christian

On 29/10/2010 12:48 PM, Juergen Quittek wrote:
> Hi Christian,
>
> Thank you for this interesting comment.
>
> It looks like we have to distinguish two cases: power state monitoring
and
> energy consumption monitoring.
>
> For a logical entity and a virtual machine it may be well possible to
report
> on their power state. However, reporting their energy consumption
seems to
> be a tough challenge at least if be base it on real measurements.
>
> It is well feasible to measure energy consumption of physical
entities, but
> if you have a logical entity that consumes only partial resources of a
> physical entity, then precise measurement of the energy consumption
will be
> hardly possible. Estimations may be possible based on a model of the
logical
> entity, but I don't know how good such models can be.
>
> Thanks,
>
>      Juergen
>
>
> On 29.10.10 03:25  "Christian Groves"<Christian.Groves@nteczone.com>
wrote:
>
>> Hello
>>
>> I've just started to digest the various drafts of the eman wg and I
see
>> the comment below on logical entities. It's not clear to me how/if
>> network virtualization is intended on being handled in the eman work.
>>
>> In networks there's now a trend towards network virtualization and
cloud
>> computing with the different "X" as a service models (i.e. Amazon EC2
>> "platform as a service" running different server instances). Even in
>> today's networks we have physical gateways that are virtualized into
>> different logical gateways. For example: H.248/Megaco virtual MG
(VMG)
>> concept.
>>
>> I think it would be advantageous to be able to assess the energy
>> consumption of the VMGs or instances (which are logical entities)
>> independent of the physical gateway so that a customers energy use
may
>> be recording. Will this sort of functionality be allowed?
>>
>> Regards, Christian
>>
>> On 29/10/2010 1:22 AM, Juergen Quittek wrote:
>>> Hi Chris,
>>>
>>> I think it may become very difficult if we want to assess energy
consumption
>>> of logical entities. It seems to be reasonable and practical to
limit energy
>>> consumption measurements to physical entities. The ENERGY AWARE MIB
module
>>> (draft-parello-eman-energy-aware-mib) and the POWER MIB
>>> (draft-quittek-power-mib-02) went this way.
>>>
>>> Just using entPhysicalIndex solves some of the problem you
mentioned.
>>> Particularly, you don't need a mapping table to entities if you
restrict
>>> Yourself to entPhysicalIndex.
>>>
>>> Thanks,
>>>
>>>       Juergen
>>>
>>> On 28.10.10 13:34  "Chris Verges"<chrisv@cyberswitching.com>
wrote:
>>>
>>>> Hi Jurgen and all,
>>>>
>>>> The more I've been thinking about these scenarios, the more
something
>>>> doesn't seem quite right.  I'll try to explain my thought process
behind
>>>> this and see if my concerns/confusions get captured.
>>>>
>>>> ENTITY-MIB provides enumerated lists of physical and logical
entities on
>>>> the system.  The indices in both lists are maintained separately,
so
>>>> there is not a single, unique identifier provided.  Because of
this, the
>>>> MIBs being discussed by the EMAN WG must only reference to one type
>>>> (physical or logical) and are limited to that without additional
work.
>>>> At some point in my mind, I'm asking myself the question, "What's
the
>>>> point of linking to ENTITY-MIB?"
>>>>
>>>> More on that question in later scenarios below ...
>>>>
>>>> One possibility would be to create a separate mapping table that
gives a
>>>> guaranteed unique index based on all entities, regardless of type.
The
>>>> physical vs. logical extensions would then become sparse tables
that
>>>> augment this.  For example:
>>>>
>>>>     ENTITY-MIB : entityGeneral.entGeneralTable.entGeneralEntry
>>>>     +-----------------+-----------------+-----+
>>>>     | entGeneralIndex | entGeneralDescr | ... |
>>>>     +-----------------+-----------------+-----+
>>>>     |        1        | PDU Chassis     |     |
>>>>     +-----------------+-----------------+-----+
>>>>     |        2        | Meter #1        |     |
>>>>     +-----------------+-----------------+-----+
>>>>     |        3        | Meter #2        |     |
>>>>     +-----------------+-----------------+-----+
>>>>     |        4        | Remote Meter #1 |     |
>>>>     +-----------------+-----------------+-----+
>>>>
>>>>     ENTITY-MIB : entityPhysical.entPhysicalTable.entPhysicalEntry
>>>>     +-----------------+-----------------+-----+
>>>>     | entGeneralIndex | entVendorType   | ... |
>>>>     +-----------------+-----------------+-----+
>>>>     |        1        | enterprises.foo |     |
>>>>     +-----------------+-----------------+-----+
>>>>     |        2        | enterprises.foo |     |
>>>>     +-----------------+-----------------+-----+
>>>>     |        3        | enterprises.foo |     |
>>>>     +-----------------+-----------------+-----+
>>>>
>>>>     ENTITY-MIB : entityLogical.entLogicalTable.entLogicalEntry
>>>>     +-----------------+----------------------+-----+
>>>>     | entGeneralIndex | entLogicalCommunity  | ... |
>>>>     +-----------------+----------------------+-----+
>>>>     |        4        | remote-power-group-1 |     |
>>>>     +-----------------+----------------------+-----+
>>>>
>>>> It seems like this 'entGeneralIndex' concept is what's missing from
the
>>>> current ENTITY-MIB, and is causing problems when thinking about
local
>>>> and remote power data being reported by the same agent.
>>>>
>>>> Another possibility would be to choose one -- entLogicalIndex, most
>>>> likely -- and require that anyone who wants to implement the EMAN
WG
>>>> MIBs to always create an entLogicalEntry for the power data.  In
this
>>>> context, the entLogicalTable fills the role of entGeneralTable as
>>>> described above.  For all entPhysicalTable entries, there would
need to
>>>> be a corresponding entry in entLogicalTable with a 1:1 mapping
between
>>>> them.  For all remote entries, there would be a unique entry in
>>>> entLogicalTable.  Of course, this would add some additional
overhead on
>>>> the part of the implementer, but isn't too overburdening.
>>>>
>>>> A third possibility is that ENTITY-MIB just doesn't do what we need
in
>>>> its present form and we need to think about enumerating power
sensors
>>>> separately from other components/sensors on the system.  It seems
like
>>>> entPhysicalTable gives a good starting template for a new
>>>> 'POWER-ENTITY-MIB', but can be extended to include support for
remote
>>>> agents.  The difference would be a clean break from the legacy
>>>> ENTITY-MIB structure.
>>>>
>>>> And with that, I look forward to others' feedback and ideas on
solving
>>>> this problem!
>>>>
>>>> Thanks,
>>>> Chris
>>>>
>>>> -----Original Message-----
>>>> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On
Behalf Of
>>>> Chris Verges
>>>> Sent: Tuesday, October 26, 2010 9:26 PM
>>>> To: Juergen Quittek; Benoit Claise; eman mailing list
>>>> Subject: Re: [eman] Entity identification method (was: EMAN
chartered
>>>> itemsversus drafts)
>>>>
>>>> Hi Juergen and all,
>>>>
>>>> Agreed that a common ID method makes sense, and ENTITY-MIB seems to
be a
>>>> good choice.  In case (c) from your list, wouldn't the remote agent
>>>> condition be handled by ENTITY-MIB supporting a logical entity that
is
>>>> the remote agent iself?  Since the logical entity is in the
ENTITY-MIB
>>>> table, it would be given a unique ID mixed amongst the other
logical and
>>>> physical entities.
>>>>
>>>> At that point, should all of the MIBs being discussed in the EMAN
WG be
>>>> sparse table augmentations of ENTITY-MIB?
>>>>
>>>> Thanks,
>>>> Chris
>>>>
>>>> -----Original Message-----
>>>> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On
Behalf Of
>>>> Juergen Quittek
>>>> Sent: Tuesday, October 26, 2010 6:01 AM
>>>> To: Benoit Claise; eman mailing list
>>>> Subject: [eman] Entity identification method (was: EMAN chartered
items
>>>> versus drafts)
>>>>
>>>> Hi Benoit and all,
>>>>
>>>> I agree that we should find a common identification method for
entities
>>>> used by all MIB modules. This does not apply to the POWER MIB only,
but
>>>> to all MIB modules in the eman WG.
>>>> The modules will use an entity ID as index for their tables.
>>>> Which entity is identified by the index can be resolved by other
MIB
>>>> modules, such as the POWER AWARE MIB module
>>>> (draft-parello-eman-energy-aware-mib) or the ENTITY MIB module (RFC
>>>> 4133).
>>>>
>>>> I see three basic scenarios for the entity identification:
>>>>
>>>>     a) a device just reports on its own power state and energy
>>>>        consumption and it reports on its own as a single unit.
>>>>
>>>>        Then we have a single index only stating "it's me".
>>>>        Such a device usually does not need further identification
>>>>        of itself, because typically there are sufficient other
>>>>        MIB modules for this purpose running in the same SNMP
engine,
>>>>        that provide information about the device's IP address,
>>>>        manufacturer, operating system, etc. In such a case a
>>>>        'trivial' index, such as '0' should be used in order to
>>>>        keep it simple in this most simple case.
>>>>
>>>>     b) a device reports on its own but not just as a single unit
>>>>        but it reports power states and energy consumption for its
>>>>        individual components, for example it may report separately
>>>>        on contained hard drives, line cards, back planes,
>>>>        processor boards, etc.
>>>>
>>>>        In such a case, identification of these components as
>>>>        individual entities would be required. The ENTITY MIB
>>>>        module was designed for this purpose and would be a good
>>>>        choice here. Also the POWER AWARE MIB module would be
>>>>        useful in this case.
>>>>
>>>>     c) a device reports on energy consumption of other, remote
>>>>        devices. Then remote devices (and potentially also their
>>>>        contained components need to be identified. For
>>>>        identifying remote components there is the POWER AWARE MIB
>>>>        module that has been designed for this purpose. As far as
>>>>        I understand, the ENTITY MIB module is not applicable to
>>>>        remote devices.
>>>>
>>>> In summary,
>>>>     - if you need to report on remote entities (case c)),
>>>>       you need the POWER AWARE MIB module,
>>>>     - if you report only on entities locally contained
>>>>       in the reporting device (case b)), you can use
>>>>       the POWER AWARE MIB or the ENTITY MIB
>>>>     - if you report just on your own as a single device
>>>>       (case a)), identification is trivial
>>>>
>>>> Hence, my recommendation (stated for POWER-STATE MIB and ENERGY MIB
in
>>>> draft-quittek-power-mib-02) would be:
>>>>
>>>> If there is an implementation of the POWER AWARE MIB module
instantiated
>>>> in the local SNMP engine, then you SHOULD (or MUST?) use it for
indexing
>>>> (pmIndex).
>>>> If this is not the case but there is an ENTITY MIB instance
available,
>>>> then you SHOULD use this one (entPhysicalIndex).
>>>> If neither of this MIB modules is available you should use index 0
only
>>>> and be limited to report on the local device as a single entity
only.
>>>>
>>>> That's just my view. Certainly, there are more ways of entity
>>>> identification. I look forward to discussing them.
>>>>
>>>> Thanks,
>>>>
>>>>       Juergen
>>>>
>>>>
>>>> On 26.10.10 11:44  "Benoit Claise"<bclaise@cisco.com>   wrote:
>>>>
>>>>> Hi Juergen,
>>>>>
>>>>> Thanks for the clarification.
>>>>>
>>>>> Something key is to agree on the Power Monitor index for all MIB
>>>>> modules, which IMHO should be part of the Energy-aware Networks
and
>>>>> Devices MIB module, but reuse in the other MIB modules.
>>>>>
>>>>> Regards, Benoit.
>>>>>> Hi Benoit,
>>>>>>
>>>>>> Thanks for checking all drafts.
>>>>>>
>>>>>> I don't think that draft-quittek-power-mib-02 makes significant
>>>>>> contributions to the Energy-aware Networks and Devices MIB.
>>>>>> It just covers the Power and Energy Monitoring MIB and the
Battery
>>>> MIB.
>>>>>> Thanks,
>>>>>>        Juergen
>>>>>>
>>>>>>
>>>>>> On 26.10.10 08:22  "Benoit Claise"<bclaise@cisco.com>    wrote:
>>>>>>
>>>>>>> Dear all,
>>>>>>>
>>>>>>> I went through the exercise of mapping the existing six
chartered
>>>>>>> items with the existing draft content.
>>>>>>>
>>>>>>> _Energy Management Requirements_
>>>>>>>
http://tools.ietf.org/html/draft-quittek-power-monitoring-requiremen
>>>>>>> ts-02
https://datatracker.ietf.org/doc/draft-norwin-energy-consider/
>>>>>>> _
>>>>>>> Energy Management Framework_
>>>>>>> http://tools.ietf.org/html/draft-claise-power-management-arch-02
>>>>>>>
>>>>>>> _Energy-aware Networks and Devices MIB_
>>>>>>>
http://tools.ietf.org/html/draft-parello-eman-energy-aware-mib-00
>>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>>>>>>>
>>>>>>> _Power and Energy Monitoring MIB_
>>>>>>> http://tools.ietf.org/html/draft-claise-energy-monitoring-mib-06
>>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>>>>>>>
>>>>>>> _Battery MIB_
>>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>>>>>>>
>>>>>>> _Energy Management Applicability_
>>>>>>>
http://datatracker.ietf.org/doc/draft-tychon-eman-applicability-stat
>>>>>>> ement/
>>>>>>>
>>>>>>> Please let me know if I made any mistakes or if I missed any
draft?
>>>>>>>
>>>>>>> Regards, Benoit.
>>>>>>> _______________________________________________
>>>>>>> eman mailing list
>>>>>>> eman@ietf.org
>>>>>>> https://www.ietf.org/mailman/listinfo/eman
>>>> _______________________________________________
>>>> eman mailing list
>>>> eman@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/eman
>>>
>>> _______________________________________________
>>> eman mailing list
>>> eman@ietf.org
>>> https://www.ietf.org/mailman/listinfo/eman
>> _______________________________________________
>> eman mailing list
>> eman@ietf.org
>> https://www.ietf.org/mailman/listinfo/eman
>
>
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman
_______________________________________________
eman mailing list
eman@ietf.org
https://www.ietf.org/mailman/listinfo/eman

From bnordman@lbl.gov  Mon Nov  1 23:49:07 2010
Return-Path: <bnordman@lbl.gov>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1230A3A681D for <eman@core3.amsl.com>; Mon,  1 Nov 2010 23:49:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.488
X-Spam-Level: 
X-Spam-Status: No, score=-4.488 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UKZjJDUGUIOf for <eman@core3.amsl.com>; Mon,  1 Nov 2010 23:49:05 -0700 (PDT)
Received: from ironport2.lbl.gov (ironport2.lbl.gov [128.3.41.14]) by core3.amsl.com (Postfix) with ESMTP id 7E0863A6811 for <eman@ietf.org>; Mon,  1 Nov 2010 23:49:05 -0700 (PDT)
X-Ironport-SBRS: 4.4
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvUAADtRz0zRVdQ0kGdsb2JhbACTaAGNdAgVAQEBAQkJDAcRAx+jdZp+gnIZgjoEhFeFfQ
X-IronPort-AV: E=Sophos;i="4.58,279,1286175600"; d="scan'208";a="115445924"
Received: from mail-vw0-f52.google.com ([209.85.212.52]) by ironport2.lbl.gov with ESMTP; 01 Nov 2010 23:49:08 -0700
Received: by vws15 with SMTP id 15so4529521vws.39 for <eman@ietf.org>; Mon, 01 Nov 2010 23:49:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.241.194 with SMTP id lf2mr13270483qcb.164.1288680547400; Mon, 01 Nov 2010 23:49:07 -0700 (PDT)
Received: by 10.229.105.8 with HTTP; Mon, 1 Nov 2010 23:49:07 -0700 (PDT)
Date: Mon, 1 Nov 2010 23:49:07 -0700
Message-ID: <AANLkTinHam40dHw5xDDeQrUhERHtW3XbaQmu4BPSRV+C@mail.gmail.com>
From: Bruce Nordman <bnordman@lbl.gov>
To: eman@ietf.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: [eman] Introduction; past comments
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the creation of an Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Nov 2010 06:49:07 -0000

Greetings--

  As incoming co-chair of eman, I look forward to meeting many of you
next week in Beijing.  I bring an energy-centric background to the process,
which I believe will be a useful complement to more usual IETF participants=
.
I have been on the edge of several IETF meetings, but this will be my first
actual attendance.  You can learn more about my interests from my web page
(below).
  For our working group, I have no interest in expanding our charter.
I am however
interested in follow-on activities that may make sense within the IETF
as well as in
other standards organizations, for how we network the physical world
(I call this
"building networks" for devices that use energy or that influence it).
 I look forward
to discussions on this outside our WG meeting.
  In the interest of transparency and completeness, below are some comments=
 on
several of the Internet Drafts as they were a few weeks ago, before
recent revisions.
These are offered as an individual participant, not in my role as
co-chair.  I am not
seeking to start email discussions with these comments.
  Pleasant travels,

--Bruce

--=20
Bruce Nordman
Lawrence Berkeley National Laboratory
eetd.lbl.gov/ea/nordman
BNordman@LBL.gov
510-486-7089
m: 510-501-7943




claise-power-management-arch-01
   =93power level=94 to me is a measurement in watts of the device.  I
prefer =93power mode=94 or =93power state=94 (I treat them as synonyms and
don=92t much care which is used) for states like on, sleep, off.
  1. Introduction =96 any device on an IP network should be in scope,
and while today that is almost entirely IT devices, in future it may
be dominated by non-IT ones.
  Power Monitor =96 I see this as something which tracks power coming
into a device, or going out of it (the meter case could be either, the
only difference being whether the meter consumption is included or
not).  (actually, section 5.1 of c-p-m-mib states this).  Every device
can measure its power input.  Power output can be measured on any
interface that provides power.  We need to be clear about which side
of a link the measurement is on, as the line losses will be included
if on the supply side, but not if on the demand side.  Could of course
have a power monitor on both.  The examples should be organized along
these lines (the distinction is already mentioned).  The text says
that a PM can be =93independently managed=94.  How does one manage a
device or component if it does not have an IP address?
  Power quality =96 I wasn=92t sure if it was quality of the power or of
the measurement being referenced here.
  =93each monitor must be a member of a domain=94. =96 why?  I think each
device must be able to operate independently, and if it discovers it
has a parent, then be able to report up to it, but not have that be a
requirement.  It seems like some of the discussion references a
reporting hierarchy along the lines of the LAN structure, e.g. up to a
switch, but if the power is not distributed along the same lines, this
seems like a problem.
  4.3 =96 clarify if the connection referenced is for communications,
power, or both.
  Keywords =96 I think that consideration of these in the context of use
cases may lead us to pulling aside a few key attributes, such as
location and identity; the =93role description=94 concept is doing this
already.
  4.5 =96 Again, I think the number of basic states is far more than
needed, and that differentiation within a state should be accomplished
by other means (often strictly internal to the device, with the
preference =96 e.g. expressed by price =96 being manifested in lower power
levels that are reported).
  4.6 =96 Is =93instantaneous=94 finer than one AC cycle?  I don=92t think =
it
needs to be (perhaps can=92t or shouldn=92t), and could be more than one.
Also, nameplate power is so far from reality I don=92t think worth
bringing up.  I do think worth considering a value for maximum
possible demand for the device in question (if this is what was meant
than I would not use nameplate as it has other meaning).
  4.8 =96 demand charges.  I suspect these will eventually disappear as
we move to dynamic prices, so I would not let them change the
architecture.   Besides, a NMS can always query a device every 15
minutes to get its contribution to peak for the building.  Also, I
would leave off the two bullets at the end as out of scope, or at
least move the topic to the introduction.
  5. Presumably a power supplying device may sometimes not be able to
contact those it is serving power to, either because they lack
communications, or the comms are not on the same link and so may not
be present even though power is being used.
  Manufacturers power levels.  I am not convinced we need this
concept.  Again, I think the use cases will help.
  IEC 61850 =96 is this important?  Does someone have a PDF they can send m=
e?

quittek-power-mib-01
   For accuracy, I suspect eventually that direct measurement will
become cheap, but agree that in the meantime many devices won=92t have
this.  However, I suspect most of those can reliably estimate their
energy use from other factors, so I think that making good use of
estimates is important to facilitate (while exposing the accuracy
reduction for those devices that care).
  I didn=92t print out quittek-power-monitoring-requirements so these
comments don=92t reflect that document.
  Power states =96 the term =93low power mode=94 is useful (and a way to
avoid using the word =93standby=94).
  3.1 entity state mib =96 worth considering if what they are getting at
here is the functional state, rather than the power state.  While they
are related, I think usefully distinguished, and perhaps key to
explaining the relationship between what we define and what this mib
already defines (even if what it defines in this case goes away).
  Also in 3.1, as noted above, I don=92t think we need more detail in
power states, or rather, additional complexity should be driven by use
cases, as I think the needs they have will point us to a different
solution.
  4.1 =96 detail about power supply voltage, etc.  Why do we care about
this? What about devices with multiple power supplies, of the same
type, or heterogeneous?
  4.1 =96 is it normal to mix static values with highly dynamic ones?  I
have an urge to keep these separate, but am not familiar with mib
design.
  4.1 =96 I think the sentence under the table is key =96 that current
power and accumulated energy are the main items of interest in most
cases.  That needs to be kept front and center.
  4.1 =96 interruptions =96 I assume this is from power cycles or from
system OS failure.  As in other cases, I=92d like to see use cases
inform this.  I=92m not sure what solution(s) might make sense, but I am
reluctant to add too much complexity for this.  A real issue
regardless.
  5. batteries =96 are the alarm levels being simply reported, or being
set by an external device?

claise-energy-monitoring-mib-05
  6. =96 scenario 1 =96 =93switch does not have a parent=94 =96 doesn=92t t=
his
violate the statement that every monitor is part of a domain?  Mind
you, I don=92t think that should be a requirement (to have a parent).
  6. =96 scenario 7 =96 the paragraph above the diagram seems key =96 the
relationship between parent/child re: communications, re: power
distribution, and re: control.  I don=92t think we have clarity on this
yet.

From bnordman@lbl.gov  Tue Nov  2 00:07:02 2010
Return-Path: <bnordman@lbl.gov>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B21E3A6836 for <eman@core3.amsl.com>; Tue,  2 Nov 2010 00:07:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.733
X-Spam-Level: 
X-Spam-Status: No, score=-3.733 tagged_above=-999 required=5 tests=[AWL=-0.756, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nj7-vyyWPd4k for <eman@core3.amsl.com>; Tue,  2 Nov 2010 00:07:00 -0700 (PDT)
Received: from ironport4.lbl.gov (ironport4.lbl.gov [128.3.41.45]) by core3.amsl.com (Postfix) with ESMTP id A3D3F3A67F6 for <eman@ietf.org>; Tue,  2 Nov 2010 00:07:00 -0700 (PDT)
X-Ironport-SBRS: 4.4
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvkAADdVz0zRVdQ0kGdsb2JhbACTaAEBjXMIFQEBAQEJCQwHEQMfo2ObAYMLgjoEhFeFfQ
X-IronPort-AV: E=Sophos;i="4.58,279,1286175600"; d="scan'208";a="28165064"
Received: from mail-vw0-f52.google.com ([209.85.212.52]) by ironport4.lbl.gov with ESMTP; 02 Nov 2010 00:07:03 -0700
Received: by vws15 with SMTP id 15so4544445vws.39 for <eman@ietf.org>; Tue, 02 Nov 2010 00:07:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.181.83 with SMTP id bx19mr2672924qab.304.1288681623441; Tue, 02 Nov 2010 00:07:03 -0700 (PDT)
Received: by 10.229.105.8 with HTTP; Tue, 2 Nov 2010 00:07:03 -0700 (PDT)
Date: Tue, 2 Nov 2010 00:07:03 -0700
Message-ID: <AANLkTinkAyB3LMh6TW6gaQxKUNCqmj+buuvt+bofuC1k@mail.gmail.com>
From: Bruce Nordman <bnordman@lbl.gov>
To: eman@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [eman] Topics
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the creation of an Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Nov 2010 07:07:02 -0000

As an individual, the following are some topics that I have particular
interest in.  They are in no particular order.

Mode names
  I have dealt with these in many contexts over the last fifteen years,
both for electronic devices and others.  I have found them to be considerably
more important than one might initially think.

Use cases
  I think collecting existing examples of these into one location and expanding
it could be helpful in organizing our thinking and working towards consensus.

Parallel networks
  While sometimes communications and power distribution will be aligned, in
other cases they will not be.  This affects our notion of a parent device.

Units
  Our choices in energy, power, and other physical units may have a long
legacy so deserve extended consideration.

Complexity
  There are many directions that we could go that add complexity.  Some of these
are in our current drafts; others are not.  I think most of our
difficult decisions may
likely be which of these to include, and which not.  I have several of my own
favorite topics that probably do not rate inclusion in our first products.

Priority
  Elsewhere in life, price is used as a priority-setting mechanism,
and it embodies
a significant degree of simplicity and transparency.  I think it has
to be considered
along with other approaches to this problem.

Control
  I think we need to consider how much linkage there is between mechanisms for
reporting energy-related information, and those for control.

That's enough for now.  See you in Beijing.

--Bruce

-- 
Bruce Nordman
Lawrence Berkeley National Laboratory
eetd.lbl.gov/ea/nordman
BNordman@LBL.gov
510-486-7089
m: 510-501-7943

From jinchoe@gmail.com  Tue Nov  2 04:28:20 2010
Return-Path: <jinchoe@gmail.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 89FF628C121 for <eman@core3.amsl.com>; Tue,  2 Nov 2010 04:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yeee1XT5s8Ze for <eman@core3.amsl.com>; Tue,  2 Nov 2010 04:28:19 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id EEA1C28C112 for <eman@ietf.org>; Tue,  2 Nov 2010 04:28:18 -0700 (PDT)
Received: by wyb28 with SMTP id 28so6523953wyb.31 for <eman@ietf.org>; Tue, 02 Nov 2010 04:28:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=oM4zk3zqR/Xo5epi87tFzli1bVal+IMiYu7AKtsHbLQ=; b=li3R6bDqFwN700ElqnooUUN+54G+5LmZL3jHT9RawJWdGMSzlGc9nrYbfYjQ2qT95U 33sOYJBvHyEQfmpnm0mktA41uBmpeJG6ByjhJsTofppkGdPX9Enl4fgSk12GeRt+01a7 0hezNYEN7tlIFVVzybbLDlDZxgka5i4VMghTE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=V8hJV8CryfTzdvHbfVYbmyAjMeALJvc0+UU8YJn2TUxbYw1pzUZQSF9vvzjCaEZ7NZ 6E/AasJZ8JH5nogawAHRIxIrYIUioHs4m+KlOrGWavP1KaLV225lmFEk5tO7vFdwsQJl /xWwUIVhgom+HFpQjOycvBYN1546JSWDkUh+Q=
MIME-Version: 1.0
Received: by 10.227.127.79 with SMTP id f15mr92959wbs.86.1288697302121; Tue, 02 Nov 2010 04:28:22 -0700 (PDT)
Received: by 10.227.58.131 with HTTP; Tue, 2 Nov 2010 04:28:22 -0700 (PDT)
In-Reply-To: <4CB8A0D3.2000403@cisco.com>
References: <AANLkTi=kPF6=VNmewwoao0eTk9mwLOgjodaKm=sdeRE-@mail.gmail.com> <4CB8A0D3.2000403@cisco.com>
Date: Tue, 2 Nov 2010 20:28:22 +0900
Message-ID: <AANLkTi=gETakX9HQahFybo2-RBF6yijtW4+YeHJA6wOz@mail.gmail.com>
From: JinHyeock Choi <jinchoe@gmail.com>
To: john parello <jparello@cisco.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: eman@ietf.org
Subject: Re: [eman] Comments on Power Management Architecture
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the creation of an Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Nov 2010 11:28:20 -0000

Hi John

thanks for your reply
with which, in combination with the updated draft,
I can grasp more clear picture.

> [jparello] That's true however the assumption is that the communication
> between the NMS and POwer Monitors would be via SNMP. So the Architecture=
 is
> a description of what we need that is then implemented via SNMP data mode=
l.

Now with explicit reference model in ver-02, I can see it clear.

>> For example I guess that
>>
>> =A0 Large time series of energy consumption values of a Power Monitor Ch=
ild
>> =A0 are reported by Power Monitor Parent to NMS though IPFIX (or Syslog)
>>
>> but can=92t be sure that=92s right.
>
> [jparello] The group has not put a requirement for IPFIX but that could b=
e
> brought up the the WG meeting.

ok.

>> BTW which entity is IP enabled?
>> Which entity understands IP to report to NMS (via SNMP)?
>> All Power Monitor or Power Monitor Parent?
>
> [jparello] The assumption is that we are starting with SNMP first so a
> Parent power monitor would implement the mib and then and subtended devic=
es
> that did not or could not implement SNMP would be aggregated to the Power
> Monitor parent.

ok. I assume it=92s Power Monitor Parent

>>> From the document, I assume either
>>
>> i) a Parent provides a Child power (as in PoE) or
>> ii) a Child reports power information to its Parent.
>
> [jparello] The parent may or may not provide power to the child. For
> instance a PoE switch would have PoE endpoints as children and in this ca=
se
> would clearly provide power to the child. In the case of a wireless
> controller the controller may be the parent of the wireless APs but they =
may
> draw power directly from a wall outlet.

I assume
Power Monitor Children reports its power information to its Parent
and may or may not draw power from the Parent.

thanks for your clarification & see you in Beijing

best regards

JinHyeock





On Sat, Oct 16, 2010 at 3:43 AM, john parello <jparello@cisco.com> wrote:
> Hi JinHyeock,
>
> Thanks for the feedback and review. We have made changes to help clarify
> some of your point and it will be posted to the list.
>
> Please see inline for our thinking on the various points.
>
> On 10/5/10 11:05 PM, JinHyeock Choi wrote:
>>
>> Hi
>>
>> Here are some comments.
>>
>> 1. Communication model
>> I wish the communication model between Power Monitor& =A0NMS
>> (to which information would be ultimately reported, I assume).
>> is more clearly presented.
>>
>> The power monitoring information is defined in detail
>> but it=92s not clear
>> which entity report that information
>> to which entity through which mechanism.
>>
>
> [jparello] That's true however the assumption is that the communication
> between the NMS and POwer Monitors would be via SNMP. So the Architecture=
 is
> a description of what we need that is then implemented via SNMP data mode=
l.
>
>> For example I guess that
>>
>> =A0 Large time series of energy consumption values of a Power Monitor Ch=
ild
>> =A0 are reported by Power Monitor Parent to NMS though IPFIX (or Syslog)
>>
>> but can=92t be sure that=92s right.
>>
>
> [jparello] The group has not put a requirement for IPFIX but that could b=
e
> brought up the the WG meeting.
>
>> Though there are some related contents in 7. Fault Management,
>> I wish more clear statements& =A0elaboration.
>>
>> For more clear communication model,
>> it would help to add some paragraphs about
>>
>> 1) participating entities
>> =A0 =A0 as defined in Nordman I-D .
>>
>> =A0 =A0 Participating entities are monitoring systems that receive
>> =A0 =A0 information and networked devices that provide information on en=
ergy
>> =A0 =A0 consumption and power state information concerning themselves or
>> =A0 =A0 potentially also other devices.
>>
>
> [jparello] Yes I think we have this covered in the definition of Power
> Monitor itself.
>
>> BTW which entity is IP enabled?
>> Which entity understands IP to report to NMS (via SNMP)?
>> All Power Monitor or Power Monitor Parent?
>>
>
> [jparello] The assumption is that we are starting with SNMP first so a
> Parent power monitor would implement the mib and then and subtended devic=
es
> that did not or could not implement SNMP would be aggregated to the Power
> Monitor parent.
>
>> 2) monitoring model
>> =A0 =A0 SNMP/ MIB or IPFIX
>> =A0 =A0 as presented in [POWER-MON-REQ].
>>
>> BTW [POWER-MON-REQ] propose to (in Sec 6) develop
>> a standard for pull-based power state monitoring
>> and push based one (with IPFIX or Syslog).
>> About which, this document won=92t make any statement?
>>
>
> [jparello] See previous that IPFIX could be brought up as a WG item IMO.
>
>> 2. Power Monitor Parent& =A0Child
>> There are some ambiguities regarding
>> Power Monitor Parent& =A0Child relationship.
>>
>> First it=92s not clear which makes two entities
>> Power Monitor Parent& =A0Power Monitor Child.
>>
>
> [jparello] We have added this in the next revision about to be posted.
>
>>> From the document, I assume either
>>
>> i) a Parent provides a Child power (as in PoE) or
>> ii) a Child reports power information to its Parent.
>>
>
> [jparello] The parent may or may not provide power to the child. For
> instance a PoE switch would have PoE endpoints as children and in this ca=
se
> would clearly provide power to the child. In the case of a wireless
> controller the controller may be the parent of the wireless APs but they =
may
> draw power directly from a wall outlet.
>
>> However, in 4.3, it=92s written
>>
>> =A0 =A0 =A0 =A0 A Power Monitor Child can be fully dependent on the Powe=
r
>> =A0 =A0 =A0 =A0 Monitor Parent (as in the case of Power Over Ethernet) o=
r
>> =A0 =A0 =A0 =A0 independent from the parent (such as a PC connected to a
>> =A0 =A0 =A0 =A0 switch).
>>
>> What makes a PC a child to a switch?
>> Just because it=92s connected to the switch or
>> is it assumed that the PC report its power usage to the switch?
>>
> [jparello] Yes. The idea is that some device that is capable of
> communicating power usage could act as an aggregation point for other
> subtended devices. So a switch could be a parent for connected PCs. One
> could have one PC that is the parent and SNMP capable and other PCs that =
are
> not capable as children. The proposed architecture allows for one device
> that can communicate power information to an NMS can act as a parent or
> aggregation point for others that cannot communicate to the NMS.
>
>
>> Also what if a Parent provides a Child a power
>> but the Parent neither monitor the Child=92s power usage
>> nor the Child makes no report to the Parent?
>>
>
> [jparello] In that case we envision the parent to at least provide the
> nameplate power characteristics of itself or even better of the children.
> The power usage data model allows the Power Monitor parent to describe ho=
w
> and to what accuracy the usage is reported. In this scenario it would be =
a
> poor participant but could still presumably report nameplate power.
>
>> In the above case,
>> The Parent plays no role in the Child=92s Power Monitoring.
>>
>
> [jparello] see above.
>
>> Here are some more questions.
>>
>> 1) Can a Child have more than one Parents?
>> For example a IP phone may get a power from PoE
>> but report its power usage to a building gateway.
>>
>
> [jparello] The parent is defines as the device that aggregates and provid=
es
> reporting it may not be the source of the power. So we specifically don't
> want a device to report its power to two parents as that would cause doub=
le
> counting.
>
>> 2) Does Parent always report
>> the power information of its=92 Child for its stead?
>> If so, to whom, NMS of it=92s own Parent?
>>
>
> [jparello] The parent may report the power usage on behalf of the child o=
r
> may delegate it to the child and aggregate it to the NMS.
>
>> 3) It=92s written
>>
>> =A0 =A0 =A0A Power Monitor cannot be at the same time a Power Monitor
>> =A0 =A0 =A0Parent and a Power Monitor Child.
>>
>> But the above seems to contradict with
>> Figure 4 of Scenario 1 of [POWER-MON-MIB]
>> in which
>> SWITCH PORT is the CHILD of SWITCH and
>> the PARENT of IP PHONE at that same time.
>> Please clarify.
>>
>
> [jparello] For SNMP the NMS would talk to each parent directly to get pow=
er
> information. Having a parent that is also a child of another parent would
> cause the devices to begin to "walk the network". As such we specified ea=
ch
> parent as a disjoint tree of power reporting.
>
>
>> 4) Which entity report to NMS with IP?
>> A Child can make its own report to NMS
>> or always a Parent should report for its stead?
>>
>
> [jparello] By definition the parent aggregates it.
>
>
> Thanks so much!
> John
>
>

From jinchoe@gmail.com  Tue Nov  2 04:30:44 2010
Return-Path: <jinchoe@gmail.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E27F028C124 for <eman@core3.amsl.com>; Tue,  2 Nov 2010 04:30:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yBUBoEBLHJdb for <eman@core3.amsl.com>; Tue,  2 Nov 2010 04:30:39 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id AEE6328C121 for <eman@ietf.org>; Tue,  2 Nov 2010 04:30:38 -0700 (PDT)
Received: by wyb28 with SMTP id 28so6525918wyb.31 for <eman@ietf.org>; Tue, 02 Nov 2010 04:30:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=jLg/JiblIM4M/KQhnb7+jp/SNDAJKhIsDbSHqiG/oQ8=; b=nskbJAFmiy8GDLZ8vcRgG/xPWuFnj1OcLdCt1rXnQxI7GK4TJAUvQuWZmhZwzXmCxD 0Za1PKvq8GO7qSEepgYwTLdmAcXjoKlimH25WBRYLevenT0Y4xiFWFommnt7pfY4Wn+x PFirgLnpSeNj3QE9eJ9ZHpMNidwnhBcT15zSc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=m6WYeaMj34sDgz80BdF7+r53703Rsn9GMFDQWQytHD/sWdr0w7+o5IT4SQH+O9ZLQy xzmTWJLk2M4g14BX3Jh910kGbhjZmPZI0A5yccbSi+k7TTRd6cUF3Ena54OvD5T0ffKI 7R3IRShelWs6kBbzcYd1bCC2WhnqFoiVNMp4Q=
MIME-Version: 1.0
Received: by 10.227.141.137 with SMTP id m9mr3401328wbu.115.1288697441517; Tue, 02 Nov 2010 04:30:41 -0700 (PDT)
Received: by 10.227.58.131 with HTTP; Tue, 2 Nov 2010 04:30:41 -0700 (PDT)
In-Reply-To: <AANLkTimQmR8qEddc4KoB-JXst4Je2L12FVyPJOidp9T6@mail.gmail.com>
References: <AANLkTi=kPF6=VNmewwoao0eTk9mwLOgjodaKm=sdeRE-@mail.gmail.com> <AANLkTimQmR8qEddc4KoB-JXst4Je2L12FVyPJOidp9T6@mail.gmail.com>
Date: Tue, 2 Nov 2010 20:30:41 +0900
Message-ID: <AANLkTin-vVNhxiD75RfOXuTQW4_KkgGZNmDfyrGGZCxY@mail.gmail.com>
From: JinHyeock Choi <jinchoe@gmail.com>
To: Ted Ghose <ted@ghose.us>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: eman@ietf.org
Subject: Re: [eman] Comments on Power Management Architecture
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the creation of an Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Nov 2010 11:30:45 -0000

Hi Ted

Kindly see in line comments.

> [tg] model we should be looking for is:
>
> * entity that are not capable of monitoring/manage its own power to align=
 up
> to a device who can do this for it, hence this device will be a child of =
the
> device who control it.

ok. I see the general reasoning behind PARENT-CHILDREN relationship

>> 3) It=92s written
>>
>> =A0 =A0 A Power Monitor cannot be at the same time a Power Monitor
>> =A0 =A0 Parent and a Power Monitor Child.
>>
>> But the above seems to contradict with
>> Figure 4 of Scenario 1 of [POWER-MON-MIB]
>> in which
>> SWITCH PORT is the CHILD of SWITCH and
>> the PARENT of IP PHONE at that same time.
>> Please clarify.
>
> [tg] please read: monitoring of the device who is monitoring other device=
s
> is orthogonal about its own consumption. Take the case of an electric met=
er
> of a home. The meter may not be capable of measuring its own usage, but c=
an
> measure the power drawn by the home. Now the power drawn by the meter can=
 be
> monitored by someone else, hence the flexibility presented!

Oh, this is the angle I didn=92t perceive before, interestingly intricate.

In the above case, Electric meter
is a PARENT to the home with respect to home power consumption and
can be a CHILDREN to some monitoring device
with respect to its own power consumption, right?

I guess this prevents double energy counting
and PARENT-CHILDREN relationship is more flexible/ complicated
than I had expected.

>> 4) Which entity report to NMS with IP?
>> A Child can make its own report to NMS
>> or always a Parent should report for its stead?
>
> [tg] in the light of all above cases, it depends. if a device is capable =
of
> doing so, it will, else it can ask somebody else to manage it for him.

If a CHILD can make its own reporting,
why does it need a PARENT in the first place?

Also to the same question, John replied as below

[jparello] By definition the parent aggregates it.

Thanks for your clarification and see you in Beijing.

Best regards

JinHyeock



On Sun, Oct 17, 2010 at 4:47 PM, Ted Ghose <ted@ghose.us> wrote:
> in line, look for [tg]
> On Tue, Oct 5, 2010 at 11:05 PM, JinHyeock Choi <jinchoe@gmail.com> wrote=
:
>>
>> Hi
>>
>> Here are some comments.
>>
>> 1. Communication model
>> I wish the communication model between Power Monitor & NMS
>> (to which information would be ultimately reported, I assume).
>> is more clearly presented.
>>
>> The power monitoring information is defined in detail
>> but it=92s not clear
>> which entity report that information
>> to which entity through which mechanism.
>>
>> For example I guess that
>>
>> =A0Large time series of energy consumption values of a Power Monitor Chi=
ld
>> =A0are reported by Power Monitor Parent to NMS though IPFIX (or Syslog)
>>
>> but can=92t be sure that=92s right.
>>
>> Though there are some related contents in 7. Fault Management,
>> I wish more clear statements & elaboration.
>>
>> For more clear communication model,
>> it would help to add some paragraphs about
>>
>> 1) participating entities
>> =A0 =A0as defined in Nordman I-D .
>>
>> =A0 =A0Participating entities are monitoring systems that receive
>> =A0 =A0information and networked devices that provide information on ene=
rgy
>> =A0 =A0consumption and power state information concerning themselves or
>> =A0 =A0potentially also other devices.
>>
>> BTW which entity is IP enabled?
>> Which entity understands IP to report to NMS (via SNMP)?
>> All Power Monitor or Power Monitor Parent?
>>
>
> [tg] if entity is ip enable, it can report its own information. if the
> entity is ip enable and do not have capability to monitor its own energy
> usage, it should at least be capable of telling (automatically or by
> configuration) who is monitoring its usage.
>
>
>> 2) monitoring model
>> =A0 =A0SNMP/ MIB or IPFIX
>> =A0 =A0as presented in [POWER-MON-REQ].
>>
>> BTW [POWER-MON-REQ] propose to (in Sec 6) develop
>> a standard for pull-based power state monitoring
>> and push based one (with IPFIX or Syslog).
>> About which, this document won=92t make any statement?
>
> [tg] ipfix is a better choice, I'd keep it open for discussion. ipfix is
> more designed towards data collection for data mining.
>>
>> 2. Power Monitor Parent & Child
>> There are some ambiguities regarding
>> Power Monitor Parent & Child relationship.
>>
>> First it=92s not clear which makes two entities
>> Power Monitor Parent & Power Monitor Child.
>>
>> From the document, I assume either
>> i) a Parent provides a Child power (as in PoE) or
>> ii) a Child reports power information to its Parent.
>>
>> However, in 4.3, it=92s written
>>
>> =A0 =A0 =A0 =A0A Power Monitor Child can be fully dependent on the Power
>> =A0 =A0 =A0 =A0Monitor Parent (as in the case of Power Over Ethernet) or
>> =A0 =A0 =A0 =A0independent from the parent (such as a PC connected to a
>> =A0 =A0 =A0 =A0switch).
>>
>> What makes a PC a child to a switch?
>> Just because it=92s connected to the switch or
>> is it assumed that the PC report its power usage to the switch?
>>
>> Also what if a Parent provides a Child a power
>> but the Parent neither monitor the Child=92s power usage
>> nor the Child makes no report to the Parent?
>>
>> In the above case,
>> The Parent plays no role in the Child=92s Power Monitoring.
>>
>
> [tg] model we should be looking for is:
>
> * entity that are not capable of monitoring/manage its own power to align=
 up
> to a device who can do this for it, hence this device will be a child of =
the
> device who control it.
>
>>
>> Here are some more questions.
>>
>> 1) Can a Child have more than one Parents?
>> For example a IP phone may get a power from PoE
>> but report its power usage to a building gateway.
>
> [tg] if someone providing the PoE power, it will be double counting to
> measure it from building gateway. In this light we should have one and on=
ly
> one parent.
>>
>> 2) Does Parent always report
>> the power information of its=92 Child for its stead?
>> If so, to whom, NMS of it=92s own Parent?
>
> [tg] if and only if a child wish the parent to report or control its powe=
r.
> We will always like to to make the end device to make the call.
>>
>> 3) It=92s written
>>
>> =A0 =A0 A Power Monitor cannot be at the same time a Power Monitor
>> =A0 =A0 Parent and a Power Monitor Child.
>>
>> But the above seems to contradict with
>> Figure 4 of Scenario 1 of [POWER-MON-MIB]
>> in which
>> SWITCH PORT is the CHILD of SWITCH and
>> the PARENT of IP PHONE at that same time.
>> Please clarify.
>
> [tg] please read: monitoring of the device who is monitoring other device=
s
> is orthogonal about its own consumption. Take the case of an electric met=
er
> of a home. The meter may not be capable of measuring its own usage, but c=
an
> measure the power drawn by the home. Now the power drawn by the meter can=
 be
> monitored by someone else, hence the flexibility presented!
>>
>> 4) Which entity report to NMS with IP?
>> A Child can make its own report to NMS
>> or always a Parent should report for its stead?
>
> [tg] in the light of all above cases, it depends. if a device is capable =
of
> doing so, it will, else it can ask somebody else to manage it for him.
>
> Best Regards
>
> -tg-
>>
>> Best Regards
>>
>> JinHyeock Choi
>> _______________________________________________
>> eman mailing list
>> eman@ietf.org
>> https://www.ietf.org/mailman/listinfo/eman
>
>

From Christian.Groves@nteczone.com  Tue Nov  2 19:12:42 2010
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EE0AD28C0E6 for <eman@core3.amsl.com>; Tue,  2 Nov 2010 19:12:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GnvtNf6Gxbx8 for <eman@core3.amsl.com>; Tue,  2 Nov 2010 19:12:39 -0700 (PDT)
Received: from quasar.websiteactive.com (quasar.websiteactive.com [202.191.61.215]) by core3.amsl.com (Postfix) with ESMTP id 34ECF3A68A9 for <eman@ietf.org>; Tue,  2 Nov 2010 19:12:38 -0700 (PDT)
Received: from ppp118-209-52-37.lns20.mel4.internode.on.net ([118.209.52.37] helo=[127.0.0.1]) by quasar.websiteactive.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Christian.Groves@nteczone.com>) id 1PDSq8-0001qc-S5; Wed, 03 Nov 2010 13:12:41 +1100
Message-ID: <4CD0C560.7080907@nteczone.com>
Date: Wed, 03 Nov 2010 13:13:52 +1100
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: Chris Verges <chrisv@cyberswitching.com>
References: <C8EFF4A6.163CA%quittek@neclab.eu> <4CCE3065.6050705@nteczone.com> <68FBE0F3CE97264395875AC1C468F22C514765@mail03.cyberswitching.local>
In-Reply-To: <68FBE0F3CE97264395875AC1C468F22C514765@mail03.cyberswitching.local>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - quasar.websiteactive.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: eman@ietf.org
Subject: Re: [eman] Entity identification method
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the creation of an Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Nov 2010 02:12:42 -0000

Hello Chris,

I don't have any concrete suggestions for implementing virtual entity 
energy usage support. I'm still at the stage of trying to see what the 
requirements and framework is for the work. There seems to be a focus on 
the MIBs themselves, when without good requirements its hard to see what 
needs they are meeting. The work of the eman WG could address IP type 
servers only or the MIBs could also be used in other telecommunication 
equipment i.e. those used in outside plant. I'm encouraged to see 
Bruce's email on topics for discussion as think its in important to get 
consensus/understanding on these before the MIBs are developed.

Please see my comment below marked [CNG].

Regards, Christian

On 1/11/2010 11:39 PM, Chris Verges wrote:
>
> Hi Christian,
>
> Are you looking to allocate actual energy usage by a virtual entity, 
> like the amount of energy used by a virtual machine running on a 
> shared server? Certainly an interesting problem ... gives a lot of 
> room for innovation for different vendors to find solutions.
>
[CNG] I agree its an interesting problem. In some instances it may be 
possible to allocate the actual energy however in many cases it would be 
very difficult/impossible. In these more difficult cases it may be 
possible to simply report the identities of the virtual/logical entities 
that are included in the physical measurement.
>
> From a MIB standpoint, it seems like the requirement is to have a 
> flexible power-related MIB that can either map to physical or logical 
> entities. One question is, “where do you want those entities enumerated?”
>
> Are virtual entities that need to be mapped to power usage normally 
> enumerated in ENTITY-MIB in the “logical” table?
>
> If so, perhaps something like this would fit the bill:
>
> POWER-ENTITY-MIB:
>
> pwrEntityTable
>
> pwrEntityEntry
>
> pwrEntityIndex
>
> pwrEntityName
>
> pwrEntityType
>
> pwrEntityParent
>
> pwrEntityPhysical
>
> pwrEntityLogical
>
> The pwrEntity[Physical|Logical] objects would point to the appropriate 
> index in ENTITY-MIB.
>
> However, if the virtual entities are not enumerated in ENTITY-MIB, the 
> pwrEntityLogical column is probably overkill. The virtual entities can 
> be enumerated in pwrEntityTable and linked to the Physical meter using 
> the pwrEntityParent column, much like how ENTITY-MIB currently manages 
> references between parent and component entities. It would just 
> involve a new pwrEntityType being added for “virtual” or something 
> similar.
>
> So what’s the typical use case as these virtual entities relate to 
> ENTITY-MIB?
>
[CNG] I'm not sure the typical case. Either of the approaches above 
could be sufficient but I think it depends on what people agree on with 
respect to virtual entities and how the data collected on them would be 
used.
>
> Chris
>
> -----Original Message-----
> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf 
> Of Christian Groves
> Sent: Sunday, October 31, 2010 8:14 PM
> To: eman@ietf.org
> Subject: Re: [eman] Entity identification method
>
> Hello Juergen,
>
> I think distinguishing the two cases is the correct way to go.
>
> I agree that reporting energy consumption for logical entities is a 
> challenge and not straight forward. I guess there are a number of ways 
> to look at this problem and how address the problem depends on the 
> ambition level.
>
> As you rightly mention where there is partial use of a physical 
> resource by a logical entity it is very difficult to have an exact 
> figure.
>
> However I think the "grain size" of the measurement comes into play. 
> For example if we have a large gateway implementing several virtual 
> gateways if we take an overall measurement then we have the problem 
> determining a figure. If the however the virtual gateways were each 
> assigned a physical rack and the measurements were taken at a rack 
> level then we have a more precise estimate of contribution of each 
> virtual gateway to the overall picture.
>
> For me logical entities ultimately will be realised by physical 
> hardware. The key is understanding the relationship between these 
> entities. Thus I think virtualization can in some way be supported by 
> allowing energy consumption reports for physical entities to indicate 
> if/what logical entities they relate to. As they say information is 
> power (pardon the pun :-) ).
>
> Regards, Christian
>
> On 29/10/2010 12:48 PM, Juergen Quittek wrote:
>
> > Hi Christian,
>
> >
>
> > Thank you for this interesting comment.
>
> >
>
> > It looks like we have to distinguish two cases: power state monitoring
>
> > and energy consumption monitoring.
>
> >
>
> > For a logical entity and a virtual machine it may be well possible to
>
> > report on their power state. However, reporting their energy
>
> > consumption seems to be a tough challenge at least if be base it on 
> real measurements.
>
> >
>
> > It is well feasible to measure energy consumption of physical
>
> > entities, but if you have a logical entity that consumes only partial
>
> > resources of a physical entity, then precise measurement of the energy
>
> > consumption will be hardly possible. Estimations may be possible based
>
> > on a model of the logical entity, but I don't know how good such 
> models can be.
>
> >
>
> > Thanks,
>
> >
>
> > Juergen
>
> >
>
> >
>
> > On 29.10.10 03:25 "Christian Groves"<Christian.Groves@nteczone.com 
> <mailto:Christian.Groves@nteczone.com>> wrote:
>
> >
>
> >> Hello
>
> >>
>
> >> I've just started to digest the various drafts of the eman wg and I
>
> >> see the comment below on logical entities. It's not clear to me
>
> >> how/if network virtualization is intended on being handled in the 
> eman work.
>
> >>
>
> >> In networks there's now a trend towards network virtualization and
>
> >> cloud computing with the different "X" as a service models (i.e.
>
> >> Amazon EC2 "platform as a service" running different server
>
> >> instances). Even in today's networks we have physical gateways that
>
> >> are virtualized into different logical gateways. For example:
>
> >> H.248/Megaco virtual MG (VMG) concept.
>
> >>
>
> >> I think it would be advantageous to be able to assess the energy
>
> >> consumption of the VMGs or instances (which are logical entities)
>
> >> independent of the physical gateway so that a customers energy use
>
> >> may be recording. Will this sort of functionality be allowed?
>
> >>
>
> >> Regards, Christian
>
> >>
>
> >> On 29/10/2010 1:22 AM, Juergen Quittek wrote:
>
> >>> Hi Chris,
>
> >>>
>
> >>> I think it may become very difficult if we want to assess energy
>
> >>> consumption of logical entities. It seems to be reasonable and
>
> >>> practical to limit energy consumption measurements to physical
>
> >>> entities. The ENERGY AWARE MIB module
>
> >>> (draft-parello-eman-energy-aware-mib) and the POWER MIB
>
> >>> (draft-quittek-power-mib-02) went this way.
>
> >>>
>
> >>> Just using entPhysicalIndex solves some of the problem you mentioned.
>
> >>> Particularly, you don't need a mapping table to entities if you
>
> >>> restrict Yourself to entPhysicalIndex.
>
> >>>
>
> >>> Thanks,
>
> >>>
>
> >>> Juergen
>
> >>>
>
> >>> On 28.10.10 13:34 "Chris Verges"<chrisv@cyberswitching.com 
> <mailto:chrisv@cyberswitching.com>> wrote:
>
> >>>
>
> >>>> Hi Jurgen and all,
>
> >>>>
>
> >>>> The more I've been thinking about these scenarios, the more
>
> >>>> something doesn't seem quite right. I'll try to explain my thought
>
> >>>> process behind this and see if my concerns/confusions get captured.
>
> >>>>
>
> >>>> ENTITY-MIB provides enumerated lists of physical and logical
>
> >>>> entities on the system. The indices in both lists are maintained
>
> >>>> separately, so there is not a single, unique identifier provided.
>
> >>>> Because of this, the MIBs being discussed by the EMAN WG must only
>
> >>>> reference to one type (physical or logical) and are limited to 
> that without additional work.
>
> >>>> At some point in my mind, I'm asking myself the question, "What's
>
> >>>> the point of linking to ENTITY-MIB?"
>
> >>>>
>
> >>>> More on that question in later scenarios below ...
>
> >>>>
>
> >>>> One possibility would be to create a separate mapping table that
>
> >>>> gives a guaranteed unique index based on all entities, regardless
>
> >>>> of type. The physical vs. logical extensions would then become
>
> >>>> sparse tables that augment this. For example:
>
> >>>>
>
> >>>> ENTITY-MIB : entityGeneral.entGeneralTable.entGeneralEntry
>
> >>>> +-----------------+-----------------+-----+
>
> >>>> | entGeneralIndex | entGeneralDescr | ... |
>
> >>>> +-----------------+-----------------+-----+
>
> >>>> | 1 | PDU Chassis | |
>
> >>>> +-----------------+-----------------+-----+
>
> >>>> | 2 | Meter #1 | |
>
> >>>> +-----------------+-----------------+-----+
>
> >>>> | 3 | Meter #2 | |
>
> >>>> +-----------------+-----------------+-----+
>
> >>>> | 4 | Remote Meter #1 | |
>
> >>>> +-----------------+-----------------+-----+
>
> >>>>
>
> >>>> ENTITY-MIB : entityPhysical.entPhysicalTable.entPhysicalEntry
>
> >>>> +-----------------+-----------------+-----+
>
> >>>> | entGeneralIndex | entVendorType | ... |
>
> >>>> +-----------------+-----------------+-----+
>
> >>>> | 1 | enterprises.foo | |
>
> >>>> +-----------------+-----------------+-----+
>
> >>>> | 2 | enterprises.foo | |
>
> >>>> +-----------------+-----------------+-----+
>
> >>>> | 3 | enterprises.foo | |
>
> >>>> +-----------------+-----------------+-----+
>
> >>>>
>
> >>>> ENTITY-MIB : entityLogical.entLogicalTable.entLogicalEntry
>
> >>>> +-----------------+----------------------+-----+
>
> >>>> | entGeneralIndex | entLogicalCommunity | ... |
>
> >>>> +-----------------+----------------------+-----+
>
> >>>> | 4 | remote-power-group-1 | |
>
> >>>> +-----------------+----------------------+-----+
>
> >>>>
>
> >>>> It seems like this 'entGeneralIndex' concept is what's missing from
>
> >>>> the current ENTITY-MIB, and is causing problems when thinking about
>
> >>>> local and remote power data being reported by the same agent.
>
> >>>>
>
> >>>> Another possibility would be to choose one -- entLogicalIndex, most
>
> >>>> likely -- and require that anyone who wants to implement the EMAN
>
> >>>> WG MIBs to always create an entLogicalEntry for the power data. In
>
> >>>> this context, the entLogicalTable fills the role of entGeneralTable
>
> >>>> as described above. For all entPhysicalTable entries, there would
>
> >>>> need to be a corresponding entry in entLogicalTable with a 1:1
>
> >>>> mapping between them. For all remote entries, there would be a
>
> >>>> unique entry in entLogicalTable. Of course, this would add some
>
> >>>> additional overhead on the part of the implementer, but isn't too 
> overburdening.
>
> >>>>
>
> >>>> A third possibility is that ENTITY-MIB just doesn't do what we need
>
> >>>> in its present form and we need to think about enumerating power
>
> >>>> sensors separately from other components/sensors on the system. It
>
> >>>> seems like entPhysicalTable gives a good starting template for a
>
> >>>> new 'POWER-ENTITY-MIB', but can be extended to include support for
>
> >>>> remote agents. The difference would be a clean break from the
>
> >>>> legacy ENTITY-MIB structure.
>
> >>>>
>
> >>>> And with that, I look forward to others' feedback and ideas on
>
> >>>> solving this problem!
>
> >>>>
>
> >>>> Thanks,
>
> >>>> Chris
>
> >>>>
>
> >>>> -----Original Message-----
>
> >>>> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On
>
> >>>> Behalf Of Chris Verges
>
> >>>> Sent: Tuesday, October 26, 2010 9:26 PM
>
> >>>> To: Juergen Quittek; Benoit Claise; eman mailing list
>
> >>>> Subject: Re: [eman] Entity identification method (was: EMAN
>
> >>>> chartered itemsversus drafts)
>
> >>>>
>
> >>>> Hi Juergen and all,
>
> >>>>
>
> >>>> Agreed that a common ID method makes sense, and ENTITY-MIB seems to
>
> >>>> be a good choice. In case (c) from your list, wouldn't the remote
>
> >>>> agent condition be handled by ENTITY-MIB supporting a logical
>
> >>>> entity that is the remote agent iself? Since the logical entity is
>
> >>>> in the ENTITY-MIB table, it would be given a unique ID mixed
>
> >>>> amongst the other logical and physical entities.
>
> >>>>
>
> >>>> At that point, should all of the MIBs being discussed in the EMAN
>
> >>>> WG be sparse table augmentations of ENTITY-MIB?
>
> >>>>
>
> >>>> Thanks,
>
> >>>> Chris
>
> >>>>
>
> >>>> -----Original Message-----
>
> >>>> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On
>
> >>>> Behalf Of Juergen Quittek
>
> >>>> Sent: Tuesday, October 26, 2010 6:01 AM
>
> >>>> To: Benoit Claise; eman mailing list
>
> >>>> Subject: [eman] Entity identification method (was: EMAN chartered
>
> >>>> items versus drafts)
>
> >>>>
>
> >>>> Hi Benoit and all,
>
> >>>>
>
> >>>> I agree that we should find a common identification method for
>
> >>>> entities used by all MIB modules. This does not apply to the POWER
>
> >>>> MIB only, but to all MIB modules in the eman WG.
>
> >>>> The modules will use an entity ID as index for their tables.
>
> >>>> Which entity is identified by the index can be resolved by other
>
> >>>> MIB modules, such as the POWER AWARE MIB module
>
> >>>> (draft-parello-eman-energy-aware-mib) or the ENTITY MIB module (RFC
>
> >>>> 4133).
>
> >>>>
>
> >>>> I see three basic scenarios for the entity identification:
>
> >>>>
>
> >>>> a) a device just reports on its own power state and energy
>
> >>>> consumption and it reports on its own as a single unit.
>
> >>>>
>
> >>>> Then we have a single index only stating "it's me".
>
> >>>> Such a device usually does not need further identification
>
> >>>> of itself, because typically there are sufficient other
>
> >>>> MIB modules for this purpose running in the same SNMP engine,
>
> >>>> that provide information about the device's IP address,
>
> >>>> manufacturer, operating system, etc. In such a case a
>
> >>>> 'trivial' index, such as '0' should be used in order to
>
> >>>> keep it simple in this most simple case.
>
> >>>>
>
> >>>> b) a device reports on its own but not just as a single unit
>
> >>>> but it reports power states and energy consumption for its
>
> >>>> individual components, for example it may report separately
>
> >>>> on contained hard drives, line cards, back planes,
>
> >>>> processor boards, etc.
>
> >>>>
>
> >>>> In such a case, identification of these components as
>
> >>>> individual entities would be required. The ENTITY MIB
>
> >>>> module was designed for this purpose and would be a good
>
> >>>> choice here. Also the POWER AWARE MIB module would be
>
> >>>> useful in this case.
>
> >>>>
>
> >>>> c) a device reports on energy consumption of other, remote
>
> >>>> devices. Then remote devices (and potentially also their
>
> >>>> contained components need to be identified. For
>
> >>>> identifying remote components there is the POWER AWARE MIB
>
> >>>> module that has been designed for this purpose. As far as
>
> >>>> I understand, the ENTITY MIB module is not applicable to
>
> >>>> remote devices.
>
> >>>>
>
> >>>> In summary,
>
> >>>> - if you need to report on remote entities (case c)),
>
> >>>> you need the POWER AWARE MIB module,
>
> >>>> - if you report only on entities locally contained
>
> >>>> in the reporting device (case b)), you can use
>
> >>>> the POWER AWARE MIB or the ENTITY MIB
>
> >>>> - if you report just on your own as a single device
>
> >>>> (case a)), identification is trivial
>
> >>>>
>
> >>>> Hence, my recommendation (stated for POWER-STATE MIB and ENERGY MIB
>
> >>>> in
>
> >>>> draft-quittek-power-mib-02) would be:
>
> >>>>
>
> >>>> If there is an implementation of the POWER AWARE MIB module
>
> >>>> instantiated in the local SNMP engine, then you SHOULD (or MUST?)
>
> >>>> use it for indexing (pmIndex).
>
> >>>> If this is not the case but there is an ENTITY MIB instance
>
> >>>> available, then you SHOULD use this one (entPhysicalIndex).
>
> >>>> If neither of this MIB modules is available you should use index 0
>
> >>>> only and be limited to report on the local device as a single 
> entity only.
>
> >>>>
>
> >>>> That's just my view. Certainly, there are more ways of entity
>
> >>>> identification. I look forward to discussing them.
>
> >>>>
>
> >>>> Thanks,
>
> >>>>
>
> >>>> Juergen
>
> >>>>
>
> >>>>
>
> >>>> On 26.10.10 11:44 "Benoit Claise"<bclaise@cisco.com 
> <mailto:bclaise@cisco.com>> wrote:
>
> >>>>
>
> >>>>> Hi Juergen,
>
> >>>>>
>
> >>>>> Thanks for the clarification.
>
> >>>>>
>
> >>>>> Something key is to agree on the Power Monitor index for all MIB
>
> >>>>> modules, which IMHO should be part of the Energy-aware Networks
>
> >>>>> and Devices MIB module, but reuse in the other MIB modules.
>
> >>>>>
>
> >>>>> Regards, Benoit.
>
> >>>>>> Hi Benoit,
>
> >>>>>>
>
> >>>>>> Thanks for checking all drafts.
>
> >>>>>>
>
> >>>>>> I don't think that draft-quittek-power-mib-02 makes significant
>
> >>>>>> contributions to the Energy-aware Networks and Devices MIB.
>
> >>>>>> It just covers the Power and Energy Monitoring MIB and the
>
> >>>>>> Battery
>
> >>>> MIB.
>
> >>>>>> Thanks,
>
> >>>>>> Juergen
>
> >>>>>>
>
> >>>>>>
>
> >>>>>> On 26.10.10 08:22 "Benoit Claise"<bclaise@cisco.com 
> <mailto:bclaise@cisco.com>> wrote:
>
> >>>>>>
>
> >>>>>>> Dear all,
>
> >>>>>>>
>
> >>>>>>> I went through the exercise of mapping the existing six
>
> >>>>>>> chartered items with the existing draft content.
>
> >>>>>>>
>
> >>>>>>> _Energy Management Requirements_
>
> >>>>>>> http://tools.ietf.org/html/draft-quittek-power-monitoring-requir
>
> >>>>>>> emen
>
> >>>>>>> ts-02
>
> >>>>>>> https://datatracker.ietf.org/doc/draft-norwin-energy-consider/
>
> >>>>>>> _
>
> >>>>>>> Energy Management Framework_
>
> >>>>>>> http://tools.ietf.org/html/draft-claise-power-management-arch-02
>
> >>>>>>>
>
> >>>>>>> _Energy-aware Networks and Devices MIB_
>
> >>>>>>> http://tools.ietf.org/html/draft-parello-eman-energy-aware-mib-0
>
> >>>>>>> 0
>
> >>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>
> >>>>>>>
>
> >>>>>>> _Power and Energy Monitoring MIB_
>
> >>>>>>> http://tools.ietf.org/html/draft-claise-energy-monitoring-mib-06
>
> >>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>
> >>>>>>>
>
> >>>>>>> _Battery MIB_
>
> >>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>
> >>>>>>>
>
> >>>>>>> _Energy Management Applicability_
>
> >>>>>>> http://datatracker.ietf.org/doc/draft-tychon-eman-applicability-
>
> >>>>>>> stat
>
> >>>>>>> ement/
>
> >>>>>>>
>
> >>>>>>> Please let me know if I made any mistakes or if I missed any 
> draft?
>
> >>>>>>>
>
> >>>>>>> Regards, Benoit.
>
> >>>>>>> _______________________________________________
>
> >>>>>>> eman mailing list
>
> >>>>>>> eman@ietf.org <mailto:eman@ietf.org>
>
> >>>>>>> https://www.ietf.org/mailman/listinfo/eman
>
> >>>> _______________________________________________
>
> >>>> eman mailing list
>
> >>>> eman@ietf.org <mailto:eman@ietf.org>
>
> >>>> https://www.ietf.org/mailman/listinfo/eman
>
> >>>
>
> >>> _______________________________________________
>
> >>> eman mailing list
>
> >>> eman@ietf.org <mailto:eman@ietf.org>
>
> >>> https://www.ietf.org/mailman/listinfo/eman
>
> >> _______________________________________________
>
> >> eman mailing list
>
> >> eman@ietf.org <mailto:eman@ietf.org>
>
> >> https://www.ietf.org/mailman/listinfo/eman
>
> >
>
> >
>
> > _______________________________________________
>
> > eman mailing list
>
> > eman@ietf.org <mailto:eman@ietf.org>
>
> > https://www.ietf.org/mailman/listinfo/eman
>
> _______________________________________________
>
> eman mailing list
>
> eman@ietf.org <mailto:eman@ietf.org>
>
> https://www.ietf.org/mailman/listinfo/eman
>

From Christian.Groves@nteczone.com  Tue Nov  2 19:20:24 2010
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5DD3A3A6A53 for <eman@core3.amsl.com>; Tue,  2 Nov 2010 19:20:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level: 
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=0.650,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TBiceHRzoEky for <eman@core3.amsl.com>; Tue,  2 Nov 2010 19:20:22 -0700 (PDT)
Received: from quasar.websiteactive.com (quasar.websiteactive.com [202.191.61.215]) by core3.amsl.com (Postfix) with ESMTP id B4F463A69BD for <eman@ietf.org>; Tue,  2 Nov 2010 19:20:21 -0700 (PDT)
Received: from ppp118-209-52-37.lns20.mel4.internode.on.net ([118.209.52.37] helo=[127.0.0.1]) by quasar.websiteactive.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Christian.Groves@nteczone.com>) id 1PDSxc-0002bZ-1x for eman@ietf.org; Wed, 03 Nov 2010 13:20:24 +1100
Message-ID: <4CD0C730.4030603@nteczone.com>
Date: Wed, 03 Nov 2010 13:21:36 +1100
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: eman@ietf.org
References: <C8EFF4A6.163CA%quittek@neclab.eu> <4CCE3065.6050705@nteczone.com> <E9B25823FA871E4AA9EDA7B163E5D8A903443ECA@XMB-RCD-106.cisco.com>
In-Reply-To: <E9B25823FA871E4AA9EDA7B163E5D8A903443ECA@XMB-RCD-106.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - quasar.websiteactive.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: Re: [eman] Entity identification method
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the creation of an Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Nov 2010 02:20:24 -0000

Hello Mouli,

Please see my comments below.

Regards, Christian

On 2/11/2010 5:37 PM, Mouli Chandramouli (moulchan) wrote:
> Hi Christian,
>
> Presently, the power measurement technology and instrumentation (power
> sensors) exist for physical entities.
> While the MIBs in circulation attempt to provide power consumption by
> physical components, cost of measurement sensors should be taken into
> account.
[CNG] I certainly agree cost of measurement is an issue. As the IETF are 
producing a new MIB future flexibility/extensibility (and backward 
compatibility) should also be considered. It may be possible to add 
support for logical/virtual entities in a way that does not burden 
vendors who don't want to implement this feature. Considering this issue 
may save costs in the future.
> Clearly, the power cost of software features or virtual machines
> (logical entities) should be determined, the technology/methodology is
> work in progress as given in the research paper.
>
> Power measurement of virtual machines is still at research stage.
>
> http://www.sigmetrics.org/sigmetrics2010/greenmetrics/greenMetrics10.Kri
> shnan.pdf
[CNG] Thanks for the link.
>
> On another point, it has been widely reported in several bench marking
> studies that most of the power consumption is due to physical entities.
> Clearly, this notion should be extended to logical entities as you have
> pointed out.
>
> Thanks
> Mouli
>
>
> -----Original Message-----
> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of
> Christian Groves
> Sent: Monday, November 01, 2010 8:44 AM
> To: eman@ietf.org
> Subject: Re: [eman] Entity identification method
>
> Hello Juergen,
>
> I think distinguishing the two cases is the correct way to go.
>
> I agree that reporting energy consumption for logical entities is a
> challenge and not straight forward. I guess there are a number of ways
> to look at this problem and how address the problem depends on the
> ambition level.
>
> As you rightly mention where there is partial use of a physical resource
>
> by a logical entity it is very difficult to have an exact figure.
> However I think the "grain size" of the measurement comes into play. For
>
> example if we have a large gateway implementing several virtual gateways
>
> if we take an overall measurement then we have the problem determining a
>
> figure. If the however the virtual gateways were each assigned a
> physical rack and the measurements were taken at a rack level then we
> have a more precise estimate of contribution of each virtual gateway to
> the overall picture.
>
> For me logical entities ultimately will be realised by physical
> hardware. The key is understanding the relationship between these
> entities. Thus I think virtualization can in some way be supported by
> allowing energy consumption reports for physical entities to indicate
> if/what logical entities they relate to. As they say information is
> power (pardon the pun :-) ).
>
> Regards, Christian
>
> On 29/10/2010 12:48 PM, Juergen Quittek wrote:
>> Hi Christian,
>>
>> Thank you for this interesting comment.
>>
>> It looks like we have to distinguish two cases: power state monitoring
> and
>> energy consumption monitoring.
>>
>> For a logical entity and a virtual machine it may be well possible to
> report
>> on their power state. However, reporting their energy consumption
> seems to
>> be a tough challenge at least if be base it on real measurements.
>>
>> It is well feasible to measure energy consumption of physical
> entities, but
>> if you have a logical entity that consumes only partial resources of a
>> physical entity, then precise measurement of the energy consumption
> will be
>> hardly possible. Estimations may be possible based on a model of the
> logical
>> entity, but I don't know how good such models can be.
>>
>> Thanks,
>>
>>       Juergen
>>
>>
>> On 29.10.10 03:25  "Christian Groves"<Christian.Groves@nteczone.com>
> wrote:
>>> Hello
>>>
>>> I've just started to digest the various drafts of the eman wg and I
> see
>>> the comment below on logical entities. It's not clear to me how/if
>>> network virtualization is intended on being handled in the eman work.
>>>
>>> In networks there's now a trend towards network virtualization and
> cloud
>>> computing with the different "X" as a service models (i.e. Amazon EC2
>>> "platform as a service" running different server instances). Even in
>>> today's networks we have physical gateways that are virtualized into
>>> different logical gateways. For example: H.248/Megaco virtual MG
> (VMG)
>>> concept.
>>>
>>> I think it would be advantageous to be able to assess the energy
>>> consumption of the VMGs or instances (which are logical entities)
>>> independent of the physical gateway so that a customers energy use
> may
>>> be recording. Will this sort of functionality be allowed?
>>>
>>> Regards, Christian
>>>
>>> On 29/10/2010 1:22 AM, Juergen Quittek wrote:
>>>> Hi Chris,
>>>>
>>>> I think it may become very difficult if we want to assess energy
> consumption
>>>> of logical entities. It seems to be reasonable and practical to
> limit energy
>>>> consumption measurements to physical entities. The ENERGY AWARE MIB
> module
>>>> (draft-parello-eman-energy-aware-mib) and the POWER MIB
>>>> (draft-quittek-power-mib-02) went this way.
>>>>
>>>> Just using entPhysicalIndex solves some of the problem you
> mentioned.
>>>> Particularly, you don't need a mapping table to entities if you
> restrict
>>>> Yourself to entPhysicalIndex.
>>>>
>>>> Thanks,
>>>>
>>>>        Juergen
>>>>
>>>> On 28.10.10 13:34  "Chris Verges"<chrisv@cyberswitching.com>
> wrote:
>>>>> Hi Jurgen and all,
>>>>>
>>>>> The more I've been thinking about these scenarios, the more
> something
>>>>> doesn't seem quite right.  I'll try to explain my thought process
> behind
>>>>> this and see if my concerns/confusions get captured.
>>>>>
>>>>> ENTITY-MIB provides enumerated lists of physical and logical
> entities on
>>>>> the system.  The indices in both lists are maintained separately,
> so
>>>>> there is not a single, unique identifier provided.  Because of
> this, the
>>>>> MIBs being discussed by the EMAN WG must only reference to one type
>>>>> (physical or logical) and are limited to that without additional
> work.
>>>>> At some point in my mind, I'm asking myself the question, "What's
> the
>>>>> point of linking to ENTITY-MIB?"
>>>>>
>>>>> More on that question in later scenarios below ...
>>>>>
>>>>> One possibility would be to create a separate mapping table that
> gives a
>>>>> guaranteed unique index based on all entities, regardless of type.
> The
>>>>> physical vs. logical extensions would then become sparse tables
> that
>>>>> augment this.  For example:
>>>>>
>>>>>      ENTITY-MIB : entityGeneral.entGeneralTable.entGeneralEntry
>>>>>      +-----------------+-----------------+-----+
>>>>>      | entGeneralIndex | entGeneralDescr | ... |
>>>>>      +-----------------+-----------------+-----+
>>>>>      |        1        | PDU Chassis     |     |
>>>>>      +-----------------+-----------------+-----+
>>>>>      |        2        | Meter #1        |     |
>>>>>      +-----------------+-----------------+-----+
>>>>>      |        3        | Meter #2        |     |
>>>>>      +-----------------+-----------------+-----+
>>>>>      |        4        | Remote Meter #1 |     |
>>>>>      +-----------------+-----------------+-----+
>>>>>
>>>>>      ENTITY-MIB : entityPhysical.entPhysicalTable.entPhysicalEntry
>>>>>      +-----------------+-----------------+-----+
>>>>>      | entGeneralIndex | entVendorType   | ... |
>>>>>      +-----------------+-----------------+-----+
>>>>>      |        1        | enterprises.foo |     |
>>>>>      +-----------------+-----------------+-----+
>>>>>      |        2        | enterprises.foo |     |
>>>>>      +-----------------+-----------------+-----+
>>>>>      |        3        | enterprises.foo |     |
>>>>>      +-----------------+-----------------+-----+
>>>>>
>>>>>      ENTITY-MIB : entityLogical.entLogicalTable.entLogicalEntry
>>>>>      +-----------------+----------------------+-----+
>>>>>      | entGeneralIndex | entLogicalCommunity  | ... |
>>>>>      +-----------------+----------------------+-----+
>>>>>      |        4        | remote-power-group-1 |     |
>>>>>      +-----------------+----------------------+-----+
>>>>>
>>>>> It seems like this 'entGeneralIndex' concept is what's missing from
> the
>>>>> current ENTITY-MIB, and is causing problems when thinking about
> local
>>>>> and remote power data being reported by the same agent.
>>>>>
>>>>> Another possibility would be to choose one -- entLogicalIndex, most
>>>>> likely -- and require that anyone who wants to implement the EMAN
> WG
>>>>> MIBs to always create an entLogicalEntry for the power data.  In
> this
>>>>> context, the entLogicalTable fills the role of entGeneralTable as
>>>>> described above.  For all entPhysicalTable entries, there would
> need to
>>>>> be a corresponding entry in entLogicalTable with a 1:1 mapping
> between
>>>>> them.  For all remote entries, there would be a unique entry in
>>>>> entLogicalTable.  Of course, this would add some additional
> overhead on
>>>>> the part of the implementer, but isn't too overburdening.
>>>>>
>>>>> A third possibility is that ENTITY-MIB just doesn't do what we need
> in
>>>>> its present form and we need to think about enumerating power
> sensors
>>>>> separately from other components/sensors on the system.  It seems
> like
>>>>> entPhysicalTable gives a good starting template for a new
>>>>> 'POWER-ENTITY-MIB', but can be extended to include support for
> remote
>>>>> agents.  The difference would be a clean break from the legacy
>>>>> ENTITY-MIB structure.
>>>>>
>>>>> And with that, I look forward to others' feedback and ideas on
> solving
>>>>> this problem!
>>>>>
>>>>> Thanks,
>>>>> Chris
>>>>>
>>>>> -----Original Message-----
>>>>> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On
> Behalf Of
>>>>> Chris Verges
>>>>> Sent: Tuesday, October 26, 2010 9:26 PM
>>>>> To: Juergen Quittek; Benoit Claise; eman mailing list
>>>>> Subject: Re: [eman] Entity identification method (was: EMAN
> chartered
>>>>> itemsversus drafts)
>>>>>
>>>>> Hi Juergen and all,
>>>>>
>>>>> Agreed that a common ID method makes sense, and ENTITY-MIB seems to
> be a
>>>>> good choice.  In case (c) from your list, wouldn't the remote agent
>>>>> condition be handled by ENTITY-MIB supporting a logical entity that
> is
>>>>> the remote agent iself?  Since the logical entity is in the
> ENTITY-MIB
>>>>> table, it would be given a unique ID mixed amongst the other
> logical and
>>>>> physical entities.
>>>>>
>>>>> At that point, should all of the MIBs being discussed in the EMAN
> WG be
>>>>> sparse table augmentations of ENTITY-MIB?
>>>>>
>>>>> Thanks,
>>>>> Chris
>>>>>
>>>>> -----Original Message-----
>>>>> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On
> Behalf Of
>>>>> Juergen Quittek
>>>>> Sent: Tuesday, October 26, 2010 6:01 AM
>>>>> To: Benoit Claise; eman mailing list
>>>>> Subject: [eman] Entity identification method (was: EMAN chartered
> items
>>>>> versus drafts)
>>>>>
>>>>> Hi Benoit and all,
>>>>>
>>>>> I agree that we should find a common identification method for
> entities
>>>>> used by all MIB modules. This does not apply to the POWER MIB only,
> but
>>>>> to all MIB modules in the eman WG.
>>>>> The modules will use an entity ID as index for their tables.
>>>>> Which entity is identified by the index can be resolved by other
> MIB
>>>>> modules, such as the POWER AWARE MIB module
>>>>> (draft-parello-eman-energy-aware-mib) or the ENTITY MIB module (RFC
>>>>> 4133).
>>>>>
>>>>> I see three basic scenarios for the entity identification:
>>>>>
>>>>>      a) a device just reports on its own power state and energy
>>>>>         consumption and it reports on its own as a single unit.
>>>>>
>>>>>         Then we have a single index only stating "it's me".
>>>>>         Such a device usually does not need further identification
>>>>>         of itself, because typically there are sufficient other
>>>>>         MIB modules for this purpose running in the same SNMP
> engine,
>>>>>         that provide information about the device's IP address,
>>>>>         manufacturer, operating system, etc. In such a case a
>>>>>         'trivial' index, such as '0' should be used in order to
>>>>>         keep it simple in this most simple case.
>>>>>
>>>>>      b) a device reports on its own but not just as a single unit
>>>>>         but it reports power states and energy consumption for its
>>>>>         individual components, for example it may report separately
>>>>>         on contained hard drives, line cards, back planes,
>>>>>         processor boards, etc.
>>>>>
>>>>>         In such a case, identification of these components as
>>>>>         individual entities would be required. The ENTITY MIB
>>>>>         module was designed for this purpose and would be a good
>>>>>         choice here. Also the POWER AWARE MIB module would be
>>>>>         useful in this case.
>>>>>
>>>>>      c) a device reports on energy consumption of other, remote
>>>>>         devices. Then remote devices (and potentially also their
>>>>>         contained components need to be identified. For
>>>>>         identifying remote components there is the POWER AWARE MIB
>>>>>         module that has been designed for this purpose. As far as
>>>>>         I understand, the ENTITY MIB module is not applicable to
>>>>>         remote devices.
>>>>>
>>>>> In summary,
>>>>>      - if you need to report on remote entities (case c)),
>>>>>        you need the POWER AWARE MIB module,
>>>>>      - if you report only on entities locally contained
>>>>>        in the reporting device (case b)), you can use
>>>>>        the POWER AWARE MIB or the ENTITY MIB
>>>>>      - if you report just on your own as a single device
>>>>>        (case a)), identification is trivial
>>>>>
>>>>> Hence, my recommendation (stated for POWER-STATE MIB and ENERGY MIB
> in
>>>>> draft-quittek-power-mib-02) would be:
>>>>>
>>>>> If there is an implementation of the POWER AWARE MIB module
> instantiated
>>>>> in the local SNMP engine, then you SHOULD (or MUST?) use it for
> indexing
>>>>> (pmIndex).
>>>>> If this is not the case but there is an ENTITY MIB instance
> available,
>>>>> then you SHOULD use this one (entPhysicalIndex).
>>>>> If neither of this MIB modules is available you should use index 0
> only
>>>>> and be limited to report on the local device as a single entity
> only.
>>>>> That's just my view. Certainly, there are more ways of entity
>>>>> identification. I look forward to discussing them.
>>>>>
>>>>> Thanks,
>>>>>
>>>>>        Juergen
>>>>>
>>>>>
>>>>> On 26.10.10 11:44  "Benoit Claise"<bclaise@cisco.com>    wrote:
>>>>>
>>>>>> Hi Juergen,
>>>>>>
>>>>>> Thanks for the clarification.
>>>>>>
>>>>>> Something key is to agree on the Power Monitor index for all MIB
>>>>>> modules, which IMHO should be part of the Energy-aware Networks
> and
>>>>>> Devices MIB module, but reuse in the other MIB modules.
>>>>>>
>>>>>> Regards, Benoit.
>>>>>>> Hi Benoit,
>>>>>>>
>>>>>>> Thanks for checking all drafts.
>>>>>>>
>>>>>>> I don't think that draft-quittek-power-mib-02 makes significant
>>>>>>> contributions to the Energy-aware Networks and Devices MIB.
>>>>>>> It just covers the Power and Energy Monitoring MIB and the
> Battery
>>>>> MIB.
>>>>>>> Thanks,
>>>>>>>         Juergen
>>>>>>>
>>>>>>>
>>>>>>> On 26.10.10 08:22  "Benoit Claise"<bclaise@cisco.com>     wrote:
>>>>>>>
>>>>>>>> Dear all,
>>>>>>>>
>>>>>>>> I went through the exercise of mapping the existing six
> chartered
>>>>>>>> items with the existing draft content.
>>>>>>>>
>>>>>>>> _Energy Management Requirements_
>>>>>>>>
> http://tools.ietf.org/html/draft-quittek-power-monitoring-requiremen
>>>>>>>> ts-02
> https://datatracker.ietf.org/doc/draft-norwin-energy-consider/
>>>>>>>> _
>>>>>>>> Energy Management Framework_
>>>>>>>> http://tools.ietf.org/html/draft-claise-power-management-arch-02
>>>>>>>>
>>>>>>>> _Energy-aware Networks and Devices MIB_
>>>>>>>>
> http://tools.ietf.org/html/draft-parello-eman-energy-aware-mib-00
>>>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>>>>>>>>
>>>>>>>> _Power and Energy Monitoring MIB_
>>>>>>>> http://tools.ietf.org/html/draft-claise-energy-monitoring-mib-06
>>>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>>>>>>>>
>>>>>>>> _Battery MIB_
>>>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>>>>>>>>
>>>>>>>> _Energy Management Applicability_
>>>>>>>>
> http://datatracker.ietf.org/doc/draft-tychon-eman-applicability-stat
>>>>>>>> ement/
>>>>>>>>
>>>>>>>> Please let me know if I made any mistakes or if I missed any
> draft?
>>>>>>>> Regards, Benoit.
>>>>>>>> _______________________________________________
>>>>>>>> eman mailing list
>>>>>>>> eman@ietf.org
>>>>>>>> https://www.ietf.org/mailman/listinfo/eman
>>>>> _______________________________________________
>>>>> eman mailing list
>>>>> eman@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/eman
>>>> _______________________________________________
>>>> eman mailing list
>>>> eman@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/eman
>>> _______________________________________________
>>> eman mailing list
>>> eman@ietf.org
>>> https://www.ietf.org/mailman/listinfo/eman
>>
>> _______________________________________________
>> eman mailing list
>> eman@ietf.org
>> https://www.ietf.org/mailman/listinfo/eman
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman
>

From Christian.Groves@nteczone.com  Tue Nov  2 19:31:59 2010
Return-Path: <Christian.Groves@nteczone.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8C5E63A6A0A for <eman@core3.amsl.com>; Tue,  2 Nov 2010 19:31:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.166
X-Spam-Level: 
X-Spam-Status: No, score=-2.166 tagged_above=-999 required=5 tests=[AWL=0.433,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5gcs3Wn-rwbc for <eman@core3.amsl.com>; Tue,  2 Nov 2010 19:31:58 -0700 (PDT)
Received: from quasar.websiteactive.com (quasar.websiteactive.com [202.191.61.215]) by core3.amsl.com (Postfix) with ESMTP id 457B83A6A08 for <eman@ietf.org>; Tue,  2 Nov 2010 19:31:58 -0700 (PDT)
Received: from ppp118-209-52-37.lns20.mel4.internode.on.net ([118.209.52.37] helo=[127.0.0.1]) by quasar.websiteactive.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Christian.Groves@nteczone.com>) id 1PDT8t-0003h9-0k for eman@ietf.org; Wed, 03 Nov 2010 13:32:03 +1100
Message-ID: <4CD0C9EB.7080103@nteczone.com>
Date: Wed, 03 Nov 2010 13:33:15 +1100
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: eman@ietf.org
References: <AANLkTinHam40dHw5xDDeQrUhERHtW3XbaQmu4BPSRV+C@mail.gmail.com>
In-Reply-To: <AANLkTinHam40dHw5xDDeQrUhERHtW3XbaQmu4BPSRV+C@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - quasar.websiteactive.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Subject: Re: [eman] Introduction; past comments
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the creation of an Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Nov 2010 02:31:59 -0000

Hello Bruce,

Thanks for the introduction.

Your comment on other SDOs and the charter actually made me have a good 
read of the EMAN charter. It mentions a list of SDOs whose work may be 
applicable: IEC, ANSI, DTMF etc. However it doesn't mention ITU-T Study 
Group 5"electromagnetic compatibility and electromagnetic effects" 
<http://www.itu.int/net/ITU-T/lists/questions.aspx?Group=5&Period=14>. 
This group was formed from two study groups, one looking at 
electro-magnetic issues and one looking at indoor and outdoor plant. My 
understanding is that operators are well represented in this group. It 
may be beneficial for both SG5 and the EMAN WG to exchange information.

Regards, Christian

On 2/11/2010 5:49 PM, Bruce Nordman wrote:
> Greetings--
>
>    As incoming co-chair of eman, I look forward to meeting many of you
> next week in Beijing.  I bring an energy-centric background to the process,
> which I believe will be a useful complement to more usual IETF participants.
> I have been on the edge of several IETF meetings, but this will be my first
> actual attendance.  You can learn more about my interests from my web page
> (below).
>    For our working group, I have no interest in expanding our charter.
> I am however
> interested in follow-on activities that may make sense within the IETF
> as well as in
> other standards organizations, for how we network the physical world
> (I call this
> "building networks" for devices that use energy or that influence it).
>   I look forward
> to discussions on this outside our WG meeting.
>    In the interest of transparency and completeness, below are some comments on
> several of the Internet Drafts as they were a few weeks ago, before
> recent revisions.
> These are offered as an individual participant, not in my role as
> co-chair.  I am not
> seeking to start email discussions with these comments.
>    Pleasant travels,
>
> --Bruce
>

From chrisv@cyberswitching.com  Tue Nov  2 20:30:37 2010
Return-Path: <chrisv@cyberswitching.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 399483A68A2 for <eman@core3.amsl.com>; Tue,  2 Nov 2010 20:30:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hsGMjOtSVEvt for <eman@core3.amsl.com>; Tue,  2 Nov 2010 20:30:34 -0700 (PDT)
Received: from p01c12o145.mxlogic.net (p01c12o145.mxlogic.net [208.65.145.68]) by core3.amsl.com (Postfix) with ESMTP id D86573A682A for <eman@ietf.org>; Tue,  2 Nov 2010 20:30:33 -0700 (PDT)
Received: from unknown [207.47.28.34] (EHLO mail03.cyberswitching.local) by p01c12o145.mxlogic.net(mxl_mta-6.7.0-2) with ESMTP id e57d0dc4.0.55689.00-359.119806.p01c12o145.mxlogic.net (envelope-from <chrisv@cyberswitching.com>);  Tue, 02 Nov 2010 21:30:40 -0600 (MDT)
X-MXL-Hash: 4cd0d7604a068a65-fd668a9160aa4c1a2f118f2056ccbef38c248e3c
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 2 Nov 2010 20:30:23 -0700
Message-ID: <68FBE0F3CE97264395875AC1C468F22C5148AE@mail03.cyberswitching.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [eman] Entity identification method
Thread-Index: Act6/JJHidCdr+1FR0GNWWs5STgMAAACERug
References: <C8EFF4A6.163CA%quittek@neclab.eu> <4CCE3065.6050705@nteczone.com> <68FBE0F3CE97264395875AC1C468F22C514765@mail03.cyberswitching.local> <4CD0C560.7080907@nteczone.com>
From: "Chris Verges" <chrisv@cyberswitching.com>
To: "Christian Groves" <Christian.Groves@nteczone.com>
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010110201)]
X-MAIL-FROM: <chrisv@cyberswitching.com>
X-SOURCE-IP: [207.47.28.34]
X-AnalysisOut: [v=1.0 c=1 a=aPxnrr7mnCkA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel]
X-AnalysisOut: [0A:10 a=1Eql4bHns2NoxN2V9ejGkg==:17 a=r3s3_62XAAAA:8 a=48v]
X-AnalysisOut: [gC7mUAAAA:8 a=wzgqfsuUAAAA:8 a=AUd_NHdVAAAA:8 a=K8_Pq_RQRO]
X-AnalysisOut: [VvOXdiOt4A:9 a=apTXq80P-IfG8Fblk0kA:7 a=cSK0aj0OpNowBUL7Q4]
X-AnalysisOut: [0NVYqUYyAA:4 a=CjuIK1q_8ugA:10 a=3wXEbymkWtoA:10 a=lZB815d]
X-AnalysisOut: [zVvQA:10 a=yvfu_RGVus0A:10 a=JfD0Fch1gWkA:10 a=-dfsXmy6FaQ]
X-AnalysisOut: [-eXHX:21 a=f0W3jCH8XrW2lpPx:21]
Cc: eman@ietf.org
Subject: Re: [eman] Entity identification method
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the creation of an Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Nov 2010 03:30:37 -0000

Hi Christian et al.,

How about the following two use cases to augment the existing
power-allocation-per-virtual-machine scenario?

	1. "Grouped" outlets on a smart PDU

	2. Tenant submetering on a smart meter

In the first scenario, several smart PDUs allow the user to create a
user-defined grouping that consists of several outlets.  Physical
outlets 1 and 7, for example, could be grouped together as logical
entity "server01".  This mapping could be created using the existing
ENTITY-MIB architecture.  The power data for both the physical and
logical entities are useful to facilities and IT managers to understand
power flow and usage.

In the second scenario, a smart meter provides submetering for a
commercial rental building.  Such buildings often occur turnover in
tenants.  A submeter that meters each circuit in the building, for
example, could maintain that data in both granular and aggregate form.
When a tenant moves in, the facilities manager can create a new logical
entity for that tenant and map the physical circuit entries to the
tenant's logical entity.  This enables both real-time power usage and
management on an individual circuit basis (useful for troubleshooting
facilities problems) as well as on a customized aggregate basis (useful
for the bean counters who have to allocate costs).

Here's an interesting question as far as implementation is concerned ...
why not implement pmPhysicalMap and pmLogicalMap tables (like
entLPMappingTable) to map the pmIndex entity to the appropriate physical
or logical entity (1:1 only?)

Chris


-----Original Message-----
From: Christian Groves [mailto:Christian.Groves@nteczone.com]=20
Sent: Tuesday, November 02, 2010 7:14 PM
To: Chris Verges
Cc: eman@ietf.org
Subject: Re: [eman] Entity identification method

Hello Chris,

I don't have any concrete suggestions for implementing virtual entity
energy usage support. I'm still at the stage of trying to see what the
requirements and framework is for the work. There seems to be a focus on
the MIBs themselves, when without good requirements its hard to see what
needs they are meeting. The work of the eman WG could address IP type
servers only or the MIBs could also be used in other telecommunication
equipment i.e. those used in outside plant. I'm encouraged to see
Bruce's email on topics for discussion as think its in important to get
consensus/understanding on these before the MIBs are developed.

Please see my comment below marked [CNG].

Regards, Christian

On 1/11/2010 11:39 PM, Chris Verges wrote:
>
> Hi Christian,
>
> Are you looking to allocate actual energy usage by a virtual entity,=20
> like the amount of energy used by a virtual machine running on a=20
> shared server? Certainly an interesting problem ... gives a lot of=20
> room for innovation for different vendors to find solutions.
>
[CNG] I agree its an interesting problem. In some instances it may be
possible to allocate the actual energy however in many cases it would be
very difficult/impossible. In these more difficult cases it may be
possible to simply report the identities of the virtual/logical entities
that are included in the physical measurement.
>
> From a MIB standpoint, it seems like the requirement is to have a=20
> flexible power-related MIB that can either map to physical or logical=20
> entities. One question is, "where do you want those entities
enumerated?"
>
> Are virtual entities that need to be mapped to power usage normally=20
> enumerated in ENTITY-MIB in the "logical" table?
>
> If so, perhaps something like this would fit the bill:
>
> POWER-ENTITY-MIB:
>
> pwrEntityTable
>
> pwrEntityEntry
>
> pwrEntityIndex
>
> pwrEntityName
>
> pwrEntityType
>
> pwrEntityParent
>
> pwrEntityPhysical
>
> pwrEntityLogical
>
> The pwrEntity[Physical|Logical] objects would point to the appropriate

> index in ENTITY-MIB.
>
> However, if the virtual entities are not enumerated in ENTITY-MIB, the

> pwrEntityLogical column is probably overkill. The virtual entities can

> be enumerated in pwrEntityTable and linked to the Physical meter using

> the pwrEntityParent column, much like how ENTITY-MIB currently manages

> references between parent and component entities. It would just=20
> involve a new pwrEntityType being added for "virtual" or something=20
> similar.
>
> So what's the typical use case as these virtual entities relate to=20
> ENTITY-MIB?
>
[CNG] I'm not sure the typical case. Either of the approaches above
could be sufficient but I think it depends on what people agree on with
respect to virtual entities and how the data collected on them would be
used.
>
> Chris
>
> -----Original Message-----
> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf=20
> Of Christian Groves
> Sent: Sunday, October 31, 2010 8:14 PM
> To: eman@ietf.org
> Subject: Re: [eman] Entity identification method
>
> Hello Juergen,
>
> I think distinguishing the two cases is the correct way to go.
>
> I agree that reporting energy consumption for logical entities is a=20
> challenge and not straight forward. I guess there are a number of ways

> to look at this problem and how address the problem depends on the=20
> ambition level.
>
> As you rightly mention where there is partial use of a physical=20
> resource by a logical entity it is very difficult to have an exact=20
> figure.
>
> However I think the "grain size" of the measurement comes into play.=20
> For example if we have a large gateway implementing several virtual=20
> gateways if we take an overall measurement then we have the problem=20
> determining a figure. If the however the virtual gateways were each=20
> assigned a physical rack and the measurements were taken at a rack=20
> level then we have a more precise estimate of contribution of each=20
> virtual gateway to the overall picture.
>
> For me logical entities ultimately will be realised by physical=20
> hardware. The key is understanding the relationship between these=20
> entities. Thus I think virtualization can in some way be supported by=20
> allowing energy consumption reports for physical entities to indicate=20
> if/what logical entities they relate to. As they say information is=20
> power (pardon the pun :-) ).
>
> Regards, Christian
>
> On 29/10/2010 12:48 PM, Juergen Quittek wrote:
>
> > Hi Christian,
>
> >
>
> > Thank you for this interesting comment.
>
> >
>
> > It looks like we have to distinguish two cases: power state=20
> > monitoring
>
> > and energy consumption monitoring.
>
> >
>
> > For a logical entity and a virtual machine it may be well possible=20
> > to
>
> > report on their power state. However, reporting their energy
>
> > consumption seems to be a tough challenge at least if be base it on
> real measurements.
>
> >
>
> > It is well feasible to measure energy consumption of physical
>
> > entities, but if you have a logical entity that consumes only=20
> > partial
>
> > resources of a physical entity, then precise measurement of the=20
> > energy
>
> > consumption will be hardly possible. Estimations may be possible=20
> > based
>
> > on a model of the logical entity, but I don't know how good such
> models can be.
>
> >
>
> > Thanks,
>
> >
>
> > Juergen
>
> >
>
> >
>
> > On 29.10.10 03:25 "Christian Groves"<Christian.Groves@nteczone.com
> <mailto:Christian.Groves@nteczone.com>> wrote:
>
> >
>
> >> Hello
>
> >>
>
> >> I've just started to digest the various drafts of the eman wg and I
>
> >> see the comment below on logical entities. It's not clear to me
>
> >> how/if network virtualization is intended on being handled in the
> eman work.
>
> >>
>
> >> In networks there's now a trend towards network virtualization and
>
> >> cloud computing with the different "X" as a service models (i.e.
>
> >> Amazon EC2 "platform as a service" running different server
>
> >> instances). Even in today's networks we have physical gateways that
>
> >> are virtualized into different logical gateways. For example:
>
> >> H.248/Megaco virtual MG (VMG) concept.
>
> >>
>
> >> I think it would be advantageous to be able to assess the energy
>
> >> consumption of the VMGs or instances (which are logical entities)
>
> >> independent of the physical gateway so that a customers energy use
>
> >> may be recording. Will this sort of functionality be allowed?
>
> >>
>
> >> Regards, Christian
>
> >>
>
> >> On 29/10/2010 1:22 AM, Juergen Quittek wrote:
>
> >>> Hi Chris,
>
> >>>
>
> >>> I think it may become very difficult if we want to assess energy
>
> >>> consumption of logical entities. It seems to be reasonable and
>
> >>> practical to limit energy consumption measurements to physical
>
> >>> entities. The ENERGY AWARE MIB module
>
> >>> (draft-parello-eman-energy-aware-mib) and the POWER MIB
>
> >>> (draft-quittek-power-mib-02) went this way.
>
> >>>
>
> >>> Just using entPhysicalIndex solves some of the problem you
mentioned.
>
> >>> Particularly, you don't need a mapping table to entities if you
>
> >>> restrict Yourself to entPhysicalIndex.
>
> >>>
>
> >>> Thanks,
>
> >>>
>
> >>> Juergen
>
> >>>
>
> >>> On 28.10.10 13:34 "Chris Verges"<chrisv@cyberswitching.com
> <mailto:chrisv@cyberswitching.com>> wrote:
>
> >>>
>
> >>>> Hi Jurgen and all,
>
> >>>>
>
> >>>> The more I've been thinking about these scenarios, the more
>
> >>>> something doesn't seem quite right. I'll try to explain my=20
> >>>> thought
>
> >>>> process behind this and see if my concerns/confusions get
captured.
>
> >>>>
>
> >>>> ENTITY-MIB provides enumerated lists of physical and logical
>
> >>>> entities on the system. The indices in both lists are maintained
>
> >>>> separately, so there is not a single, unique identifier provided.
>
> >>>> Because of this, the MIBs being discussed by the EMAN WG must=20
> >>>> only
>
> >>>> reference to one type (physical or logical) and are limited to
> that without additional work.
>
> >>>> At some point in my mind, I'm asking myself the question, "What's
>
> >>>> the point of linking to ENTITY-MIB?"
>
> >>>>
>
> >>>> More on that question in later scenarios below ...
>
> >>>>
>
> >>>> One possibility would be to create a separate mapping table that
>
> >>>> gives a guaranteed unique index based on all entities, regardless
>
> >>>> of type. The physical vs. logical extensions would then become
>
> >>>> sparse tables that augment this. For example:
>
> >>>>
>
> >>>> ENTITY-MIB : entityGeneral.entGeneralTable.entGeneralEntry
>
> >>>> +-----------------+-----------------+-----+
>
> >>>> | entGeneralIndex | entGeneralDescr | ... |
>
> >>>> +-----------------+-----------------+-----+
>
> >>>> | 1 | PDU Chassis | |
>
> >>>> +-----------------+-----------------+-----+
>
> >>>> | 2 | Meter #1 | |
>
> >>>> +-----------------+-----------------+-----+
>
> >>>> | 3 | Meter #2 | |
>
> >>>> +-----------------+-----------------+-----+
>
> >>>> | 4 | Remote Meter #1 | |
>
> >>>> +-----------------+-----------------+-----+
>
> >>>>
>
> >>>> ENTITY-MIB : entityPhysical.entPhysicalTable.entPhysicalEntry
>
> >>>> +-----------------+-----------------+-----+
>
> >>>> | entGeneralIndex | entVendorType | ... |
>
> >>>> +-----------------+-----------------+-----+
>
> >>>> | 1 | enterprises.foo | |
>
> >>>> +-----------------+-----------------+-----+
>
> >>>> | 2 | enterprises.foo | |
>
> >>>> +-----------------+-----------------+-----+
>
> >>>> | 3 | enterprises.foo | |
>
> >>>> +-----------------+-----------------+-----+
>
> >>>>
>
> >>>> ENTITY-MIB : entityLogical.entLogicalTable.entLogicalEntry
>
> >>>> +-----------------+----------------------+-----+
>
> >>>> | entGeneralIndex | entLogicalCommunity | ... |
>
> >>>> +-----------------+----------------------+-----+
>
> >>>> | 4 | remote-power-group-1 | |
>
> >>>> +-----------------+----------------------+-----+
>
> >>>>
>
> >>>> It seems like this 'entGeneralIndex' concept is what's missing=20
> >>>> from
>
> >>>> the current ENTITY-MIB, and is causing problems when thinking=20
> >>>> about
>
> >>>> local and remote power data being reported by the same agent.
>
> >>>>
>
> >>>> Another possibility would be to choose one -- entLogicalIndex,=20
> >>>> most
>
> >>>> likely -- and require that anyone who wants to implement the EMAN
>
> >>>> WG MIBs to always create an entLogicalEntry for the power data.=20
> >>>> In
>
> >>>> this context, the entLogicalTable fills the role of=20
> >>>> entGeneralTable
>
> >>>> as described above. For all entPhysicalTable entries, there would
>
> >>>> need to be a corresponding entry in entLogicalTable with a 1:1
>
> >>>> mapping between them. For all remote entries, there would be a
>
> >>>> unique entry in entLogicalTable. Of course, this would add some
>
> >>>> additional overhead on the part of the implementer, but isn't too
> overburdening.
>
> >>>>
>
> >>>> A third possibility is that ENTITY-MIB just doesn't do what we=20
> >>>> need
>
> >>>> in its present form and we need to think about enumerating power
>
> >>>> sensors separately from other components/sensors on the system.=20
> >>>> It
>
> >>>> seems like entPhysicalTable gives a good starting template for a
>
> >>>> new 'POWER-ENTITY-MIB', but can be extended to include support=20
> >>>> for
>
> >>>> remote agents. The difference would be a clean break from the
>
> >>>> legacy ENTITY-MIB structure.
>
> >>>>
>
> >>>> And with that, I look forward to others' feedback and ideas on
>
> >>>> solving this problem!
>
> >>>>
>
> >>>> Thanks,
>
> >>>> Chris
>
> >>>>
>
> >>>> -----Original Message-----
>
> >>>> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On
>
> >>>> Behalf Of Chris Verges
>
> >>>> Sent: Tuesday, October 26, 2010 9:26 PM
>
> >>>> To: Juergen Quittek; Benoit Claise; eman mailing list
>
> >>>> Subject: Re: [eman] Entity identification method (was: EMAN
>
> >>>> chartered itemsversus drafts)
>
> >>>>
>
> >>>> Hi Juergen and all,
>
> >>>>
>
> >>>> Agreed that a common ID method makes sense, and ENTITY-MIB seems=20
> >>>> to
>
> >>>> be a good choice. In case (c) from your list, wouldn't the remote
>
> >>>> agent condition be handled by ENTITY-MIB supporting a logical
>
> >>>> entity that is the remote agent iself? Since the logical entity=20
> >>>> is
>
> >>>> in the ENTITY-MIB table, it would be given a unique ID mixed
>
> >>>> amongst the other logical and physical entities.
>
> >>>>
>
> >>>> At that point, should all of the MIBs being discussed in the EMAN
>
> >>>> WG be sparse table augmentations of ENTITY-MIB?
>
> >>>>
>
> >>>> Thanks,
>
> >>>> Chris
>
> >>>>
>
> >>>> -----Original Message-----
>
> >>>> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On
>
> >>>> Behalf Of Juergen Quittek
>
> >>>> Sent: Tuesday, October 26, 2010 6:01 AM
>
> >>>> To: Benoit Claise; eman mailing list
>
> >>>> Subject: [eman] Entity identification method (was: EMAN chartered
>
> >>>> items versus drafts)
>
> >>>>
>
> >>>> Hi Benoit and all,
>
> >>>>
>
> >>>> I agree that we should find a common identification method for
>
> >>>> entities used by all MIB modules. This does not apply to the=20
> >>>> POWER
>
> >>>> MIB only, but to all MIB modules in the eman WG.
>
> >>>> The modules will use an entity ID as index for their tables.
>
> >>>> Which entity is identified by the index can be resolved by other
>
> >>>> MIB modules, such as the POWER AWARE MIB module
>
> >>>> (draft-parello-eman-energy-aware-mib) or the ENTITY MIB module=20
> >>>> (RFC
>
> >>>> 4133).
>
> >>>>
>
> >>>> I see three basic scenarios for the entity identification:
>
> >>>>
>
> >>>> a) a device just reports on its own power state and energy
>
> >>>> consumption and it reports on its own as a single unit.
>
> >>>>
>
> >>>> Then we have a single index only stating "it's me".
>
> >>>> Such a device usually does not need further identification
>
> >>>> of itself, because typically there are sufficient other
>
> >>>> MIB modules for this purpose running in the same SNMP engine,
>
> >>>> that provide information about the device's IP address,
>
> >>>> manufacturer, operating system, etc. In such a case a
>
> >>>> 'trivial' index, such as '0' should be used in order to
>
> >>>> keep it simple in this most simple case.
>
> >>>>
>
> >>>> b) a device reports on its own but not just as a single unit
>
> >>>> but it reports power states and energy consumption for its
>
> >>>> individual components, for example it may report separately
>
> >>>> on contained hard drives, line cards, back planes,
>
> >>>> processor boards, etc.
>
> >>>>
>
> >>>> In such a case, identification of these components as
>
> >>>> individual entities would be required. The ENTITY MIB
>
> >>>> module was designed for this purpose and would be a good
>
> >>>> choice here. Also the POWER AWARE MIB module would be
>
> >>>> useful in this case.
>
> >>>>
>
> >>>> c) a device reports on energy consumption of other, remote
>
> >>>> devices. Then remote devices (and potentially also their
>
> >>>> contained components need to be identified. For
>
> >>>> identifying remote components there is the POWER AWARE MIB
>
> >>>> module that has been designed for this purpose. As far as
>
> >>>> I understand, the ENTITY MIB module is not applicable to
>
> >>>> remote devices.
>
> >>>>
>
> >>>> In summary,
>
> >>>> - if you need to report on remote entities (case c)),
>
> >>>> you need the POWER AWARE MIB module,
>
> >>>> - if you report only on entities locally contained
>
> >>>> in the reporting device (case b)), you can use
>
> >>>> the POWER AWARE MIB or the ENTITY MIB
>
> >>>> - if you report just on your own as a single device
>
> >>>> (case a)), identification is trivial
>
> >>>>
>
> >>>> Hence, my recommendation (stated for POWER-STATE MIB and ENERGY=20
> >>>> MIB
>
> >>>> in
>
> >>>> draft-quittek-power-mib-02) would be:
>
> >>>>
>
> >>>> If there is an implementation of the POWER AWARE MIB module
>
> >>>> instantiated in the local SNMP engine, then you SHOULD (or MUST?)
>
> >>>> use it for indexing (pmIndex).
>
> >>>> If this is not the case but there is an ENTITY MIB instance
>
> >>>> available, then you SHOULD use this one (entPhysicalIndex).
>
> >>>> If neither of this MIB modules is available you should use index=20
> >>>> 0
>
> >>>> only and be limited to report on the local device as a single
> entity only.
>
> >>>>
>
> >>>> That's just my view. Certainly, there are more ways of entity
>
> >>>> identification. I look forward to discussing them.
>
> >>>>
>
> >>>> Thanks,
>
> >>>>
>
> >>>> Juergen
>
> >>>>
>
> >>>>
>
> >>>> On 26.10.10 11:44 "Benoit Claise"<bclaise@cisco.com
> <mailto:bclaise@cisco.com>> wrote:
>
> >>>>
>
> >>>>> Hi Juergen,
>
> >>>>>
>
> >>>>> Thanks for the clarification.
>
> >>>>>
>
> >>>>> Something key is to agree on the Power Monitor index for all MIB
>
> >>>>> modules, which IMHO should be part of the Energy-aware Networks
>
> >>>>> and Devices MIB module, but reuse in the other MIB modules.
>
> >>>>>
>
> >>>>> Regards, Benoit.
>
> >>>>>> Hi Benoit,
>
> >>>>>>
>
> >>>>>> Thanks for checking all drafts.
>
> >>>>>>
>
> >>>>>> I don't think that draft-quittek-power-mib-02 makes significant
>
> >>>>>> contributions to the Energy-aware Networks and Devices MIB.
>
> >>>>>> It just covers the Power and Energy Monitoring MIB and the
>
> >>>>>> Battery
>
> >>>> MIB.
>
> >>>>>> Thanks,
>
> >>>>>> Juergen
>
> >>>>>>
>
> >>>>>>
>
> >>>>>> On 26.10.10 08:22 "Benoit Claise"<bclaise@cisco.com
> <mailto:bclaise@cisco.com>> wrote:
>
> >>>>>>
>
> >>>>>>> Dear all,
>
> >>>>>>>
>
> >>>>>>> I went through the exercise of mapping the existing six
>
> >>>>>>> chartered items with the existing draft content.
>
> >>>>>>>
>
> >>>>>>> _Energy Management Requirements_
>
> >>>>>>> http://tools.ietf.org/html/draft-quittek-power-monitoring-requ
> >>>>>>> ir
>
> >>>>>>> emen
>
> >>>>>>> ts-02
>
> >>>>>>> https://datatracker.ietf.org/doc/draft-norwin-energy-consider/
>
> >>>>>>> _
>
> >>>>>>> Energy Management Framework_
>
> >>>>>>> http://tools.ietf.org/html/draft-claise-power-management-arch-
> >>>>>>> 02
>
> >>>>>>>
>
> >>>>>>> _Energy-aware Networks and Devices MIB_
>
> >>>>>>> http://tools.ietf.org/html/draft-parello-eman-energy-aware-mib
> >>>>>>> -0
>
> >>>>>>> 0
>
> >>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>
> >>>>>>>
>
> >>>>>>> _Power and Energy Monitoring MIB_
>
> >>>>>>> http://tools.ietf.org/html/draft-claise-energy-monitoring-mib-
> >>>>>>> 06
>
> >>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>
> >>>>>>>
>
> >>>>>>> _Battery MIB_
>
> >>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>
> >>>>>>>
>
> >>>>>>> _Energy Management Applicability_
>
> >>>>>>> http://datatracker.ietf.org/doc/draft-tychon-eman-applicabilit
> >>>>>>> y-
>
> >>>>>>> stat
>
> >>>>>>> ement/
>
> >>>>>>>
>
> >>>>>>> Please let me know if I made any mistakes or if I missed any
> draft?
>
> >>>>>>>
>
> >>>>>>> Regards, Benoit.
>
> >>>>>>> _______________________________________________
>
> >>>>>>> eman mailing list
>
> >>>>>>> eman@ietf.org <mailto:eman@ietf.org>
>
> >>>>>>> https://www.ietf.org/mailman/listinfo/eman
>
> >>>> _______________________________________________
>
> >>>> eman mailing list
>
> >>>> eman@ietf.org <mailto:eman@ietf.org>
>
> >>>> https://www.ietf.org/mailman/listinfo/eman
>
> >>>
>
> >>> _______________________________________________
>
> >>> eman mailing list
>
> >>> eman@ietf.org <mailto:eman@ietf.org>
>
> >>> https://www.ietf.org/mailman/listinfo/eman
>
> >> _______________________________________________
>
> >> eman mailing list
>
> >> eman@ietf.org <mailto:eman@ietf.org>
>
> >> https://www.ietf.org/mailman/listinfo/eman
>
> >
>
> >
>
> > _______________________________________________
>
> > eman mailing list
>
> > eman@ietf.org <mailto:eman@ietf.org>
>
> > https://www.ietf.org/mailman/listinfo/eman
>
> _______________________________________________
>
> eman mailing list
>
> eman@ietf.org <mailto:eman@ietf.org>
>
> https://www.ietf.org/mailman/listinfo/eman
>

From bclaise@cisco.com  Wed Nov  3 08:57:12 2010
Return-Path: <bclaise@cisco.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 72EFA28C0E7 for <eman@core3.amsl.com>; Wed,  3 Nov 2010 08:57:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O1MzlEMK33Dv for <eman@core3.amsl.com>; Wed,  3 Nov 2010 08:57:03 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id 4FA763A69D4 for <eman@ietf.org>; Wed,  3 Nov 2010 08:57:02 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oA3FQOPH015743; Wed, 3 Nov 2010 16:26:25 +0100 (CET)
Received: from [10.55.43.53] (ams-bclaise-8714.cisco.com [10.55.43.53]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oA3FQNg2004576; Wed, 3 Nov 2010 16:26:24 +0100 (CET)
Message-ID: <4CD17F1F.3080505@cisco.com>
Date: Wed, 03 Nov 2010 23:26:23 +0800
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: Chris Verges <chrisv@cyberswitching.com>
References: <68FBE0F3CE97264395875AC1C468F22C5146E3@mail03.cyberswitching.local>
In-Reply-To: <68FBE0F3CE97264395875AC1C468F22C5146E3@mail03.cyberswitching.local>
Content-Type: multipart/alternative; boundary="------------040801000001020509000209"
Cc: eman@ietf.org
Subject: Re: [eman] EMAN MIB reviews and development process understanding
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the creation of an Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Nov 2010 15:57:13 -0000

This is a multi-part message in MIME format.
--------------040801000001020509000209
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Hi Chris,

Thanks for interest and comments.
Your phase approach is the right one in terms of priorities of issues.
Let's see how it matches the charter.

> Hi EMAN WG,
>
> I've been looking further into the ENERGY-AWARE-MIB, 
> POWER-MONITOR-MIB, and POWER-QUALITY-MIB from an implementer's 
> perspective.  Speaking personally and not on behalf of my employer, I 
> am extremely excited by the potential that these MIBs and the EMAN 
> group has on simplifying power management.  A common schema for data 
> reporting and control management will be awesome to finally get in place.
>
> That being said, the three MIBs currently being proposed are 
> definitely expansive.  Understanding their nuances and providing 
> adequate reviews for all possible scenarios (intelligent PDUs, PoE 
> network switches, PoE edge devices, etc.) seems to be challenges that 
> could impact release dates.  I'm also a little confused with some of 
> these MIBs, as they appear to have some overlapping scope/implied 
> meaning.  As an implementer, I am eagerly poised to start coding these 
> up, but want to ensure that they are going to meet my long-term needs 
> without significant changes.
>
> As an agenda suggestion for the next WG meeting, would it be 
> appropriate to discuss a phased release process?  In such a process, 
> the functionality added at each stage is separately contained, modular 
> for maintenance purposes, and adds upon each other in a focused 
> approach.  For example, by exposing Phase 1 sooner, then 
> enterprise-specific extensions can be worked on while the features in 
> Phases 2 and 3 are being developed further.
>
> To prompt discussion, here's one suggestion of how the work can be 
> broken down into phases:
>
> *Phase 1 -- Core Functionality*
>
> ·Setup a table that lists all power management entities (like 
> ENTITY-MIB, but for power entities, so perhaps POWER-ENTITY-MIB?)
>
> oPurpose of the table is focused on enumerating all entities that 
> support power management using a concise, flexible structure
>
> oObjects pass the test "Is this object necessary to describing all 
> power entities?"
>
> oCreate a unique index value (pwrEntityIndex)
>
> oLink pwrEntityIndex with entPhysicalIndex, if ENTITY-MIB is supported
>
> oDescribe the entity with pwrEntityName, pwrEntityDescr, 
> pwrEntityType, and pwrEntityParent
>
This matches this entry in the charter:

    3. Energy-aware Networks and Devices MIB document The EMAN WG will
    develop a MIB module for monitoring energy-aware networks and devices.
    The module will address devices identification, context information, and
    potential relationship between reporting devices, remote devices, and
    monitoring probes.


> *Phase 2 -- State Functionality*
>
> ·Setup a sparse table that supports state monitoring/control of power 
> management entities (POWER-STATE-MIB?)
>
> oPurpose of the table is focused on providing state management of 
> power entities
>
> oLink to pwrEntityIndex
>
> oDescribe the state with pwrStateLevel (off, on, tripped, shed, 
> reboot, ...?)
>
> oDescribe the relative state with pwrStateRelLevel (0-100%?) and/or 
> pwrStateAcpiLevel (0..12?)
>
This matches this entry in the charter:

    4. Power and Energy Monitoring MIB document The EMAN WG will develop a
    document defining managed objects for monitoring of power states and
    energy consumption/production. The monitoring of power states includes:
    retrieving power states, properties of power states, current power
    state, power state transitions, and power state statistics.
    The managed objects will provide means for reporting detailed properties
    of the actual energy rate (power) and of accumulated energy. Further, it
    will provide information on electrical power quality.

> *Phase 3 -- Meter Functionality*
>
> ·Setup a sparse table that supports power management entities that 
> report meter data (POWER-METER-MIB?)
>
> oPurpose of the table is focused on providing meter data for power 
> entities
>
> oLink to pwrEntityIndex
>
> oStructure TBD ... probably similar to POWER-MONITOR-MIB or 
> POWER-QUALITY-MIB
>
This matches this entry in the charter:

    4. Power and Energy Monitoring MIB document The EMAN WG will develop a
    document defining managed objects for monitoring of power states and
    energy consumption/production. The monitoring of power states includes:
    retrieving power states, properties of power states, current power
    state, power state transitions, and power state statistics.
    The managed objects will provide means for reporting detailed properties
    of the actual energy rate (power) and of accumulated energy. Further, it
    will provide information on electrical power quality.

> *Phase 4 -- Configuration Control Functionality*
>
> ·Setup a sparse table that supports configuration parameters of power 
> management entities (POWER-CONFIG-MIB?)
>
> oPurpose of the table is focused on providing configuration management 
> of power entities
>
> oLink to pwrEntityIndex
>
> oStructure TBD ... probably based on the components of 
> ENERGY-AWARE-MIB not used in Phase 1
>
> oDescribe the entity with pwrConfigKeywords, pwrConfigImportance, 
> pwrConfigRole, etc.
>
The MIB oid would exist already in the previous MIB module. Isn't it 
just a question of making read-write.
>
> If the development plan/approach isn't already on the agenda, is this 
> something we can add?
>
The agenda is actually matching this order of issues. See 
http://www.ietf.org/proceedings/79/agenda/eman.txt, with some time on 
the framework to make sure we agree on the high level concepts

Regards, Benoit
>
> If there is a call-in to the meeting, I'd be happy to participate 
> remotely as a interested implementer.  (Unfortunately, Beijing is 
> beyond my travel budget!  :-)
>
> Again, thank you for your work in establishing an industry standard in 
> this area!  Please let me know if there's anything I can do to help.
>
> Best regards,
>
> Chris
>
>
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman


--------------040801000001020509000209
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#ffffff">
    Hi Chris,<br>
    <br>
    Thanks for interest and comments.<br>
    Your phase approach is the right one in terms of priorities of
    issues.<br>
    Let's see how it matches the charter.<br>
    <br>
    <blockquote
cite="mid:68FBE0F3CE97264395875AC1C468F22C5146E3@mail03.cyberswitching.local"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 14 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1232740390;
	mso-list-type:hybrid;
	mso-list-template-ids:-1053683756 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:.75in;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.25in;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:1.75in;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:2.25in;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:2.75in;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:3.25in;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:3.75in;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:4.25in;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:4.75in;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoPlainText"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Hi EMAN WG,<o:p></o:p></span></p>
        <p class="MsoPlainText"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">I&#8217;ve been looking further into the
            ENERGY-AWARE-MIB, POWER-MONITOR-MIB, and POWER-QUALITY-MIB
            from an implementer&#8217;s perspective.&nbsp; Speaking personally and
            not on behalf of my employer, I am extremely excited by the
            potential that these MIBs and the EMAN group has on
            simplifying power management.&nbsp; A common schema for data
            reporting and control management will be awesome to finally
            get in place.<o:p></o:p></span></p>
        <p class="MsoPlainText"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">That being said, the three MIBs currently being
            proposed are definitely expansive.&nbsp; Understanding their
            nuances and providing adequate reviews for all possible
            scenarios (intelligent PDUs, PoE network switches, PoE edge
            devices, etc.) seems to be challenges that could impact
            release dates.&nbsp; I&#8217;m also a little confused with some of
            these MIBs, as they appear to have some overlapping
            scope/implied meaning.&nbsp; As an implementer, I am eagerly
            poised to start coding these up, but want to ensure that
            they are going to meet my long-term needs without
            significant changes.<o:p></o:p></span></p>
        <p class="MsoPlainText"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">As an agenda suggestion for the next WG meeting,
            would it be appropriate to discuss a phased release
            process?&nbsp; In such a process, the functionality added at each
            stage is separately contained, modular for maintenance
            purposes, and adds upon each other in a focused approach.&nbsp;
            For example, by exposing Phase 1 sooner, then
            enterprise-specific extensions can be worked on while the
            features in Phases 2 and 3 are being developed further.<o:p></o:p></span></p>
        <p class="MsoPlainText"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">To prompt discussion, here&#8217;s one suggestion of
            how the work can be broken down into phases:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.5in;"><b><span
              style="font-family:
              &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
              73, 125);">Phase 1 &#8211; Core Functionality</span></b><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);"><o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.75in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span style="font-family:
            Symbol; color: rgb(31, 73, 125);"><span style="">&middot;<span
                style="font: 7pt &quot;Times New Roman&quot;;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
              </span></span></span><!--[endif]--><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Setup a table that lists all power management
            entities (like ENTITY-MIB, but for power entities, so
            perhaps POWER-ENTITY-MIB?)<o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 1.25in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span style="font-family:
            &quot;Courier New&quot;; color: rgb(31, 73, 125);"><span
              style="">o<span style="font: 7pt &quot;Times New
                Roman&quot;;">&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Purpose of the table is focused on enumerating
            all entities that support power management using a concise,
            flexible structure<o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 1.25in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span style="font-family:
            &quot;Courier New&quot;; color: rgb(31, 73, 125);"><span
              style="">o<span style="font: 7pt &quot;Times New
                Roman&quot;;">&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Objects pass the test &#8220;Is this object necessary
            to describing all power entities?&#8221;<o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 1.25in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span style="font-family:
            &quot;Courier New&quot;; color: rgb(31, 73, 125);"><span
              style="">o<span style="font: 7pt &quot;Times New
                Roman&quot;;">&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Create a unique index value (pwrEntityIndex)<o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 1.25in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span style="font-family:
            &quot;Courier New&quot;; color: rgb(31, 73, 125);"><span
              style="">o<span style="font: 7pt &quot;Times New
                Roman&quot;;">&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Link pwrEntityIndex with entPhysicalIndex, if
            ENTITY-MIB is supported<o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 1.25in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span style="font-family:
            &quot;Courier New&quot;; color: rgb(31, 73, 125);"><span
              style="">o<span style="font: 7pt &quot;Times New
                Roman&quot;;">&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Describe the entity with pwrEntityName,
            pwrEntityDescr, pwrEntityType, and pwrEntityParent</span></p>
      </div>
    </blockquote>
    This matches this entry in the charter:<br>
    <blockquote><font color="#ff0000">3. Energy-aware Networks and
        Devices MIB document The EMAN WG will<br>
        develop a MIB module for monitoring energy-aware networks and
        devices.<br>
        The module will address devices identification</font>, context
      information, and<br>
      potential relationship between reporting devices, remote devices,
      and<br>
      monitoring probes.</blockquote>
    <br>
    <blockquote
cite="mid:68FBE0F3CE97264395875AC1C468F22C5146E3@mail03.cyberswitching.local"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText" style="margin-left: 0.5in;"><b><span
              style="font-family:
              &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
              73, 125);">Phase 2 &#8211; State Functionality</span></b><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);"><o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.75in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span style="font-family:
            Symbol; color: rgb(31, 73, 125);"><span style="">&middot;<span
                style="font: 7pt &quot;Times New Roman&quot;;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
              </span></span></span><!--[endif]--><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Setup a sparse table that supports state
            monitoring/control of power management entities
            (POWER-STATE-MIB?)<o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 1.25in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span style="font-family:
            &quot;Courier New&quot;; color: rgb(31, 73, 125);"><span
              style="">o<span style="font: 7pt &quot;Times New
                Roman&quot;;">&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Purpose of the table is focused on providing
            state management of power entities<o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 1.25in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span style="font-family:
            &quot;Courier New&quot;; color: rgb(31, 73, 125);"><span
              style="">o<span style="font: 7pt &quot;Times New
                Roman&quot;;">&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Link to pwrEntityIndex<o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 1.25in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span style="font-family:
            &quot;Courier New&quot;; color: rgb(31, 73, 125);"><span
              style="">o<span style="font: 7pt &quot;Times New
                Roman&quot;;">&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Describe the state with pwrStateLevel (off, on,
            tripped, shed, reboot, &#8230;?)<o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 1.25in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span style="font-family:
            &quot;Courier New&quot;; color: rgb(31, 73, 125);"><span
              style="">o<span style="font: 7pt &quot;Times New
                Roman&quot;;">&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Describe the relative state with pwrStateRelLevel
            (0-100%?) and/or pwrStateAcpiLevel (0..12?)</span></p>
      </div>
    </blockquote>
    This matches this entry in the charter:<br>
    <blockquote><font color="#ff0000">4. Power and Energy Monitoring MIB
        document The EMAN WG will develop a<br>
        document defining managed objects for monitoring of power states
        and<br>
        energy consumption/production. The monitoring of power states
        includes:<br>
        retrieving power states, properties of power states, current
        power<br>
        state, power state transitions, and power state statistics.</font><br>
      The managed objects will provide means for reporting detailed
      properties<br>
      of the actual energy rate (power) and of accumulated energy.
      Further, it<br>
      will provide information on electrical power quality.</blockquote>
    <blockquote
cite="mid:68FBE0F3CE97264395875AC1C468F22C5146E3@mail03.cyberswitching.local"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText" style="margin-left: 1.25in; text-indent:
          -0.25in;"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);"><o:p></o:p></span></p>
        <p class="MsoPlainText"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.5in;"><b><span
              style="font-family:
              &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
              73, 125);">Phase 3 &#8211; Meter Functionality</span></b><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);"><o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.75in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span style="font-family:
            Symbol; color: rgb(31, 73, 125);"><span style="">&middot;<span
                style="font: 7pt &quot;Times New Roman&quot;;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
              </span></span></span><!--[endif]--><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Setup a sparse table that supports power
            management entities that report meter data
            (POWER-METER-MIB?)<o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 1.25in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span style="font-family:
            &quot;Courier New&quot;; color: rgb(31, 73, 125);"><span
              style="">o<span style="font: 7pt &quot;Times New
                Roman&quot;;">&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Purpose of the table is focused on providing
            meter data for power entities<o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 1.25in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span style="font-family:
            &quot;Courier New&quot;; color: rgb(31, 73, 125);"><span
              style="">o<span style="font: 7pt &quot;Times New
                Roman&quot;;">&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Link to pwrEntityIndex<o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 1.25in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span style="font-family:
            &quot;Courier New&quot;; color: rgb(31, 73, 125);"><span
              style="">o<span style="font: 7pt &quot;Times New
                Roman&quot;;">&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Structure TBD &#8230; probably similar to
            POWER-MONITOR-MIB or POWER-QUALITY-MIB</span></p>
      </div>
    </blockquote>
    This matches this entry in the charter:<br>
    <blockquote><font color="#000000">4. Power and Energy Monitoring MIB
        document The EMAN WG will develop a<br>
        document defining managed objects for monitoring of power states
        and<br>
        energy consumption/production. The monitoring of power states
        includes:<br>
        retrieving power states, properties of power states, current
        power<br>
        state, power state transitions, and power state statistics.</font><br>
      <font color="#ff0000">The managed objects will provide means for
        reporting detailed properties<br>
        of the actual energy rate (power) and of accumulated energy.
        Further, it<br>
        will provide information on electrical power quality.</font></blockquote>
    <blockquote
cite="mid:68FBE0F3CE97264395875AC1C468F22C5146E3@mail03.cyberswitching.local"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText" style="margin-left: 1.25in; text-indent:
          -0.25in;"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);"><o:p></o:p></span></p>
        <p class="MsoPlainText"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.5in;"><b><span
              style="font-family:
              &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
              73, 125);">Phase 4 &#8211; Configuration Control Functionality</span></b><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);"><o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 0.75in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span style="font-family:
            Symbol; color: rgb(31, 73, 125);"><span style="">&middot;<span
                style="font: 7pt &quot;Times New Roman&quot;;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
              </span></span></span><!--[endif]--><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Setup a sparse table that supports configuration
            parameters of power management entities (POWER-CONFIG-MIB?)<o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 1.25in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span style="font-family:
            &quot;Courier New&quot;; color: rgb(31, 73, 125);"><span
              style="">o<span style="font: 7pt &quot;Times New
                Roman&quot;;">&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Purpose of the table is focused on providing
            configuration management of power entities<o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 1.25in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span style="font-family:
            &quot;Courier New&quot;; color: rgb(31, 73, 125);"><span
              style="">o<span style="font: 7pt &quot;Times New
                Roman&quot;;">&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Link to pwrEntityIndex<o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 1.25in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span style="font-family:
            &quot;Courier New&quot;; color: rgb(31, 73, 125);"><span
              style="">o<span style="font: 7pt &quot;Times New
                Roman&quot;;">&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Structure TBD &#8230; probably based on the components
            of ENERGY-AWARE-MIB not used in Phase 1<o:p></o:p></span></p>
        <p class="MsoPlainText" style="margin-left: 1.25in; text-indent:
          -0.25in;"><!--[if !supportLists]--><span style="font-family:
            &quot;Courier New&quot;; color: rgb(31, 73, 125);"><span
              style="">o<span style="font: 7pt &quot;Times New
                Roman&quot;;">&nbsp;&nbsp;&nbsp; </span></span></span><!--[endif]--><span
            style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Describe the entity with pwrConfigKeywords,
            pwrConfigImportance, pwrConfigRole, etc.</span></p>
      </div>
    </blockquote>
    The MIB oid would exist already in the previous MIB module. Isn't it
    just a question of making read-write.<br>
    <blockquote
cite="mid:68FBE0F3CE97264395875AC1C468F22C5146E3@mail03.cyberswitching.local"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText" style="margin-left: 1.25in; text-indent:
          -0.25in;"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);"><o:p></o:p></span></p>
        <p class="MsoPlainText"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">If the development plan/approach isn&#8217;t already on
            the agenda, is this something we can add?&nbsp; </span></p>
      </div>
    </blockquote>
    The agenda is actually matching this order of issues. See
    <a class="moz-txt-link-freetext" href="http://www.ietf.org/proceedings/79/agenda/eman.txt">http://www.ietf.org/proceedings/79/agenda/eman.txt</a>, with some time
    on the framework to make sure we agree on the high level concepts<br>
    <br>
    Regards, Benoit<br>
    <blockquote
cite="mid:68FBE0F3CE97264395875AC1C468F22C5146E3@mail03.cyberswitching.local"
      type="cite">
      <div class="WordSection1">
        <p class="MsoPlainText"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">If there is a call-in to the meeting, I&#8217;d be
            happy to participate remotely as a interested implementer.&nbsp;
            (Unfortunately, Beijing is beyond my travel budget!&nbsp; :-)<o:p></o:p></span></p>
        <p class="MsoPlainText"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Again, thank you for your work in establishing an
            industry standard in this area!&nbsp; Please let me know if
            there&#8217;s anything I can do to help.<o:p></o:p></span></p>
        <p class="MsoPlainText"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Best regards,<o:p></o:p></span></p>
        <p class="MsoPlainText"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoPlainText"><span style="font-family:
            &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31,
            73, 125);">Chris<o:p></o:p></span></p>
      </div>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
eman mailing list
<a class="moz-txt-link-abbreviated" href="mailto:eman@ietf.org">eman@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/eman">https://www.ietf.org/mailman/listinfo/eman</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------040801000001020509000209--

From bclaise@cisco.com  Thu Nov  4 06:42:49 2010
Return-Path: <bclaise@cisco.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A3D6A3A6A0B for <eman@core3.amsl.com>; Thu,  4 Nov 2010 06:42:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y9+lue5nNTbx for <eman@core3.amsl.com>; Thu,  4 Nov 2010 06:42:48 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id 41D443A69FD for <eman@ietf.org>; Thu,  4 Nov 2010 06:42:48 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oA4DgvMX008785 for <eman@ietf.org>; Thu, 4 Nov 2010 14:42:57 +0100 (CET)
Received: from [10.55.43.53] (ams-bclaise-8714.cisco.com [10.55.43.53]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oA4DgvUb012598 for <eman@ietf.org>; Thu, 4 Nov 2010 14:42:57 +0100 (CET)
Message-ID: <4CD2B860.8080507@cisco.com>
Date: Thu, 04 Nov 2010 14:42:56 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: eman mailing list <eman@ietf.org>
Content-Type: multipart/alternative; boundary="------------090402050802060408010105"
Subject: [eman] Review of draft-tychon-eman-applicability-statement-00
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the creation of an Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Nov 2010 13:42:50 -0000

This is a multi-part message in MIME format.
--------------090402050802060408010105
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Emmanuel, Matt, Brad,

Speaking as a contributor, I reviewed 
draft-tychon-eman-applicability-statement-00 
<http://datatracker.ietf.org/doc/draft-tychon-eman-applicability-statement/>
Thanks for this first draft.

A couple of high levels points (more editorial notes will be sent 
separately)
- the Abstract speaks about "describe the relevant information elements 
for these applications". I'm not sure what you refer to
- by convention, when a term is capitalized, it's defined in the 
terminology section. For example, I see Energy
- Not sure what you mean by "as traditional methods such as SNMP have 
proved not to be sufficient" because this charter is specified to define 
MIB modules ;-)
- this draft would benefit from some references
     * to other EMAN documents
       This might imply that we have a generic section for all EMAN 
documents, referring to each other.
       See section 1.2 in http://tools.ietf.org/html/rfc5470 for an 
IPFIX example
       A typical example: "in other cases, there are intermediate power 
levels between off and on, such as standby, sleep or deep sleep mode".
       It would be good to refer to the others EMAN documents where this 
is specified.
     * to external documents from other organisations.
- in section 1.3 "examples", I believe that the primary example should 
be "IT".
   In section 1.3.1 "building networks", you mention: laptops, phone, 
desktop.  IMHO, these are part of the IT examples.
- IMHO, building networks is a specific case that requires a proxy... 
while waiting for the IP protocol to be more ubiquitous.
- by convention acronyms should be explained.
     Example: HEG, EPA, EISA
     You should write "Home Energy Gateways (HEG)" the first time you 
mention it
- while [PARELLO] is certainly a very nice reference, it would certainly 
be more appropriate to cite the reference within the book ;-)
- the sections 2.x are interesting, but I'm sometimes missing the link 
with EMAN
     A good example is section 2.2 "The IETF effort would be complementary"
    For the other sections, I don't clearly see the link, i.e: none, 
complimentary, overlap, can be used together, etc...
    Examples:
         IEC -> we should try to reuse it as much as possible
         DMTF "power utilization management profile" -> explain the 
overlap/complementarity with EMAN
         DASH -> could be used to configure the Power Monitor Child from 
the Power Monitor Parent
         etc...
- section 4.2 "energywise"
     Not sure what the share secret is used for. We deal with MIB 
modules here.


Looking at the charter description,

    6. Applicability statement
    The EMAN WG will develop an applicability statement, describing the
    variety of applications that can use the energy framework and associated
    MIB modules. Potential examples are building networks, home energy
    gateway, etc. Finally, the document will also discuss relationships of
    the framework to other architectures and frameworks (such as smartgrid).
    The applicability statement will explain the relationship between the
    work in this WG and the other existing standards such as those from the
    IEC, ANSI, DMTF, and others.

Maybe what we would need to cover:
- described the applications (
     1. monitoring energy
             1.1 smart metering
             ...
     2. management energy
             2.1 just for the sake of consuming less
             2.2 to avoid blackout
             2.3 to flatten the demand/response
             ...
- also the link between the smartgrid use cases and these energy-aware 
devices should be explained.

Regards, Benoit.

--------------090402050802060408010105
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body text="#000000" bgcolor="#ffffff">
    Emmanuel, Matt, Brad,<br>
    <br>
    Speaking as a contributor, I reviewed <a
href="http://datatracker.ietf.org/doc/draft-tychon-eman-applicability-statement/">draft-tychon-eman-applicability-statement-00</a><br>
    Thanks for this first draft.<br>
    <br>
    A couple of high levels points (more editorial notes will be sent
    separately) <br>
    - the Abstract speaks about "describe the relevant information
    elements for these applications". I'm not sure what you refer to<br>
    - by convention, when a term is capitalized, it's defined in the
    terminology section. For example, I see Energy<br>
    - Not sure what you mean by "as traditional methods such as SNMP
    have proved not to be sufficient" because this charter is specified
    to define MIB modules ;-)<br>
    - this draft would benefit from some references<br>
    &nbsp;&nbsp;&nbsp; * to other EMAN documents<br>
    &nbsp;&nbsp;&nbsp; &nbsp; This might imply that we have a generic section for all EMAN
    documents, referring to each other.<br>
    &nbsp;&nbsp;&nbsp; &nbsp; See section 1.2 in <a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/rfc5470">http://tools.ietf.org/html/rfc5470</a> for an
    IPFIX example<br>
    &nbsp;&nbsp;&nbsp; &nbsp; A typical example: "in other cases, there are intermediate
    power levels between off and on, such as standby, sleep or deep
    sleep mode". <br>
    &nbsp;&nbsp;&nbsp; &nbsp; It would be good to refer to the others EMAN documents where
    this is specified.<br>
    &nbsp;&nbsp;&nbsp; * to external documents from other organisations.<br>
    - in section 1.3 "examples", I believe that the primary example
    should be "IT".<br>
    &nbsp; In section 1.3.1 "building networks", you mention: laptops, phone,
    desktop.&nbsp; IMHO, these are part of the IT examples.<br>
    - IMHO, building networks is a specific case that requires a
    proxy... while waiting for the IP protocol to be more ubiquitous.&nbsp; <br>
    - by convention acronyms should be explained. <br>
    &nbsp;&nbsp;&nbsp; Example: HEG, EPA, EISA<br>
    &nbsp;&nbsp;&nbsp; You should write "Home Energy Gateways (HEG)" the first time you
    mention it<br>
    - while [PARELLO] is certainly a very nice reference, it would
    certainly be more appropriate to cite the reference within the book
    ;-)<br>
    - the sections 2.x are interesting, but I'm sometimes missing the
    link with EMAN<br>
    &nbsp;&nbsp;&nbsp; A good example is section 2.2 "The IETF effort would be
    complementary"<br>
    &nbsp;&nbsp; For the other sections, I don't clearly see the link, i.e: none,
    complimentary, overlap, can be used together, etc...<br>
    &nbsp;&nbsp; Examples:<br>
    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; IEC -&gt; we should try to reuse it as much as possible <br>
    &nbsp;&nbsp;&nbsp; &nbsp; &nbsp; DMTF "power utilization management profile" -&gt; explain
    the overlap/complementarity with EMAN<br>
    &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; DASH -&gt; could be used to configure the Power Monitor
    Child from the Power Monitor Parent<br>
    &nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; etc...<br>
    - section 4.2 "energywise"<br>
    &nbsp;&nbsp;&nbsp; Not sure what the share secret is used for. We deal with MIB
    modules here.<br>
    <br>
    <br>
    Looking at the charter description,<br>
    <blockquote>6. Applicability statement<br>
      The EMAN WG will develop an applicability statement, describing
      the<br>
      variety of applications that can use the energy framework and
      associated<br>
      MIB modules. Potential examples are building networks, home energy<br>
      gateway, etc. Finally, the document will also discuss
      relationships of<br>
      the framework to other architectures and frameworks (such as
      smartgrid).<br>
      The applicability statement will explain the relationship between
      the<br>
      work in this WG and the other existing standards such as those
      from the<br>
      IEC, ANSI, DMTF, and others.<br>
    </blockquote>
    Maybe what we would need to cover:<br>
    - described the applications (<br>
    &nbsp;&nbsp;&nbsp; 1. monitoring energy<br>
    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 1.1 smart metering<br>
    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; ...<br>
    &nbsp;&nbsp;&nbsp; 2. management energy<br>
    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 2.1 just for the sake of consuming less<br>
    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 2.2 to avoid blackout<br>
    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 2.3 to flatten the demand/response <br>
    &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; ...<br>
    - also the link between the smartgrid use cases and these
    energy-aware devices should be explained.<br>
    <br>
    Regards, Benoit.<br>
  </body>
</html>

--------------090402050802060408010105--

From bclaise@cisco.com  Thu Nov  4 09:15:27 2010
Return-Path: <bclaise@cisco.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E161528C0DE for <eman@core3.amsl.com>; Thu,  4 Nov 2010 09:15:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KfklDD0BKI9m for <eman@core3.amsl.com>; Thu,  4 Nov 2010 09:15:23 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id 46E4D3A6927 for <eman@ietf.org>; Thu,  4 Nov 2010 09:15:23 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oA4GFWKp028084 for <eman@ietf.org>; Thu, 4 Nov 2010 17:15:32 +0100 (CET)
Received: from [10.55.43.53] (ams-bclaise-8714.cisco.com [10.55.43.53]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oA4GFWdC000277 for <eman@ietf.org>; Thu, 4 Nov 2010 17:15:32 +0100 (CET)
Message-ID: <4CD2DC24.6030006@cisco.com>
Date: Thu, 04 Nov 2010 17:15:32 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: eman mailing list <eman@ietf.org>
Content-Type: multipart/alternative; boundary="------------050703000601090301080205"
Subject: [eman] for the newcomers at the IETF
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Nov 2010 16:15:28 -0000

This is a multi-part message in MIME format.
--------------050703000601090301080205
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dear all,

As for every new working group, new charters bring new people to the IETF.
I would say this is particularly true for this EMAN WG as this is the 
first time that the IETF deals with energy management.
A couple of people contacted the chairs directly, expressing that 
they're new to the IETF.

So a couple of pointers for newcomers (for non newcomers, that's also a 
good refresh)
- The Tao of the IETF: A novice's guide to Internet Engineering Task 
Force, RFC 4677 <http://www.rfc-editor.org/rfc/rfc4677.txt>, is very 
interesting

    Abstract

        This document describes the inner workings of IETF meetings and
        Working Groups, discusses organizations related to the IETF, and
        introduces the standards process.  It is not a formal IETF process
        document but instead an informational overview.


 From this document, you can read this sentence: "If you participate in 
the IETF and read only one BCP, this is the one you should read."
Note that BCP means "Best Current Practices"

- There are two newcomer's trainings on Sunday. From the agenda 
<https://datatracker.ietf.org/meeting/79/agenda.html>, you can see
1300-1450 Newcomer's Training - Garden Ballroom 1 
<http://tools.ietf.org/agenda/79/venue/?room=garden-ballroom-1>
1500-1650 Newcomer's Training (Mandarin) - Garden Ballroom 1 
<http://tools.ietf.org/agenda/79/venue/?room=garden-ballroom-1>

- The note well is important to read
http://www.ietf.org/about/note-well.html

If you want to know more:
- RFC 2026 "The Internet Standards Process -- Revision 3",
- RFC 2418, "IETF Working Group Guidelines and Procedures"
- RFC2223, "Instructions to RFC Authors"

All these should keep you busy during the flight to Beijing ;-)

Regards, Benoit.


--------------050703000601090301080205
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body text="#000000" bgcolor="#ffffff">
    Dear all,<br>
    <br>
    As for every new working group, new charters bring new people to the
    IETF.<br>
    I would say this is particularly true for this EMAN WG as this is
    the first time that the IETF deals with energy management.<br>
    A couple of people contacted the chairs directly, expressing that
    they're new to the IETF.<br>
    <br>
    So a couple of pointers for newcomers (for non newcomers, that's
    also a good refresh)<br>
    - The Tao of the IETF: A novice's guide to Internet Engineering Task
    Force, <a href="http://www.rfc-editor.org/rfc/rfc4677.txt">RFC 4677</a>,
    is very interesting<br>
    <blockquote>
      <pre>Abstract

   This document describes the inner workings of IETF meetings and
   Working Groups, discusses organizations related to the IETF, and
   introduces the standards process.  It is not a formal IETF process
   document but instead an informational overview.

</pre>
    </blockquote>
    From this document, you can read this sentence: "If you participate
    in the IETF and read only one BCP, this is the one you should read."<br>
    Note that BCP means "Best Current Practices"<br>
    <br>
    - There are two newcomer's trainings on Sunday. From the <a
      href="https://datatracker.ietf.org/meeting/79/agenda.html">agenda</a>,
    you can see<br>
    1300-1450 Newcomer's Training - <a
      href="http://tools.ietf.org/agenda/79/venue/?room=garden-ballroom-1">Garden
      Ballroom 1</a><br>
    1500-1650 Newcomer's Training (Mandarin) - <a
      href="http://tools.ietf.org/agenda/79/venue/?room=garden-ballroom-1">Garden
      Ballroom 1</a><br>
    <br>
    - The note well is important to read<br>
    <a class="moz-txt-link-freetext" href="http://www.ietf.org/about/note-well.html">http://www.ietf.org/about/note-well.html</a><br>
    <br>
    If you want to know more:<br>
    - RFC 2026 "The Internet Standards Process -- Revision 3",<br>
    - RFC 2418, &#8220;IETF Working Group Guidelines and Procedures&#8221; <br>
    - RFC2223, "Instructions to RFC Authors"<br>
    <br>
    All these should keep you busy during the flight to Beijing ;-)<br>
    <br>
    Regards, Benoit.<br>
    <br>
  </body>
</html>

--------------050703000601090301080205--

From bnordman@lbl.gov  Sun Nov  7 15:08:01 2010
Return-Path: <bnordman@lbl.gov>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 64F2E28C119 for <eman@core3.amsl.com>; Sun,  7 Nov 2010 15:08:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.228
X-Spam-Level: 
X-Spam-Status: No, score=-5.228 tagged_above=-999 required=5 tests=[AWL=0.748,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nRAEQemGeOpR for <eman@core3.amsl.com>; Sun,  7 Nov 2010 15:07:59 -0800 (PST)
Received: from ironport2.lbl.gov (ironport2.lbl.gov [128.3.41.14]) by core3.amsl.com (Postfix) with ESMTP id DD51628C113 for <eman@ietf.org>; Sun,  7 Nov 2010 15:07:56 -0800 (PST)
X-Ironport-SBRS: 4.4
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhABAFrA1kzRVdg0kGdsb2JhbACBZ5IdAYVyAYgFCBUBAQEBCQkMBxEDH59GmVCDC4I9BIRYhX0
X-IronPort-AV: E=Sophos;i="4.58,311,1286175600"; d="scan'208";a="115646531"
Received: from mail-qw0-f52.google.com ([209.85.216.52]) by ironport2.lbl.gov with ESMTP; 07 Nov 2010 15:08:16 -0800
Received: by qwc9 with SMTP id 9so4053591qwc.39 for <eman@ietf.org>; Sun, 07 Nov 2010 15:08:15 -0800 (PST)
MIME-Version: 1.0
Received: by 10.224.195.1 with SMTP id ea1mr987188qab.304.1289171295708; Sun, 07 Nov 2010 15:08:15 -0800 (PST)
Received: by 10.229.105.8 with HTTP; Sun, 7 Nov 2010 15:08:15 -0800 (PST)
Date: Sun, 7 Nov 2010 15:08:15 -0800
Message-ID: <AANLkTinJ1MUnjU7uDxhGpE48-K3evJLHZ2FULKH0FkJf@mail.gmail.com>
From: Bruce Nordman <bnordman@lbl.gov>
To: eman@ietf.org
Content-Type: multipart/alternative; boundary=20cf300fab8122a67004947e954b
Subject: [eman] Overall approach
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Nov 2010 23:08:01 -0000

--20cf300fab8122a67004947e954b
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

This email is my opinion as a contributor,  not as WG co-chair.



I was not involved in creation of our charter, so did not express my views

on it at that time.  Also, as new to the IETF process, I have been cautious

on how much I put out to the email list.  As we can now meet in person,

I would welcome side conversations with any of you that I have not yet

been conversing with directly =96 please find me since I don=92t know who

you are.



Perhaps the most basic issue is determining the balance between *reporting*

and *control* in our discussions and final product(s).  Reporting seems a

precondition for control.  The question is whether control is no part of ou=
r

initial work, a small part, or large.  Certainly control is part of the
topic of

=93Energy Management=94.



I believe that power/energy reporting can be universal as it is independent

of functionality, control objectives, and usage contexts.  Reporting only
gets

to be device-specific to the degree that we assign detailed functional
meaning

to power states (this is one reason why I believe in few basic power states
for

a generic facility).  Even if we created a good and useful facility for
control,

it would not be universal, and I expect never used by even a majority of
devices

on the Internet (but may get good use by many so well-worth pursuing).



So, I think the architecture/framework for eman should be designed for
reporting

only so that it is optimized for that.  Then, we can consider what control

mechanisms can be layered on top and are a logical extension of it.  If the

architecture were to be designed for the control scenarios, it could
undermine

its effectiveness for reporting.  My reading of item 1. of our charter is
that it

gives us flexibility for a wide range of approaches, but does suggest that
control

might be secondary.



I think the difficult part of this process is the requirements and
framework.  Once

those are set, specifying the MIBs that implement that will I expect be muc=
h

easier and quicker.



As new to the IETF, I am unsure how to separate Applicability consideration=
s

(last item) from the first requirements of Requirements and Framework (firs=
t

items).  Best I can do is see Applicability as a short description of the
result, but

Requirements and Framework speaking to why particular approaches were taken

or not taken.



On other matters from the charter, I am unsure about how critical the issue
of

transitions is.  I think we need to consider our use cases more to inform
that.

Reporting on batteries seems a worthwhile part of our work but seems on the

sidelines for the issue of how to construct the requirements and framework.



Once we have a basic facility for reporting, I do believe that we will want
to

extend it to more complex (but less universal) applications, and to control=
.

I do see it appropriate and necessary to be considering these in parallel t=
o

creating our first products, and can imagine working on I-Ds that advance

these in parallel to ones that have the more narrow basic reporting focus.






--=20
*Bruce Nordman*
Lawrence Berkeley National Laboratory
eetd.lbl.gov/ea/nordman
BNordman@LBL.gov
510-486-7089
m: 510-501-7943

--20cf300fab8122a67004947e954b
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable












<style>@font-face {
  font-family: "Cambria";
}p.MsoNormal, li.MsoNormal, div.MsoNormal { margin: 0in 0in 0.0001pt; font-=
size: 12pt; font-family: "Times New Roman"; }div.Section1 { page: Section1;=
 }</style>




<p class=3D"MsoNormal">This email is my opinion as a contributor,<span styl=
e=3D"">=A0 </span>not as WG co-chair.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">I was not involved in creation of our charter, so di=
d not
express my views</p>

<p class=3D"MsoNormal">on it at that time.<span style=3D"">=A0
</span>Also, as new to the IETF process, I have been cautious</p>

<p class=3D"MsoNormal">on how much I put out to the email list.<span style=
=3D"">=A0 </span>As we can now meet in person,</p>

<p class=3D"MsoNormal">I would welcome side conversations with any of you t=
hat I
have not yet</p>

<p class=3D"MsoNormal">been conversing with directly =96 please find me sin=
ce I don=92t
know who</p>

<p class=3D"MsoNormal">you are.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">Perhaps the most basic issue is determining the bala=
nce
between <b style=3D"">reporting</b></p>

<p class=3D"MsoNormal">and <b style=3D"">control</b> in
our discussions and final product(s).<span style=3D"">=A0
</span>Reporting seems a</p>

<p class=3D"MsoNormal">precondition for control.<span style=3D"">=A0 </span=
>The question is whether control is no part of our</p>

<p class=3D"MsoNormal">initial work, a small part, or large.<span style=3D"=
">=A0 </span>Certainly control is part of the topic
of</p>

<p class=3D"MsoNormal">=93Energy Management=94.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">I believe that power/energy reporting can be univers=
al as it
is independent</p>

<p class=3D"MsoNormal">of functionality, control objectives, and usage
contexts.<span style=3D"">=A0 </span>Reporting only gets</p>

<p class=3D"MsoNormal">to be device-specific to the degree that we assign d=
etailed
functional meaning</p>

<p class=3D"MsoNormal">to power states (this is one reason why I believe in=
 few
basic power states for</p>

<p class=3D"MsoNormal">a generic facility).<span style=3D"">=A0
</span>Even if we created a good and useful facility for control,</p>

<p class=3D"MsoNormal">it would not be universal, and I expect never used b=
y even a
majority of devices</p>

<p class=3D"MsoNormal">on the Internet (but may get good use by many so wel=
l-worth
pursuing).</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">So, I think the architecture/framework for eman shou=
ld be
designed for reporting</p>

<p class=3D"MsoNormal">only so that it is optimized for that.<span style=3D=
"">=A0 </span>Then, we can consider what control</p>

<p class=3D"MsoNormal">mechanisms can be layered on top and are a logical e=
xtension
of it.<span style=3D"">=A0 </span>If the</p>

<p class=3D"MsoNormal">architecture were to be designed for the control sce=
narios,
it could undermine</p>

<p class=3D"MsoNormal">its effectiveness for reporting.<span style=3D"">=A0=
 </span>My reading of item 1. of our charter is that it</p>

<p class=3D"MsoNormal">gives us flexibility for a wide range of approaches,=
 but
does suggest that control</p>

<p class=3D"MsoNormal">might be secondary.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">I think the difficult part of this process is the
requirements and framework.<span style=3D"">=A0 </span>Once</p>

<p class=3D"MsoNormal">those are set, specifying the MIBs that implement th=
at will
I expect be much</p>

<p class=3D"MsoNormal">easier and quicker.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">As new to the IETF, I am unsure how to separate
Applicability considerations</p>

<p class=3D"MsoNormal">(last item) from the first requirements of Requireme=
nts and
Framework (first</p>

<p class=3D"MsoNormal">items).<span style=3D"">=A0 </span>Best I
can do is see Applicability as a short description of the result, but</p>

<p class=3D"MsoNormal">Requirements and Framework speaking to why particula=
r
approaches were taken</p>

<p class=3D"MsoNormal">or not taken.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">On other matters from the charter, I am unsure about=
 how
critical the issue of</p>

<p class=3D"MsoNormal">transitions is.<span style=3D"">=A0
</span>I think we need to consider our use cases more to inform that.</p>

<p class=3D"MsoNormal">Reporting on batteries seems a worthwhile part of ou=
r work
but seems on the</p>

<p class=3D"MsoNormal">sidelines for the issue of how to construct the requ=
irements
and framework.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">Once we have a basic facility for reporting, I do be=
lieve
that we will want to </p>

<p class=3D"MsoNormal">extend it to more complex (but less universal) appli=
cations,
and to control.</p>

<p class=3D"MsoNormal">I do see it appropriate and necessary to be consider=
ing
these in parallel to</p>

<p class=3D"MsoNormal">creating our first products, and can imagine working=
 on I-Ds
that advance</p>

<p class=3D"MsoNormal">these in parallel to ones that have the more narrow =
basic
reporting focus.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">=A0</p>


<br clear=3D"all"><br>-- <br><font size=3D"4"><b>Bruce Nordman</b></font><b=
r><span style=3D"color: rgb(0, 0, 153);">Lawrence Berkeley National Laborat=
ory</span><br><a href=3D"http://eetd.lbl.gov/ea/nordman" target=3D"_blank">=
eetd.lbl.gov/ea/nordman</a><br>
BNordman@LBL.gov<br>510-486-7089<br>m: 510-501-7943<br><br>

--20cf300fab8122a67004947e954b--

From bnordman@lbl.gov  Sun Nov  7 15:09:22 2010
Return-Path: <bnordman@lbl.gov>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 39B2B28C11E for <eman@core3.amsl.com>; Sun,  7 Nov 2010 15:09:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.415
X-Spam-Level: 
X-Spam-Status: No, score=-5.415 tagged_above=-999 required=5 tests=[AWL=0.561,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WkXtcPIl1u1o for <eman@core3.amsl.com>; Sun,  7 Nov 2010 15:09:20 -0800 (PST)
Received: from ironport3.lbl.gov (ironport3.lbl.gov [128.3.41.25]) by core3.amsl.com (Postfix) with ESMTP id 160AB28C113 for <eman@ietf.org>; Sun,  7 Nov 2010 15:09:20 -0800 (PST)
X-Ironport-SBRS: 4.4
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhABANLA1kzRVdg0kGdsb2JhbACBZ5IdAYVyAYgFCBUBAQEBCQkMBxEDH59JmVCCchmCPQSEWIV9
X-IronPort-AV: E=Sophos;i="4.58,311,1286175600"; d="scan'208";a="28915102"
Received: from mail-qw0-f52.google.com ([209.85.216.52]) by ironport3.lbl.gov with ESMTP; 07 Nov 2010 15:09:38 -0800
Received: by qwc9 with SMTP id 9so4054292qwc.39 for <eman@ietf.org>; Sun, 07 Nov 2010 15:09:37 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.241.194 with SMTP id lf2mr4410626qcb.164.1289171375121; Sun, 07 Nov 2010 15:09:35 -0800 (PST)
Received: by 10.229.105.8 with HTTP; Sun, 7 Nov 2010 15:09:35 -0800 (PST)
Date: Sun, 7 Nov 2010 15:09:35 -0800
Message-ID: <AANLkTikFy7hzFSFtQonWZRXe_WAMbpZLLAGWrNjOVcFw@mail.gmail.com>
From: Bruce Nordman <bnordman@lbl.gov>
To: eman@ietf.org
Content-Type: multipart/alternative; boundary=0016364d2b89de63f504947e99d5
Subject: [eman] Proposed alternation of framework
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Nov 2010 23:09:22 -0000

--0016364d2b89de63f504947e99d5
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<< warning: long email >>

eman proposal for adjusting framework in current I-Ds

Bruce Nordman

November 7, 2010



The following takes the basic principles from the current I-Ds, and

makes a few changes that I see as making the framework simpler

and more transparent, and also provides some additional features.

It does not address control, nor many (future) optional features.



As an observation, power state is a property of an individual device

and cannot be aggregated.  Power level (W) and energy use can be

readily aggregated.



There are a number of complications that I would propose deferring

from our initial product.  These include transition states, support for

reporting intervals, and reporting on components within a host.

As noted above, we could be making progress on these in parallel to

the more basic work, particularly if the content was in separate I-Ds.



There is nothing magic about the terminology used below and I am

sure it can be improved.



Basic concepts I propose are:



Powered Device



An electricity-using device that is almost always =93atomic=94 =96 not

separated into constituent parts that can be powered and function

autonomously in normal use.  They may have IP connectivity or lack it.

They may be able to report energy/power information themselves,

or rely on a power proxy to do this.



Most devices have a single power source, no battery, and do not power

other devices, so these just report a unitary notion of energy/power.

Other devices have multiple power sources (from different electricity

=93domains=94), an internal battery (which is functionally an additional
source),

and/or downstream power loads (other devices; a battery that is charging

is effectively an additional load).  Thus, these have the total net
consumption

of the device itself, the power input from each source, and the power outpu=
t

to each load.  The complexity required for these more complex devices

should not be burdensome on the simpler devices.  We need terms that

distinguish simple from complex devices; whether having a battery always

makes a device complex I am not sure.



In addition to the information noted in the current I-Ds, a device is also =
a

member of a =93Power Domain=94 (or more specifically, each power source is)=
.



Power Proxy



A power proxy reports power/energy data on behalf of a second device.

For purposes of energy management, it IS the device.  The second device

may or may not have IP connectivity, but in either case, all energy/power

information (including any subsidiary notion of identity) should come from

the proxy to the rest of the IP network.  In the long run, we should hope
that

fewer and fewer devices require a proxy, but for a considerable time we wil=
l

have devices that lack IP connectivity, or that have it but lack ability to
report

on their own power/energy status.



Note that a host may implement many power proxies; each proxy is logically

independent of the others.  It seems likely that any device that provides
proxy

services can report on its own power/energy status.  A proxy will almost
always

(perhaps always) be implemented by a Power Distributor, but proxying a
distinct

function.



The proxy may be in the same domain as the second device, or a different
domain.

If in the same domain, the proxy may be in a device that distributes power
to the

second device, or not.  Thus, there are three possible relationships:
different domain,

powering (consequently same domain), not powering (but same domain).



Power Distributor



These consumes power themselves and distribute power to other devices, whic=
h

may include further distributors.  A distributor may have incomplete
information

about downstream devices and their power consumption, missing identity,
power

consumption, or both, from some devices.  A distributor is a device, so may
have

more than one power source, and may include a battery.



It is helpful to first think of power being distributed along a tree
structure, with

parent and child controllers, but the structure need not be limited to
classic trees.

Other than batteries, at this time power flow is only in one direction (tha=
t
is, all

flows are either sources into a device, or sinks out of it).



A distributor may be in one power domain, but more commonly the downstream

powered devices will be in a different domain; a Power over Ethernet switch
is a

prime example of this.  Most commonly, each domain will have a single sourc=
e
of

power (ignoring batteries), but this may not be required.



Power Domain



A system of power distribution with a common technology and fate.
Technologies

are usually distinguished by voltages and whether AC or DC.  AC examples
include

100V, 115V, 200V, and 230V.  DC examples include 380V, 48V, 24V, 12V, and 5=
V

(variously including eMerge, PoE, USB, and vehicle standards).  Increasingl=
y

communications go along with power, but this is incidental to power
reporting.



Power domains are often in trees, but this is not strictly required.  A
domain with

a single source may have a controller at its root (e.g. a PoE switch), or
not (e.g.

a circuit breaker in a building).  At this time, we should consider domains
as having

a single source of power; later we could relax that requirement.



Common fate includes quality, reliability, availability, total capacity, an=
d
price.

How devices learn what domain they are in is out of our scope.



Power Manager



This concept is NOT defined in our standard, but is a key expected user of

the facility.  It is an interested entity and has no specific relation to
device.

It may be in the same power domain, or not.



A power manager will commonly send out a broadcast request to all devices

in a power domain and ask for current information.  In this case, a
distributor is

not involved in the request for that function, though a device which is a
distributor

will report its own (net) consumption, and may implement proxies that
respond

to this request.



To avoid double-counting, the manager needs to know what domains provide

power to others).  A manager may use distributors that are gateways between

domains as aggregators, and so not bothering to query devices in the second

domain at all, or as often.  For example, the domain that a PoE switch is i=
n
may

be queried more often than the domain of devices powered by that switch.



Other Notes



This system has no concept of a meter.  Rather, a meter is a distributor,
and

today=92s meters don=92t have direct knowledge of what they are providing p=
ower
to

(remember that a distributor can have incomplete knowledge, including none)=
.



A key point is that there is no assumed relationship between the power
distribution

topology and the communications topology.



Somewhere, attention needs to be paid to wire losses =96 there is a differe=
nce

between power supplied to a device, and power consumed by one.   When

measurement is done at both ends of the wire, it can be calculated, but mor=
e

commonly, the measurement is done at only one end so just needs to have a

flag for which it is.



Power data are allowed to be estimated by a device from knowledge it has

rather than directly measured.  This is then noted in accuracy reporting.

Power estimation may be as important as proxying in the coming years.



Communication



The core definition is what information a device provides when queried.

A proxy IS the device for these purposes, so responds the same as a direct

device (with a flag somewhere noting it is a proxy in case someone cares).

A distributor is a device so responds the same way as a simple device
(albeit

with more complexity to the response).



Distributors may find it helpful to query devices they supply power to, but

this is simply a usage of our facility, not a separate mechanism.



Because control and intervals are not implemented, communication is only

in one direction.



Usage examples



Most common today is devices on mains AC power in which a domain is

a circuit breaker, a larger area (e.g. zone or floor of a building), or an
entire

building.  A vehicle is a building on wheels (and always its own domain).



PoE necessarily creates a different domain.   Usually all devices powered

from a PoE switch are in the same domain.  PoE switches usually have a

capacity constraint distinct from that of the domain it is part of.



A UPS has a distinct domain downstream of it from its mains power source,

as the fate of these devices is different from what the UPS sees from its
primary

source.



Other Other Notes



There is no distinction by building type (home, commercial, vehicle) in any

of this.



Likely none of this affects the battery MIB proposal.



Many control approaches will include distribution a price (and price
forecast)

to devices.  Prices will be by domain, as they may vary.  For example, UPS
will

have its own price when off-grid.  PoE devices may get higher price if
switch

is near capacity.  People in charge of a domain may want to impose their ow=
n

carbon taxes implicitly.  Local batteries/generation may raise or lower the
price

otherwise seen on a domain.  Price distribution NOT part of the energy/powe=
r

reporting mechanism, though will use the same domain concept.  There is a

standard for getting a price to a building =96 my concern is only local
distribution

of a price within a building or a domain.


--=20
*Bruce Nordman*
Lawrence Berkeley National Laboratory
eetd.lbl.gov/ea/nordman
BNordman@LBL.gov
510-486-7089
m: 510-501-7943

--0016364d2b89de63f504947e99d5
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<span style=3D"color: rgb(102, 0, 204);">&lt;&lt; warning: long email &gt;&=
gt;</span><br><br><style>@font-face {
  font-family: "Cambria";
}@font-face {
  font-family: "Lucida Grande";
}p.MsoNormal, li.MsoNormal, div.MsoNormal { margin: 0in 0in 0.0001pt; font-=
size: 12pt; font-family: "Times New Roman"; }p.MsoAcetate, li.MsoAcetate, d=
iv.MsoAcetate { margin: 0in 0in 0.0001pt; font-size: 9pt; font-family: "Tim=
es New Roman"; }span.BalloonTextChar { font-family: "Lucida Grande"; }div.S=
ection1 { page: Section1; }</style>




<p class=3D"MsoNormal">eman proposal for adjusting framework in current I-D=
s</p>

<p class=3D"MsoNormal">Bruce Nordman</p>

<p class=3D"MsoNormal">November 7, 2010</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">The following takes the basic principles from the cu=
rrent
I-Ds, and</p>

<p class=3D"MsoNormal">makes a few changes that I see as making the framewo=
rk
simpler</p>

<p class=3D"MsoNormal">and more transparent, and also provides some additio=
nal
features.</p>

<p class=3D"MsoNormal">It does not address control, nor many (future) optio=
nal
features.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">As an observation, power state is a property of an
individual device</p>

<p class=3D"MsoNormal">and cannot be aggregated.<span style=3D"">=A0 </span=
>Power level (W) and energy use can be</p>

<p class=3D"MsoNormal">readily aggregated.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">There are a number of complications that I would pro=
pose
deferring </p>

<p class=3D"MsoNormal">from our initial product.<span style=3D"">=A0 </span=
>These include transition states, support for</p>

<p class=3D"MsoNormal">reporting intervals, and reporting on components wit=
hin a
host.</p>

<p class=3D"MsoNormal">As noted above, we could be making progress on these=
 in parallel
to</p>

<p class=3D"MsoNormal">the more basic work, particularly if the content was=
 in
separate I-Ds.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">There is nothing magic about the terminology used be=
low and
I am</p>

<p class=3D"MsoNormal">sure it can be improved.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">Basic concepts I propose are:</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">Powered Device</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">An electricity-using device that is almost always =
=93atomic=94 =96
not </p>

<p class=3D"MsoNormal">separated into constituent parts that can be powered=
 and
function</p>

<p class=3D"MsoNormal">autonomously in normal use.<span style=3D"">=A0 </sp=
an>They may have IP connectivity or lack it.</p>

<p class=3D"MsoNormal">They may be able to report energy/power information
themselves,</p>

<p class=3D"MsoNormal">or rely on a power proxy to do this.<span style=3D""=
>=A0 </span></p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">Most devices have a single power source, no battery,=
 and do
not power </p>

<p class=3D"MsoNormal">other devices, so these just report a unitary notion=
 of
energy/power.<span style=3D"">=A0 </span></p>

<p class=3D"MsoNormal">Other devices have multiple power sources (from diff=
erent
electricity </p>

<p class=3D"MsoNormal">=93domains=94), an internal battery (which is functi=
onally an
additional source), </p>

<p class=3D"MsoNormal">and/or downstream power loads (other devices; a batt=
ery that
is charging </p>

<p class=3D"MsoNormal">is effectively an additional load).<span style=3D"">=
=A0 </span>Thus, these have the total net
consumption </p>

<p class=3D"MsoNormal">of the device itself, the power input from each sour=
ce, and
the power output</p>

<p class=3D"MsoNormal">to each load.<span style=3D"">=A0
</span>The complexity required for these more complex devices</p>

<p class=3D"MsoNormal">should not be burdensome on the simpler devices.<spa=
n style=3D"">=A0 </span>We need terms that</p>

<p class=3D"MsoNormal">distinguish simple from complex devices; whether hav=
ing a
battery always </p>

<p class=3D"MsoNormal">makes a device complex I am not sure.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">In addition to the information noted in the current =
I-Ds, a
device is also a</p>

<p class=3D"MsoNormal">member of a =93Power Domain=94 (or more specifically=
, each power
source is).</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">Power Proxy</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">A power proxy reports power/energy data on behalf of=
 a
second device.<span style=3D"">=A0 </span></p>

<p class=3D"MsoNormal">For purposes of energy management, it IS the device.=
<span style=3D"">=A0 </span>The second device</p>

<p class=3D"MsoNormal">may or may not have IP connectivity, but in either c=
ase, all
energy/power</p>

<p class=3D"MsoNormal">information (including any subsidiary notion of iden=
tity)
should come from</p>

<p class=3D"MsoNormal">the proxy to the rest of the IP network.<span style=
=3D"">=A0 </span>In the long run, we should hope that</p>

<p class=3D"MsoNormal">fewer and fewer devices require a proxy, but for a
considerable time we will</p>

<p class=3D"MsoNormal">have devices that lack IP connectivity, or that have=
 it but
lack ability to report</p>

<p class=3D"MsoNormal">on their own power/energy status.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">Note that a host may implement many power proxies; e=
ach
proxy is logically</p>

<p class=3D"MsoNormal">independent of the others.<span style=3D"">=A0 </spa=
n>It seems likely that any device that provides proxy</p>

<p class=3D"MsoNormal">services can report on its own power/energy status.<=
span style=3D"">=A0 </span>A proxy will almost always</p>

<p class=3D"MsoNormal">(perhaps always) be implemented by a Power Distribut=
or, but
proxying a distinct </p>

<p class=3D"MsoNormal">function.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">The proxy may be in the same domain as the second de=
vice, or
a different domain.</p>

<p class=3D"MsoNormal">If in the same domain, the proxy may be in a device =
that
distributes power to the</p>

<p class=3D"MsoNormal">second device, or not.<span style=3D"">=A0
</span>Thus, there are three possible relationships: different domain,</p>

<p class=3D"MsoNormal">powering (consequently same domain), not powering (b=
ut same
domain).</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">Power Distributor</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">These consumes power themselves and distribute power=
 to
other devices, which</p>

<p class=3D"MsoNormal">may include further distributors.<span style=3D"">=
=A0 </span>A distributor may have incomplete information </p>

<p class=3D"MsoNormal">about downstream devices and their power consumption=
,
missing identity, power</p>

<p class=3D"MsoNormal">consumption, or both, from some devices.<span style=
=3D"">=A0 </span>A distributor is a device, so may have</p>

<p class=3D"MsoNormal">more than one power source, and may include a batter=
y.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">It is helpful to first think of power being distribu=
ted
along a tree structure, with</p>

<p class=3D"MsoNormal">parent and child controllers, but the structure need=
 not be
limited to classic trees.</p>

<p class=3D"MsoNormal">Other than batteries, at this time power flow is onl=
y in one
direction (that is, all</p>

<p class=3D"MsoNormal">flows are either sources into a device, or sinks out=
 of it).</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">A distributor may be in one power domain, but more c=
ommonly
the downstream</p>

<p class=3D"MsoNormal">powered devices will be in a different domain; a Pow=
er over
Ethernet switch is a</p>

<p class=3D"MsoNormal">prime example of this.<span style=3D"">=A0
</span>Most commonly, each domain will have a single source of</p>

<p class=3D"MsoNormal">power (ignoring batteries), but this may not be requ=
ired.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">Power Domain</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">A system of power distribution with a common technol=
ogy and
fate.<span style=3D"">=A0 </span>Technologies</p>

<p class=3D"MsoNormal">are usually distinguished by voltages and whether AC=
 or DC.<span style=3D"">=A0 </span>AC examples include </p>

<p class=3D"MsoNormal">100V, 115V, 200V, and 230V.<span style=3D"">=A0 </sp=
an>DC examples include 380V, 48V, 24V, 12V, and 5V</p>

<p class=3D"MsoNormal">(variously including eMerge, PoE, USB, and vehicle
standards).<span style=3D"">=A0 </span>Increasingly</p>

<p class=3D"MsoNormal">communications go along with power, but this is inci=
dental
to power reporting.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">Power domains are often in trees, but this is not st=
rictly
required.<span style=3D"">=A0 </span>A domain with</p>

<p class=3D"MsoNormal">a single source may have a controller at its root (e=
.g. a
PoE switch), or not (e.g.</p>

<p class=3D"MsoNormal">a circuit breaker in a building).<span style=3D"">=
=A0 </span>At this time, we should consider domains as having</p>

<p class=3D"MsoNormal">a single source of power; later we could relax that
requirement.</p>

<p class=3D"MsoNormal"><span style=3D"">=A0</span></p>

<p class=3D"MsoNormal">Common fate includes quality, reliability, availabil=
ity, total
capacity, and price.</p>

<p class=3D"MsoNormal">How devices learn what domain they are in is out of =
our
scope.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">Power Manager</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">This concept is NOT defined in our standard, but is =
a key
expected user of</p>

<p class=3D"MsoNormal">the facility.<span style=3D"">=A0
</span>It is an interested entity and has no specific relation to device.</=
p>

<p class=3D"MsoNormal">It may be in the same power domain, or not.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">A power manager will commonly send out a broadcast r=
equest
to all devices </p>

<p class=3D"MsoNormal">in a power domain and ask for current information.<s=
pan style=3D"">=A0 </span>In this case, a distributor is </p>

<p class=3D"MsoNormal">not involved in the request for that function, thoug=
h a
device which is a distributor </p>

<p class=3D"MsoNormal">will report its own (net) consumption, and may imple=
ment
proxies that respond </p>

<p class=3D"MsoNormal">to this request.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">To avoid double-counting, the manager needs to know =
what
domains provide </p>

<p class=3D"MsoNormal">power to others).<span style=3D"">=A0
</span>A manager may use distributors that are gateways between</p>

<p class=3D"MsoNormal">domains as aggregators, and so not bothering to quer=
y
devices in the second</p>

<p class=3D"MsoNormal">domain at all, or as often.<span style=3D"">=A0 </sp=
an>For example, the domain that a PoE switch is in may</p>

<p class=3D"MsoNormal">be queried more often than the domain of devices pow=
ered by
that switch.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">Other Notes</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">This system has no concept of a meter.<span style=3D=
"">=A0 </span>Rather, a meter is a distributor, and</p>

<p class=3D"MsoNormal">today=92s meters don=92t have direct knowledge of wh=
at they are
providing power to</p>

<p class=3D"MsoNormal">(remember that a distributor can have incomplete kno=
wledge,
including none).</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">A key point is that there is no assumed relationship=
 between
the power distribution</p>

<p class=3D"MsoNormal">topology and the communications topology.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">Somewhere, attention needs to be paid to wire losses=
 =96 there
is a difference</p>

<p class=3D"MsoNormal">between power supplied to a device, and power consum=
ed by
one.<span style=3D"">=A0=A0 </span>When</p>

<p class=3D"MsoNormal">measurement is done at both ends of the wire, it can=
 be
calculated, but more</p>

<p class=3D"MsoNormal">commonly, the measurement is done at only one end so=
 just
needs to have a</p>

<p class=3D"MsoNormal">flag for which it is.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">Power data are allowed to be estimated by a device f=
rom
knowledge it has</p>

<p class=3D"MsoNormal">rather than directly measured.<span style=3D"">=A0 <=
/span>This is then noted in accuracy reporting.</p>

<p class=3D"MsoNormal">Power estimation may be as important as proxying in =
the
coming years.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">Communication</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">The core definition is what information a device pro=
vides
when queried.</p>

<p class=3D"MsoNormal">A proxy IS the device for these purposes, so respond=
s the
same as a direct</p>

<p class=3D"MsoNormal">device (with a flag somewhere noting it is a proxy i=
n case
someone cares).</p>

<p class=3D"MsoNormal">A distributor is a device so responds the same way a=
s a
simple device (albeit</p>

<p class=3D"MsoNormal">with more complexity to the response).</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">Distributors may find it helpful to query devices th=
ey
supply power to, but</p>

<p class=3D"MsoNormal">this is simply a usage of our facility, not a separa=
te
mechanism.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">Because control and intervals are not implemented,
communication is only</p>

<p class=3D"MsoNormal">in one direction.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">Usage examples</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">Most common today is devices on mains AC power in wh=
ich a
domain is</p>

<p class=3D"MsoNormal">a circuit breaker, a larger area (e.g. zone or floor=
 of a
building), or an entire</p>

<p class=3D"MsoNormal">building.<span style=3D"">=A0 </span>A
vehicle is a building on wheels (and always its own domain).</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">PoE necessarily creates a different domain.<span sty=
le=3D"">=A0=A0 </span>Usually all devices powered</p>

<p class=3D"MsoNormal">from a PoE switch are in the same domain.<span style=
=3D"">=A0 </span>PoE switches usually have a</p>

<p class=3D"MsoNormal">capacity constraint distinct from that of the domain=
 it is
part of.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">A UPS has a distinct domain downstream of it from it=
s mains
power source,</p>

<p class=3D"MsoNormal">as the fate of these devices is different from what =
the UPS
sees from its primary</p>

<p class=3D"MsoNormal">source.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">Other Other Notes</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">There is no distinction by building type (home, comm=
ercial,
vehicle) in any</p>

<p class=3D"MsoNormal">of this.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">Likely none of this affects the battery MIB proposal=
.</p>

<p class=3D"MsoNormal">=A0</p>

<p class=3D"MsoNormal">Many control approaches will include distribution a =
price (and
price forecast)</p>

<p class=3D"MsoNormal">to devices.<span style=3D"">=A0
</span>Prices will be by domain, as they may vary.<span style=3D"">=A0 </sp=
an>For example, UPS will</p>

<p class=3D"MsoNormal">have its own price when off-grid.<span style=3D"">=
=A0 </span>PoE devices may get higher price if switch</p>

<p class=3D"MsoNormal">is near capacity.<span style=3D"">=A0
</span>People in charge of a domain may want to impose their own</p>

<p class=3D"MsoNormal">carbon taxes implicitly.<span style=3D"">=A0 </span>=
Local batteries/generation may raise or lower the price</p>

<p class=3D"MsoNormal">otherwise seen on a domain.<span style=3D"">=A0 </sp=
an>Price distribution NOT part of the energy/power</p>

<p class=3D"MsoNormal">reporting mechanism, though will use the same domain
concept.<span style=3D"">=A0 </span>There is a </p>

<p class=3D"MsoNormal">standard for getting a price to a building =96 my co=
ncern is
only local distribution</p>

<p class=3D"MsoNormal">of a price within a building or a domain.</p>


<br clear=3D"all"><br>-- <br><font size=3D"4"><b>Bruce Nordman</b></font><b=
r><span style=3D"color: rgb(0, 0, 153);">Lawrence Berkeley National Laborat=
ory</span><br><a href=3D"http://eetd.lbl.gov/ea/nordman" target=3D"_blank">=
eetd.lbl.gov/ea/nordman</a><br>
BNordman@LBL.gov<br>510-486-7089<br>m: 510-501-7943<br><br>

--0016364d2b89de63f504947e99d5--

From chrisv@cyberswitching.com  Sun Nov  7 17:15:38 2010
Return-Path: <chrisv@cyberswitching.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C83183A68E2 for <eman@core3.amsl.com>; Sun,  7 Nov 2010 17:15:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2h7FtJO7hdYs for <eman@core3.amsl.com>; Sun,  7 Nov 2010 17:15:32 -0800 (PST)
Received: from p01c12o148.mxlogic.net (p01c12o148.mxlogic.net [208.65.145.71]) by core3.amsl.com (Postfix) with ESMTP id C52CE3A68F1 for <eman@ietf.org>; Sun,  7 Nov 2010 17:15:31 -0800 (PST)
Received: from unknown [64.81.28.110] (EHLO mail03.cyberswitching.local) by p01c12o148.mxlogic.net(mxl_mta-6.7.0-2) with ESMTP id 74f47dc4.0.168657.00-373.270792.p01c12o148.mxlogic.net (envelope-from <chrisv@cyberswitching.com>);  Sun, 07 Nov 2010 18:15:52 -0700 (MST)
X-MXL-Hash: 4cd74f484a61268d-cdaefbd5e2fef0fbeb8d878b2628010ce2bfd7c5
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB7EE2.626A7A1B"
Date: Sun, 7 Nov 2010 17:15:08 -0800
Message-ID: <68FBE0F3CE97264395875AC1C468F22C514A74@mail03.cyberswitching.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [eman] Proposed alternation of framework
Thread-Index: Act+0MWGgJ51kuLaQZ+XO5sxLXJfHQADY2Lg
References: <AANLkTikFy7hzFSFtQonWZRXe_WAMbpZLLAGWrNjOVcFw@mail.gmail.com>
From: "Chris Verges" <chrisv@cyberswitching.com>
To: "Bruce Nordman" <bnordman@lbl.gov>, <eman@ietf.org>
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010110201)]
X-MAIL-FROM: <chrisv@cyberswitching.com>
X-SOURCE-IP: [64.81.28.110]
X-AnalysisOut: [v=1.0 c=1 a=rpQdwwq_DzYA:10 a=BLceEmwcHowA:10 a=4zsJQXJisS]
X-AnalysisOut: [Y22NXBO5KRuA==:17 a=nxz6s0g7QSGR-OsOnOEA:9 a=qCqbat-EhVF01]
X-AnalysisOut: [MbpIe4A:7 a=MQIPHAi6REB4RFO8ikumJ55n0g8A:4 a=CjuIK1q_8ugA:]
X-AnalysisOut: [10 a=KfuUYP09UMgGjtob:21 a=5YVCTrI9l8j3zmW0:21 a=yMhMjlubA]
X-AnalysisOut: [AAA:8 a=SSmOFEACAAAA:8 a=krOwHqcR2woKz-QG44oA:9 a=FNr_WkRp]
X-AnalysisOut: [KrxThZdqye8A:7 a=5diFRSBCHHXsNuFm6cHdg9JqSZ0A:4]
Subject: Re: [eman] Proposed alternation of framework
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 01:15:38 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB7EE2.626A7A1B
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Bruce,

=20

Questions and comments inline:

=20

[BN] As an observation, power state is a property of an individual
device and cannot be aggregated.  Power level (W) and energy use can be
readily aggregated.

=20

[CV] With respect, I think power state can be aggregated.  For example,
please consider a standard datacenter.  When all servers are turned on
in the datacenter, it is at 100% "on" state.  If 30% of the servers are
turned off, the datacenter's state has reduced to 70%.  This is fairly
congruous with the ACPI model, where a server can be in different
states, and each state represents a power usage level.

=20

[CV] How such aggregated state is determined is beyond the scope of any
MIB, but the ability to report such information can offer a hook for
innovation in the industry.

=20

[CV] I agree that power state, like reporting meter data, could be
pushed off to a later release, as enumerating the entities themselves is
far more critical (core?) to establishing anything more complex.

=20

[BN] There are a number of complications that I would propose deferring
from our initial product.  These include transition states, support for

reporting intervals, and reporting on components within a host.  As
noted above, we could be making progress on these in parallel to the
more basic work, particularly if the content was in separate I-Ds.

=20

[CV] What would now be in the initial product?  After reading your two
recent threads, I'm a little confused over what the "initial product"
is, as a definition and in its scope.

=20

[BN] Power Domain

=20

[BN] A system of power distribution with a common technology and fate.
Technologies are usually distinguished by voltages and whether AC or DC.
AC examples include 100V, 115V, 200V, and 230V.  DC examples include
380V, 48V, 24V, 12V, and 5V (variously including eMerge, PoE, USB, and
vehicle standards).  Increasingly communications go along with power,
but this is incidental to power reporting.

=20

[BN] Power domains are often in trees, but this is not strictly
required.  A domain with a single source may have a controller at its
root (e.g. a PoE switch), or not (e.g. a circuit breaker in a building).
At this time, we should consider domains as having a single source of
power; later we could relax that requirement.

=20

[BN] Common fate includes quality, reliability, availability, total
capacity, and price.  How devices learn what domain they are in is out
of our scope.

=20

[CV] With respect, this concept of a "Power Domain" is very limited to
the standard utility/facilities definition.  Given the advent of newer
reporting models and systems, should we extend this concept to simply
mean any logical grouping of power entities.  The mapping between power
domains and power entities can be many-to-many, not just one-to-many.

=20

[CV] For example, consider a deployment where the "power domain" is
segmented in two ways: (1) the physical infrastructure, taking into
account branch circuit and transformer capacities; and (2) the billing
structure, where entities are "grouped" according to who pays the costs.
If the MIB model only handles a 1:N mapping, the administrator needs to
choose only one.  If the MIB model handles a M:N mapping, more complex
and useful systems can be built on top of this schema.

=20

Enjoy Beijing,

Chris


------_=_NextPart_001_01CB7EE2.626A7A1B
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:"Lucida Grande";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:9.0pt;
	font-family:"Times New Roman","serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.balloontextchar0
	{mso-style-name:balloontextchar;
	font-family:"Lucida Grande";}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hi Bruce,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Questions and comments inline:<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[BN] </span><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif"'>As an =
observation, power state is a property of an individual device<span =
style=3D'color:#1F497D'> </span>and cannot be aggregated.&nbsp; Power =
level (W) and energy use can be<span style=3D'color:#1F497D'> =
</span>readily aggregated.<span =
style=3D'color:#1F497D'><o:p></o:p></span></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:.5in'><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[CV] With respect, I think power state can be aggregated.&nbsp; For =
example, please consider a standard datacenter.&nbsp; When all servers =
are turned on in the datacenter, it is at 100% &#8220;on&#8221; =
state.&nbsp; If 30% of the servers are turned off, the =
datacenter&#8217;s state has reduced to 70%.&nbsp; This is fairly =
congruous with the ACPI model, where a server can be in different =
states, and each state represents a power usage =
level.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:.5in'><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:.5in'><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[CV] How such aggregated state is determined is beyond the scope of =
any MIB, but the ability to report such information can offer a hook for =
innovation in the industry.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:.5in'><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:.5in'><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[CV] I agree that power state, like reporting meter data, could be =
pushed off to a later release, as enumerating the entities themselves is =
far more critical (core?) to establishing anything more =
complex.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[BN] </span><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif"'>There are =
a number of complications that I would propose deferring from our =
initial product.&nbsp; These include transition states, support =
for<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif"'>reporting =
intervals, and reporting on components within a host.<span =
style=3D'color:#1F497D'>&nbsp; </span>As noted above, we could be making =
progress on these in parallel to<span style=3D'color:#1F497D'> =
</span>the more basic work, particularly if the content was in separate =
I-Ds.<span style=3D'color:#1F497D'><o:p></o:p></span></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:.5in'><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[CV] What would now be in the initial product?&nbsp; After reading =
your two recent threads, I&#8217;m a little confused over what the =
&#8220;initial product&#8221; is, as a definition and in its =
scope.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[BN] </span><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif"'>Power =
Domain<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif"'>&nbsp;<o:p>=
</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[BN] </span><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif"'>A system =
of power distribution with a common technology and fate.&nbsp; =
Technologies<span style=3D'color:#1F497D'> </span>are usually =
distinguished by voltages and whether AC or DC.&nbsp; AC examples =
include 100V, 115V, 200V, and 230V.&nbsp; DC examples include 380V, 48V, =
24V, 12V, and 5V<span style=3D'color:#1F497D'> </span>(variously =
including eMerge, PoE, USB, and vehicle standards).&nbsp; =
Increasingly<span style=3D'color:#1F497D'> </span>communications go =
along with power, but this is incidental to power =
reporting.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif"'>&nbsp;<o:p>=
</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[BN] </span><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif"'>Power =
domains are often in trees, but this is not strictly required.&nbsp; A =
domain with<span style=3D'color:#1F497D'> </span>a single source may =
have a controller at its root (e.g. a PoE switch), or not (e.g.<span =
style=3D'color:#1F497D'> </span>a circuit breaker in a building).&nbsp; =
At this time, we should consider domains as having<span =
style=3D'color:#1F497D'> </span>a single source of power; later we could =
relax that requirement.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif"'>&nbsp;<o:p>=
</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[BN] </span><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif"'>Common =
fate includes quality, reliability, availability, total capacity, and =
price.<span style=3D'color:#1F497D'>&nbsp; </span>How devices learn what =
domain they are in is out of our scope.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif"'>&nbsp;<o:p>=
</o:p></span></p><p class=3DMsoNormal style=3D'margin-left:.5in'><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[CV] With respect, this concept of a &#8220;Power Domain&#8221; is =
very limited to the standard utility/facilities definition.&nbsp; Given =
the advent of newer reporting models and systems, should we extend this =
concept to simply mean any logical grouping of power entities.&nbsp; The =
mapping between power domains and power entities can be many-to-many, =
not just one-to-many.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:.5in'><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:.5in'><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>[CV] For example, consider a deployment where the &#8220;power =
domain&#8221; is segmented in two ways: (1) the physical infrastructure, =
taking into account branch circuit and transformer capacities; and (2) =
the billing structure, where entities are &#8220;grouped&#8221; =
according to who pays the costs.&nbsp; If the MIB model only handles a =
1:N mapping, the administrator needs to choose only one.&nbsp; If the =
MIB model handles a M:N mapping, more complex and useful systems can be =
built on top of this schema.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:.5in'><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Enjoy Beijing,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Chris<o:p></o:p></span></p></div></body></html>
------_=_NextPart_001_01CB7EE2.626A7A1B--

From bill.mielke@alcatel-lucent.com  Sun Nov  7 20:51:57 2010
Return-Path: <bill.mielke@alcatel-lucent.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3945428C0E4 for <eman@core3.amsl.com>; Sun,  7 Nov 2010 20:51:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7mnHS4Q2VW8s for <eman@core3.amsl.com>; Sun,  7 Nov 2010 20:51:27 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id 8486428C0F8 for <eman@ietf.org>; Sun,  7 Nov 2010 20:51:17 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id oA84pXRH023862 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 7 Nov 2010 22:51:33 -0600 (CST)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id oA84pWb1024014 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Sun, 7 Nov 2010 22:51:33 -0600
Received: from USNAVSXCHMBSA3.ndc.alcatel-lucent.com ([135.3.39.119]) by USNAVSXCHHUB01.ndc.alcatel-lucent.com ([135.3.39.110]) with mapi; Sun, 7 Nov 2010 22:51:32 -0600
From: "Mielke, William F (Bill)" <bill.mielke@alcatel-lucent.com>
To: Bruce Nordman <bnordman@lbl.gov>, "eman@ietf.org" <eman@ietf.org>
Date: Sun, 7 Nov 2010 22:51:21 -0600
Thread-Topic: [eman] Proposed alternation of framework
Thread-Index: Act+0N7Aic4FGhTCRdWZUO0aEJV53QAIJSEA
Message-ID: <0DEE3BCEE44BFD4EBC3B7DC009C8E79225064C324D@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
References: <AANLkTikFy7hzFSFtQonWZRXe_WAMbpZLLAGWrNjOVcFw@mail.gmail.com>
In-Reply-To: <AANLkTikFy7hzFSFtQonWZRXe_WAMbpZLLAGWrNjOVcFw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0005_01CB7ED6.ADDD8C70"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Subject: Re: [eman] Proposed alternation of framework
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 04:51:57 -0000

------=_NextPart_000_0005_01CB7ED6.ADDD8C70
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_0006_01CB7ED6.ADDD8C70"


------=_NextPart_001_0006_01CB7ED6.ADDD8C70
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hello all.  Being new to the IETF I have been mainly lurking on the EMAN
list until now.  I am in Beijing and will be attending the EMAN WG meeting
on Wednesday and look forward to meeting those who can attend face-to-face.
I am in the process of reading through the current drafts and should be
prepared to offer any insights or thoughts by the Wednesday meeting.
 
I want to thank everyone for their thought provoking contributions thus far
and look forward to working with you in this important area.
 
With that as an introduction I have provided some informal thoughts on
Bruce's comments in-line below.
 
Sincerely,

William F. Mielke
Alcatel-Lucent
Distinguished Member of Technical Staff
6200 East Broad Street
Room: 4B01-1V
Columbus, OH  43213-1530
Email:  <mailto:mielke@alcatel-lucent.com> Bill.Mielke@alcatel-lucent.com
Phone: 614 367 5628
Fax: 614 367 5965

"Live like you're going to die tomorrow.
 Learn like you're going to live forever."

    - Albert Einstein 

 

  _____  

From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of
Bruce Nordman
Sent: Sunday, November 07, 2010 6:10 PM
To: eman@ietf.org
Subject: [eman] Proposed alternation of framework


<< warning: long email >>



eman proposal for adjusting framework in current I-Ds

Bruce Nordman

November 7, 2010

 

The following takes the basic principles from the current I-Ds, and

makes a few changes that I see as making the framework simpler

and more transparent, and also provides some additional features.

It does not address control, nor many (future) optional features.

 

As an observation, power state is a property of an individual device

and cannot be aggregated.  Power level (W) and energy use can be

readily aggregated. 

 

[WFM] As Chris Verges has pointed out there may be some reasonable
approaches to state aggregation.  The ability to do so will depend to some
degree on the semantics and definition that are assigned to the term power
state. For example, a generic set of power states could be defined (along
with some concept of extensibility thereof) which each device is free to map
to a rough percentage of the total potential power consumption of that
device.  These values could be device specific and exposed through a MIB.
By mapping these values to a unitless quantity like a percentage we could
enable a useful form of aggregation for power states which can remain device
specific.

 

I am not advocating anything here, merely observing the possibility.

 

There are a number of complications that I would propose deferring 

from our initial product.  These include transition states, support for

reporting intervals, and reporting on components within a host.

As noted above, we could be making progress on these in parallel to

the more basic work, particularly if the content was in separate I-Ds. 

 

[WFM] I agree that we need to have some discussion of the first set of work
products from this group and a potential rollout of functions across those.
Reporting is a logical first step which could be addressed in isolation but
from my perspective power states and control mechanisms are key features of
any final working products this group must address.  I personally am
agnostic, however, on the specific timing of how these features are to be
rolled out across formal WG outputs.

 

There is nothing magic about the terminology used below and I am

sure it can be improved.

 

Basic concepts I propose are:

 

Powered Device

 

An electricity-using device that is almost always "atomic" - not 

separated into constituent parts that can be powered and function

autonomously in normal use.  They may have IP connectivity or lack it.

They may be able to report energy/power information themselves,

or rely on a power proxy to do this.  

 

Most devices have a single power source, no battery, and do not power 

other devices, so these just report a unitary notion of energy/power.  

Other devices have multiple power sources (from different electricity 

"domains"), an internal battery (which is functionally an additional
source), 

and/or downstream power loads (other devices; a battery that is charging 

is effectively an additional load).  Thus, these have the total net
consumption 

of the device itself, the power input from each source, and the power output

to each load.  The complexity required for these more complex devices

should not be burdensome on the simpler devices.  We need terms that

distinguish simple from complex devices; whether having a battery always 

makes a device complex I am not sure.

 

In addition to the information noted in the current I-Ds, a device is also a

member of a "Power Domain" (or more specifically, each power source is).

 

Power Proxy

 

A power proxy reports power/energy data on behalf of a second device.  

For purposes of energy management, it IS the device.  The second device

may or may not have IP connectivity, but in either case, all energy/power

information (including any subsidiary notion of identity) should come from

the proxy to the rest of the IP network.  In the long run, we should hope
that

fewer and fewer devices require a proxy, but for a considerable time we will

have devices that lack IP connectivity, or that have it but lack ability to
report

on their own power/energy status.

 

Note that a host may implement many power proxies; each proxy is logically

independent of the others.  It seems likely that any device that provides
proxy

services can report on its own power/energy status.  A proxy will almost
always

(perhaps always) be implemented by a Power Distributor, but proxying a
distinct 

function.

 

The proxy may be in the same domain as the second device, or a different
domain.

If in the same domain, the proxy may be in a device that distributes power
to the

second device, or not.  Thus, there are three possible relationships:
different domain,

powering (consequently same domain), not powering (but same domain).

 

Power Distributor

 

These consumes power themselves and distribute power to other devices, which

may include further distributors.  A distributor may have incomplete
information 

about downstream devices and their power consumption, missing identity,
power

consumption, or both, from some devices.  A distributor is a device, so may
have

more than one power source, and may include a battery.

 

It is helpful to first think of power being distributed along a tree
structure, with

parent and child controllers, but the structure need not be limited to
classic trees.

Other than batteries, at this time power flow is only in one direction (that
is, all

flows are either sources into a device, or sinks out of it). 

 

[WFM] While the concept of uni-directional flow is a nice simplifying
concept, and indeed it may be true at any particular instant in time, it is
not clear that this would be true in general for a given device over time.
The example that I am thinking of is a house with solar panels installed.
During the daytime on a sunny day these systems can produce more power than
is required which can then flow backwards through the main electric meter
and is thus "sold" back to the power utility on the main grid.  At night the
house then operates as normal with respect to the grid, or it may also
supplement its power needs via battery reserves which are typically
recharged via the solar panels during the day as well.

 

Whether this concept extends to other devices or uses in other alternative
energy scenarios remains to be seen.

 

This does raise the issue that the power flow on a given metering point may
actually be negative, something that may not be immediately obvious.  Using
the example of the house described above, the power meter provided by the
utility may actually report "negative KW" during the day and "positive KW"
at night.

 

A distributor may be in one power domain, but more commonly the downstream

powered devices will be in a different domain; a Power over Ethernet switch
is a

prime example of this.  Most commonly, each domain will have a single source
of

power (ignoring batteries), but this may not be required. 

 

[WFM] Interestingly, batteries are actually an interesting case.  In this
context I am speaking of rechargable batteries (not single use chemical
batteries which I suppose could be considered a specialized power
source/domain in their own right with their own environmental impacts).
Rechargable batteries have an internal resistance which will cause them to
discharge over time.  As such they are a load to the overall system.  When
they are being utilized as a temporary power source they are depleting their
internal reserves which must ultimately be restored from some other primary
power source.  So the environmental footprint of a battery is ultimately
tied to the primary energy source which is used to charge it.  Solar cells
would have one carbon footprint, whereas a coal burning power plant would
have another.  This suggests to me that carbon footprint of a battery is
ultimately tied back to the primary source used to charge it, which could
vary over time (i.e. it may typically be recharged from solar cells when
they are available and producing power, or from the power utility
otherwise).

 

So if on one day they happen to be recharged via the solar cells their
instantaneous carbon footprint at that point in time would be zero, whereas
if on a differnt day they happened to be recharged from utility power their
carbon footprint would be a function of the utility's carbon load.

 

Whether we need or indeed want to produce a standard which can reasonably
account for such cases or not is something that we will need to decide.
Perhaps initially not, but as alternative energy sources become a larger
part of every day life these may become important.

 

This then raises the question of whether our power reporting mechanism can
or should account for allowing each device to report it's own carbon impact
to facilitate a more meaningful form of aggregation.  This in turn raises
the question of how a given device would even know what it's carbon impact
was since this is a function/attribute of the source.

 

I am not personally at a point of advocating any particular position on
these issues.  I am merely raising them for consideration.  The direction we
take will have downstream consequences.

 

 

Power Domain

 

A system of power distribution with a common technology and fate.
Technologies

are usually distinguished by voltages and whether AC or DC.  AC examples
include 

100V, 115V, 200V, and 230V.  DC examples include 380V, 48V, 24V, 12V, and 5V

(variously including eMerge, PoE, USB, and vehicle standards).  Increasingly

communications go along with power, but this is incidental to power
reporting.

 

Power domains are often in trees, but this is not strictly required.  A
domain with

a single source may have a controller at its root (e.g. a PoE switch), or
not (e.g.

a circuit breaker in a building).  At this time, we should consider domains
as having

a single source of power; later we could relax that requirement.

 

Common fate includes quality, reliability, availability, total capacity, and
price.

How devices learn what domain they are in is out of our scope. 

 

[WFM] This seems a reason simplifying assumption for a first version of the
standard but long term we may wish to consider scenarios where the devices
query their sources as well as vice versa. 

 

Power Manager

 

This concept is NOT defined in our standard, but is a key expected user of

the facility.  It is an interested entity and has no specific relation to
device.

It may be in the same power domain, or not.

 

A power manager will commonly send out a broadcast request to all devices 

in a power domain and ask for current information.  In this case, a
distributor is 

not involved in the request for that function, though a device which is a
distributor 

will report its own (net) consumption, and may implement proxies that
respond 

to this request. 

 

[WFM] I agree that discovery mechanisms such as the one you describe are
something that we will need to take account of.  This is true even for
common reporting use cases.

 

To avoid double-counting, the manager needs to know what domains provide 

power to others).  A manager may use distributors that are gateways between

domains as aggregators, and so not bothering to query devices in the second

domain at all, or as often.  For example, the domain that a PoE switch is in
may

be queried more often than the domain of devices powered by that switch.

 

Other Notes

 

This system has no concept of a meter.  Rather, a meter is a distributor,
and

today's meters don't have direct knowledge of what they are providing power
to

(remember that a distributor can have incomplete knowledge, including none).

 

A key point is that there is no assumed relationship between the power
distribution

topology and the communications topology. 

 

[WFM] Agreed.  The two are completely distinct.  To the extent that
management systems will need to understand both we may wish to consider
whether the power reporting capabilities we define are capable of providing
the information necessary to enable them to discern the structure of the
power distribution topology when devices have been configured with such
information.

 

This is also something that we will need to decide if it is in or out of
scope for our efforts. 

 

Somewhere, attention needs to be paid to wire losses - there is a difference

between power supplied to a device, and power consumed by one.   When

measurement is done at both ends of the wire, it can be calculated, but more

commonly, the measurement is done at only one end so just needs to have a

flag for which it is.

 

Power data are allowed to be estimated by a device from knowledge it has

rather than directly measured.  This is then noted in accuracy reporting.

Power estimation may be as important as proxying in the coming years.

 

Communication

 

The core definition is what information a device provides when queried.

A proxy IS the device for these purposes, so responds the same as a direct

device (with a flag somewhere noting it is a proxy in case someone cares).

A distributor is a device so responds the same way as a simple device
(albeit

with more complexity to the response).

 

Distributors may find it helpful to query devices they supply power to, but

this is simply a usage of our facility, not a separate mechanism.

 

Because control and intervals are not implemented, communication is only

in one direction. 

 

[WFM] I understand your comment and why you make it given your stated
assumptions regarding scope.  I would hope that intervals might actually
still be addressed from a reporting perspective even if only based on
default intervals defined by the standard, or by enabling device specific
default intervals coupled with a means of reporting the durations thereof.
Without some device maintained means of reporting historical information the
per device polling overhead introduced on the communications network is
likely to be far greater than is actually required for efficient operations.
In addition, enabling the devices to report historical information
decentralizes the collection of the raw data and removes the need for
"tight" timing constraints on the actual polling of the devices making the
system more tolerant of network outages and delays.

 

Usage examples

 

Most common today is devices on mains AC power in which a domain is

a circuit breaker, a larger area (e.g. zone or floor of a building), or an
entire

building.  A vehicle is a building on wheels (and always its own domain).

 

PoE necessarily creates a different domain.   Usually all devices powered

from a PoE switch are in the same domain.  PoE switches usually have a

capacity constraint distinct from that of the domain it is part of.

 

A UPS has a distinct domain downstream of it from its mains power source,

as the fate of these devices is different from what the UPS sees from its
primary

source.

 

Other Other Notes

 

There is no distinction by building type (home, commercial, vehicle) in any

of this.

 

Likely none of this affects the battery MIB proposal.

 

Many control approaches will include distribution a price (and price
forecast)

to devices.  Prices will be by domain, as they may vary.  For example, UPS
will

have its own price when off-grid.  PoE devices may get higher price if
switch

is near capacity.  People in charge of a domain may want to impose their own

carbon taxes implicitly.  Local batteries/generation may raise or lower the
price

otherwise seen on a domain.  Price distribution NOT part of the energy/power

reporting mechanism, though will use the same domain concept.  There is a 

standard for getting a price to a building - my concern is only local
distribution

of a price within a building or a domain. 

 

[WFM] In addition to pricing a parallel concept exists for reporting of the
carbon loading.  Agreed?  From a reporting perspective enabling a reasonable
ability to distribute such cost and environmental data from the sources to
the ultimate sinks would seem to be a significant goal of this work. 


-- 
Bruce Nordman
Lawrence Berkeley National Laboratory
eetd.lbl.gov/ea/nordman
BNordman@LBL.gov
510-486-7089
m: 510-501-7943



------=_NextPart_001_0006_01CB7ED6.ADDD8C70
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dus-ascii" =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.18939"></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D706590203-08112010>Hello all.&nbsp; Being new to the IETF I have =
been=20
mainly lurking on the EMAN list until now.&nbsp; I am in Beijing and =
will be=20
attending the EMAN WG meeting on Wednesday and look forward to meeting =
those who=20
can attend face-to-face.&nbsp; I am in the process of reading through =
the=20
current drafts and should be prepared to offer any insights or thoughts =
by the=20
Wednesday meeting.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D706590203-08112010></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D706590203-08112010>I want to thank everyone for their thought =
provoking=20
contributions thus far and look forward to working with you in this =
important=20
area.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D706590203-08112010></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D706590203-08112010>With that as an introduction I have provided =
some=20
informal&nbsp;thoughts on Bruce's comments in-line =
below.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D706590203-08112010></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT color=3D#0000ff size=3D2 =
face=3DArial><SPAN=20
class=3D706590203-08112010>Sincerely,</SPAN></FONT></DIV><!-- Converted =
from text/rtf format -->
<P><SPAN lang=3Den-us><FONT size=3D2 face=3D"Courier New">William F.=20
Mielke<BR>Alcatel-Lucent<BR>Distinguished Member of Technical =
Staff<BR>6200 East=20
Broad Street<BR>Room: 4B01-1V<BR>Columbus, OH&nbsp; =
43213-1530<BR>Email:</FONT>=20
</SPAN><A href=3D"mailto:mielke@alcatel-lucent.com"><SPAN=20
lang=3Den-us><U></U><U></U><U><FONT color=3D#0000ff size=3D2=20
face=3D"Courier =
New">Bill.Mielke@alcatel-lucent.com</FONT></U></SPAN></A><SPAN=20
lang=3Den-us><BR><FONT size=3D2 face=3D"Courier New">Phone: 614 367 =
5628<BR>Fax: 614=20
367 5965<BR><BR>"Live like you're going to die tomorrow.<BR>&nbsp;Learn =
like=20
you're going to live forever."<BR><BR>&nbsp;&nbsp;&nbsp; - Albert=20
Einstein</FONT></SPAN> </P>
<DIV>&nbsp;</DIV><BR>
<DIV dir=3Dltr lang=3Den-us class=3DOutlookMessageHeader align=3Dleft>
<HR tabIndex=3D-1>
<FONT size=3D2 face=3DTahoma><B>From:</B> eman-bounces@ietf.org=20
[mailto:eman-bounces@ietf.org] <B>On Behalf Of </B>Bruce =
Nordman<BR><B>Sent:</B>=20
Sunday, November 07, 2010 6:10 PM<BR><B>To:</B> =
eman@ietf.org<BR><B>Subject:</B>=20
[eman] Proposed alternation of framework<BR></FONT><BR></DIV>
<DIV></DIV><SPAN style=3D"COLOR: rgb(102,0,204)">&lt;&lt; warning: long =
email=20
&gt;&gt;</SPAN><BR><BR>
<STYLE>@font-face {
  font-family: "Cambria";
}@font-face {
  font-family: "Lucida Grande";
}p.MsoNormal, li.MsoNormal, div.MsoNormal { margin: 0in 0in 0.0001pt; =
font-size: 12pt; font-family: "Times New Roman"; }p.MsoAcetate, =
li.MsoAcetate, div.MsoAcetate { margin: 0in 0in 0.0001pt; font-size: =
9pt; font-family: "Times New Roman"; }span.BalloonTextChar { =
font-family: "Lucida Grande"; }div.Section1 { page: Section1; }</STYLE>

<P class=3DMsoNormal>eman proposal for adjusting framework in current =
I-Ds</P>
<P class=3DMsoNormal>Bruce Nordman</P>
<P class=3DMsoNormal>November 7, 2010</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>The following takes the basic principles from the =
current=20
I-Ds, and</P>
<P class=3DMsoNormal>makes a few changes that I see as making the =
framework=20
simpler</P>
<P class=3DMsoNormal>and more transparent, and also provides some =
additional=20
features.</P>
<P class=3DMsoNormal>It does not address control, nor many (future) =
optional=20
features.</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>As an observation, power state is a property of an =
individual=20
device</P>
<P class=3DMsoNormal>and cannot be aggregated.<SPAN>&nbsp; </SPAN>Power =
level (W)=20
and energy use can be</P>
<P class=3DMsoNormal>readily aggregated.<SPAN =
class=3D706590203-08112010><FONT=20
color=3D#0000ff size=3D2 face=3DArial>&nbsp;</FONT></SPAN></P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010></SPAN>&nbsp;</P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial>[WFM] As Chris Verges has pointed out there may be some =
reasonable=20
approaches to state aggregation.&nbsp; The ability to do so =
will&nbsp;depend to=20
some degree on the semantics and definition that are assigned to the =
term power=20
state.</FONT>&nbsp;<FONT color=3D#0000ff size=3D2 face=3DArial>For =
example, a generic=20
set of power states could be defined (along with&nbsp;some concept of=20
extensibility thereof) which each device is free to map to a rough =
percentage of=20
the total potential power consumption of that device.&nbsp; These values =
could=20
be device specific and exposed through a MIB.&nbsp; By mapping these =
values to a=20
unitless quantity like a percentage we could enable a useful form of =
aggregation=20
for power states which can remain device specific.</FONT></SPAN></P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial></FONT></SPAN>&nbsp;</P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial>I am not advocating anything here, merely observing the=20
possibility.</FONT></SPAN></P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>There are a number of complications that I would =
propose=20
deferring </P>
<P class=3DMsoNormal>from our initial product.<SPAN>&nbsp; </SPAN>These =
include=20
transition states, support for</P>
<P class=3DMsoNormal>reporting intervals, and reporting on components =
within a=20
host.</P>
<P class=3DMsoNormal>As noted above, we could be making progress on =
these in=20
parallel to</P>
<P class=3DMsoNormal>the more basic work, particularly if the content =
was in=20
separate I-Ds.<SPAN class=3D706590203-08112010><FONT color=3D#0000ff =
size=3D2=20
face=3DArial>&nbsp;</FONT></SPAN></P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010></SPAN>&nbsp;</P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial>[WFM] I&nbsp;agree that we need to have some discussion of =
the first=20
set of work products from this group and a potential rollout of =
functions across=20
those.</FONT>&nbsp;<FONT color=3D#0000ff size=3D2 face=3DArial>Reporting =
is a logical=20
first step which could be addressed in isolation but from my perspective =
power=20
states and control mechanisms are key features of any final working =
products=20
this group must address.&nbsp; I personally am agnostic, =
however,&nbsp;on the=20
specific timing of&nbsp;how these features are to be rolled out across =
formal WG=20
outputs.</FONT></SPAN></P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>There is nothing magic about the terminology used =
below and I=20
am</P>
<P class=3DMsoNormal>sure it can be improved.</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>Basic concepts I propose are:</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>Powered Device</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>An electricity-using device that is almost always =
&#8220;atomic&#8221; &#8211;=20
not </P>
<P class=3DMsoNormal>separated into constituent parts that can be =
powered and=20
function</P>
<P class=3DMsoNormal>autonomously in normal use.<SPAN>&nbsp; </SPAN>They =
may have=20
IP connectivity or lack it.</P>
<P class=3DMsoNormal>They may be able to report energy/power information =

themselves,</P>
<P class=3DMsoNormal>or rely on a power proxy to do this.<SPAN>&nbsp; =
</SPAN></P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>Most devices have a single power source, no =
battery, and do=20
not power </P>
<P class=3DMsoNormal>other devices, so these just report a unitary =
notion of=20
energy/power.<SPAN>&nbsp; </SPAN></P>
<P class=3DMsoNormal>Other devices have multiple power sources (from =
different=20
electricity </P>
<P class=3DMsoNormal>&#8220;domains&#8221;), an internal battery (which =
is functionally an=20
additional source), </P>
<P class=3DMsoNormal>and/or downstream power loads (other devices; a =
battery that=20
is charging </P>
<P class=3DMsoNormal>is effectively an additional load).<SPAN>&nbsp; =
</SPAN>Thus,=20
these have the total net consumption </P>
<P class=3DMsoNormal>of the device itself, the power input from each =
source, and=20
the power output</P>
<P class=3DMsoNormal>to each load.<SPAN>&nbsp; </SPAN>The complexity =
required for=20
these more complex devices</P>
<P class=3DMsoNormal>should not be burdensome on the simpler =
devices.<SPAN>&nbsp;=20
</SPAN>We need terms that</P>
<P class=3DMsoNormal>distinguish simple from complex devices; whether =
having a=20
battery always </P>
<P class=3DMsoNormal>makes a device complex I am not sure.</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>In addition to the information noted in the current =
I-Ds, a=20
device is also a</P>
<P class=3DMsoNormal>member of a &#8220;Power Domain&#8221; (or more =
specifically, each power=20
source is).</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>Power Proxy</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>A power proxy reports power/energy data on behalf =
of a second=20
device.<SPAN>&nbsp; </SPAN></P>
<P class=3DMsoNormal>For purposes of energy management, it IS the=20
device.<SPAN>&nbsp; </SPAN>The second device</P>
<P class=3DMsoNormal>may or may not have IP connectivity, but in either =
case, all=20
energy/power</P>
<P class=3DMsoNormal>information (including any subsidiary notion of =
identity)=20
should come from</P>
<P class=3DMsoNormal>the proxy to the rest of the IP =
network.<SPAN>&nbsp;=20
</SPAN>In the long run, we should hope that</P>
<P class=3DMsoNormal>fewer and fewer devices require a proxy, but for a=20
considerable time we will</P>
<P class=3DMsoNormal>have devices that lack IP connectivity, or that =
have it but=20
lack ability to report</P>
<P class=3DMsoNormal>on their own power/energy status.</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>Note that a host may implement many power proxies; =
each proxy=20
is logically</P>
<P class=3DMsoNormal>independent of the others.<SPAN>&nbsp; </SPAN>It =
seems likely=20
that any device that provides proxy</P>
<P class=3DMsoNormal>services can report on its own power/energy=20
status.<SPAN>&nbsp; </SPAN>A proxy will almost always</P>
<P class=3DMsoNormal>(perhaps always) be implemented by a Power =
Distributor, but=20
proxying a distinct </P>
<P class=3DMsoNormal>function.</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>The proxy may be in the same domain as the second =
device, or=20
a different domain.</P>
<P class=3DMsoNormal>If in the same domain, the proxy may be in a device =
that=20
distributes power to the</P>
<P class=3DMsoNormal>second device, or not.<SPAN>&nbsp; </SPAN>Thus, =
there are=20
three possible relationships: different domain,</P>
<P class=3DMsoNormal>powering (consequently same domain), not powering =
(but same=20
domain).</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>Power Distributor</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>These consumes power themselves and distribute =
power to other=20
devices, which</P>
<P class=3DMsoNormal>may include further distributors.<SPAN>&nbsp; =
</SPAN>A=20
distributor may have incomplete information </P>
<P class=3DMsoNormal>about downstream devices and their power =
consumption, missing=20
identity, power</P>
<P class=3DMsoNormal>consumption, or both, from some =
devices.<SPAN>&nbsp; </SPAN>A=20
distributor is a device, so may have</P>
<P class=3DMsoNormal>more than one power source, and may include a =
battery.</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>It is helpful to first think of power being =
distributed along=20
a tree structure, with</P>
<P class=3DMsoNormal>parent and child controllers, but the structure =
need not be=20
limited to classic trees.</P>
<P class=3DMsoNormal>Other than batteries, at this time power flow is =
only in one=20
direction (that is, all</P>
<P class=3DMsoNormal>flows are either sources into a device, or sinks =
out of=20
it).<SPAN class=3D706590203-08112010><FONT color=3D#0000ff size=3D2=20
face=3DArial>&nbsp;</FONT></SPAN></P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010></SPAN>&nbsp;</P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial>[WFM] While the concept of uni-directional =
flow</FONT>&nbsp;<FONT=20
color=3D#0000ff size=3D2 face=3DArial>is a nice simplifying concept, and =
indeed it may=20
be true at any particular instant in time, it is not clear that this =
would be=20
true in general for a given device over time.&nbsp; The example that I =
am=20
thinking of is a house with solar panels installed.&nbsp; During the =
daytime on=20
a sunny day these systems can produce more power than is required which =
can then=20
flow backwards through the main electric meter and is thus "sold" back =
to the=20
power utility on the main grid.&nbsp; At night the house then operates =
as normal=20
with respect to the grid, or it may also supplement its power needs via =
battery=20
reserves which are typically recharged via the solar panels during the =
day as=20
well.</FONT></SPAN></P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial></FONT></SPAN>&nbsp;</P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial>Whether this concept extends to other devices or uses in =
other=20
alternative energy scenarios remains to be seen.</FONT></SPAN></P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial></FONT></SPAN>&nbsp;</P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial>This does raise the issue that the power flow on a given =
metering=20
point may actually be negative, something that may not be immediately=20
obvious.&nbsp; Using the example of the house described above, the power =
meter=20
provided by the utility may actually report "negative KW" during the day =
and=20
"positive KW" at night.</FONT></SPAN></P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>A distributor may be in one power domain, but more =
commonly=20
the downstream</P>
<P class=3DMsoNormal>powered devices will be in a different domain; a =
Power over=20
Ethernet switch is a</P>
<P class=3DMsoNormal>prime example of this.<SPAN>&nbsp; </SPAN>Most =
commonly, each=20
domain will have a single source of</P>
<P class=3DMsoNormal>power (ignoring batteries), but this may not be=20
required.<SPAN class=3D706590203-08112010><FONT color=3D#0000ff size=3D2 =

face=3DArial>&nbsp;</FONT></SPAN></P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010></SPAN>&nbsp;</P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial>[WFM] Interestingly, batteries are actually an interesting=20
case.&nbsp; In this context I am speaking of rechargable batteries (not =
single=20
use chemical batteries which I suppose could be considered a specialized =
power=20
source/domain in their own right with their own environmental =
impacts).&nbsp;=20
Rechargable batteries have an internal resistance which will cause them =
to=20
discharge over time.&nbsp; As such they are a load to the overall =
system.&nbsp;=20
When they are being utilized as a temporary power source they are =
depleting=20
their internal reserves which must ultimately be restored from some =
other=20
primary power source.&nbsp; So the environmental footprint of a battery =
is=20
ultimately tied to the primary energy source which is used to charge =
it.&nbsp;=20
Solar cells would have one carbon footprint, whereas a coal burning =
power plant=20
would have another.&nbsp; This suggests to me that carbon footprint of a =
battery=20
is ultimately tied back to the primary source used to charge it, which =
could=20
vary over time (i.e. it may typically be recharged from solar cells when =
they=20
are available and producing power, or from the power utility=20
otherwise).</FONT></SPAN></P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial></FONT></SPAN>&nbsp;</P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial>So if on one day they happen to be recharged via the solar =
cells=20
their instantaneous carbon footprint at that point in time would be =
zero,=20
whereas if on a differnt day they happened to be recharged from utility =
power=20
their carbon footprint would be a function of the utility's carbon=20
load.</FONT></SPAN></P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial></FONT></SPAN>&nbsp;</P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial>Whether we need or indeed want to produce a standard which =
can=20
reasonably account for such cases or not is something that we will need =
to=20
decide.&nbsp; Perhaps initially not, but as alternative energy sources =
become a=20
larger part of every day life these may become =
important.</FONT></SPAN></P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial></FONT></SPAN>&nbsp;</P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial>This then raises the question of whether our power =
reporting=20
mechanism can or should account for allowing each device to report it's =
own=20
carbon impact to facilitate a more meaningful form of aggregation.&nbsp; =
This in=20
turn raises the question of how a given device would even know what it's =
carbon=20
impact was since this is a function/attribute of the =
source.</FONT></SPAN></P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial></FONT></SPAN>&nbsp;</P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial>I am not personally at a point of advocating any particular =
position=20
on these issues.&nbsp; I am merely raising them for consideration.&nbsp; =
The=20
direction we take will have downstream consequences.</FONT></SPAN></P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial></FONT></SPAN>&nbsp;</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>Power Domain</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>A system of power distribution with a common =
technology and=20
fate.<SPAN>&nbsp; </SPAN>Technologies</P>
<P class=3DMsoNormal>are usually distinguished by voltages and whether =
AC or=20
DC.<SPAN>&nbsp; </SPAN>AC examples include </P>
<P class=3DMsoNormal>100V, 115V, 200V, and 230V.<SPAN>&nbsp; </SPAN>DC =
examples=20
include 380V, 48V, 24V, 12V, and 5V</P>
<P class=3DMsoNormal>(variously including eMerge, PoE, USB, and vehicle=20
standards).<SPAN>&nbsp; </SPAN>Increasingly</P>
<P class=3DMsoNormal>communications go along with power, but this is =
incidental to=20
power reporting.</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>Power domains are often in trees, but this is not =
strictly=20
required.<SPAN>&nbsp; </SPAN>A domain with</P>
<P class=3DMsoNormal>a single source may have a controller at its root =
(e.g. a PoE=20
switch), or not (e.g.</P>
<P class=3DMsoNormal>a circuit breaker in a building).<SPAN>&nbsp; =
</SPAN>At this=20
time, we should consider domains as having</P>
<P class=3DMsoNormal>a single source of power; later we could relax that =

requirement.</P>
<P class=3DMsoNormal><SPAN></SPAN>&nbsp;</P>
<P class=3DMsoNormal>Common fate includes quality, reliability, =
availability,=20
total capacity, and price.</P>
<P class=3DMsoNormal>How devices learn what domain they are in is out of =
our=20
scope.<SPAN class=3D706590203-08112010><FONT color=3D#0000ff size=3D2=20
face=3DArial>&nbsp;</FONT></SPAN></P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010></SPAN>&nbsp;</P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial>[WFM] This seems a reason simplifying assumption for a =
first version=20
of the standard but long term we may wish to consider scenarios where =
the=20
devices query their sources as well as vice =
versa.</FONT>&nbsp;</SPAN></P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>Power Manager</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>This concept is NOT defined in our standard, but is =
a key=20
expected user of</P>
<P class=3DMsoNormal>the facility.<SPAN>&nbsp; </SPAN>It is an =
interested entity=20
and has no specific relation to device.</P>
<P class=3DMsoNormal>It may be in the same power domain, or not.</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>A power manager will commonly send out a broadcast =
request to=20
all devices </P>
<P class=3DMsoNormal>in a power domain and ask for current=20
information.<SPAN>&nbsp; </SPAN>In this case, a distributor is </P>
<P class=3DMsoNormal>not involved in the request for that function, =
though a=20
device which is a distributor </P>
<P class=3DMsoNormal>will report its own (net) consumption, and may =
implement=20
proxies that respond </P>
<P class=3DMsoNormal>to this request.<SPAN =
class=3D706590203-08112010><FONT=20
color=3D#0000ff size=3D2 face=3DArial>&nbsp;</FONT></SPAN></P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010></SPAN>&nbsp;</P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial>[WFM] I agree that discovery mechanisms such as&nbsp;the =
one=20
you&nbsp;describe are something that we will need to take account =
of.&nbsp; This=20
is true even for common reporting use cases.</FONT></SPAN></P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>To avoid double-counting, the manager needs to know =
what=20
domains provide </P>
<P class=3DMsoNormal>power to others).<SPAN>&nbsp; </SPAN>A manager may =
use=20
distributors that are gateways between</P>
<P class=3DMsoNormal>domains as aggregators, and so not bothering to =
query devices=20
in the second</P>
<P class=3DMsoNormal>domain at all, or as often.<SPAN>&nbsp; </SPAN>For =
example,=20
the domain that a PoE switch is in may</P>
<P class=3DMsoNormal>be queried more often than the domain of devices =
powered by=20
that switch.</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>Other Notes</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>This system has no concept of a meter.<SPAN>&nbsp;=20
</SPAN>Rather, a meter is a distributor, and</P>
<P class=3DMsoNormal>today&#8217;s meters don&#8217;t have direct =
knowledge of what they are=20
providing power to</P>
<P class=3DMsoNormal>(remember that a distributor can have incomplete =
knowledge,=20
including none).</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>A key point is that there is no assumed =
relationship between=20
the power distribution</P>
<P class=3DMsoNormal>topology and the communications topology.<SPAN=20
class=3D706590203-08112010><FONT color=3D#0000ff size=3D2=20
face=3DArial>&nbsp;</FONT></SPAN></P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010></SPAN>&nbsp;</P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial>[WFM] Agreed.&nbsp; The two are completely distinct.&nbsp; =
To the=20
extent that management systems will need to understand both we may wish =
to=20
consider whether the power reporting capabilities we define are capable =
of=20
providing the information necessary to enable them to discern the =
structure of=20
the power distribution topology when devices have been configured with =
such=20
information.</FONT></SPAN></P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010></SPAN>&nbsp;</P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial>This is also something that we will need to decide if it is =
in or out=20
of scope for our efforts.</FONT>&nbsp;</SPAN></P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>Somewhere, attention needs to be paid to wire =
losses &#8211; there=20
is a difference</P>
<P class=3DMsoNormal>between power supplied to a device, and power =
consumed by=20
one.<SPAN>&nbsp;&nbsp; </SPAN>When</P>
<P class=3DMsoNormal>measurement is done at both ends of the wire, it =
can be=20
calculated, but more</P>
<P class=3DMsoNormal>commonly, the measurement is done at only one end =
so just=20
needs to have a</P>
<P class=3DMsoNormal>flag for which it is.</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>Power data are allowed to be estimated by a device =
from=20
knowledge it has</P>
<P class=3DMsoNormal>rather than directly measured.<SPAN>&nbsp; =
</SPAN>This is=20
then noted in accuracy reporting.</P>
<P class=3DMsoNormal>Power estimation may be as important as proxying in =
the=20
coming years.</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>Communication</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>The core definition is what information a device =
provides=20
when queried.</P>
<P class=3DMsoNormal>A proxy IS the device for these purposes, so =
responds the=20
same as a direct</P>
<P class=3DMsoNormal>device (with a flag somewhere noting it is a proxy =
in case=20
someone cares).</P>
<P class=3DMsoNormal>A distributor is a device so responds the same way =
as a=20
simple device (albeit</P>
<P class=3DMsoNormal>with more complexity to the response).</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>Distributors may find it helpful to query devices =
they supply=20
power to, but</P>
<P class=3DMsoNormal>this is simply a usage of our facility, not a =
separate=20
mechanism.</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>Because control and intervals are not implemented,=20
communication is only</P>
<P class=3DMsoNormal>in one direction.<SPAN =
class=3D706590203-08112010><FONT=20
color=3D#0000ff size=3D2 face=3DArial>&nbsp;</FONT></SPAN></P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010></SPAN>&nbsp;</P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial>[WFM] I understand your comment and why you make it given =
your stated=20
assumptions regarding scope.&nbsp; I would hope that intervals might =
actually=20
still be addressed&nbsp;from a reporting perspective even if only based =
on=20
default intervals defined by the standard, or by enabling device =
specific=20
default intervals</FONT>&nbsp;<FONT color=3D#0000ff size=3D2 =
face=3DArial>coupled with=20
a means of reporting the durations thereof.&nbsp; Without some device =
maintained=20
means of reporting historical information the per device polling =
overhead=20
introduced on the communications network is likely to be far greater =
than is=20
actually required for efficient operations.&nbsp; In addition, enabling =
the=20
devices to report historical information decentralizes the collection of =
the raw=20
data and removes the need for "tight" timing constraints on the actual =
polling=20
of the devices making the system more tolerant of network outages and=20
delays.</FONT></SPAN></P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>Usage examples</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>Most common today is devices on mains AC power in =
which a=20
domain is</P>
<P class=3DMsoNormal>a circuit breaker, a larger area (e.g. zone or =
floor of a=20
building), or an entire</P>
<P class=3DMsoNormal>building.<SPAN>&nbsp; </SPAN>A vehicle is a =
building on=20
wheels (and always its own domain).</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>PoE necessarily creates a different =
domain.<SPAN>&nbsp;&nbsp;=20
</SPAN>Usually all devices powered</P>
<P class=3DMsoNormal>from a PoE switch are in the same =
domain.<SPAN>&nbsp;=20
</SPAN>PoE switches usually have a</P>
<P class=3DMsoNormal>capacity constraint distinct from that of the =
domain it is=20
part of.</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>A UPS has a distinct domain downstream of it from =
its mains=20
power source,</P>
<P class=3DMsoNormal>as the fate of these devices is different from what =
the UPS=20
sees from its primary</P>
<P class=3DMsoNormal>source.</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>Other Other Notes</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>There is no distinction by building type (home, =
commercial,=20
vehicle) in any</P>
<P class=3DMsoNormal>of this.</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>Likely none of this affects the battery MIB =
proposal.</P>
<P class=3DMsoNormal>&nbsp;</P>
<P class=3DMsoNormal>Many control approaches will include distribution a =
price=20
(and price forecast)</P>
<P class=3DMsoNormal>to devices.<SPAN>&nbsp; </SPAN>Prices will be by =
domain, as=20
they may vary.<SPAN>&nbsp; </SPAN>For example, UPS will</P>
<P class=3DMsoNormal>have its own price when off-grid.<SPAN>&nbsp; =
</SPAN>PoE=20
devices may get higher price if switch</P>
<P class=3DMsoNormal>is near capacity.<SPAN>&nbsp; </SPAN>People in =
charge of a=20
domain may want to impose their own</P>
<P class=3DMsoNormal>carbon taxes implicitly.<SPAN>&nbsp; </SPAN>Local=20
batteries/generation may raise or lower the price</P>
<P class=3DMsoNormal>otherwise seen on a domain.<SPAN>&nbsp; =
</SPAN>Price=20
distribution NOT part of the energy/power</P>
<P class=3DMsoNormal>reporting mechanism, though will use the same =
domain=20
concept.<SPAN>&nbsp; </SPAN>There is a </P>
<P class=3DMsoNormal>standard for getting a price to a building &#8211; =
my concern is=20
only local distribution</P>
<P class=3DMsoNormal>of a price within a building or a domain.<SPAN=20
class=3D706590203-08112010><FONT color=3D#0000ff size=3D2=20
face=3DArial>&nbsp;</FONT></SPAN></P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010></SPAN>&nbsp;</P>
<P class=3DMsoNormal><SPAN class=3D706590203-08112010><FONT =
color=3D#0000ff size=3D2=20
face=3DArial>[WFM] In addition to pricing a parallel concept exists=20
for&nbsp;reporting of the carbon loading.&nbsp; Agreed?&nbsp; From a =
reporting=20
perspective enabling a reasonable ability to distribute such cost and=20
environmental data from the sources to the&nbsp;ultimate sinks would =
seem to be=20
a significant goal of this work.</FONT>&nbsp;</SPAN></P><BR>-- <BR><FONT =

size=3D4><B>Bruce Nordman</B></FONT><BR><SPAN style=3D"COLOR: =
rgb(0,0,153)">Lawrence=20
Berkeley National Laboratory</SPAN><BR><A =
href=3D"http://eetd.lbl.gov/ea/nordman"=20
target=3D_blank>eetd.lbl.gov/ea/nordman</A><BR>BNordman@LBL.gov<BR>510-48=
6-7089<BR>m:=20
510-501-7943<BR><BR></BODY></HTML>

------=_NextPart_001_0006_01CB7ED6.ADDD8C70--

------=_NextPart_000_0005_01CB7ED6.ADDD8C70
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIV8jCCA7Ew
ggKZoAMCAQICEBErBTlXKN63QvT+VRPTt1EwDQYJKoZIhvcNAQEFBQAwQzEXMBUGA1UEChMOQWxj
YXRlbCBMdWNlbnQxKDAmBgNVBAMTH0FsY2F0ZWwgTHVjZW50IEludGVybmFsIFJvb3QgQ0EwHhcN
MDgxMTAzMTU0MTE2WhcNMjgxMTAzMTU0MTE2WjBDMRcwFQYDVQQKEw5BbGNhdGVsIEx1Y2VudDEo
MCYGA1UEAxMfQWxjYXRlbCBMdWNlbnQgSW50ZXJuYWwgUm9vdCBDQTCCASIwDQYJKoZIhvcNAQEB
BQADggEPADCCAQoCggEBAL5IGBVth8afQdnpuLDI0Z37GgIcPWznOOzFJUV1gVbztqQ5CIxkVL4K
soAfLzc8LQHqNl2Nk3YbVBputIyCe2nzGsRjQeVt+HO2PV7h2YpMQlVd+XGsmpJ4fAP3A38wkTl6
tFPAYspyUFvjNON1J3BJE/2cuY7apvn9ZfSz99x7y4QBZh3hvm4g5Fn7mK04/q7K6O4Z8Y6zkSxG
ZFNyZ6NIuAPNCODZASqYnHiAgtEcCR4WPs6rj+Y8MU0q56ddwuIZ0qeP2ScHY0wVtnmqXzHyCzEQ
Eb2eJCsGpXFwUalVaxPUZEVoVDfjO+2ZN5gNJrGMTu7Mv9k1WG0LR3zZ1QsCAwEAAaOBoDCBnTAL
BgNVHQ8EBAMCAYYwDwYDVR0TAQH/BAUwAwEB/zAdBgNVHQ4EFgQUB6yyWvZhiXxcfOvilycpaQyK
H/AwEAYJKwYBBAGCNxUBBAMCAQAwTAYDVR0gBEUwQzBBBgRVHSAAMDkwNwYIKwYBBQUHAgEWK2h0
dHA6Ly93d3cuYWxjYXRlbC1sdWNlbnQuY29tL1BLSS9jcC9jcC5odG0wDQYJKoZIhvcNAQEFBQAD
ggEBADBMWG3WQyC6+mBzuuFuCGqJAiC4v+TQ3ZErd5KKSRGh8dwjzK5L2C51wJPVe6EAjb59CEb2
p2aPKSkoMrCC8seBRM/bs23DMyna1Jr9Q5EZDrmRqBLJy3Cs8NFpa/cKb6SkegFHcB/vi+SYgSdR
BwoNE5+y6MRPXcEBadI/9W8Zlkk5sJ3w55e+i8OCNg/fDYAQuJPa+hD3/byWGxUgGSMNGQ/GS2st
NETAa5Z/88Sh9FHk2BtrxSz7jPtekKhjsidD2ANJZTCyj9iRB+Nt9FEetNpcN6ke1FlepRbCsV10
I0y6weLwZ34h2GWbN9qEOSQV88NBA149a5ugJ/oCbHEwggTdMIIDxaADAgECAgoanQrOAAAAAAAG
MA0GCSqGSIb3DQEBBQUAMEMxFzAVBgNVBAoTDkFsY2F0ZWwgTHVjZW50MSgwJgYDVQQDEx9BbGNh
dGVsIEx1Y2VudCBJbnRlcm5hbCBSb290IENBMB4XDTA4MTEyMTIxNTcyOFoXDTE4MTEyMTIyMDcy
OFowgYUxEzARBgoJkiaJk/IsZAEZFgNjb20xFjAUBgoJkiaJk/IsZAEZFgZsdWNlbnQxFDASBgoJ
kiaJk/IsZAEZFgRuYTAyMRcwFQYDVQQKEw5BbGNhdGVsIEx1Y2VudDEnMCUGA1UEAxMeQWxjYXRl
bCBMdWNlbnQgSW50ZXJuYWwgU3ViIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA
2Ocmcli3LbVU6TRh+JLMtquBr5/grS+gzfN5YL/lauFCHmDlF7kNQvxtDWqwNpOkzb97CwWcVsdf
kyWAiGzVWeRIrYGhK/xNPFRYXOKYXLGqxFWkltZkYpSRudHzjTneUC4EVdMXnREMu8FTC0CM38Vb
xMvQ+ygjEyicg2QT9lZHWkKP9kCI1818P+AmS7905t6kXR9Q2m1GjcCa0KqARPGX/xe2toQS+Vdi
UwDary1Enk8j19KFmvFg1bhY2mNSHgzN2AWnhsOi/EID1SalzBwHylByB/UbbEv2dZUsAdMuOtYt
Z/8dM1axS0d3fW7q7mAYV5uM42mYX9o1B/RzjwIDAQABo4IBjjCCAYowDwYDVR0TAQH/BAUwAwEB
/zAdBgNVHQ4EFgQU2exrvZZYIvfYpnfN/k2B77qXvRIwCwYDVR0PBAQDAgHGMBAGCSsGAQQBgjcV
AQQDAgEAMBkGCSsGAQQBgjcUAgQMHgoAUwB1AGIAQwBBMB8GA1UdIwQYMBaAFAesslr2YYl8XHzr
4pcnKWkMih/wMHgGA1UdHwRxMG8wbaBroGmGOWh0dHA6Ly9zZXJ2aWNlcy5zdXBwb3J0LmFsY2F0
ZWwtbHVjZW50LmNvbS9QS0kvcm9vdENBLmNybIYsaHR0cDovL3d3dy5hbGNhdGVsLWx1Y2VudC5j
b20vUEtJL3Jvb3RDQS5jcmwwgYIGCCsGAQUFBwEBBHYwdDA4BggrBgEFBQcwAoYsaHR0cDovL3d3
dy5hbGNhdGVsLWx1Y2VudC5jb20vUEtJL3Jvb3RDQS5jcnQwOAYIKwYBBQUHMAKGLGh0dHA6Ly93
d3cuYWxjYXRlbC1sdWNlbnQuY29tL1BLSS9yb290Q0EuY3J0MA0GCSqGSIb3DQEBBQUAA4IBAQCl
GxDp5Z1IDjIEz8VaTEWa8Q1OWUbXwsszdoNg5Gg3F1a2VFFVegmsrpt4axbESlgE6AT/rkUUiyjb
EhcUgY2OHdeKN5Gc7VOGh9D7SER9peARwSwx4NYRrsIaRXDrUswWAM6T6ilDUogjKYk3uK2zZ6Vy
7z3JewxVlhpeSsNPQSMoyNibKkYLRoh6rvz94vB0mvcT0uVx7xowPNoTOjjGRAk4J/MBaNOupvwf
RfPmwRetdnD6NC5x8aRkhr4ZNBjvYxFT8IJaeLk8piQYMPRDlzi7dlb9d6C5WuC0LRpomk2r3bd6
/XpNOx2FyG18axeeASWtENgPvqEirM5MjwkCMIIGejCCBWKgAwIBAgIKGdtaDAAAAAA9bjANBgkq
hkiG9w0BAQUFADCBhTETMBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT8ixkARkWBmx1Y2Vu
dDEUMBIGCgmSJomT8ixkARkWBG5hMDIxFzAVBgNVBAoTDkFsY2F0ZWwgTHVjZW50MScwJQYDVQQD
Ex5BbGNhdGVsIEx1Y2VudCBJbnRlcm5hbCBTdWIgQ0EwHhcNMTAwNTMwMDIwNDQzWhcNMTIwNTI5
MDIwNDQzWjBAMQ8wDQYDVQQDEwZtaWVsa2UxLTArBgkqhkiG9w0BCQEWHmJpbGwubWllbGtlQGFs
Y2F0ZWwtbHVjZW50LmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAo1P58gTZrHri5vsA
ksaizRgNXUTQXDg7A2bIh725bEC7Y8V57vMTMx7kzzXR6iwpLbhn71jbdKFFHV4unSPWMssxwi8g
WanrFLaCSPnaAv/kqeLZ/XjRIsSunLvYpYvYLUuEtjzBUBEnp8uJ7WwhknUVFCf9f6yEXAUBtlbR
eokCAwEAAaOCA7IwggOuMAsGA1UdDwQEAwIHgDAdBgNVHQ4EFgQUs3huZkhOkBtaorqjkncKXxvY
iVowPgYJKwYBBAGCNxUHBDEwLwYnKwYBBAGCNxUIhb3FWYPjsTmHpYEqhr/DQoWUmBmBC4TQtFqF
w+FEAgFkAgEMMB8GA1UdIwQYMBaAFNnsa72WWCL32KZ3zf5Nge+6l70SMIIBXAYDVR0fBIIBUzCC
AU8wggFLoIIBR6CCAUOGgdlsZGFwOi8vL0NOPUFsY2F0ZWwlMjBMdWNlbnQlMjBJbnRlcm5hbCUy
MFN1YiUyMENBLENOPXVzbmF2c3BraTAzcCxDTj1DRFAsQ049UHVibGljJTIwS2V5JTIwU2Vydmlj
ZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixEQz1sdWFkLERDPWx1Y2VudCxEQz1jb20/
Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdD9iYXNlP29iamVjdENsYXNzPWNSTERpc3RyaWJ1dGlv
blBvaW50hitodHRwOi8vd3d3LmFsY2F0ZWwtbHVjZW50LmNvbS9QS0kvc3ViQ0EuY3JshjhodHRw
Oi8vc2VydmljZXMuc3VwcG9ydC5hbGNhdGVsLWx1Y2VudC5jb20vUEtJL3N1YkNBLmNybDCCAWAG
CCsGAQUFBwEBBIIBUjCCAU4wgcwGCCsGAQUFBzAChoG/bGRhcDovLy9DTj1BbGNhdGVsJTIwTHVj
ZW50JTIwSW50ZXJuYWwlMjBTdWIlMjBDQSxDTj1BSUEsQ049UHVibGljJTIwS2V5JTIwU2Vydmlj
ZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixEQz1sdWFkLERDPWx1Y2VudCxEQz1jb20/
Y0FDZXJ0aWZpY2F0ZT9iYXNlP29iamVjdENsYXNzPWNlcnRpZmljYXRpb25BdXRob3JpdHkwNwYI
KwYBBQUHMAKGK2h0dHA6Ly93d3cuYWxjYXRlbC1sdWNlbnQuY29tL1BLSS9zdWJDQS5jcnQwRAYI
KwYBBQUHMAKGOGh0dHA6Ly9zZXJ2aWNlcy5zdXBwb3J0LmFsY2F0ZWwtbHVjZW50LmNvbS9QS0kv
c3ViQ0EuY3J0MBMGA1UdJQQMMAoGCCsGAQUFBwMEMBsGCSsGAQQBgjcVCgQOMAwwCgYIKwYBBQUH
AwQwKQYDVR0RBCIwIIEeYmlsbC5taWVsa2VAYWxjYXRlbC1sdWNlbnQuY29tMA0GCSqGSIb3DQEB
BQUAA4IBAQAZRA+LIZRrEeIu8rlW3yprtze3O5EjtjyNS37sq2o0DatvvucKfFJoes1tLUmgeqKz
eObrOx2ZMpqjhvdzKPw0BmG+vIS2oVU/gSu+Kp9IvlYa/LBJgGqL6uwucG7NKb/KoYwY9XBQerPh
9NcfbsBcFoZlcV9e9J4NIXok2HOwyr+p8hKhK5SpeIoHf3Si8qSuyJuk4FtrjmTlUkgHmoFmj6U9
gKJR6WKpcBZhmOE8eQ9OZAaD1AycT7zdCAsxcBykgM58d59OeZajj1m7ZHTtOppCRMYl1A1lNxOo
w4IuokZ4L85KKzL6WqnuGflYCcNtO9it9JGZharIN+HarP3JMIIG2jCCBcKgAwIBAgIKGdxk1QAA
AAA9bzANBgkqhkiG9w0BAQUFADCBhTETMBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT8ixk
ARkWBmx1Y2VudDEUMBIGCgmSJomT8ixkARkWBG5hMDIxFzAVBgNVBAoTDkFsY2F0ZWwgTHVjZW50
MScwJQYDVQQDEx5BbGNhdGVsIEx1Y2VudCBJbnRlcm5hbCBTdWIgQ0EwHhcNMTAwNTMwMDIwNTUx
WhcNMTIwNTI5MDIwNTUxWjBAMQ8wDQYDVQQDEwZtaWVsa2UxLTArBgkqhkiG9w0BCQEWHmJpbGwu
bWllbGtlQGFsY2F0ZWwtbHVjZW50LmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAqpHW
Jco1co4MTnJ1WFCsJGeMVemFG7SQrcH0LARvpO/o9diiV3/Qvt08MYIv71lXTVBr/Kn8J9Rxq+Ew
eEGygQmO8v+kN3SIUOnWInanbEZkYFdf9jWNEArSvFZiazgrp9vgE3bKK3Id7kUFXXdWj2hK1xjQ
5BidCf9IpfyzKsECAwEAAaOCBBIwggQOMAsGA1UdDwQEAwIFIDBEBgkqhkiG9w0BCQ8ENzA1MA4G
CCqGSIb3DQMCAgIAgDAOBggqhkiG9w0DBAICAIAwBwYFKw4DAgcwCgYIKoZIhvcNAwcwHQYDVR0O
BBYEFFFsCLe38LJX1iIg54BxslUYaXvYMD4GCSsGAQQBgjcVBwQxMC8GJysGAQQBgjcVCIW9xVmD
47E5h6WBKoa/w0KFlJgZgQuCupMPhOrffgIBZAIBDTAfBgNVHSMEGDAWgBTZ7Gu9llgi99imd83+
TYHvupe9EjCCAVwGA1UdHwSCAVMwggFPMIIBS6CCAUegggFDhoHZbGRhcDovLy9DTj1BbGNhdGVs
JTIwTHVjZW50JTIwSW50ZXJuYWwlMjBTdWIlMjBDQSxDTj11c25hdnNwa2kwM3AsQ049Q0RQLENO
PVB1YmxpYyUyMEtleSUyMFNlcnZpY2VzLENOPVNlcnZpY2VzLENOPUNvbmZpZ3VyYXRpb24sREM9
bHVhZCxEQz1sdWNlbnQsREM9Y29tP2NlcnRpZmljYXRlUmV2b2NhdGlvbkxpc3Q/YmFzZT9vYmpl
Y3RDbGFzcz1jUkxEaXN0cmlidXRpb25Qb2ludIYraHR0cDovL3d3dy5hbGNhdGVsLWx1Y2VudC5j
b20vUEtJL3N1YkNBLmNybIY4aHR0cDovL3NlcnZpY2VzLnN1cHBvcnQuYWxjYXRlbC1sdWNlbnQu
Y29tL1BLSS9zdWJDQS5jcmwwggFgBggrBgEFBQcBAQSCAVIwggFOMIHMBggrBgEFBQcwAoaBv2xk
YXA6Ly8vQ049QWxjYXRlbCUyMEx1Y2VudCUyMEludGVybmFsJTIwU3ViJTIwQ0EsQ049QUlBLENO
PVB1YmxpYyUyMEtleSUyMFNlcnZpY2VzLENOPVNlcnZpY2VzLENOPUNvbmZpZ3VyYXRpb24sREM9
bHVhZCxEQz1sdWNlbnQsREM9Y29tP2NBQ2VydGlmaWNhdGU/YmFzZT9vYmplY3RDbGFzcz1jZXJ0
aWZpY2F0aW9uQXV0aG9yaXR5MDcGCCsGAQUFBzAChitodHRwOi8vd3d3LmFsY2F0ZWwtbHVjZW50
LmNvbS9QS0kvc3ViQ0EuY3J0MEQGCCsGAQUFBzAChjhodHRwOi8vc2VydmljZXMuc3VwcG9ydC5h
bGNhdGVsLWx1Y2VudC5jb20vUEtJL3N1YkNBLmNydDAfBgNVHSUEGDAWBggrBgEFBQcDBAYKKwYB
BAGCNwoDBDApBgkrBgEEAYI3FQoEHDAaMAoGCCsGAQUFBwMEMAwGCisGAQQBgjcKAwQwKQYDVR0R
BCIwIIEeYmlsbC5taWVsa2VAYWxjYXRlbC1sdWNlbnQuY29tMA0GCSqGSIb3DQEBBQUAA4IBAQCR
rwYqycRkzGvAxMozWQCh7wJ0axCuF5vqoBkjnhKz4gFtn89WViNTxeLdq+DhfAp3nnzqkE8ggrFn
X5b/DJZgUAGoLlvZ3IL1L0i2Ne3dK5QGq58VFK7KYrluedog6FXZ93jfXtZFq9Z4acpaR0H6DXvg
DAsdbnaLYkWI0+X/enGC7dzkJNQ8D5YUHxAA5qSGATRm6x71kb0R/ShzzFJvpxidYi2bht/mPOIa
ASZD7CSskrRKeaWEke7dKPaUpEPOFVG/do6yuG8iH1PEZ7IYy97x4SuemQmFEMwnjLz1ubf2wzhv
8Hw5Ku2kW2Vw+wI6O+IkjYAir40DgHHLNh4WMYIDVzCCA1MCAQEwgZQwgYUxEzARBgoJkiaJk/Is
ZAEZFgNjb20xFjAUBgoJkiaJk/IsZAEZFgZsdWNlbnQxFDASBgoJkiaJk/IsZAEZFgRuYTAyMRcw
FQYDVQQKEw5BbGNhdGVsIEx1Y2VudDEnMCUGA1UEAxMeQWxjYXRlbCBMdWNlbnQgSW50ZXJuYWwg
U3ViIENBAgoZ21oMAAAAAD1uMAkGBSsOAwIaBQCgggIYMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0B
BwEwHAYJKoZIhvcNAQkFMQ8XDTEwMTEwODA0NTEyMVowIwYJKoZIhvcNAQkEMRYEFBH0Y7hhLwYB
5E0cIi5cyfZdd/BqMGcGCSqGSIb3DQEJDzFaMFgwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCA
MA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMAcGBSsOAwIaMAoGCCqGSIb3
DQIFMIGlBgkrBgEEAYI3EAQxgZcwgZQwgYUxEzARBgoJkiaJk/IsZAEZFgNjb20xFjAUBgoJkiaJ
k/IsZAEZFgZsdWNlbnQxFDASBgoJkiaJk/IsZAEZFgRuYTAyMRcwFQYDVQQKEw5BbGNhdGVsIEx1
Y2VudDEnMCUGA1UEAxMeQWxjYXRlbCBMdWNlbnQgSW50ZXJuYWwgU3ViIENBAgoZ3GTVAAAAAD1v
MIGnBgsqhkiG9w0BCRACCzGBl6CBlDCBhTETMBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT
8ixkARkWBmx1Y2VudDEUMBIGCgmSJomT8ixkARkWBG5hMDIxFzAVBgNVBAoTDkFsY2F0ZWwgTHVj
ZW50MScwJQYDVQQDEx5BbGNhdGVsIEx1Y2VudCBJbnRlcm5hbCBTdWIgQ0ECChncZNUAAAAAPW8w
DQYJKoZIhvcNAQEBBQAEgYBLUpiwENoBYz0Yl3Pkf+NF0UcezgoGAGXhVRvPuXOlWm0B5fy4eM96
dEDxGMi/9WYBi9LPxhimHddemmgC9cKD0sn9ur0j2uKzHd/nvzgT/X4RlYT+vHOPt6TuXfcPYfpt
WK/91upPf/ITHFVhz6qQUVRSkjQpSvXeTXc9F2OfjQAAAAAAAA==

------=_NextPart_000_0005_01CB7ED6.ADDD8C70--

From bclaise@cisco.com  Sun Nov  7 22:16:33 2010
Return-Path: <bclaise@cisco.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 207923A69D4 for <eman@core3.amsl.com>; Sun,  7 Nov 2010 22:16:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.531
X-Spam-Level: 
X-Spam-Status: No, score=-2.531 tagged_above=-999 required=5 tests=[AWL=0.067,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ElRODC4zAajK for <eman@core3.amsl.com>; Sun,  7 Nov 2010 22:16:27 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id 6ECEE3A6996 for <eman@ietf.org>; Sun,  7 Nov 2010 22:16:25 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oA86GRon015272 for <eman@ietf.org>; Mon, 8 Nov 2010 07:16:27 +0100 (CET)
Received: from [10.68.17.197] (sin-vpn-client-17-197.cisco.com [10.68.17.197]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oA86GL3f027342 for <eman@ietf.org>; Mon, 8 Nov 2010 07:16:23 +0100 (CET)
Message-ID: <4CD795B3.9050609@cisco.com>
Date: Mon, 08 Nov 2010 14:16:19 +0800
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: eman mailing list <eman@ietf.org>
Content-Type: multipart/alternative; boundary="------------040608060208000301090400"
Subject: [eman] Webex and jabber
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 06:16:33 -0000

This is a multi-part message in MIME format.
--------------040608060208000301090400
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Dear all,

All instructions on how to use jabber can be found at 
http://www.ietf.org/jabber/

For webex, that would be good if someone in the audience could share the 
presentations for the people remote.
The webex invite is:

Topic:EMAN WG

Date:Tuesday, November 9, 2010

Time:9:00 pm, Pacific Standard Time (San Francisco, GMT-08:00)

Meeting Number:966 849 110

Meeting Password:(This meeting does not require a password.)

-------------------------------------------------------

To join the online meeting (Now from the Apple iPhone ® too!)

-------------------------------------------------------

1.Go to 
https://workgreen.webex.com/workgreen/j.php?ED=148485382&UID=-1&RT=MiM0 
<https://workgreen.webex.com/workgreen/j.php?ED=148485382&UID=-1&RT=MiM0>

2.If requested, enter your name and email address.

3.If a password is required, enter the meeting password: (This meeting 
does not require a password.)

4.Click "Join".

5.Follow the instructions that appear on your screen.

Note: You can view more information about the meeting at 
https://workgreen.webex.com/workgreen/j.php?ED=148485382&UID=-1&RT=MiM0 
<https://workgreen.webex.com/workgreen/j.php?ED=148485382&UID=-1&RT=MiM0>.

-------------------------------------------------------


  For assistance

-------------------------------------------------------

1.Go to https://workgreen.webex.com/workgreen/mc

2.On the left navigation bar, click "Support".

You can contact me at:

amorris@amsl.com <mailto:amorris@amsl.com>

1-510-492-4081

The playback of UCF (Universal Communications Format) rich media files 
requires appropriate players. To view this type of rich media files in 
the meeting, please check whether you have the players installed on your 
computer by going 
tohttps://workgreen.webex.com/workgreen/systemdiagnosis.php

Sign up for a free trial of WebEx

http://www.webex.com/go/mcemfreetrial

http://www.webex.com

IMPORTANT NOTICE: This WebEx service includes a feature that allows 
audio and any documents and other materials exchanged or viewed during 
the session to be recorded. By joining this session, you automatically 
consent to such recordings. If you do not consent to the recording, 
discuss your concerns with the meeting host prior to the start of the 
recording or do not join the session. Please note that any such 
recordings may be subject to discovery in the event of litigation.



Regards, Benoit.

--------------040608060208000301090400
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body text="#000000" bgcolor="#ffffff">
    Dear all,<br>
    <br>
    All instructions on how to use jabber can be found at
    <a class="moz-txt-link-freetext" href="http://www.ietf.org/jabber/">http://www.ietf.org/jabber/</a><br>
    <br>
    For webex, that would be good if someone in the audience could share
    the presentations for the people remote.<br>
    The webex invite is:<br>
    <!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:TrackMoves/>
  <w:TrackFormatting/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:DoNotPromoteQF/>
  <w:LidThemeOther>EN-US</w:LidThemeOther>
  <w:LidThemeAsian>X-NONE</w:LidThemeAsian>
  <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
   <w:SplitPgBreakAndParaMark/>
   <w:DontVertAlignCellWithSp/>
   <w:DontBreakConstrainedForcedTables/>
   <w:DontVertAlignInTxbx/>
   <w:Word11KerningPairs/>
   <w:CachedColBalance/>
  </w:Compatibility>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
  <m:mathPr>
   <m:mathFont m:val="Cambria Math"/>
   <m:brkBin m:val="before"/>
   <m:brkBinSub m:val="&#45;-"/>
   <m:smallFrac m:val="off"/>
   <m:dispDef/>
   <m:lMargin m:val="0"/>
   <m:rMargin m:val="0"/>
   <m:defJc m:val="centerGroup"/>
   <m:wrapIndent m:val="1440"/>
   <m:intLim m:val="subSup"/>
   <m:naryLim m:val="undOvr"/>
  </m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
  DefSemiHidden="true" DefQFormat="false" DefPriority="99"
  LatentStyleCount="267">
  <w:LsdException Locked="false" Priority="0" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Normal"/>
  <w:LsdException Locked="false" Priority="9" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="heading 1"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8"/>
  <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 1"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 2"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 3"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 4"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 5"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 6"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 7"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 8"/>
  <w:LsdException Locked="false" Priority="39" Name="toc 9"/>
  <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption"/>
  <w:LsdException Locked="false" Priority="10" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Title"/>
  <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font"/>
  <w:LsdException Locked="false" Priority="11" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtitle"/>
  <w:LsdException Locked="false" Priority="22" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Strong"/>
  <w:LsdException Locked="false" Priority="20" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Emphasis"/>
  <w:LsdException Locked="false" Priority="59" SemiHidden="false"
   UnhideWhenUsed="false" Name="Table Grid"/>
  <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text"/>
  <w:LsdException Locked="false" Priority="1" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="No Spacing"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 1"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 1"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 1"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 1"/>
  <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision"/>
  <w:LsdException Locked="false" Priority="34" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="List Paragraph"/>
  <w:LsdException Locked="false" Priority="29" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Quote"/>
  <w:LsdException Locked="false" Priority="30" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Quote"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 1"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 1"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 1"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 1"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 1"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 2"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 2"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 2"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 2"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 2"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 2"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 2"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 2"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 2"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 3"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 3"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 3"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 3"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 3"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 3"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 3"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 3"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 3"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 4"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 4"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 4"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 4"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 4"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 4"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 4"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 4"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 4"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 5"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 5"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 5"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 5"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 5"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 5"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 5"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 5"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 5"/>
  <w:LsdException Locked="false" Priority="60" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Shading Accent 6"/>
  <w:LsdException Locked="false" Priority="61" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light List Accent 6"/>
  <w:LsdException Locked="false" Priority="62" SemiHidden="false"
   UnhideWhenUsed="false" Name="Light Grid Accent 6"/>
  <w:LsdException Locked="false" Priority="63" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6"/>
  <w:LsdException Locked="false" Priority="64" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6"/>
  <w:LsdException Locked="false" Priority="65" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 1 Accent 6"/>
  <w:LsdException Locked="false" Priority="66" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium List 2 Accent 6"/>
  <w:LsdException Locked="false" Priority="67" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6"/>
  <w:LsdException Locked="false" Priority="68" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6"/>
  <w:LsdException Locked="false" Priority="69" SemiHidden="false"
   UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6"/>
  <w:LsdException Locked="false" Priority="70" SemiHidden="false"
   UnhideWhenUsed="false" Name="Dark List Accent 6"/>
  <w:LsdException Locked="false" Priority="71" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Shading Accent 6"/>
  <w:LsdException Locked="false" Priority="72" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful List Accent 6"/>
  <w:LsdException Locked="false" Priority="73" SemiHidden="false"
   UnhideWhenUsed="false" Name="Colorful Grid Accent 6"/>
  <w:LsdException Locked="false" Priority="19" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis"/>
  <w:LsdException Locked="false" Priority="21" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis"/>
  <w:LsdException Locked="false" Priority="31" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference"/>
  <w:LsdException Locked="false" Priority="32" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Intense Reference"/>
  <w:LsdException Locked="false" Priority="33" SemiHidden="false"
   UnhideWhenUsed="false" QFormat="true" Name="Book Title"/>
  <w:LsdException Locked="false" Priority="37" Name="Bibliography"/>
  <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading"/>
 </w:LatentStyles>
</xml><![endif]--><!--[if gte mso 10]>
<style>
 /* Style Definitions */
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-qformat:yes;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-ascii-font-family:Calibri;
	mso-ascii-theme-font:minor-latin;
	mso-fareast-font-family:"Times New Roman";
	mso-fareast-theme-font:minor-fareast;
	mso-hansi-font-family:Calibri;
	mso-hansi-theme-font:minor-latin;}
</style>
<![endif]-->
    <p class="ReplyForwardToFromDate">Topic:<span style="">&nbsp;&nbsp;&nbsp; </span>EMAN
      WG</p>
    <p class="ReplyForwardToFromDate">Date:<span style="">&nbsp;&nbsp;&nbsp;&nbsp; </span>Tuesday,
November
      9, 2010</p>
    <p class="ReplyForwardToFromDate">Time:<span style="">&nbsp;&nbsp;&nbsp;&nbsp; </span>9:00
pm,
      Pacific Standard Time (San Francisco, GMT-08:00)</p>
    <p class="ReplyForwardToFromDate">Meeting Number:<span style="">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </span>966
      849 110</p>
    <p class="ReplyForwardToFromDate">Meeting Password:<span style="">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
      </span>(This meeting does not require a password.)</p>
    <p class="MsoNormal" style=""><span style="font-size: 10pt;
        font-family: &quot;Arial&quot;,&quot;sans-serif&quot;;">&nbsp;</span></p>
    <p class="MsoNormal" style=""><span style="font-size: 10pt;
        font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; display:
        none;">-------------------------------------------------------</span></p>
    <div style="border-width: 1pt medium; border-style: solid none;
      border-color: windowtext -moz-use-text-color; padding: 1pt 0cm;">
      <p class="MsoBodyText" style="border: medium none; padding: 0cm;">To
join
        the online meeting (Now from the Apple iPhone &reg; too!)</p>
    </div>
    <p class="MsoNormal" style=""><span style="font-size: 10pt;
        font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; display:
        none;">-------------------------------------------------------</span></p>
    <p class="MsoList">1.<span style="">&nbsp;&nbsp; </span>Go to <a
href="https://workgreen.webex.com/workgreen/j.php?ED=148485382&amp;UID=-1&amp;RT=MiM0"><span
          style="font-size: 10pt; font-family:
          &quot;Arial&quot;,&quot;sans-serif&quot;;">https://workgreen.webex.com/workgreen/j.php?ED=148485382&amp;UID=-1&amp;RT=MiM0</span></a></p>
    <p class="MsoList">2.<span style="">&nbsp;&nbsp; </span>If requested, enter
      your name and email address.</p>
    <p class="MsoList">3.<span style="">&nbsp;&nbsp; </span>If a password is
      required, enter the meeting password: (This meeting does not
      require a
      password.)</p>
    <p class="MsoList">4.<span style="">&nbsp;&nbsp; </span>Click &#8220;Join&#8221;.</p>
    <p class="MsoList">5.<span style="">&nbsp;&nbsp; </span>Follow the
      instructions that appear on your screen.</p>
    <p class="MsoBodyText">Note: You can view more information about the
      meeting at <a
href="https://workgreen.webex.com/workgreen/j.php?ED=148485382&amp;UID=-1&amp;RT=MiM0"><span
          style="font-size: 10pt; font-family:
          &quot;Arial&quot;,&quot;sans-serif&quot;;">https://workgreen.webex.com/workgreen/j.php?ED=148485382&amp;UID=-1&amp;RT=MiM0</span></a>.</p>
    <p class="MsoNormal" style=""><span style="font-size: 10pt;
        font-family: &quot;Arial&quot;,&quot;sans-serif&quot;;">&nbsp;</span></p>
    <p class="MsoNormal" style=""><span style="font-size: 10pt;
        font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; display:
        none;">-------------------------------------------------------</span></p>
    <div style="border-width: 1pt medium; border-style: solid none;
      border-color: windowtext -moz-use-text-color; padding: 1pt 0cm;">
      <h1 style="border: medium none; padding: 0cm;">For
        assistance</h1>
    </div>
    <p class="MsoNormal" style=""><span style="font-size: 10pt;
        font-family: &quot;Arial&quot;,&quot;sans-serif&quot;; display:
        none;">-------------------------------------------------------</span></p>
    <p class="MsoList">1.<span style="">&nbsp;&nbsp; </span>Go to <a
        href="https://workgreen.webex.com/workgreen/mc"><span
          style="font-size: 10pt; font-family:
          &quot;Arial&quot;,&quot;sans-serif&quot;;">https://workgreen.webex.com/workgreen/mc</span></a></p>
    <p class="MsoList">2.<span style="">&nbsp;&nbsp; </span>On the left
      navigation bar, click &#8220;Support&#8221;.</p>
    <p class="MsoNormal" style=""><span style="font-size: 10pt;
        font-family: &quot;Arial&quot;,&quot;sans-serif&quot;;">&nbsp;</span></p>
    <p class="MsoBodyText">You can contact me at:</p>
    <p class="MsoList"><a href="mailto:amorris@amsl.com"><span
          style="font-size: 10pt; font-family:
          &quot;Arial&quot;,&quot;sans-serif&quot;;">amorris@amsl.com</span></a></p>
    <p class="MsoList">1-510-492-4081</p>
    <p class="MsoNormal" style=""><span style="font-size: 10pt;
        font-family: &quot;Arial&quot;,&quot;sans-serif&quot;;">&nbsp;</span></p>
    <p class="MsoBodyText">The playback of UCF (Universal Communications
      Format) rich
      media files requires appropriate players. To view this type of
      rich media files
      in the meeting, please check whether you have the players
      installed on your
      computer by going to<span style="">&nbsp; </span><a
        href="https://workgreen.webex.com/workgreen/systemdiagnosis.php"><span
          style="font-size: 10pt; font-family:
          &quot;Arial&quot;,&quot;sans-serif&quot;;">https://workgreen.webex.com/workgreen/systemdiagnosis.php</span></a></p>
    <p class="MsoList">Sign up for a free trial of WebEx</p>
    <p class="MsoList"><a href="http://www.webex.com/go/mcemfreetrial"><span
          style="font-size: 10pt; font-family:
          &quot;Arial&quot;,&quot;sans-serif&quot;;">http://www.webex.com/go/mcemfreetrial</span></a></p>
    <p class="MsoNormal" style=""><span style="font-size: 10pt;
        font-family: &quot;Arial&quot;,&quot;sans-serif&quot;;">&nbsp;</span></p>
    <p class="MsoBodyText"><a href="http://www.webex.com"><span
          style="font-size: 10pt; font-family:
          &quot;Arial&quot;,&quot;sans-serif&quot;;">http://www.webex.com</span></a></p>
    <p class="MsoNormal" style=""><span style="font-size: 10pt;
        font-family: &quot;Arial&quot;,&quot;sans-serif&quot;;">&nbsp;</span></p>
    <p class="MsoNormal" style=""><span style="font-size: 10pt;
        font-family: &quot;Arial&quot;,&quot;sans-serif&quot;;">&nbsp;</span></p>
    <p class="MsoBodyText">IMPORTANT NOTICE: This WebEx service includes
      a feature
      that allows audio and any documents and other materials exchanged
      or viewed
      during the session to be recorded. By joining this session, you
      automatically
      consent to such recordings. If you do not consent to the
      recording, discuss
      your concerns with the meeting host prior to the start of the
      recording or do
      not join the session. Please note that any such recordings may be
      subject to
      discovery in the event of litigation.</p>
    <br>
    <br>
    Regards, Benoit.<br>
  </body>
</html>

--------------040608060208000301090400--

From bclaise@cisco.com  Sun Nov  7 22:41:46 2010
Return-Path: <bclaise@cisco.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 268CA3A69B1 for <eman@core3.amsl.com>; Sun,  7 Nov 2010 22:41:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.537
X-Spam-Level: 
X-Spam-Status: No, score=-2.537 tagged_above=-999 required=5 tests=[AWL=0.062,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w-V8zomSBcON for <eman@core3.amsl.com>; Sun,  7 Nov 2010 22:41:44 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id 4F34A3A69C5 for <eman@ietf.org>; Sun,  7 Nov 2010 22:38:47 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oA86cR6t017653; Mon, 8 Nov 2010 07:38:27 +0100 (CET)
Received: from [10.68.17.197] (sin-vpn-client-17-197.cisco.com [10.68.17.197]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oA86cDM2012216; Mon, 8 Nov 2010 07:38:15 +0100 (CET)
Message-ID: <4CD79AD4.7020909@cisco.com>
Date: Mon, 08 Nov 2010 14:38:12 +0800
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: Bruce Nordman <bnordman@lbl.gov>
References: <AANLkTinkAyB3LMh6TW6gaQxKUNCqmj+buuvt+bofuC1k@mail.gmail.com>
In-Reply-To: <AANLkTinkAyB3LMh6TW6gaQxKUNCqmj+buuvt+bofuC1k@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: eman@ietf.org
Subject: Re: [eman] Topics
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 06:41:46 -0000

Hi Bruce,
> As an individual, the following are some topics that I have particular
> interest in.  They are in no particular order.
>
> Mode names
>    I have dealt with these in many contexts over the last fifteen years,
> both for electronic devices and others.  I have found them to be considerably
> more important than one might initially think.
>
> Use cases
>    I think collecting existing examples of these into one location and expanding
> it could be helpful in organizing our thinking and working towards consensus.
>
> Parallel networks
>    While sometimes communications and power distribution will be aligned, in
> other cases they will not be.  This affects our notion of a parent device.
This is a good point, which is explained the EMAN framework.

         A Power Monitor Child can be fully dependent on the Power
         Monitor Parent for its power or independent from the parent
         (such as a PC connected to a switch).  In the dependently
         powered case, the Power Monitor Parent provides power for the
         Power Monitor Child (as in the case of Power Over Ethernet
         devices).  In the independently powered case, the Power Monitor
         Child draws power from another source (typically a wall outlet).

This is also the reason why the Power Monitor Domain has been renamed to 
Power Monitor Meter Domain.

However, we could do a better job at explaining the two different 
domain: metering versus power domain

Regards, Benoit, as a contributor.
> Units
>    Our choices in energy, power, and other physical units may have a long
> legacy so deserve extended consideration.
>
> Complexity
>    There are many directions that we could go that add complexity.  Some of these
> are in our current drafts; others are not.  I think most of our
> difficult decisions may
> likely be which of these to include, and which not.  I have several of my own
> favorite topics that probably do not rate inclusion in our first products.
>
> Priority
>    Elsewhere in life, price is used as a priority-setting mechanism,
> and it embodies
> a significant degree of simplicity and transparency.  I think it has
> to be considered
> along with other approaches to this problem.
>
> Control
>    I think we need to consider how much linkage there is between mechanisms for
> reporting energy-related information, and those for control.
>
> That's enough for now.  See you in Beijing.
>
> --Bruce
>


From moulchan@cisco.com  Sun Nov  7 23:02:02 2010
Return-Path: <moulchan@cisco.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C1CBA3A6866 for <eman@core3.amsl.com>; Sun,  7 Nov 2010 23:02:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level: 
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dtBM4Z7sGSiw for <eman@core3.amsl.com>; Sun,  7 Nov 2010 23:01:55 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by core3.amsl.com (Postfix) with ESMTP id 58C783A6975 for <eman@ietf.org>; Sun,  7 Nov 2010 23:01:44 -0800 (PST)
Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuAGAK4v10ytJV2Z/2dsb2JhbACBZ5gQAYgNcZ9ammOCcoJWBIRYiQ0
X-IronPort-AV: E=Sophos;i="4.58,313,1286150400";  d="scan'208,217";a="179377578"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rtp-iport-1.cisco.com with ESMTP; 08 Nov 2010 07:02:03 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id oA8723cZ010832 for <eman@ietf.org>; Mon, 8 Nov 2010 07:02:03 GMT
Received: from xmb-rcd-106.cisco.com ([72.163.62.148]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 8 Nov 2010 01:02:03 -0600
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB7F12.D8D7CD99"
Date: Mon, 8 Nov 2010 01:02:01 -0600
Message-ID: <E9B25823FA871E4AA9EDA7B163E5D8A903503FAF@XMB-RCD-106.cisco.com>
In-Reply-To: <68FBE0F3CE97264395875AC1C468F22C514A74@mail03.cyberswitching.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Review of draft-norwin-energy-consider-01 
Thread-Index: Act+0MWGgJ51kuLaQZ+XO5sxLXJfHQADY2LgAAzujRA=
References: <AANLkTikFy7hzFSFtQonWZRXe_WAMbpZLLAGWrNjOVcFw@mail.gmail.com> <68FBE0F3CE97264395875AC1C468F22C514A74@mail03.cyberswitching.local>
From: "Mouli Chandramouli (moulchan)" <moulchan@cisco.com>
To: <eman@ietf.org>
X-OriginalArrivalTime: 08 Nov 2010 07:02:03.0538 (UTC) FILETIME=[D8E77F20:01CB7F12]
Subject: [eman] Review of draft-norwin-energy-consider-01
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 07:02:03 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB7F12.D8D7CD99
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello,

=20

Here are my comments on norwin-energy-consider-01.

=20

1.  Section 3 - Scope of energy management is already covered in
requirements draft. There are no additional requirements in this draft.=20

=20

2.  Section 4 - Terminology - The purpose is to have common terminology
understood by all - I agree this is import and is sort of similar to the
work in other WG; for e.g.
http://tools.ietf.org/html/draft-ietf-roll-terminology-04  for RPL. =20

=20

=20

If Terminology is the focus, then this draft should explain/clarify lot
of other commonly used terminology - perhaps, from the basics - what is
energy, what is power, devices,  what are the methods of power/energy
measurement, then moving on to monitoring, power states, configuration
....

=20

In terms of power states, my thought is it will take some time to evolve
to precise definitions for the devices. It may be useful if we can focus
on the devices in consideration - network devices, devices attached to
the network;  building devices and then perhaps, we can converge on this
discussion soon.=20

=20

I do not agree Power Levels should be equivalent to measured value of
power.=20

=20

=20

3.  Section 5.1 Control  - This section calls for distributed control
instead of restricting to policy based control only. This is a valid and
interesting point to be considered.=20

=20

    Section 5.2 - Identity - calls for recognizing a Universal Product
Code (UPC) and discovering if the device is a TV.  Firstly, this
requires that TV, MicroWave has a network connection (IPV6, 6lowPAN,
...). Protocols developed in WG such CORE can be be used in that
scenario. Refer to  http://tools.ietf.org/html/rfc5826

=20

    Section 5.3 - NMS considerations - This section the describes how
NMS would work for energy management.=20

=20

    Section 5.6 - Power considerations - There is an interesting point
on power source - internal or external - (powered by outlet of powered
by battery). I think this can be useful.=20

    Section 5.7 - Power state monitoring - this material is covered in
the requirements doc.=20

    Section 5.8 - Use cases - There many use cases presented in the
requirements doc.  I am not sure if the use case on - Vehicles is
relevant to energy monitoring - Vehicle energy is fuel or battery ? =20

=20

4.  Section 7 - Outstanding questions - Units of measurement - I thought
this question was settled and there is rough consensus on the IEC
measurement model ?=20

                                        Multiple power sources -is an
interesting point.=20

=20

=20

In conclusion, this draft is a combination of some requirements, some
terminology, and some open issues.=20

=20

Thanks

Mouli

=20


------_=_NextPart_001_01CB7F12.D8D7CD99
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
	{font-family:"Lucida Grande";}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:9.0pt;
	font-family:"Times New Roman","serif";}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.balloontextchar0
	{mso-style-name:balloontextchar;
	font-family:"Lucida Grande";}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DWordSection1>

<p class=3DMsoPlainText>Hello,<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>Here are my comments on =
norwin-energy-consider-01.<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>1.&nbsp; Section 3 - Scope of energy management =
is
already covered in requirements draft. There are no additional =
requirements in
this draft. <o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>2.&nbsp; Section 4 &#8211; Terminology - The =
purpose is
to have common terminology understood by all &#8211; I agree this is =
import and
is sort of similar to the work in other WG; for e.g. &nbsp;&nbsp;<a
href=3D"http://tools.ietf.org/html/draft-ietf-roll-terminology-04">http:/=
/tools.ietf.org/html/draft-ietf-roll-terminology-04</a>&nbsp;
for RPL.&nbsp; <o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>If Terminology is the focus, then this draft =
should
explain/clarify lot of other commonly used terminology &#8211; perhaps, =
from
the basics &#8211; what is energy, what is power, devices,&nbsp; what =
are the
methods of power/energy measurement, then moving on to monitoring, power
states, configuration &nbsp;&#8230;.<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>In terms of power states, my thought is it will =
take some
time to evolve to precise definitions for the devices. It may be useful =
if we
can focus on the devices in consideration - network devices, devices =
attached
to the network;&nbsp; building devices and then perhaps, we can converge =
on
this discussion soon. <o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>I do not agree Power Levels should be equivalent =
to measured
value of power. <o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>3.&nbsp; Section 5.1 Control&nbsp; - This =
section calls
for distributed control instead of restricting to policy based control =
only.
This is a valid and interesting point to be considered. <o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&nbsp;&nbsp;&nbsp; Section 5.2 - Identity - =
calls for
recognizing a Universal Product Code (UPC) and discovering if the device =
is a
TV.&nbsp; Firstly, this requires that TV, MicroWave has a network =
connection
(IPV6, 6lowPAN, ...). Protocols developed in WG such CORE can be be used =
in
that scenario. Refer to&nbsp; <a =
href=3D"http://tools.ietf.org/html/rfc5826">http://tools.ietf.org/html/rf=
c5826</a><o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&nbsp;&nbsp;&nbsp; Section 5.3 - NMS =
considerations &#8211;
This section the describes how NMS would work for energy management. =
<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>&nbsp; &nbsp;&nbsp;Section 5.6 &#8211; Power =
considerations
- There is an interesting point on power source - internal or external -
(powered by outlet of powered by battery). I think this can be useful. =
<o:p></o:p></p>

<p class=3DMsoPlainText>&nbsp;&nbsp;&nbsp; Section 5.7 &#8211; Power =
state
monitoring &#8211; this material is covered in the requirements doc. =
<o:p></o:p></p>

<p class=3DMsoPlainText>&nbsp;&nbsp;&nbsp; Section 5.8 - Use cases =
&#8211; There many
use cases presented in the requirements doc.&nbsp; I am not sure if the =
use
case on &#8211; Vehicles is relevant to energy monitoring &#8211; =
Vehicle energy
is fuel or battery ? &nbsp;<o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>4.&nbsp; Section 7 - Outstanding questions - =
Units of
measurement - I thought this question was settled and there is rough =
consensus
on the IEC measurement model ? <o:p></o:p></p>

<p class=3DMsoPlainText>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Multiple
power sources &#8211;is an interesting point. <o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>In conclusion, this draft is a combination of =
some
requirements, some terminology, and some open issues. <o:p></o:p></p>

<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p>

<p class=3DMsoPlainText>Thanks<o:p></o:p></p>

<p class=3DMsoPlainText>Mouli<o:p></o:p></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

</div>

</body>

</html>

------_=_NextPart_001_01CB7F12.D8D7CD99--

From bclaise@cisco.com  Sun Nov  7 23:05:24 2010
Return-Path: <bclaise@cisco.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C439E28C10D for <eman@core3.amsl.com>; Sun,  7 Nov 2010 23:05:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level: 
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5B6fKSfQhuv8 for <eman@core3.amsl.com>; Sun,  7 Nov 2010 23:05:11 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id 79CA43A69D9 for <eman@ietf.org>; Sun,  7 Nov 2010 23:05:10 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oA875UFP021091 for <eman@ietf.org>; Mon, 8 Nov 2010 08:05:30 +0100 (CET)
Received: from [10.68.17.197] (sin-vpn-client-17-197.cisco.com [10.68.17.197]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oA875Qn7003470 for <eman@ietf.org>; Mon, 8 Nov 2010 08:05:29 +0100 (CET)
Message-ID: <4CD7A135.5050007@cisco.com>
Date: Mon, 08 Nov 2010 15:05:25 +0800
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: eman mailing list <eman@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [eman] presentations needed in	advance!
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 07:05:24 -0000

Dear all,

Presenters are kindly asked to send the presentations to the WG chairs 
in advance so that they can be loaded on the meeting site (
https://datatracker.ietf.org/meeting/79/materials.html) and be available 
for the remote participants at the time the meeting starts.

Thanks and Regards, Bruce and Benoit.



From bclaise@cisco.com  Sun Nov  7 23:27:36 2010
Return-Path: <bclaise@cisco.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3D6F03A6801 for <eman@core3.amsl.com>; Sun,  7 Nov 2010 23:27:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.546
X-Spam-Level: 
X-Spam-Status: No, score=-2.546 tagged_above=-999 required=5 tests=[AWL=0.053,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0zsQ2BEoqJqw for <eman@core3.amsl.com>; Sun,  7 Nov 2010 23:27:34 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id 8ED2F3A67E4 for <eman@ietf.org>; Sun,  7 Nov 2010 23:27:33 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oA87KKvj023069; Mon, 8 Nov 2010 08:20:20 +0100 (CET)
Received: from [10.68.17.175] (sin-vpn-client-17-175.cisco.com [10.68.17.175]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oA87KE7q016762; Mon, 8 Nov 2010 08:20:16 +0100 (CET)
Message-ID: <4CD7A4AD.1040608@cisco.com>
Date: Mon, 08 Nov 2010 15:20:13 +0800
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: Chris Verges <chrisv@cyberswitching.com>
References: <C8EFF4A6.163CA%quittek@neclab.eu> <4CCE3065.6050705@nteczone.com>	<68FBE0F3CE97264395875AC1C468F22C514765@mail03.cyberswitching.local>	<4CD0C560.7080907@nteczone.com> <68FBE0F3CE97264395875AC1C468F22C5148AE@mail03.cyberswitching.local>
In-Reply-To: <68FBE0F3CE97264395875AC1C468F22C5148AE@mail03.cyberswitching.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: eman@ietf.org, Christian Groves <Christian.Groves@nteczone.com>
Subject: Re: [eman] Entity identification method
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 07:27:36 -0000

Hi Chris,

Question: could the business context be used to achieve what you want to?
See 
http://tools.ietf.org/html/draft-claise-power-management-arch-02#section-5.4

Regards, Benoit
> Hi Christian et al.,
>
> How about the following two use cases to augment the existing
> power-allocation-per-virtual-machine scenario?
>
> 	1. "Grouped" outlets on a smart PDU
>
> 	2. Tenant submetering on a smart meter
>
> In the first scenario, several smart PDUs allow the user to create a
> user-defined grouping that consists of several outlets.  Physical
> outlets 1 and 7, for example, could be grouped together as logical
> entity "server01".  This mapping could be created using the existing
> ENTITY-MIB architecture.  The power data for both the physical and
> logical entities are useful to facilities and IT managers to understand
> power flow and usage.
>
> In the second scenario, a smart meter provides submetering for a
> commercial rental building.  Such buildings often occur turnover in
> tenants.  A submeter that meters each circuit in the building, for
> example, could maintain that data in both granular and aggregate form.
> When a tenant moves in, the facilities manager can create a new logical
> entity for that tenant and map the physical circuit entries to the
> tenant's logical entity.  This enables both real-time power usage and
> management on an individual circuit basis (useful for troubleshooting
> facilities problems) as well as on a customized aggregate basis (useful
> for the bean counters who have to allocate costs).
>
> Here's an interesting question as far as implementation is concerned ...
> why not implement pmPhysicalMap and pmLogicalMap tables (like
> entLPMappingTable) to map the pmIndex entity to the appropriate physical
> or logical entity (1:1 only?)
>
> Chris
>
>
> -----Original Message-----
> From: Christian Groves [mailto:Christian.Groves@nteczone.com]
> Sent: Tuesday, November 02, 2010 7:14 PM
> To: Chris Verges
> Cc: eman@ietf.org
> Subject: Re: [eman] Entity identification method
>
> Hello Chris,
>
> I don't have any concrete suggestions for implementing virtual entity
> energy usage support. I'm still at the stage of trying to see what the
> requirements and framework is for the work. There seems to be a focus on
> the MIBs themselves, when without good requirements its hard to see what
> needs they are meeting. The work of the eman WG could address IP type
> servers only or the MIBs could also be used in other telecommunication
> equipment i.e. those used in outside plant. I'm encouraged to see
> Bruce's email on topics for discussion as think its in important to get
> consensus/understanding on these before the MIBs are developed.
>
> Please see my comment below marked [CNG].
>
> Regards, Christian
>
> On 1/11/2010 11:39 PM, Chris Verges wrote:
>> Hi Christian,
>>
>> Are you looking to allocate actual energy usage by a virtual entity,
>> like the amount of energy used by a virtual machine running on a
>> shared server? Certainly an interesting problem ... gives a lot of
>> room for innovation for different vendors to find solutions.
>>
> [CNG] I agree its an interesting problem. In some instances it may be
> possible to allocate the actual energy however in many cases it would be
> very difficult/impossible. In these more difficult cases it may be
> possible to simply report the identities of the virtual/logical entities
> that are included in the physical measurement.
>>  From a MIB standpoint, it seems like the requirement is to have a
>> flexible power-related MIB that can either map to physical or logical
>> entities. One question is, "where do you want those entities
> enumerated?"
>> Are virtual entities that need to be mapped to power usage normally
>> enumerated in ENTITY-MIB in the "logical" table?
>>
>> If so, perhaps something like this would fit the bill:
>>
>> POWER-ENTITY-MIB:
>>
>> pwrEntityTable
>>
>> pwrEntityEntry
>>
>> pwrEntityIndex
>>
>> pwrEntityName
>>
>> pwrEntityType
>>
>> pwrEntityParent
>>
>> pwrEntityPhysical
>>
>> pwrEntityLogical
>>
>> The pwrEntity[Physical|Logical] objects would point to the appropriate
>> index in ENTITY-MIB.
>>
>> However, if the virtual entities are not enumerated in ENTITY-MIB, the
>> pwrEntityLogical column is probably overkill. The virtual entities can
>> be enumerated in pwrEntityTable and linked to the Physical meter using
>> the pwrEntityParent column, much like how ENTITY-MIB currently manages
>> references between parent and component entities. It would just
>> involve a new pwrEntityType being added for "virtual" or something
>> similar.
>>
>> So what's the typical use case as these virtual entities relate to
>> ENTITY-MIB?
>>
> [CNG] I'm not sure the typical case. Either of the approaches above
> could be sufficient but I think it depends on what people agree on with
> respect to virtual entities and how the data collected on them would be
> used.
>> Chris
>>
>> -----Original Message-----
>> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf
>> Of Christian Groves
>> Sent: Sunday, October 31, 2010 8:14 PM
>> To: eman@ietf.org
>> Subject: Re: [eman] Entity identification method
>>
>> Hello Juergen,
>>
>> I think distinguishing the two cases is the correct way to go.
>>
>> I agree that reporting energy consumption for logical entities is a
>> challenge and not straight forward. I guess there are a number of ways
>> to look at this problem and how address the problem depends on the
>> ambition level.
>>
>> As you rightly mention where there is partial use of a physical
>> resource by a logical entity it is very difficult to have an exact
>> figure.
>>
>> However I think the "grain size" of the measurement comes into play.
>> For example if we have a large gateway implementing several virtual
>> gateways if we take an overall measurement then we have the problem
>> determining a figure. If the however the virtual gateways were each
>> assigned a physical rack and the measurements were taken at a rack
>> level then we have a more precise estimate of contribution of each
>> virtual gateway to the overall picture.
>>
>> For me logical entities ultimately will be realised by physical
>> hardware. The key is understanding the relationship between these
>> entities. Thus I think virtualization can in some way be supported by
>> allowing energy consumption reports for physical entities to indicate
>> if/what logical entities they relate to. As they say information is
>> power (pardon the pun :-) ).
>>
>> Regards, Christian
>>
>> On 29/10/2010 12:48 PM, Juergen Quittek wrote:
>>
>>> Hi Christian,
>>> Thank you for this interesting comment.
>>> It looks like we have to distinguish two cases: power state
>>> monitoring
>>> and energy consumption monitoring.
>>> For a logical entity and a virtual machine it may be well possible
>>> to
>>> report on their power state. However, reporting their energy
>>> consumption seems to be a tough challenge at least if be base it on
>> real measurements.
>>
>>> It is well feasible to measure energy consumption of physical
>>> entities, but if you have a logical entity that consumes only
>>> partial
>>> resources of a physical entity, then precise measurement of the
>>> energy
>>> consumption will be hardly possible. Estimations may be possible
>>> based
>>> on a model of the logical entity, but I don't know how good such
>> models can be.
>>
>>> Thanks,
>>> Juergen
>>> On 29.10.10 03:25 "Christian Groves"<Christian.Groves@nteczone.com
>> <mailto:Christian.Groves@nteczone.com>>  wrote:
>>
>>>> Hello
>>>> I've just started to digest the various drafts of the eman wg and I
>>>> see the comment below on logical entities. It's not clear to me
>>>> how/if network virtualization is intended on being handled in the
>> eman work.
>>
>>>> In networks there's now a trend towards network virtualization and
>>>> cloud computing with the different "X" as a service models (i.e.
>>>> Amazon EC2 "platform as a service" running different server
>>>> instances). Even in today's networks we have physical gateways that
>>>> are virtualized into different logical gateways. For example:
>>>> H.248/Megaco virtual MG (VMG) concept.
>>>> I think it would be advantageous to be able to assess the energy
>>>> consumption of the VMGs or instances (which are logical entities)
>>>> independent of the physical gateway so that a customers energy use
>>>> may be recording. Will this sort of functionality be allowed?
>>>> Regards, Christian
>>>> On 29/10/2010 1:22 AM, Juergen Quittek wrote:
>>>>> Hi Chris,
>>>>> I think it may become very difficult if we want to assess energy
>>>>> consumption of logical entities. It seems to be reasonable and
>>>>> practical to limit energy consumption measurements to physical
>>>>> entities. The ENERGY AWARE MIB module
>>>>> (draft-parello-eman-energy-aware-mib) and the POWER MIB
>>>>> (draft-quittek-power-mib-02) went this way.
>>>>> Just using entPhysicalIndex solves some of the problem you
> mentioned.
>>>>> Particularly, you don't need a mapping table to entities if you
>>>>> restrict Yourself to entPhysicalIndex.
>>>>> Thanks,
>>>>> Juergen
>>>>> On 28.10.10 13:34 "Chris Verges"<chrisv@cyberswitching.com
>> <mailto:chrisv@cyberswitching.com>>  wrote:
>>
>>>>>> Hi Jurgen and all,
>>>>>> The more I've been thinking about these scenarios, the more
>>>>>> something doesn't seem quite right. I'll try to explain my
>>>>>> thought
>>>>>> process behind this and see if my concerns/confusions get
> captured.
>>>>>> ENTITY-MIB provides enumerated lists of physical and logical
>>>>>> entities on the system. The indices in both lists are maintained
>>>>>> separately, so there is not a single, unique identifier provided.
>>>>>> Because of this, the MIBs being discussed by the EMAN WG must
>>>>>> only
>>>>>> reference to one type (physical or logical) and are limited to
>> that without additional work.
>>
>>>>>> At some point in my mind, I'm asking myself the question, "What's
>>>>>> the point of linking to ENTITY-MIB?"
>>>>>> More on that question in later scenarios below ...
>>>>>> One possibility would be to create a separate mapping table that
>>>>>> gives a guaranteed unique index based on all entities, regardless
>>>>>> of type. The physical vs. logical extensions would then become
>>>>>> sparse tables that augment this. For example:
>>>>>> ENTITY-MIB : entityGeneral.entGeneralTable.entGeneralEntry
>>>>>> +-----------------+-----------------+-----+
>>>>>> | entGeneralIndex | entGeneralDescr | ... |
>>>>>> +-----------------+-----------------+-----+
>>>>>> | 1 | PDU Chassis | |
>>>>>> +-----------------+-----------------+-----+
>>>>>> | 2 | Meter #1 | |
>>>>>> +-----------------+-----------------+-----+
>>>>>> | 3 | Meter #2 | |
>>>>>> +-----------------+-----------------+-----+
>>>>>> | 4 | Remote Meter #1 | |
>>>>>> +-----------------+-----------------+-----+
>>>>>> ENTITY-MIB : entityPhysical.entPhysicalTable.entPhysicalEntry
>>>>>> +-----------------+-----------------+-----+
>>>>>> | entGeneralIndex | entVendorType | ... |
>>>>>> +-----------------+-----------------+-----+
>>>>>> | 1 | enterprises.foo | |
>>>>>> +-----------------+-----------------+-----+
>>>>>> | 2 | enterprises.foo | |
>>>>>> +-----------------+-----------------+-----+
>>>>>> | 3 | enterprises.foo | |
>>>>>> +-----------------+-----------------+-----+
>>>>>> ENTITY-MIB : entityLogical.entLogicalTable.entLogicalEntry
>>>>>> +-----------------+----------------------+-----+
>>>>>> | entGeneralIndex | entLogicalCommunity | ... |
>>>>>> +-----------------+----------------------+-----+
>>>>>> | 4 | remote-power-group-1 | |
>>>>>> +-----------------+----------------------+-----+
>>>>>> It seems like this 'entGeneralIndex' concept is what's missing
>>>>>> from
>>>>>> the current ENTITY-MIB, and is causing problems when thinking
>>>>>> about
>>>>>> local and remote power data being reported by the same agent.
>>>>>> Another possibility would be to choose one -- entLogicalIndex,
>>>>>> most
>>>>>> likely -- and require that anyone who wants to implement the EMAN
>>>>>> WG MIBs to always create an entLogicalEntry for the power data.
>>>>>> In
>>>>>> this context, the entLogicalTable fills the role of
>>>>>> entGeneralTable
>>>>>> as described above. For all entPhysicalTable entries, there would
>>>>>> need to be a corresponding entry in entLogicalTable with a 1:1
>>>>>> mapping between them. For all remote entries, there would be a
>>>>>> unique entry in entLogicalTable. Of course, this would add some
>>>>>> additional overhead on the part of the implementer, but isn't too
>> overburdening.
>>
>>>>>> A third possibility is that ENTITY-MIB just doesn't do what we
>>>>>> need
>>>>>> in its present form and we need to think about enumerating power
>>>>>> sensors separately from other components/sensors on the system.
>>>>>> It
>>>>>> seems like entPhysicalTable gives a good starting template for a
>>>>>> new 'POWER-ENTITY-MIB', but can be extended to include support
>>>>>> for
>>>>>> remote agents. The difference would be a clean break from the
>>>>>> legacy ENTITY-MIB structure.
>>>>>> And with that, I look forward to others' feedback and ideas on
>>>>>> solving this problem!
>>>>>> Thanks,
>>>>>> Chris
>>>>>> -----Original Message-----
>>>>>> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On
>>>>>> Behalf Of Chris Verges
>>>>>> Sent: Tuesday, October 26, 2010 9:26 PM
>>>>>> To: Juergen Quittek; Benoit Claise; eman mailing list
>>>>>> Subject: Re: [eman] Entity identification method (was: EMAN
>>>>>> chartered itemsversus drafts)
>>>>>> Hi Juergen and all,
>>>>>> Agreed that a common ID method makes sense, and ENTITY-MIB seems
>>>>>> to
>>>>>> be a good choice. In case (c) from your list, wouldn't the remote
>>>>>> agent condition be handled by ENTITY-MIB supporting a logical
>>>>>> entity that is the remote agent iself? Since the logical entity
>>>>>> is
>>>>>> in the ENTITY-MIB table, it would be given a unique ID mixed
>>>>>> amongst the other logical and physical entities.
>>>>>> At that point, should all of the MIBs being discussed in the EMAN
>>>>>> WG be sparse table augmentations of ENTITY-MIB?
>>>>>> Thanks,
>>>>>> Chris
>>>>>> -----Original Message-----
>>>>>> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On
>>>>>> Behalf Of Juergen Quittek
>>>>>> Sent: Tuesday, October 26, 2010 6:01 AM
>>>>>> To: Benoit Claise; eman mailing list
>>>>>> Subject: [eman] Entity identification method (was: EMAN chartered
>>>>>> items versus drafts)
>>>>>> Hi Benoit and all,
>>>>>> I agree that we should find a common identification method for
>>>>>> entities used by all MIB modules. This does not apply to the
>>>>>> POWER
>>>>>> MIB only, but to all MIB modules in the eman WG.
>>>>>> The modules will use an entity ID as index for their tables.
>>>>>> Which entity is identified by the index can be resolved by other
>>>>>> MIB modules, such as the POWER AWARE MIB module
>>>>>> (draft-parello-eman-energy-aware-mib) or the ENTITY MIB module
>>>>>> (RFC
>>>>>> 4133).
>>>>>> I see three basic scenarios for the entity identification:
>>>>>> a) a device just reports on its own power state and energy
>>>>>> consumption and it reports on its own as a single unit.
>>>>>> Then we have a single index only stating "it's me".
>>>>>> Such a device usually does not need further identification
>>>>>> of itself, because typically there are sufficient other
>>>>>> MIB modules for this purpose running in the same SNMP engine,
>>>>>> that provide information about the device's IP address,
>>>>>> manufacturer, operating system, etc. In such a case a
>>>>>> 'trivial' index, such as '0' should be used in order to
>>>>>> keep it simple in this most simple case.
>>>>>> b) a device reports on its own but not just as a single unit
>>>>>> but it reports power states and energy consumption for its
>>>>>> individual components, for example it may report separately
>>>>>> on contained hard drives, line cards, back planes,
>>>>>> processor boards, etc.
>>>>>> In such a case, identification of these components as
>>>>>> individual entities would be required. The ENTITY MIB
>>>>>> module was designed for this purpose and would be a good
>>>>>> choice here. Also the POWER AWARE MIB module would be
>>>>>> useful in this case.
>>>>>> c) a device reports on energy consumption of other, remote
>>>>>> devices. Then remote devices (and potentially also their
>>>>>> contained components need to be identified. For
>>>>>> identifying remote components there is the POWER AWARE MIB
>>>>>> module that has been designed for this purpose. As far as
>>>>>> I understand, the ENTITY MIB module is not applicable to
>>>>>> remote devices.
>>>>>> In summary,
>>>>>> - if you need to report on remote entities (case c)),
>>>>>> you need the POWER AWARE MIB module,
>>>>>> - if you report only on entities locally contained
>>>>>> in the reporting device (case b)), you can use
>>>>>> the POWER AWARE MIB or the ENTITY MIB
>>>>>> - if you report just on your own as a single device
>>>>>> (case a)), identification is trivial
>>>>>> Hence, my recommendation (stated for POWER-STATE MIB and ENERGY
>>>>>> MIB
>>>>>> in
>>>>>> draft-quittek-power-mib-02) would be:
>>>>>> If there is an implementation of the POWER AWARE MIB module
>>>>>> instantiated in the local SNMP engine, then you SHOULD (or MUST?)
>>>>>> use it for indexing (pmIndex).
>>>>>> If this is not the case but there is an ENTITY MIB instance
>>>>>> available, then you SHOULD use this one (entPhysicalIndex).
>>>>>> If neither of this MIB modules is available you should use index
>>>>>> 0
>>>>>> only and be limited to report on the local device as a single
>> entity only.
>>
>>>>>> That's just my view. Certainly, there are more ways of entity
>>>>>> identification. I look forward to discussing them.
>>>>>> Thanks,
>>>>>> Juergen
>>>>>> On 26.10.10 11:44 "Benoit Claise"<bclaise@cisco.com
>> <mailto:bclaise@cisco.com>>  wrote:
>>
>>>>>>> Hi Juergen,
>>>>>>> Thanks for the clarification.
>>>>>>> Something key is to agree on the Power Monitor index for all MIB
>>>>>>> modules, which IMHO should be part of the Energy-aware Networks
>>>>>>> and Devices MIB module, but reuse in the other MIB modules.
>>>>>>> Regards, Benoit.
>>>>>>>> Hi Benoit,
>>>>>>>> Thanks for checking all drafts.
>>>>>>>> I don't think that draft-quittek-power-mib-02 makes significant
>>>>>>>> contributions to the Energy-aware Networks and Devices MIB.
>>>>>>>> It just covers the Power and Energy Monitoring MIB and the
>>>>>>>> Battery
>>>>>> MIB.
>>>>>>>> Thanks,
>>>>>>>> Juergen
>>>>>>>> On 26.10.10 08:22 "Benoit Claise"<bclaise@cisco.com
>> <mailto:bclaise@cisco.com>>  wrote:
>>
>>>>>>>>> Dear all,
>>>>>>>>> I went through the exercise of mapping the existing six
>>>>>>>>> chartered items with the existing draft content.
>>>>>>>>> _Energy Management Requirements_
>>>>>>>>> http://tools.ietf.org/html/draft-quittek-power-monitoring-requ
>>>>>>>>> ir
>>>>>>>>> emen
>>>>>>>>> ts-02
>>>>>>>>> https://datatracker.ietf.org/doc/draft-norwin-energy-consider/
>>>>>>>>> _
>>>>>>>>> Energy Management Framework_
>>>>>>>>> http://tools.ietf.org/html/draft-claise-power-management-arch-
>>>>>>>>> 02
>>>>>>>>> _Energy-aware Networks and Devices MIB_
>>>>>>>>> http://tools.ietf.org/html/draft-parello-eman-energy-aware-mib
>>>>>>>>> -0
>>>>>>>>> 0
>>>>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>>>>>>>>> _Power and Energy Monitoring MIB_
>>>>>>>>> http://tools.ietf.org/html/draft-claise-energy-monitoring-mib-
>>>>>>>>> 06
>>>>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>>>>>>>>> _Battery MIB_
>>>>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>>>>>>>>> _Energy Management Applicability_
>>>>>>>>> http://datatracker.ietf.org/doc/draft-tychon-eman-applicabilit
>>>>>>>>> y-
>>>>>>>>> stat
>>>>>>>>> ement/
>>>>>>>>> Please let me know if I made any mistakes or if I missed any
>> draft?
>>
>>>>>>>>> Regards, Benoit.
>>>>>>>>> _______________________________________________
>>>>>>>>> eman mailing list
>>>>>>>>> eman@ietf.org<mailto:eman@ietf.org>
>>>>>>>>> https://www.ietf.org/mailman/listinfo/eman
>>>>>> _______________________________________________
>>>>>> eman mailing list
>>>>>> eman@ietf.org<mailto:eman@ietf.org>
>>>>>> https://www.ietf.org/mailman/listinfo/eman
>>>>> _______________________________________________
>>>>> eman mailing list
>>>>> eman@ietf.org<mailto:eman@ietf.org>
>>>>> https://www.ietf.org/mailman/listinfo/eman
>>>> _______________________________________________
>>>> eman mailing list
>>>> eman@ietf.org<mailto:eman@ietf.org>
>>>> https://www.ietf.org/mailman/listinfo/eman
>>> _______________________________________________
>>> eman mailing list
>>> eman@ietf.org<mailto:eman@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/eman
>> _______________________________________________
>>
>> eman mailing list
>>
>> eman@ietf.org<mailto:eman@ietf.org>
>>
>> https://www.ietf.org/mailman/listinfo/eman
>>
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman


From chrisv@cyberswitching.com  Mon Nov  8 07:11:26 2010
Return-Path: <chrisv@cyberswitching.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB2823A690A for <eman@core3.amsl.com>; Mon,  8 Nov 2010 07:11:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zVh6WuyzEV5m for <eman@core3.amsl.com>; Mon,  8 Nov 2010 07:11:20 -0800 (PST)
Received: from p01c12o141.mxlogic.net (p01c12o141.mxlogic.net [208.65.145.64]) by core3.amsl.com (Postfix) with ESMTP id A92FE3A68B0 for <eman@ietf.org>; Mon,  8 Nov 2010 07:11:18 -0800 (PST)
Received: from unknown [64.81.28.110] (EHLO mail03.cyberswitching.local) by p01c12o141.mxlogic.net(mxl_mta-6.7.0-2) with ESMTP id b2318dc4.0.2105.00-355.4928.p01c12o141.mxlogic.net (envelope-from <chrisv@cyberswitching.com>);  Mon, 08 Nov 2010 08:11:40 -0700 (MST)
X-MXL-Hash: 4cd8132c527ed777-85186231af1ea042d0337f26bac778f1f501be3e
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 8 Nov 2010 07:10:54 -0800
Message-ID: <68FBE0F3CE97264395875AC1C468F22C514A7F@mail03.cyberswitching.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [eman] Entity identification method
Thread-Index: Act/FdUQxnqQs8BHQOOyYjA7hTFRYAAP5g0A
References: <C8EFF4A6.163CA%quittek@neclab.eu> <4CCE3065.6050705@nteczone.com>	<68FBE0F3CE97264395875AC1C468F22C514765@mail03.cyberswitching.local>	<4CD0C560.7080907@nteczone.com> <68FBE0F3CE97264395875AC1C468F22C5148AE@mail03.cyberswitching.local> <4CD7A4AD.1040608@cisco.com>
From: "Chris Verges" <chrisv@cyberswitching.com>
To: "Benoit Claise" <bclaise@cisco.com>
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010110201)]
X-MAIL-FROM: <chrisv@cyberswitching.com>
X-SOURCE-IP: [64.81.28.110]
X-AnalysisOut: [v=1.0 c=1 a=aPxnrr7mnCkA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel]
X-AnalysisOut: [0A:10 a=4zsJQXJisSY22NXBO5KRuA==:17 a=AUd_NHdVAAAA:8 a=48v]
X-AnalysisOut: [gC7mUAAAA:8 a=r3s3_62XAAAA:8 a=wzgqfsuUAAAA:8 a=0ZaI8hDWP_]
X-AnalysisOut: [BFVjCIhfgA:9 a=FJ8aJvdPqffHt-KhTR8A:7 a=jyOaRm-1YOJbVI7l9R]
X-AnalysisOut: [D5Rsvzz_IA:4 a=CjuIK1q_8ugA:10 a=JfD0Fch1gWkA:10 a=lZB815d]
X-AnalysisOut: [zVvQA:10 a=3wXEbymkWtoA:10 a=yvfu_RGVus0A:10 a=QNAnhOz5Yt3]
X-AnalysisOut: [X6TGT:21 a=LRCBuejpyb7k5vMI:21]
Cc: eman@ietf.org, Christian Groves <Christian.Groves@nteczone.com>
Subject: Re: [eman] Entity identification method
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 15:11:26 -0000

Hi Benoit,

In Section 5.4, the "keywords" and/or "role" fields are perhaps the two
that can *best* achieve the business context being described.  However,
neither of these take into account the data reporting aspect.  For
example:

A server's redundant power supplies are connected to two different
outlets on a smart power strip.  Each outlet is enumerated in the EMAN
MIBs as separate entities, and the "role" is set to "server01",
indicating that these outlets are linking in business context through
the server's hostname.  (Use any other metric you want, the result is
still the same.)  I know how much power each power supply is then
drawing since the MIB splits the data out by outlet.  However, I do not
know the aggregate power draw of the server itself, since there is no
"server01" data entry.  There can't be, as there is no corresponding
pmIndex for the server entity.  What's useful is to know all three
datapoints: the power on supply A, the power on supply B, and the power
on the server as a whole.  Yes, it should be a fairly straight-forward
vector math calculation, but more complex scenarios could be crafted
using three phase, automatic transfer switches, solar panels, etc.

The point is that while the "role" and "keywords" fields can be used to
establish business context for a particular entity in the MIB, I'm wary
over whether they can be used to aggregate data or manage aggregated
control over multiple entities being logically grouped together.  At
least, given the current sparse table extension methodology behind the
proposed set of MIBs.

Perhaps mapping to ENTITY-MIB isn't required at this point.  What if
power entities (POWER-ENTITY-MIB?) are separate from ENTITY-MIB
entirely?  These two tables could later be mapped together through a
separate set of tables to ENTITY-MIB, which would establish the ability
for an M:N mapping between POWER-ENTITY-MIB and the physical and logical
tables of ENTITY-MIB separately.  That would allow us to link the
entities IF IT MAKES SENSE and in a way that makes sense.  But it's not
part of the core definition of a power entity, in a more limited 1:1
fashion.

Thanks,
Chris

-----Original Message-----
From: Benoit Claise [mailto:bclaise@cisco.com]=20
Sent: Sunday, November 07, 2010 11:20 PM
To: Chris Verges
Cc: Christian Groves; eman@ietf.org
Subject: Re: [eman] Entity identification method

Hi Chris,

Question: could the business context be used to achieve what you want
to?
See
http://tools.ietf.org/html/draft-claise-power-management-arch-02#section
-5.4

Regards, Benoit
> Hi Christian et al.,
>
> How about the following two use cases to augment the existing=20
> power-allocation-per-virtual-machine scenario?
>
> 	1. "Grouped" outlets on a smart PDU
>
> 	2. Tenant submetering on a smart meter
>
> In the first scenario, several smart PDUs allow the user to create a=20
> user-defined grouping that consists of several outlets.  Physical=20
> outlets 1 and 7, for example, could be grouped together as logical=20
> entity "server01".  This mapping could be created using the existing=20
> ENTITY-MIB architecture.  The power data for both the physical and=20
> logical entities are useful to facilities and IT managers to=20
> understand power flow and usage.
>
> In the second scenario, a smart meter provides submetering for a=20
> commercial rental building.  Such buildings often occur turnover in=20
> tenants.  A submeter that meters each circuit in the building, for=20
> example, could maintain that data in both granular and aggregate form.
> When a tenant moves in, the facilities manager can create a new=20
> logical entity for that tenant and map the physical circuit entries to

> the tenant's logical entity.  This enables both real-time power usage=20
> and management on an individual circuit basis (useful for=20
> troubleshooting facilities problems) as well as on a customized=20
> aggregate basis (useful for the bean counters who have to allocate
costs).
>
> Here's an interesting question as far as implementation is concerned
...
> why not implement pmPhysicalMap and pmLogicalMap tables (like
> entLPMappingTable) to map the pmIndex entity to the appropriate=20
> physical or logical entity (1:1 only?)
>
> Chris
>
>
> -----Original Message-----
> From: Christian Groves [mailto:Christian.Groves@nteczone.com]
> Sent: Tuesday, November 02, 2010 7:14 PM
> To: Chris Verges
> Cc: eman@ietf.org
> Subject: Re: [eman] Entity identification method
>
> Hello Chris,
>
> I don't have any concrete suggestions for implementing virtual entity=20
> energy usage support. I'm still at the stage of trying to see what the

> requirements and framework is for the work. There seems to be a focus=20
> on the MIBs themselves, when without good requirements its hard to see

> what needs they are meeting. The work of the eman WG could address IP=20
> type servers only or the MIBs could also be used in other=20
> telecommunication equipment i.e. those used in outside plant. I'm=20
> encouraged to see Bruce's email on topics for discussion as think its=20
> in important to get consensus/understanding on these before the MIBs
are developed.
>
> Please see my comment below marked [CNG].
>
> Regards, Christian
>
> On 1/11/2010 11:39 PM, Chris Verges wrote:
>> Hi Christian,
>>
>> Are you looking to allocate actual energy usage by a virtual entity,=20
>> like the amount of energy used by a virtual machine running on a=20
>> shared server? Certainly an interesting problem ... gives a lot of=20
>> room for innovation for different vendors to find solutions.
>>
> [CNG] I agree its an interesting problem. In some instances it may be=20
> possible to allocate the actual energy however in many cases it would=20
> be very difficult/impossible. In these more difficult cases it may be=20
> possible to simply report the identities of the virtual/logical=20
> entities that are included in the physical measurement.
>>  From a MIB standpoint, it seems like the requirement is to have a=20
>> flexible power-related MIB that can either map to physical or logical

>> entities. One question is, "where do you want those entities
> enumerated?"
>> Are virtual entities that need to be mapped to power usage normally=20
>> enumerated in ENTITY-MIB in the "logical" table?
>>
>> If so, perhaps something like this would fit the bill:
>>
>> POWER-ENTITY-MIB:
>>
>> pwrEntityTable
>>
>> pwrEntityEntry
>>
>> pwrEntityIndex
>>
>> pwrEntityName
>>
>> pwrEntityType
>>
>> pwrEntityParent
>>
>> pwrEntityPhysical
>>
>> pwrEntityLogical
>>
>> The pwrEntity[Physical|Logical] objects would point to the=20
>> appropriate index in ENTITY-MIB.
>>
>> However, if the virtual entities are not enumerated in ENTITY-MIB,=20
>> the pwrEntityLogical column is probably overkill. The virtual=20
>> entities can be enumerated in pwrEntityTable and linked to the=20
>> Physical meter using the pwrEntityParent column, much like how=20
>> ENTITY-MIB currently manages references between parent and component=20
>> entities. It would just involve a new pwrEntityType being added for=20
>> "virtual" or something similar.
>>
>> So what's the typical use case as these virtual entities relate to=20
>> ENTITY-MIB?
>>
> [CNG] I'm not sure the typical case. Either of the approaches above=20
> could be sufficient but I think it depends on what people agree on=20
> with respect to virtual entities and how the data collected on them=20
> would be used.
>> Chris
>>
>> -----Original Message-----
>> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf=20
>> Of Christian Groves
>> Sent: Sunday, October 31, 2010 8:14 PM
>> To: eman@ietf.org
>> Subject: Re: [eman] Entity identification method
>>
>> Hello Juergen,
>>
>> I think distinguishing the two cases is the correct way to go.
>>
>> I agree that reporting energy consumption for logical entities is a=20
>> challenge and not straight forward. I guess there are a number of=20
>> ways to look at this problem and how address the problem depends on=20
>> the ambition level.
>>
>> As you rightly mention where there is partial use of a physical=20
>> resource by a logical entity it is very difficult to have an exact=20
>> figure.
>>
>> However I think the "grain size" of the measurement comes into play.
>> For example if we have a large gateway implementing several virtual=20
>> gateways if we take an overall measurement then we have the problem=20
>> determining a figure. If the however the virtual gateways were each=20
>> assigned a physical rack and the measurements were taken at a rack=20
>> level then we have a more precise estimate of contribution of each=20
>> virtual gateway to the overall picture.
>>
>> For me logical entities ultimately will be realised by physical=20
>> hardware. The key is understanding the relationship between these=20
>> entities. Thus I think virtualization can in some way be supported by

>> allowing energy consumption reports for physical entities to indicate

>> if/what logical entities they relate to. As they say information is=20
>> power (pardon the pun :-) ).
>>
>> Regards, Christian
>>
>> On 29/10/2010 12:48 PM, Juergen Quittek wrote:
>>
>>> Hi Christian,
>>> Thank you for this interesting comment.
>>> It looks like we have to distinguish two cases: power state=20
>>> monitoring and energy consumption monitoring.
>>> For a logical entity and a virtual machine it may be well possible=20
>>> to report on their power state. However, reporting their energy=20
>>> consumption seems to be a tough challenge at least if be base it on
>> real measurements.
>>
>>> It is well feasible to measure energy consumption of physical=20
>>> entities, but if you have a logical entity that consumes only=20
>>> partial resources of a physical entity, then precise measurement of=20
>>> the energy consumption will be hardly possible. Estimations may be=20
>>> possible based on a model of the logical entity, but I don't know=20
>>> how good such
>> models can be.
>>
>>> Thanks,
>>> Juergen
>>> On 29.10.10 03:25 "Christian Groves"<Christian.Groves@nteczone.com
>> <mailto:Christian.Groves@nteczone.com>>  wrote:
>>
>>>> Hello
>>>> I've just started to digest the various drafts of the eman wg and I
>>>> see the comment below on logical entities. It's not clear to me
>>>> how/if network virtualization is intended on being handled in the
>> eman work.
>>
>>>> In networks there's now a trend towards network virtualization and
>>>> cloud computing with the different "X" as a service models (i.e.
>>>> Amazon EC2 "platform as a service" running different server
>>>> instances). Even in today's networks we have physical gateways that
>>>> are virtualized into different logical gateways. For example:
>>>> H.248/Megaco virtual MG (VMG) concept.
>>>> I think it would be advantageous to be able to assess the energy
>>>> consumption of the VMGs or instances (which are logical entities)
>>>> independent of the physical gateway so that a customers energy use
>>>> may be recording. Will this sort of functionality be allowed?
>>>> Regards, Christian
>>>> On 29/10/2010 1:22 AM, Juergen Quittek wrote:
>>>>> Hi Chris,
>>>>> I think it may become very difficult if we want to assess energy
>>>>> consumption of logical entities. It seems to be reasonable and
>>>>> practical to limit energy consumption measurements to physical
>>>>> entities. The ENERGY AWARE MIB module
>>>>> (draft-parello-eman-energy-aware-mib) and the POWER MIB
>>>>> (draft-quittek-power-mib-02) went this way.
>>>>> Just using entPhysicalIndex solves some of the problem you
> mentioned.
>>>>> Particularly, you don't need a mapping table to entities if you
>>>>> restrict Yourself to entPhysicalIndex.
>>>>> Thanks,
>>>>> Juergen
>>>>> On 28.10.10 13:34 "Chris Verges"<chrisv@cyberswitching.com
>> <mailto:chrisv@cyberswitching.com>>  wrote:
>>
>>>>>> Hi Jurgen and all,
>>>>>> The more I've been thinking about these scenarios, the more
>>>>>> something doesn't seem quite right. I'll try to explain my
>>>>>> thought
>>>>>> process behind this and see if my concerns/confusions get
> captured.
>>>>>> ENTITY-MIB provides enumerated lists of physical and logical
>>>>>> entities on the system. The indices in both lists are maintained
>>>>>> separately, so there is not a single, unique identifier provided.
>>>>>> Because of this, the MIBs being discussed by the EMAN WG must
>>>>>> only
>>>>>> reference to one type (physical or logical) and are limited to
>> that without additional work.
>>
>>>>>> At some point in my mind, I'm asking myself the question, "What's
>>>>>> the point of linking to ENTITY-MIB?"
>>>>>> More on that question in later scenarios below ...
>>>>>> One possibility would be to create a separate mapping table that
>>>>>> gives a guaranteed unique index based on all entities, regardless
>>>>>> of type. The physical vs. logical extensions would then become
>>>>>> sparse tables that augment this. For example:
>>>>>> ENTITY-MIB : entityGeneral.entGeneralTable.entGeneralEntry
>>>>>> +-----------------+-----------------+-----+
>>>>>> | entGeneralIndex | entGeneralDescr | ... |
>>>>>> +-----------------+-----------------+-----+
>>>>>> | 1 | PDU Chassis | |
>>>>>> +-----------------+-----------------+-----+
>>>>>> | 2 | Meter #1 | |
>>>>>> +-----------------+-----------------+-----+
>>>>>> | 3 | Meter #2 | |
>>>>>> +-----------------+-----------------+-----+
>>>>>> | 4 | Remote Meter #1 | |
>>>>>> +-----------------+-----------------+-----+
>>>>>> ENTITY-MIB : entityPhysical.entPhysicalTable.entPhysicalEntry
>>>>>> +-----------------+-----------------+-----+
>>>>>> | entGeneralIndex | entVendorType | ... |
>>>>>> +-----------------+-----------------+-----+
>>>>>> | 1 | enterprises.foo | |
>>>>>> +-----------------+-----------------+-----+
>>>>>> | 2 | enterprises.foo | |
>>>>>> +-----------------+-----------------+-----+
>>>>>> | 3 | enterprises.foo | |
>>>>>> +-----------------+-----------------+-----+
>>>>>> ENTITY-MIB : entityLogical.entLogicalTable.entLogicalEntry
>>>>>> +-----------------+----------------------+-----+
>>>>>> | entGeneralIndex | entLogicalCommunity | ... |
>>>>>> +-----------------+----------------------+-----+
>>>>>> | 4 | remote-power-group-1 | |
>>>>>> +-----------------+----------------------+-----+
>>>>>> It seems like this 'entGeneralIndex' concept is what's missing
>>>>>> from
>>>>>> the current ENTITY-MIB, and is causing problems when thinking
>>>>>> about
>>>>>> local and remote power data being reported by the same agent.
>>>>>> Another possibility would be to choose one -- entLogicalIndex,
>>>>>> most
>>>>>> likely -- and require that anyone who wants to implement the EMAN
>>>>>> WG MIBs to always create an entLogicalEntry for the power data.
>>>>>> In
>>>>>> this context, the entLogicalTable fills the role of
>>>>>> entGeneralTable
>>>>>> as described above. For all entPhysicalTable entries, there would
>>>>>> need to be a corresponding entry in entLogicalTable with a 1:1
>>>>>> mapping between them. For all remote entries, there would be a
>>>>>> unique entry in entLogicalTable. Of course, this would add some
>>>>>> additional overhead on the part of the implementer, but isn't too
>> overburdening.
>>
>>>>>> A third possibility is that ENTITY-MIB just doesn't do what we
>>>>>> need
>>>>>> in its present form and we need to think about enumerating power
>>>>>> sensors separately from other components/sensors on the system.
>>>>>> It
>>>>>> seems like entPhysicalTable gives a good starting template for a
>>>>>> new 'POWER-ENTITY-MIB', but can be extended to include support
>>>>>> for
>>>>>> remote agents. The difference would be a clean break from the
>>>>>> legacy ENTITY-MIB structure.
>>>>>> And with that, I look forward to others' feedback and ideas on
>>>>>> solving this problem!
>>>>>> Thanks,
>>>>>> Chris
>>>>>> -----Original Message-----
>>>>>> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On
>>>>>> Behalf Of Chris Verges
>>>>>> Sent: Tuesday, October 26, 2010 9:26 PM
>>>>>> To: Juergen Quittek; Benoit Claise; eman mailing list
>>>>>> Subject: Re: [eman] Entity identification method (was: EMAN
>>>>>> chartered itemsversus drafts)
>>>>>> Hi Juergen and all,
>>>>>> Agreed that a common ID method makes sense, and ENTITY-MIB seems
>>>>>> to
>>>>>> be a good choice. In case (c) from your list, wouldn't the remote
>>>>>> agent condition be handled by ENTITY-MIB supporting a logical
>>>>>> entity that is the remote agent iself? Since the logical entity
>>>>>> is
>>>>>> in the ENTITY-MIB table, it would be given a unique ID mixed
>>>>>> amongst the other logical and physical entities.
>>>>>> At that point, should all of the MIBs being discussed in the EMAN
>>>>>> WG be sparse table augmentations of ENTITY-MIB?
>>>>>> Thanks,
>>>>>> Chris
>>>>>> -----Original Message-----
>>>>>> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On
>>>>>> Behalf Of Juergen Quittek
>>>>>> Sent: Tuesday, October 26, 2010 6:01 AM
>>>>>> To: Benoit Claise; eman mailing list
>>>>>> Subject: [eman] Entity identification method (was: EMAN chartered
>>>>>> items versus drafts)
>>>>>> Hi Benoit and all,
>>>>>> I agree that we should find a common identification method for
>>>>>> entities used by all MIB modules. This does not apply to the
>>>>>> POWER
>>>>>> MIB only, but to all MIB modules in the eman WG.
>>>>>> The modules will use an entity ID as index for their tables.
>>>>>> Which entity is identified by the index can be resolved by other
>>>>>> MIB modules, such as the POWER AWARE MIB module
>>>>>> (draft-parello-eman-energy-aware-mib) or the ENTITY MIB module
>>>>>> (RFC
>>>>>> 4133).
>>>>>> I see three basic scenarios for the entity identification:
>>>>>> a) a device just reports on its own power state and energy
>>>>>> consumption and it reports on its own as a single unit.
>>>>>> Then we have a single index only stating "it's me".
>>>>>> Such a device usually does not need further identification
>>>>>> of itself, because typically there are sufficient other
>>>>>> MIB modules for this purpose running in the same SNMP engine,
>>>>>> that provide information about the device's IP address,
>>>>>> manufacturer, operating system, etc. In such a case a
>>>>>> 'trivial' index, such as '0' should be used in order to
>>>>>> keep it simple in this most simple case.
>>>>>> b) a device reports on its own but not just as a single unit
>>>>>> but it reports power states and energy consumption for its
>>>>>> individual components, for example it may report separately
>>>>>> on contained hard drives, line cards, back planes,
>>>>>> processor boards, etc.
>>>>>> In such a case, identification of these components as
>>>>>> individual entities would be required. The ENTITY MIB
>>>>>> module was designed for this purpose and would be a good
>>>>>> choice here. Also the POWER AWARE MIB module would be
>>>>>> useful in this case.
>>>>>> c) a device reports on energy consumption of other, remote
>>>>>> devices. Then remote devices (and potentially also their
>>>>>> contained components need to be identified. For
>>>>>> identifying remote components there is the POWER AWARE MIB
>>>>>> module that has been designed for this purpose. As far as
>>>>>> I understand, the ENTITY MIB module is not applicable to
>>>>>> remote devices.
>>>>>> In summary,
>>>>>> - if you need to report on remote entities (case c)),
>>>>>> you need the POWER AWARE MIB module,
>>>>>> - if you report only on entities locally contained
>>>>>> in the reporting device (case b)), you can use
>>>>>> the POWER AWARE MIB or the ENTITY MIB
>>>>>> - if you report just on your own as a single device
>>>>>> (case a)), identification is trivial
>>>>>> Hence, my recommendation (stated for POWER-STATE MIB and ENERGY
>>>>>> MIB
>>>>>> in
>>>>>> draft-quittek-power-mib-02) would be:
>>>>>> If there is an implementation of the POWER AWARE MIB module
>>>>>> instantiated in the local SNMP engine, then you SHOULD (or MUST?)
>>>>>> use it for indexing (pmIndex).
>>>>>> If this is not the case but there is an ENTITY MIB instance
>>>>>> available, then you SHOULD use this one (entPhysicalIndex).
>>>>>> If neither of this MIB modules is available you should use index
>>>>>> 0
>>>>>> only and be limited to report on the local device as a single
>> entity only.
>>
>>>>>> That's just my view. Certainly, there are more ways of entity
>>>>>> identification. I look forward to discussing them.
>>>>>> Thanks,
>>>>>> Juergen
>>>>>> On 26.10.10 11:44 "Benoit Claise"<bclaise@cisco.com
>> <mailto:bclaise@cisco.com>>  wrote:
>>
>>>>>>> Hi Juergen,
>>>>>>> Thanks for the clarification.
>>>>>>> Something key is to agree on the Power Monitor index for all MIB
>>>>>>> modules, which IMHO should be part of the Energy-aware Networks
>>>>>>> and Devices MIB module, but reuse in the other MIB modules.
>>>>>>> Regards, Benoit.
>>>>>>>> Hi Benoit,
>>>>>>>> Thanks for checking all drafts.
>>>>>>>> I don't think that draft-quittek-power-mib-02 makes significant
>>>>>>>> contributions to the Energy-aware Networks and Devices MIB.
>>>>>>>> It just covers the Power and Energy Monitoring MIB and the
>>>>>>>> Battery
>>>>>> MIB.
>>>>>>>> Thanks,
>>>>>>>> Juergen
>>>>>>>> On 26.10.10 08:22 "Benoit Claise"<bclaise@cisco.com
>> <mailto:bclaise@cisco.com>>  wrote:
>>
>>>>>>>>> Dear all,
>>>>>>>>> I went through the exercise of mapping the existing six
>>>>>>>>> chartered items with the existing draft content.
>>>>>>>>> _Energy Management Requirements_
>>>>>>>>> http://tools.ietf.org/html/draft-quittek-power-monitoring-requ
>>>>>>>>> ir
>>>>>>>>> emen
>>>>>>>>> ts-02
>>>>>>>>> https://datatracker.ietf.org/doc/draft-norwin-energy-consider/
>>>>>>>>> _
>>>>>>>>> Energy Management Framework_
>>>>>>>>> http://tools.ietf.org/html/draft-claise-power-management-arch-
>>>>>>>>> 02
>>>>>>>>> _Energy-aware Networks and Devices MIB_
>>>>>>>>> http://tools.ietf.org/html/draft-parello-eman-energy-aware-mib
>>>>>>>>> -0
>>>>>>>>> 0
>>>>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>>>>>>>>> _Power and Energy Monitoring MIB_
>>>>>>>>> http://tools.ietf.org/html/draft-claise-energy-monitoring-mib-
>>>>>>>>> 06
>>>>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>>>>>>>>> _Battery MIB_
>>>>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>>>>>>>>> _Energy Management Applicability_
>>>>>>>>> http://datatracker.ietf.org/doc/draft-tychon-eman-applicabilit
>>>>>>>>> y-
>>>>>>>>> stat
>>>>>>>>> ement/
>>>>>>>>> Please let me know if I made any mistakes or if I missed any
>> draft?
>>
>>>>>>>>> Regards, Benoit.
>>>>>>>>> _______________________________________________
>>>>>>>>> eman mailing list
>>>>>>>>> eman@ietf.org<mailto:eman@ietf.org>
>>>>>>>>> https://www.ietf.org/mailman/listinfo/eman
>>>>>> _______________________________________________
>>>>>> eman mailing list
>>>>>> eman@ietf.org<mailto:eman@ietf.org>
>>>>>> https://www.ietf.org/mailman/listinfo/eman
>>>>> _______________________________________________
>>>>> eman mailing list
>>>>> eman@ietf.org<mailto:eman@ietf.org>
>>>>> https://www.ietf.org/mailman/listinfo/eman
>>>> _______________________________________________
>>>> eman mailing list
>>>> eman@ietf.org<mailto:eman@ietf.org>
>>>> https://www.ietf.org/mailman/listinfo/eman
>>> _______________________________________________
>>> eman mailing list
>>> eman@ietf.org<mailto:eman@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/eman
>> _______________________________________________
>>
>> eman mailing list
>>
>> eman@ietf.org<mailto:eman@ietf.org>
>>
>> https://www.ietf.org/mailman/listinfo/eman
>>
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman


From braschoe@cisco.com  Mon Nov  8 08:30:40 2010
Return-Path: <braschoe@cisco.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 00D223A6975 for <eman@core3.amsl.com>; Mon,  8 Nov 2010 08:30:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.231
X-Spam-Level: 
X-Spam-Status: No, score=-9.231 tagged_above=-999 required=5 tests=[AWL=-1.368, BAYES_00=-2.599, EXTRA_MPART_TYPE=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, SARE_GIF_ATTACH=1.42, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z2xi+tqGycdV for <eman@core3.amsl.com>; Mon,  8 Nov 2010 08:30:33 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 985643A67E7 for <eman@ietf.org>; Mon,  8 Nov 2010 08:30:32 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-Files: image001.gif : 837
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtcKAFa010ytJV2b/2dsb2JhbACBF1CgInGhZptQAoMJgj0EhFiBeYcU
X-IronPort-AV: E=Sophos;i="4.58,314,1286150400";  d="gif'147?scan'147,208,217,147";a="179799251"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rtp-iport-2.cisco.com with ESMTP; 08 Nov 2010 16:30:53 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id oA8GUerU026429 for <eman@ietf.org>; Mon, 8 Nov 2010 16:30:53 GMT
Received: from xmb-rcd-204.cisco.com ([72.163.62.211]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 8 Nov 2010 10:30:52 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/related; boundary="----_=_NextPart_001_01CB7F62.4F7D3B92"; type="multipart/alternative"
Date: Mon, 8 Nov 2010 10:30:50 -0600
Message-ID: <308743659A7CB142B28029FB77F1128E0185D828@XMB-RCD-204.cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [eman] Review of draft-norwin-energy-consider-01
Thread-Index: Act/Yk5gIDthfJvVQb+n7BqkZg+aCQ==
From: "Brad Schoening -X (braschoe - Piepeople Consulting, Inc. at Cisco)" <braschoe@cisco.com>
To: <eman@ietf.org>
X-OriginalArrivalTime: 08 Nov 2010 16:30:52.0880 (UTC) FILETIME=[4F93CD00:01CB7F62]
Subject: [eman]  Review of draft-norwin-energy-consider-01
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 16:30:40 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB7F62.4F7D3B92
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_002_01CB7F62.4F7D3B92"


------_=_NextPart_002_01CB7F62.4F7D3B92
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

This document is inconsistent with the EMAN charter and should be tabled
or withdrawn.  It is deeply flawed in several areas.  First, it ignores
the basic concepts of SNMP MIB management.   Secondly, without
explaining why, it ought right opposes the power models presented in
several widely used standards such as ACPI,  DMTF's Power State and IEC
61850.=20

=20

These three standards for power management are well established and
supported on millions of devices. =20

*         The ACPI standard for CPU power management was released in
1996 and  is ubiquitous today.  It defines seven power levels. =20

*         IEC 61850 is supported by utilities worldwide and power
equipment  manufacturers.   IEC 61850 has an extensive Common
Information Model (CIM) that is the basis for many smart grid standards.


*          The DMTF Power State Management Profile was adopted in 2008
and defines an information model over web services.  It defines six
power levels and aligns them with the ACPI power levels.=20

=20

Below are some detailed comments, but my view is that this document does
nothing to advance the charter of the working group and will be a
distraction.  Instead we should focus on furthering the  existing drafts


=20

http://tools.ietf.org/html/draft-quittek-power-mib-02

http://tools.ietf.org/html/draft-parello-eman-energy-aware-mib-00

http://ietfreport.isoc.org/all-ids/draft-claise-energy-monitoring-mib-06
.txt

=20

=20

--------------------------------------------------

=20

3. "Scope of Devices" section seems to misunderstand the nature of SNMP.
Only devices with a network connection AND a SNMP agent can implement
these MIBs.

=20

4.1. The 'Terminology' section on power states don't align with existing
standards for networked equipment (DMTF and ACPI).  The authors need to
clarify why they believe these pre-existing standards are in error or
not applicable.

=20

5.1. Control "Device Considerations" also doesn't seem to understand how
SNMP management works " We should not forbid power state management of
devices that is done externally/centrally.  Today, centralized
management is the norm with SNMP.

=20

Also, the authors need to explain how this idea relates to the current
marketplace of existing devices that in general are externally
controlled and only occasionally have distributed intelligence.

=20

5.2 The comment about URL's seems ignorant of SysObjectID and not
relevant to the EMAN charter=20

=20

5.3 For "NMS Considerations", the authors need to clarify how this
relates to existing energy management systems and existing standards
such as IEC 61850 that define interval measurements. =20

=20

5.7 "For the device power state, the following information is considered
to be relevant"...   This doesn't reference any existing standards and
is therefore largely irrelevant.

=20

5.8 "Devices can report power for another device only if they are the

entity providing the power"  This would rule out managing PC's which
typically don't have a SNMP agent.   We probably don't want to forbid
this.

=20

6.o "Use Case: A house... A vehicle"  This further ignores basics about
SNMP.  Existing use cases for SNMP are not homes or vehicles.

=20

=20

=20

Brad Schoening
Consultant
Product Development
braschoe@cisco.com <mailto:braschoe@cisco.com>=20
Phone: +1 408 424 0363
Mobile: +1 917 304 7190

For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/index.html
<http://www.cisco.com/web/about/doing_business/legal/cri/index.html>=20

	=09

=20

=20


------_=_NextPart_002_01CB7F62.4F7D3B92
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1157647374;
	mso-list-type:hybrid;
	mso-list-template-ids:430717940 67698689 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DWordSection1>

<p class=3DMsoNormal>This document is inconsistent with the EMAN charter =
and
should be tabled or withdrawn.&nbsp; It is deeply flawed in several =
areas. &nbsp;First,
it ignores the basic concepts of SNMP MIB management.&nbsp;&nbsp; =
Secondly, without
explaining why, it ought right opposes the power models presented in =
several widely
used standards such as ACPI, &nbsp;DMTF&#8217;s Power State and IEC =
61850. <o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>These three standards for power management are well =
established
and supported on millions of devices.&nbsp; <o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>The ACPI standard for CPU power =
management was released
in 1996 and &nbsp;is ubiquitous today.&nbsp; It defines seven power
levels.&nbsp; <o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>IEC 61850 is supported by utilities =
worldwide and
power equipment&nbsp; manufacturers.&nbsp;&nbsp; IEC 61850 has an =
extensive
Common Information Model (CIM) that is the basis for many smart grid =
standards.&nbsp;
<o:p></o:p></p>

<p class=3DMsoListParagraph style=3D'text-indent:-.25in;mso-list:l0 =
level1 lfo1'><![if !supportLists]><span
style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span
style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span><![endif]>&nbsp;The DMTF Power State Management =
Profile was
adopted in 2008 and defines an information model over web =
services.&nbsp; It
defines six power levels and aligns them with the ACPI power levels. =
<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Below are some detailed comments, but my view is =
that this document
does nothing to advance the charter of the working group and will be a
distraction.&nbsp; Instead we should focus on furthering the =
&nbsp;existing
drafts <o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal style=3D'text-indent:.5in'><a
href=3D"http://tools.ietf.org/html/draft-quittek-power-mib-02">http://too=
ls.ietf.org/html/draft-quittek-power-mib-02</a><o:p></o:p></p>

<p class=3DMsoNormal style=3D'text-indent:.5in'><a
href=3D"http://tools.ietf.org/html/draft-parello-eman-energy-aware-mib-00=
">http://tools.ietf.org/html/draft-parello-eman-energy-aware-mib-00</a><o=
:p></o:p></p>

<p class=3DMsoNormal style=3D'text-indent:.5in'><a
href=3D"http://ietfreport.isoc.org/all-ids/draft-claise-energy-monitoring=
-mib-06.txt">http://ietfreport.isoc.org/all-ids/draft-claise-energy-monit=
oring-mib-06.txt</a><o:p></o:p></p>

<p class=3DMsoNormal style=3D'text-indent:.5in'><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p =
class=3DMsoNormal>--------------------------------------------------<o:p>=
</o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.5pt;
font-family:Consolas'>3. &quot;Scope of Devices&quot; section seems to =
misunderstand
the nature of SNMP.&nbsp;&nbsp; Only devices with a network connection =
AND a
SNMP agent can implement these MIBs.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.5pt;
font-family:Consolas'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.5pt;
font-family:Consolas'>4.1. The 'Terminology' section on power states =
don't
align with existing standards for networked equipment (DMTF and =
ACPI).&nbsp;
The authors need to clarify why they believe these pre-existing =
standards are
in error or not applicable.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.5pt;
font-family:Consolas'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.5pt;
font-family:Consolas'>5.1. Control &quot;Device Considerations&quot; =
also
doesn't seem to understand how SNMP management works &quot; We should =
not forbid
power state management of devices that is done =
externally/centrally.&nbsp; Today,
centralized management is the norm with SNMP.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.5pt;
font-family:Consolas'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.5pt;
font-family:Consolas'>Also, the authors need to explain how this idea =
relates
to the current marketplace of existing devices that in general are =
externally
controlled and only occasionally have distributed =
intelligence.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.5pt;
font-family:Consolas'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.5pt;
font-family:Consolas'>5.2 The comment about URL's seems ignorant of =
SysObjectID
and not relevant to the EMAN charter <o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.5pt;
font-family:Consolas'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.5pt;
font-family:Consolas'>5.3 For &quot;NMS Considerations&quot;, the =
authors need
to clarify how this relates to existing energy management systems and =
existing
standards such as IEC 61850 that define interval measurements.&nbsp; =
<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.5pt;
font-family:Consolas'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.5pt;
font-family:Consolas'>5.7 &quot;For the device power state, the =
following
information is considered to be relevant&quot;...&nbsp;&nbsp; This =
doesn't
reference any existing standards and is therefore largely =
irrelevant.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.5pt;
font-family:Consolas'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.5pt;
font-family:Consolas'>5.8 &quot;Devices can report power for another =
device
only if they are the<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.5pt;
font-family:Consolas'>entity providing the power&quot;&nbsp; This would =
rule
out managing PC's which typically don&#8217;t have a SNMP agent. =
&nbsp;&nbsp;We
probably don&#8217;t want to forbid this.<o:p></o:p></span></p>

<p class=3DMsoNormal style=3D'text-autospace:none'><span =
style=3D'font-size:10.5pt;
font-family:Consolas'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal =
style=3D'margin-bottom:10.0pt;line-height:115%;text-autospace:
none'><span =
style=3D'font-size:10.5pt;line-height:115%;font-family:Consolas'>6.o
&quot;Use Case: A house... A vehicle&quot;&nbsp; This further ignores =
basics
about SNMP.&nbsp; Existing use cases for SNMP are not homes or =
vehicles.</span><span
lang=3DEN><o:p></o:p></span></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<table class=3DMsoNormalTable border=3D0 cellspacing=3D0 cellpadding=3D0 =
width=3D543
 style=3D'width:407.25pt'>
 <tr>
  <td colspan=3D3 style=3D'padding:0in 0in 0in 0in'>
  <p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";
  color:#222222'><img border=3D0 width=3D110 height=3D73 =
id=3D"Picture_x0020_1"
  src=3D"cid:image001.gif@01CB7F31.B7BEA200"
  alt=3D"http://www.cisco.com/swa/i/logo.gif"></span><span =
style=3D'font-size:10.0pt;
  font-family:"Arial","sans-serif";color:#222222'><o:p></o:p></span></p>
  </td>
 </tr>
 <tr>
  <td nowrap valign=3Dtop style=3D'padding:0in 0in 11.25pt .25in'>
  <p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><b><span
  =
style=3D'font-size:8.5pt;font-family:"Arial","sans-serif";color:#666666'>=
Brad
  Schoening</span></b><span =
style=3D'font-size:8.5pt;font-family:"Arial","sans-serif";
  color:#666666'><br>
  <b>Consultant</b><br>
  <b>Product Development</b><br>
  <a href=3D"mailto:braschoe@cisco.com"><span =
style=3D'color:#666666'>braschoe@cisco.com</span></a><br>
  Phone: <b>+1 408 424 0363</b><br>
  Mobile: <b>+1 917 304 7190</b></span><b><span =
style=3D'font-size:8.5pt;
  =
font-family:"Arial","sans-serif";color:#666666'><o:p></o:p></span></b></p=
>
  <p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;margin-bottom:12.0pt'><span
  =
style=3D'font-size:7.5pt;font-family:"Arial","sans-serif";color:#999999'>=
For
  corporate legal information go to:<br>
  <a =
href=3D"http://www.cisco.com/web/about/doing_business/legal/cri/index.htm=
l"><span
  =
style=3D'color:#0E58A0'>http://www.cisco.com/web/about/doing_business/leg=
al/cri/index.html</span></a></span><o:p></o:p></p>
  </td>
  <td style=3D'padding:0in 0in 0in 0in'></td>
  <td style=3D'padding:0in 0in 0in 0in'></td>
 </tr>
</table>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>

------_=_NextPart_002_01CB7F62.4F7D3B92--

------_=_NextPart_001_01CB7F62.4F7D3B92
Content-Type: image/gif;
	name="image001.gif"
Content-Transfer-Encoding: base64
Content-ID: <image001.gif@01CB7F31.B7BEA200>
Content-Description: image001.gif
Content-Location: image001.gif

R0lGODlhbgBJAMQAAP///3OXqtapqq1MTcmRki9mgZkAALpqbMl/f6g5O/Xq6+vX2OTIyaMqK/nz
9OW/v5sVFsbV3Nfh5p0PD5kFBf78/P38/Pz6+v/+/rZdXpcKDKAhIvv396QvMO/g4Ny4uSH5BAAA
AAAALAAAAABuAEkAQAX/ICCOZGmeaKqubOu+cCzPdG3feK6nkln8pp5LSPoVgrucsbQsAp1HKPM5
alapImtyy+16SwKDmJBCiBEWgMUsPgg8JMHEQCGTMACP2HDgiBQZYglfOQ+GDy2HhiqKKI2EkJGS
k5SVlpeYmZpfWkpYmypEV1GjU6QjolmfnZ0AqZWvrj6fski2UiWxsZkcHxkNYg0IABUibAjFIgsH
wAYNBwokvb8QEMIOJAwICQYQCQgLoCgLHWIdHwoKCwzExmdpGBwcxRgDYhkXAOTm6OoMfg4CiRGg
wAOBOXzEKVzIsKHDhxAjSpxIsaKNCAEibMGo0WKLVjdAVgxQIICpEiRN/7JIeZIEy4WsVsk8BSAm
TZstLb0csVMVzZ4AgALtJLQkRY4bM3pcupDAHgMduA1Q484AGmJO7x04kCCaCAIaxFCISmGAVwZP
u+1pEK5hVgPYUBxLQ4yBvacfvlIwMCFuCbRi2I34sHfDQ0BpDUyFNxfABTZPGwgGACjsU7MiLLx9
ukEA08+gQ4seTbq06dOoU6tezbq169evd92QHRooDtujRdbQDZr3DN8RkeIaIXxFcZ8ljkPEOVwF
81ILlT9HTkL6zJwilE+aXvN68+43vUO3xL28eOrj0VdSbp0me6XV4acH8L6jRNw28IumXYM/7P8k
PJLIISkIWIKBD3GwmcIYiwGAQWP6cJMWHCIoCEFamInwQTNPdYCIQwqUM8YCC3zgWTKNOXAAg14p
kA9lIkJAAIkmYsPBim0YcsBeVjn0llcnQAjYHh14phdfQGazx2QAEGaAYQ2FMVAZ75BggTZ7HFCM
HHQYWcICeyAjgormPASZYgN00CAAjV0gwAEEEACZlsbwCMEAaWb4wFMJJMDjBkwypAABErbRzoNn
FFPBghnkRcKgCVimwQF+VSDAXXw1CuCmnHbq6aeghirqqDiEAAA7

------_=_NextPart_001_01CB7F62.4F7D3B92--

From Quittek@neclab.eu  Mon Nov  8 08:41:06 2010
Return-Path: <Quittek@neclab.eu>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 262DA3A6804 for <eman@core3.amsl.com>; Mon,  8 Nov 2010 08:41:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.203
X-Spam-Level: 
X-Spam-Status: No, score=-101.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g09YaNogvrZF for <eman@core3.amsl.com>; Mon,  8 Nov 2010 08:41:05 -0800 (PST)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41]) by core3.amsl.com (Postfix) with ESMTP id D66453A67EE for <eman@ietf.org>; Mon,  8 Nov 2010 08:41:04 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.neclab.eu (Postfix) with ESMTP id 3DB552C0001B5; Mon,  8 Nov 2010 17:41:26 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office.hd)
Received: from smtp0.neclab.eu ([127.0.0.1]) by localhost (atlas2.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VgY-efnFNi-U; Mon,  8 Nov 2010 17:41:26 +0100 (CET)
Received: from ENCELADUS.office.hd (ENCELADUS.office.hd [192.168.24.52]) by smtp0.neclab.eu (Postfix) with ESMTP id 1C13A2C0001AF; Mon,  8 Nov 2010 17:41:11 +0100 (CET)
Received: from DAPHNIS.office.hd ([169.254.2.19]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0255.000; Mon, 8 Nov 2010 17:41:11 +0100
From: Juergen Quittek <Quittek@neclab.eu>
To: Chris Verges <chrisv@cyberswitching.com>, Bruce Nordman <BNordman@lbl.gov>, eman mailing list <eman@ietf.org>
Thread-Topic: [eman] Proposed alternation of framework
Thread-Index: AQHLftDrl5Xt9tUHhUOQBHk4jIuQEAADY2Lgk2e8QgA=
Date: Mon, 8 Nov 2010 16:41:10 +0000
Message-ID: <C8FDF20A.16C78%quittek@neclab.eu>
In-Reply-To: <68FBE0F3CE97264395875AC1C468F22C514A74@mail03.cyberswitching.local>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.7.0.100913
x-originating-ip: [10.7.0.92]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3372085771_27450278"
MIME-Version: 1.0
Subject: Re: [eman] Proposed alternation of framework
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 16:41:06 -0000

--B_3372085771_27450278
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

Hi Chris,

I think Bruce and you are talking about different kinds of domains. Our
current documents do not yet define well enough what a domain is. This is
something we should take care of.

As far as I understand it, Bruce is talking about power distribution domain=
s
containing, for example, devices with the same source (and fuse) of power.
You are taking also about consumer domains related to functionality or cost
centers, etc.

All these are valid kinds of domains, but they are significantly different
and should not get confused. Let's start listing which kinds of domains we
want to support in eman, what is support needed for them, and how we can
clearly define them in order to avoid confusion.

Thanks,

    Juergen

On 08.11.10 09:15  "Chris Verges" <chrisv@cyberswitching.com> wrote:
>=20
> [BN] Power Domain
>=20
> [BN] A system of power distribution with a common technology and fate.
> Technologies are usually distinguished by voltages and whether AC or DC.
> AC examples include 100V, 115V, 200V, and 230V.  DC examples include
> 380V, 48V, 24V, 12V, and 5V (variously including eMerge, PoE, USB, and
> vehicle standards).  Increasingly communications go along with power,
> but this is incidental to power reporting.
>=20
> [BN] Power domains are often in trees, but this is not strictly
> required.  A domain with a single source may have a controller at its
> root (e.g. a PoE switch), or not (e.g. a circuit breaker in a building).
> At this time, we should consider domains as having a single source of
> power; later we could relax that requirement.
>=20
> [BN] Common fate includes quality, reliability, availability, total
> capacity, and price.  How devices learn what domain they are in is out
> of our scope.
>=20
> [CV] With respect, this concept of a "Power Domain" is very limited to
> the standard utility/facilities definition.  Given the advent of newer
> reporting models and systems, should we extend this concept to simply
> mean any logical grouping of power entities.  The mapping between power
> domains and power entities can be many-to-many, not just one-to-many.
>
> [CV] For example, consider a deployment where the =B3power domain=B2 is segme=
nted
> in two ways: (1) the physical infrastructure, taking into account branch
> circuit and transformer capacities; and (2) the billing structure, where
> entities are =B3grouped=B2 according to who pays the costs.  If the MIB model=
 only
> handles a 1:N mapping, the administrator needs to choose only one.  If th=
e MIB
> model handles a M:N mapping, more complex and useful systems can be built=
 on
> top of this schema.

--B_3372085771_27450278
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIQ5wYJKoZIhvcNAQcCoIIQ2DCCENQCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
Do8wggUzMIIEG6ADAgECAgQP7R53MA0GCSqGSIb3DQEBBQUAMIGQMQswCQYDVQQGEwJERTEY
MBYGA1UEChMPTkVDIEV1cm9wZSBMdGQuMSAwHgYDVQQLExdORUMgTGFib3JhdG9yaWVzIEV1
cm9wZTESMBAGA1UEAxMJTkVDTEFCLUNBMTEwLwYJKoZIhvcNAQkBFiJ6ZXJ0aWZpemllcnVu
Z3NzdGVsbGVAbncubmVjbGFiLmV1MB4XDTEwMDQyMDEyNDExMloXDTEzMDQxOTEyNDExMlow
YzELMAkGA1UEBhMCREUxGDAWBgNVBAoTD05FQyBFdXJvcGUgTHRkLjEgMB4GA1UECxMXTkVD
IExhYm9yYXRvcmllcyBFdXJvcGUxGDAWBgNVBAMTD0p1ZXJnZW4gUXVpdHRlazCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBANga4Hf5iSjDiva8/BTlatnXFlOWPfqZvY7AU6bt
CUKFiaGwytFar7XCwRggHcCeodYaMZoDRSEGY+bRUDvayjNvFTkhL19Fmzxg4MPmQA92tcIb
/+IylZD5YkVkw88/6zb6k+T+o875LlLAR79f8gvloaPMbxiB8KwQtdlGB9OiN1k3+7NiESpW
myT8WWrWw4F7qc0WLXaWuqv6/3vRo+jJSxyOwefEnzrRojCePJ2ZD4mgPMQvMHPqodDhTvIB
BupYoAtW53024WnL/PHH34pQ0Zmclz8u/YocnfMEYoyLDVuJKnQowDF75LVbnKmpXfCscKeb
SndFpSANP2TiI2cCAwEAAaOCAb8wggG7MAkGA1UdEwQCMAAwCwYDVR0PBAQDAgXgMCkGA1Ud
JQQiMCAGCCsGAQUFBwMCBggrBgEFBQcDBAYKKwYBBAGCNxQCAjAdBgNVHQ4EFgQU9WUPxjFB
AtJOXxJ7agqXozHDy9gwHwYDVR0jBBgwFoAUTxyHeh3gL5n2vhWq0TWdDkrmujYwHAYDVR0R
BBUwE4ERUXVpdHRla0BuZWNsYWIuZXUwfQYDVR0fBHYwdDA4oDagNIYyaHR0cDovL2NkcDEu
cGNhLmRmbi5kZS9uZWNsYWItY2EvcHViL2NybC9jYWNybC5jcmwwOKA2oDSGMmh0dHA6Ly9j
ZHAyLnBjYS5kZm4uZGUvbmVjbGFiLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGYBggrBgEFBQcB
AQSBizCBiDBCBggrBgEFBQcwAoY2aHR0cDovL2NkcDEucGNhLmRmbi5kZS9uZWNsYWItY2Ev
cHViL2NhY2VydC9jYWNlcnQuY3J0MEIGCCsGAQUFBzAChjZodHRwOi8vY2RwMi5wY2EuZGZu
LmRlL25lY2xhYi1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQEFBQADggEB
AH9VRaZ978LNoc+eM/2k/OQafNJl4UjKLjiEnH8FCuqnuNXZMAOdcfnMrRKK1bl+FhCy3sjg
gsuP4Nam2oSy7RDYWYjLY/MKMPO/MD/PpNSe6gox4948wfjWGmj4Uz3gqgDovQEC2H03jcPX
etJqBTipqmfnvMFqozoN5zjiEzJuuLpLMYNPM+E+4pQnLtRAhN94C1e9C7oP66b7as6OgVVC
CplE5llnoKM5ngtAFL5G3ygm/rZtptdmaNgRO6jDX1w9AOrsmSPGp+S+YRNonKGEqTolJpul
EJB7rMdAUimsUp/qdzvWrhIZ6A3fgzHwFhrIHqVBlDLmu7cQHu/QMUEwggUvMIIEF6ADAgEC
AgQNIQpHMA0GCSqGSIb3DQEBBQUAMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVy
ZWluMRAwDgYDVQQLEwdERk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwg
LSBHMDEwHhcNMDgxMDI0MDg1MjA4WhcNMTkwNjMwMDAwMDAwWjCBkDELMAkGA1UEBhMCREUx
GDAWBgNVBAoTD05FQyBFdXJvcGUgTHRkLjEgMB4GA1UECxMXTkVDIExhYm9yYXRvcmllcyBF
dXJvcGUxEjAQBgNVBAMTCU5FQ0xBQi1DQTExMC8GCSqGSIb3DQEJARYiemVydGlmaXppZXJ1
bmdzc3RlbGxlQG53Lm5lY2xhYi5ldTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB
AJ7yFbG1EaoyDnG5367mJEXHljmacrzNnm52KW3dXD/s3Vpuskex0jvaaTntWWRSGrAK6kKX
nTxBb3J3EhveBUbltzQ+K0XKtPJm6VE5qVpl33WJSaUHs27Dhwlke+DV6BBGyukz2SDBaSa+
nc0AwMZ0XO1DoDuiUNVeNmd/QT4SGzyFs+uLfLL2n8WzkZsbpSZ+xecwyw3EdQBBsp/i/W+u
OQBsGqaCjYe3EkBU6nW+pBsj0Iy1n7b9PXb5gQynrK3Mi2V7g1idSzHos0o1BMoHUrMzVw94
Hj4CWlWmQ0t6Pdt1uYAMjwk0saQBY/Fyfv+wKeYycGIYyYCfJIRUeyUCAwEAAaOCAcQwggHA
MBIGA1UdEwEB/wQIMAYBAf8CAQEwCwYDVR0PBAQDAgEGMB0GA1UdDgQWBBRPHId6HeAvmfa+
FarRNZ0OSua6NjAfBgNVHSMEGDAWgBRJt8bP6D0ff+pEexMp9/EKcD7eZDAtBgNVHREEJjAk
gSJ6ZXJ0aWZpemllcnVuZ3NzdGVsbGVAbncubmVjbGFiLmV1MIGIBgNVHR8EgYAwfjA9oDug
OYY3aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY3JsL2NhY3Js
LmNybDA9oDugOYY3aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIv
Y3JsL2NhY3JsLmNybDCBogYIKwYBBQUHAQEEgZUwgZIwRwYIKwYBBQUHMAKGO2h0dHA6Ly9j
ZHAxLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MEcG
CCsGAQUFBzAChjtodHRwOi8vY2RwMi5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWNhL3B1Yi9j
YWNlcnQvY2FjZXJ0LmNydDANBgkqhkiG9w0BAQUFAAOCAQEAbDEPnQ9JpouPHYA1OEekP3l3
GNM0HBzadVbtbN5MDtFmoVgdLYqlQaHb30wFhuOMbsNCOzV0k8EOvBVOT9BiEJ70RWclSZQ4
60jZS2MY6n5oG/ilZuu6N/N3GSLg2pBBNH9vZFCyBJ9n4Px7A4gQF07G+CNfV2jdE1yyPjzI
VPhg6bBgia8nXroBFe6oteavMspo0gLGIJ63NsCbl6ckPa96grT+mnnQD0h6jk/IGtXS09mE
WRbN7zZu0x0q+SScpljG36Q+jnG0U5zQI0jAx8CcYEQQH5QOlsw1Zu35OI4lsi7ycFkzJNfb
fEC4ihuw9J2L43BFGMojkhPkhVExHTCCBCEwggMJoAMCAQICAgDHMA0GCSqGSIb3DQEBBQUA
MHExCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQL
ExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMwIQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJv
b3QgQ0EgMjAeFw0wNjEyMTkxMDI5MDBaFw0xOTA2MzAyMzU5MDBaMFoxCzAJBgNVBAYTAkRF
MRMwEQYDVQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdERk4tUEtJMSQwIgYDVQQDExtERk4t
VmVyZWluIFBDQSBHbG9iYWwgLSBHMDEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB
AQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U1wBblSJ01CDrNI/W7MAxBAuZgeKmFNJSoCgjhIt0
iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6fL9KDhsAw4bpXCsxEXsM84IkQ4wcOItqaACa7txP
eKvSxhObdq3u3ibo7wGvdA/BCaL2a869080UME/15eOkyGKbghoDJzANAmVgTe3RCSMqljVY
J9N2xnG2kB3E7f81hn1vM7PbD8URwoqDoZRdQWvY0hD1TP3KUazZve+Sg7va64sWVlZDz+HV
Ez2mHycwzUlU28kTNJpxdcVs6qcLmPkhnSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjgdkwgdYw
cAYDVR0fBGkwZzBloGOgYYZfaHR0cDovL3BraS50ZWxlc2VjLmRlL2NnaS1iaW4vc2Vydmlj
ZS9hZl9Eb3dubG9hZEFSTC5jcmw/LWNybF9mb3JtYXQ9WF81MDkmLWlzc3Vlcj1EVF9ST09U
X0NBXzIwHQYDVR0OBBYEFEm3xs/oPR9/6kR7Eyn38QpwPt5kMB8GA1UdIwQYMBaAFDHDeRu6
9VPXF+CJei0XbAqzK50zMA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgECMA0G
CSqGSIb3DQEBBQUAA4IBAQA74Vp3wEgX3KkY7IGvWonwvSiSpspZGBJw7Cjy565/lizn8l0Z
MfYTK3S9vYCyufdnyTmieTvhERHua3iRM347XyYndVNljjNj7s9zw7CSI0khUHUjoR8Y4pSF
PT8z6XcgjaK95qGFKUD2P3MyWA0Ja6bahWzAP7uNZmRWJE6uDT8yNQFb6YyC2XJZT7GGhfF0
hVblw/hc843uR7NTBXDn5U2KaYMo4RMJhp5eyOpYHgwf+aTUWgRo/Sg+iwK2WLX2oSw3VwBn
qyNojWOl75lrXP1LVvarQIc01BGSbOyHxQoLBzNytG8MHVQs2FHHzL8w00Ny8TK/jM5JY6gA
9/IcMYICIDCCAhwCAQEwgZkwgZAxCzAJBgNVBAYTAkRFMRgwFgYDVQQKEw9ORUMgRXVyb3Bl
IEx0ZC4xIDAeBgNVBAsTF05FQyBMYWJvcmF0b3JpZXMgRXVyb3BlMRIwEAYDVQQDEwlORUNM
QUItQ0ExMTAvBgkqhkiG9w0BCQEWInplcnRpZml6aWVydW5nc3N0ZWxsZUBudy5uZWNsYWIu
ZXUCBA/tHncwCQYFKw4DAhoFAKBdMCMGCSqGSIb3DQEJBDEWBBR3CYGlm0tOqUkpy2SWgDAT
TK9fCzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMDExMDgx
MDI5MzBaMA0GCSqGSIb3DQEBAQUABIIBAC57TROtkRPjuo8L0cxeQwxA6QSPmgyFdn+OB8iw
jv4gV107CGhTuM/4jvrQdGqaJ54hDq/1jbGoma1oOQ+3vFDWEkx7nhsG1CBsUGljXWMAS+An
/WRXL1E/QnkGrGu+qXLWv2EySKKZijZC9NlQY2JhfnsVEmu/nV0pd97NZV5sIUKCubzDW5tO
UeblkyioDlhKjYYPSFlLstQrF+KXsRnUNX/3Hz6CJkuwukE5I5WjbVPddlgg+4bmcbmMz/Fy
d7Wh2DxcREQfN+RV3wfiw9Qa0Heue4jWvimLw4pjoA5RPkaG4TN18wqL7u3ixrLZALx3sW5D
8JBxOfe4ipDiINs=

--B_3372085771_27450278--

From Quittek@neclab.eu  Mon Nov  8 11:09:37 2010
Return-Path: <Quittek@neclab.eu>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F23903A680F for <eman@core3.amsl.com>; Mon,  8 Nov 2010 11:09:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.569
X-Spam-Level: 
X-Spam-Status: No, score=-101.569 tagged_above=-999 required=5 tests=[AWL=0.365, BAYES_00=-2.599, HELO_EQ_DE=0.35, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QdK0P-vIr1KU for <eman@core3.amsl.com>; Mon,  8 Nov 2010 11:09:35 -0800 (PST)
Received: from smtp0.netlab.nec.de (smtp0.netlab.nec.de [195.37.70.40]) by core3.amsl.com (Postfix) with ESMTP id 8A75B3A686A for <eman@ietf.org>; Mon,  8 Nov 2010 11:09:34 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.netlab.nec.de (Postfix) with ESMTP id 33EC02800017F; Mon,  8 Nov 2010 20:09:56 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office.hd)
Received: from smtp0.netlab.nec.de ([127.0.0.1]) by localhost (atlas1.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 35MauiwLxWvA; Mon,  8 Nov 2010 20:09:56 +0100 (CET)
Received: from ENCELADUS.office.hd (ENCELADUS.office.hd [192.168.24.52]) by smtp0.netlab.nec.de (Postfix) with ESMTP id 162012800017D; Mon,  8 Nov 2010 20:09:46 +0100 (CET)
Received: from DAPHNIS.office.hd ([169.254.2.19]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0255.000; Mon, 8 Nov 2010 20:09:46 +0100
From: Juergen Quittek <Quittek@neclab.eu>
To: "Brad Schoening -X (braschoe - Piepeople Consulting, Inc. at Cisco)" <braschoe@cisco.com>, eman mailing list <eman@ietf.org>
Thread-Topic: [eman]  Review of draft-norwin-energy-consider-01
Thread-Index: Act/Yk5gIDthfJvVQb+n7BqkZg+aCQAFi4HX
Date: Mon, 8 Nov 2010 19:09:45 +0000
Message-ID: <C8FE6BF1.16D1D%quittek@neclab.eu>
In-Reply-To: <308743659A7CB142B28029FB77F1128E0185D828@XMB-RCD-204.cisco.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.7.0.100913
x-originating-ip: [10.7.0.92]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3372116977_29262932"
MIME-Version: 1.0
Subject: Re: [eman] Review of draft-norwin-energy-consider-01
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 19:09:37 -0000

--B_3372116977_29262932
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Wow, what a review ...

Dear Brad,

Below please find some replies on your comments inline.
Please cool down before you reply again and read carefully what you write.

Thanks,

    Juergen


On 09.11.10 00:30  "Brad Schoening -X (braschoe - Piepeople Consulting, Inc.
at Cisco)" <braschoe@cisco.com> wrote:

> This document is inconsistent with the EMAN charter and should be tabled
> or withdrawn. 

As a general comment since you do not seem to be familiar with the IETF:
Internet drafts are preferred means to contribute discussion items and
opinions to the IETF. Asking someone to withdraw a draft is comparable to
asking someone to withdraw her or his opinion. This is not what we do in the
IETF, at least as long as it is a technical opinion. Anyway, I would not
know means for removing a draft from the Internet draft repository.

More specifically: I am not sure what you mean with "inconsistent with the
EMAN charter". It is indeed not one of the documents that we envision to
produce in the eman WG. But so far nobody claimed that this draft would
match any of the envisioned drafts. In contrary, Bruce stated in his message
on this draft that this document should "reflect conclusions", "clarify
issues" and "drive decisions". No one is talking about making it an RFC.
Please find and read Bruce's announcement in the eman mailing list archive
at http://www.ietf.org/mail-archive/web/eman/current/msg00071.html

>               It is deeply flawed in several areas.

I don't see that it even slightly flawed. Please see my replies below to all
issues that you consider to be a flaw.

>                                                     First, it ignores
> the basic concepts of SNMP MIB management.

You are right in the sense that it ignores SNMP by not mentioning it. But
that is all ignorance I can find. Nothing in this document is in conflict
with any concept of SNMP.

>                                            Secondly, without
> explaining why, it ought right opposes the power models presented in
> several widely used standards such as ACPI,  DMTF's Power State and IEC
> 61850. 

There is no statement opposing any other standard. None of the draft we have
received for eman uses exactly ACPI or DMTF (see my next comment below).
They don't even argue why they don't do so. Are they all deeply flawed?

> These three standards for power management are well established and
> supported on millions of devices.
> 
> *         The ACPI standard for CPU power management was released in
> 1996 and  is ubiquitous today.  It defines seven power levels.

So far, none of the existing draft suggested using exactly the ACPI model
for power states. draft-claise-power-management-arch-02 is close to ACPI,
but it compresses the three stage model of ACPI (G,S,P) into a single stage
model of 12 power states. No other document that I have seen for eman
suggests ignoring ACPI or does not provides means for supporting it. Still,
the existing drafts differ in how far they limit themselves to ACPI that was
defined specifically for PCs.

> *         IEC 61850 is supported by utilities worldwide and power
> equipment  manufacturers.   IEC 61850 has an extensive Common
> Information Model (CIM) that is the basis for many smart grid standards.

This is correct. Where do you see the draft you have reviewed opposing
IEC 61850?

> *          The DMTF Power State Management Profile was adopted in 2008
> and defines an information model over web services.  It defines six
> power levels and aligns them with the ACPI power levels.

The DMTF has only 6 power states, 5 of them non-operational. They merged all
operational power states into a single one: "on". This way it deviates from
ACPI providing means for several more states. It looks like Bruce's and
Rolf's draft is going into the same direction.

BTW, so far none of the drafts contributing to eman has suggested to adopt
the DMTF model of six power states although the DMTF focusing on network
management is much closer to the IETF network management issues than ACPI
focusing on PC motherboards.

> Below are some detailed comments, but my view is that this document does
> nothing to advance the charter of the working group and will be a
> distraction.  Instead we should focus on furthering the  existing drafts
> 
> http://tools.ietf.org/html/draft-quittek-power-mib-02
> 
> http://tools.ietf.org/html/draft-parello-eman-energy-aware-mib-00
> 
> http://ietfreport.isoc.org/all-ids/draft-claise-energy-monitoring-mib-06
> .txt

These are all MIB modules. Right, they are on the eman charter. But as well
on the charter are drafts on requirements, framework, and applicability.
I think the draft you reviewed is much more related to these three drafts
than to the one you refer to.
 
> --------------------------------------------------
> 
> 3. "Scope of Devices" section seems to misunderstand the nature of SNMP.
> Only devices with a network connection AND a SNMP agent can implement
> these MIBs.

I do not see any relation between this section and SNMP at all. It
definitely does not mention MIBs or SNMP. Consequently, I cannot detect any
misunderstanding of SNMP. Are you really referring to this section or do you
have another one in mind?

> 4.1. The 'Terminology' section on power states don't align with existing
> standards for networked equipment (DMTF and ACPI).  The authors need to
> clarify why they believe these pre-existing standards are in error or
> not applicable.

The drafts argues for introducing "power state categories" on, off, and
sleep. I see not problem with mapping power states defined by DMTF, ACPI or
other bodies to these categories. Do you?

But yes, I agree that if we adopt this proposal we should elaborate on the
mapping between these categories and the power states defined by other
bodies.

> 5.1. Control "Device Considerations" also doesn't seem to understand how
> SNMP management works " We should not forbid power state management of
> devices that is done externally/centrally.  Today, centralized
> management is the norm with SNMP.

There is no statement forbidding anything in this short section.
Particularly, I see no indication of anyone misunderstanding SNMP. After
working with SNMP for more than 10 years now and after editing a few
standard MIB modules I still cannot see your point. Can you help me seeing
it?

> Also, the authors need to explain how this idea relates to the current
> marketplace of existing devices that in general are externally
> controlled and only occasionally have distributed intelligence.

Good point. But you are probably aware that, for example, for mobile access
networks so-called "Self-Organizing Networks" (SON) for self-management of
base stations is already included in 3GPP standards. And energy management
functions is the next application area for SON.

> 5.2 The comment about URL's seems ignorant of SysObjectID and not
> relevant to the EMAN charter

Maybe. But so far, I do not consider the identification of energy consumers
being solved by the eman WG. Proposals are still welcome. Whether the eman
WG or another WG will solve this problem is to be discussed.

> 5.3 For "NMS Considerations", the authors need to clarify how this
> relates to existing energy management systems and existing standards
> such as IEC 61850 that define interval measurements.

Good point. IEC 61850 is important and should not be ignored.

> 5.7 "For the device power state, the following information is considered
> to be relevant"...   This doesn't reference any existing standards and
> is therefore largely irrelevant.

A very strange argument. Issues not covered already by existing standards
should not be dealt with by the IETF?

> 5.8 "Devices can report power for another device only if they are the
> 
> entity providing the power"  This would rule out managing PC's which
> typically don't have a SNMP agent.   We probably don't want to forbid
> this.

No, it rules out PCs that do not report their own power consumption. If no
device is connected to the PCs power line then the PC has to report power on
its own, because no other device will know its current power. This is quite
obvious. But I agree with you, that the authors should think about including
relaying of information from such PCs into their considerations.

> 6.o "Use Case: A house... A vehicle"  This further ignores basics about
> SNMP.  Existing use cases for SNMP are not homes or vehicles.

You talk about "basics". Do you claim that a "basic" property of SNMP is
that it cannot be applied in homes?

Let's try to be more constructive next time.

    Juergen


> Brad Schoening
> Consultant
> Product Development
> braschoe@cisco.com <mailto:braschoe@cisco.com>
> Phone: +1 408 424 0363
> Mobile: +1 917 304 7190
> 
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
> <http://www.cisco.com/web/about/doing_business/legal/cri/index.html>
> 
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman

--B_3372116977_29262932
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIQ5wYJKoZIhvcNAQcCoIIQ2DCCENQCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
Do8wggUzMIIEG6ADAgECAgQP7R53MA0GCSqGSIb3DQEBBQUAMIGQMQswCQYDVQQGEwJERTEY
MBYGA1UEChMPTkVDIEV1cm9wZSBMdGQuMSAwHgYDVQQLExdORUMgTGFib3JhdG9yaWVzIEV1
cm9wZTESMBAGA1UEAxMJTkVDTEFCLUNBMTEwLwYJKoZIhvcNAQkBFiJ6ZXJ0aWZpemllcnVu
Z3NzdGVsbGVAbncubmVjbGFiLmV1MB4XDTEwMDQyMDEyNDExMloXDTEzMDQxOTEyNDExMlow
YzELMAkGA1UEBhMCREUxGDAWBgNVBAoTD05FQyBFdXJvcGUgTHRkLjEgMB4GA1UECxMXTkVD
IExhYm9yYXRvcmllcyBFdXJvcGUxGDAWBgNVBAMTD0p1ZXJnZW4gUXVpdHRlazCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBANga4Hf5iSjDiva8/BTlatnXFlOWPfqZvY7AU6bt
CUKFiaGwytFar7XCwRggHcCeodYaMZoDRSEGY+bRUDvayjNvFTkhL19Fmzxg4MPmQA92tcIb
/+IylZD5YkVkw88/6zb6k+T+o875LlLAR79f8gvloaPMbxiB8KwQtdlGB9OiN1k3+7NiESpW
myT8WWrWw4F7qc0WLXaWuqv6/3vRo+jJSxyOwefEnzrRojCePJ2ZD4mgPMQvMHPqodDhTvIB
BupYoAtW53024WnL/PHH34pQ0Zmclz8u/YocnfMEYoyLDVuJKnQowDF75LVbnKmpXfCscKeb
SndFpSANP2TiI2cCAwEAAaOCAb8wggG7MAkGA1UdEwQCMAAwCwYDVR0PBAQDAgXgMCkGA1Ud
JQQiMCAGCCsGAQUFBwMCBggrBgEFBQcDBAYKKwYBBAGCNxQCAjAdBgNVHQ4EFgQU9WUPxjFB
AtJOXxJ7agqXozHDy9gwHwYDVR0jBBgwFoAUTxyHeh3gL5n2vhWq0TWdDkrmujYwHAYDVR0R
BBUwE4ERUXVpdHRla0BuZWNsYWIuZXUwfQYDVR0fBHYwdDA4oDagNIYyaHR0cDovL2NkcDEu
cGNhLmRmbi5kZS9uZWNsYWItY2EvcHViL2NybC9jYWNybC5jcmwwOKA2oDSGMmh0dHA6Ly9j
ZHAyLnBjYS5kZm4uZGUvbmVjbGFiLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGYBggrBgEFBQcB
AQSBizCBiDBCBggrBgEFBQcwAoY2aHR0cDovL2NkcDEucGNhLmRmbi5kZS9uZWNsYWItY2Ev
cHViL2NhY2VydC9jYWNlcnQuY3J0MEIGCCsGAQUFBzAChjZodHRwOi8vY2RwMi5wY2EuZGZu
LmRlL25lY2xhYi1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQEFBQADggEB
AH9VRaZ978LNoc+eM/2k/OQafNJl4UjKLjiEnH8FCuqnuNXZMAOdcfnMrRKK1bl+FhCy3sjg
gsuP4Nam2oSy7RDYWYjLY/MKMPO/MD/PpNSe6gox4948wfjWGmj4Uz3gqgDovQEC2H03jcPX
etJqBTipqmfnvMFqozoN5zjiEzJuuLpLMYNPM+E+4pQnLtRAhN94C1e9C7oP66b7as6OgVVC
CplE5llnoKM5ngtAFL5G3ygm/rZtptdmaNgRO6jDX1w9AOrsmSPGp+S+YRNonKGEqTolJpul
EJB7rMdAUimsUp/qdzvWrhIZ6A3fgzHwFhrIHqVBlDLmu7cQHu/QMUEwggUvMIIEF6ADAgEC
AgQNIQpHMA0GCSqGSIb3DQEBBQUAMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVy
ZWluMRAwDgYDVQQLEwdERk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwg
LSBHMDEwHhcNMDgxMDI0MDg1MjA4WhcNMTkwNjMwMDAwMDAwWjCBkDELMAkGA1UEBhMCREUx
GDAWBgNVBAoTD05FQyBFdXJvcGUgTHRkLjEgMB4GA1UECxMXTkVDIExhYm9yYXRvcmllcyBF
dXJvcGUxEjAQBgNVBAMTCU5FQ0xBQi1DQTExMC8GCSqGSIb3DQEJARYiemVydGlmaXppZXJ1
bmdzc3RlbGxlQG53Lm5lY2xhYi5ldTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB
AJ7yFbG1EaoyDnG5367mJEXHljmacrzNnm52KW3dXD/s3Vpuskex0jvaaTntWWRSGrAK6kKX
nTxBb3J3EhveBUbltzQ+K0XKtPJm6VE5qVpl33WJSaUHs27Dhwlke+DV6BBGyukz2SDBaSa+
nc0AwMZ0XO1DoDuiUNVeNmd/QT4SGzyFs+uLfLL2n8WzkZsbpSZ+xecwyw3EdQBBsp/i/W+u
OQBsGqaCjYe3EkBU6nW+pBsj0Iy1n7b9PXb5gQynrK3Mi2V7g1idSzHos0o1BMoHUrMzVw94
Hj4CWlWmQ0t6Pdt1uYAMjwk0saQBY/Fyfv+wKeYycGIYyYCfJIRUeyUCAwEAAaOCAcQwggHA
MBIGA1UdEwEB/wQIMAYBAf8CAQEwCwYDVR0PBAQDAgEGMB0GA1UdDgQWBBRPHId6HeAvmfa+
FarRNZ0OSua6NjAfBgNVHSMEGDAWgBRJt8bP6D0ff+pEexMp9/EKcD7eZDAtBgNVHREEJjAk
gSJ6ZXJ0aWZpemllcnVuZ3NzdGVsbGVAbncubmVjbGFiLmV1MIGIBgNVHR8EgYAwfjA9oDug
OYY3aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY3JsL2NhY3Js
LmNybDA9oDugOYY3aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIv
Y3JsL2NhY3JsLmNybDCBogYIKwYBBQUHAQEEgZUwgZIwRwYIKwYBBQUHMAKGO2h0dHA6Ly9j
ZHAxLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MEcG
CCsGAQUFBzAChjtodHRwOi8vY2RwMi5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWNhL3B1Yi9j
YWNlcnQvY2FjZXJ0LmNydDANBgkqhkiG9w0BAQUFAAOCAQEAbDEPnQ9JpouPHYA1OEekP3l3
GNM0HBzadVbtbN5MDtFmoVgdLYqlQaHb30wFhuOMbsNCOzV0k8EOvBVOT9BiEJ70RWclSZQ4
60jZS2MY6n5oG/ilZuu6N/N3GSLg2pBBNH9vZFCyBJ9n4Px7A4gQF07G+CNfV2jdE1yyPjzI
VPhg6bBgia8nXroBFe6oteavMspo0gLGIJ63NsCbl6ckPa96grT+mnnQD0h6jk/IGtXS09mE
WRbN7zZu0x0q+SScpljG36Q+jnG0U5zQI0jAx8CcYEQQH5QOlsw1Zu35OI4lsi7ycFkzJNfb
fEC4ihuw9J2L43BFGMojkhPkhVExHTCCBCEwggMJoAMCAQICAgDHMA0GCSqGSIb3DQEBBQUA
MHExCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQL
ExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMwIQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJv
b3QgQ0EgMjAeFw0wNjEyMTkxMDI5MDBaFw0xOTA2MzAyMzU5MDBaMFoxCzAJBgNVBAYTAkRF
MRMwEQYDVQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdERk4tUEtJMSQwIgYDVQQDExtERk4t
VmVyZWluIFBDQSBHbG9iYWwgLSBHMDEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB
AQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U1wBblSJ01CDrNI/W7MAxBAuZgeKmFNJSoCgjhIt0
iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6fL9KDhsAw4bpXCsxEXsM84IkQ4wcOItqaACa7txP
eKvSxhObdq3u3ibo7wGvdA/BCaL2a869080UME/15eOkyGKbghoDJzANAmVgTe3RCSMqljVY
J9N2xnG2kB3E7f81hn1vM7PbD8URwoqDoZRdQWvY0hD1TP3KUazZve+Sg7va64sWVlZDz+HV
Ez2mHycwzUlU28kTNJpxdcVs6qcLmPkhnSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjgdkwgdYw
cAYDVR0fBGkwZzBloGOgYYZfaHR0cDovL3BraS50ZWxlc2VjLmRlL2NnaS1iaW4vc2Vydmlj
ZS9hZl9Eb3dubG9hZEFSTC5jcmw/LWNybF9mb3JtYXQ9WF81MDkmLWlzc3Vlcj1EVF9ST09U
X0NBXzIwHQYDVR0OBBYEFEm3xs/oPR9/6kR7Eyn38QpwPt5kMB8GA1UdIwQYMBaAFDHDeRu6
9VPXF+CJei0XbAqzK50zMA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgECMA0G
CSqGSIb3DQEBBQUAA4IBAQA74Vp3wEgX3KkY7IGvWonwvSiSpspZGBJw7Cjy565/lizn8l0Z
MfYTK3S9vYCyufdnyTmieTvhERHua3iRM347XyYndVNljjNj7s9zw7CSI0khUHUjoR8Y4pSF
PT8z6XcgjaK95qGFKUD2P3MyWA0Ja6bahWzAP7uNZmRWJE6uDT8yNQFb6YyC2XJZT7GGhfF0
hVblw/hc843uR7NTBXDn5U2KaYMo4RMJhp5eyOpYHgwf+aTUWgRo/Sg+iwK2WLX2oSw3VwBn
qyNojWOl75lrXP1LVvarQIc01BGSbOyHxQoLBzNytG8MHVQs2FHHzL8w00Ny8TK/jM5JY6gA
9/IcMYICIDCCAhwCAQEwgZkwgZAxCzAJBgNVBAYTAkRFMRgwFgYDVQQKEw9ORUMgRXVyb3Bl
IEx0ZC4xIDAeBgNVBAsTF05FQyBMYWJvcmF0b3JpZXMgRXVyb3BlMRIwEAYDVQQDEwlORUNM
QUItQ0ExMTAvBgkqhkiG9w0BCQEWInplcnRpZml6aWVydW5nc3N0ZWxsZUBudy5uZWNsYWIu
ZXUCBA/tHncwCQYFKw4DAhoFAKBdMCMGCSqGSIb3DQEJBDEWBBRZDts7qCRM9xmM2h5k9KlL
xTHaVDAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMDExMDgx
OTA5MzdaMA0GCSqGSIb3DQEBAQUABIIBACwngQM5NNkKHbKa2+uFkjq2l62pWF5gPRc8joZ3
B3dd1SuGQEVxZViqTeF5YE4SmMw+QXTiAZ0IUH5e3LmEsgAHd5F9tZ/I7ijeE2ZXRDIvtvDc
q/L/AVE6NB4tgjPMc3jnIeEdgQqQEpBGNRs9kByfUTV3KP5z0UlldANnGfjbUMr4d/btAq9h
SFnYUOCm6t6jQ+WoR/cwgME/mE3EWTaL8GMWOyP42GBfLtvVDRhOE5n33JaE8b7Rkgnb0QyB
EKH56J/MtfA43oNrmYMerfGHu2z/EyXhFB4B+c86t92Sh53n7OwPwWaw1Mn0XuVd/68MuyFy
9yG1hVfOSL2HOzI=

--B_3372116977_29262932--

From braschoe@cisco.com  Mon Nov  8 12:19:36 2010
Return-Path: <braschoe@cisco.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 906863A692E for <eman@core3.amsl.com>; Mon,  8 Nov 2010 12:19:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.758
X-Spam-Level: 
X-Spam-Status: No, score=-9.758 tagged_above=-999 required=5 tests=[AWL=0.527,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V68UPexosbzl for <eman@core3.amsl.com>; Mon,  8 Nov 2010 12:19:34 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 973543A6834 for <eman@ietf.org>; Mon,  8 Nov 2010 12:19:34 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAEjq10ytJXG8/2dsb2JhbACiDnGhLJtjAoMCBwGCPASEWIkN
X-IronPort-AV: E=Sophos;i="4.59,170,1288569600"; d="scan'208";a="179887358"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rtp-iport-2.cisco.com with ESMTP; 08 Nov 2010 20:19:56 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core2-1.cisco.com (8.14.3/8.14.3) with ESMTP id oA8KJuZC016785;  Mon, 8 Nov 2010 20:19:56 GMT
Received: from xmb-rcd-204.cisco.com ([72.163.62.211]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 8 Nov 2010 14:19:56 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 8 Nov 2010 14:19:54 -0600
Message-ID: <308743659A7CB142B28029FB77F1128E018FF3FE@XMB-RCD-204.cisco.com>
In-Reply-To: <C8FE6BF1.16D1D%quittek@neclab.eu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [eman]  Review of draft-norwin-energy-consider-01
Thread-Index: Act/Yk5gIDthfJvVQb+n7BqkZg+aCQAFi4HXAAHeJzA=
References: <308743659A7CB142B28029FB77F1128E0185D828@XMB-RCD-204.cisco.com> <C8FE6BF1.16D1D%quittek@neclab.eu>
From: "Brad Schoening -X (braschoe - Piepeople Consulting, Inc. at Cisco)" <braschoe@cisco.com>
To: "Juergen Quittek" <Quittek@neclab.eu>, "eman mailing list" <eman@ietf.org>
X-OriginalArrivalTime: 08 Nov 2010 20:19:56.0238 (UTC) FILETIME=[4F41CEE0:01CB7F82]
Subject: Re: [eman] Review of draft-norwin-energy-consider-01
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 20:19:36 -0000

Juergen,

It seems like we're in basic agreement here, that drafts and comments
should take into account existing standards.  Then, we can have an
honest debate about which standards are most relevant to our work. =20

-----Original Message-----
From: Juergen Quittek [mailto:Quittek@neclab.eu]=20
Sent: Monday, November 08, 2010 2:10 PM
To: Brad Schoening -X (braschoe - Piepeople Consulting,Inc. at Cisco);
eman mailing list
Subject: Re: [eman] Review of draft-norwin-energy-consider-01

Wow, what a review ...

Dear Brad,

Below please find some replies on your comments inline.
Please cool down before you reply again and read carefully what you
write.

Thanks,

    Juergen


On 09.11.10 00:30  "Brad Schoening -X (braschoe - Piepeople Consulting,
Inc.
at Cisco)" <braschoe@cisco.com> wrote:

> This document is inconsistent with the EMAN charter and should be
tabled
> or withdrawn.=20

As a general comment since you do not seem to be familiar with the IETF:
Internet drafts are preferred means to contribute discussion items and
opinions to the IETF. Asking someone to withdraw a draft is comparable
to
asking someone to withdraw her or his opinion. This is not what we do in
the
IETF, at least as long as it is a technical opinion. Anyway, I would not
know means for removing a draft from the Internet draft repository.

More specifically: I am not sure what you mean with "inconsistent with
the
EMAN charter". It is indeed not one of the documents that we envision to
produce in the eman WG. But so far nobody claimed that this draft would
match any of the envisioned drafts. In contrary, Bruce stated in his
message
on this draft that this document should "reflect conclusions", "clarify
issues" and "drive decisions". No one is talking about making it an RFC.
Please find and read Bruce's announcement in the eman mailing list
archive
at http://www.ietf.org/mail-archive/web/eman/current/msg00071.html

>               It is deeply flawed in several areas.

I don't see that it even slightly flawed. Please see my replies below to
all
issues that you consider to be a flaw.

>                                                     First, it ignores
> the basic concepts of SNMP MIB management.

You are right in the sense that it ignores SNMP by not mentioning it.
But
that is all ignorance I can find. Nothing in this document is in
conflict
with any concept of SNMP.

>                                            Secondly, without
> explaining why, it ought right opposes the power models presented in
> several widely used standards such as ACPI,  DMTF's Power State and
IEC
> 61850.=20

There is no statement opposing any other standard. None of the draft we
have
received for eman uses exactly ACPI or DMTF (see my next comment below).
They don't even argue why they don't do so. Are they all deeply flawed?

> These three standards for power management are well established and
> supported on millions of devices.
>=20
> *         The ACPI standard for CPU power management was released in
> 1996 and  is ubiquitous today.  It defines seven power levels.

So far, none of the existing draft suggested using exactly the ACPI
model
for power states. draft-claise-power-management-arch-02 is close to
ACPI,
but it compresses the three stage model of ACPI (G,S,P) into a single
stage
model of 12 power states. No other document that I have seen for eman
suggests ignoring ACPI or does not provides means for supporting it.
Still,
the existing drafts differ in how far they limit themselves to ACPI that
was
defined specifically for PCs.

> *         IEC 61850 is supported by utilities worldwide and power
> equipment  manufacturers.   IEC 61850 has an extensive Common
> Information Model (CIM) that is the basis for many smart grid
standards.

This is correct. Where do you see the draft you have reviewed opposing
IEC 61850?

> *          The DMTF Power State Management Profile was adopted in 2008
> and defines an information model over web services.  It defines six
> power levels and aligns them with the ACPI power levels.

The DMTF has only 6 power states, 5 of them non-operational. They merged
all
operational power states into a single one: "on". This way it deviates
from
ACPI providing means for several more states. It looks like Bruce's and
Rolf's draft is going into the same direction.

BTW, so far none of the drafts contributing to eman has suggested to
adopt
the DMTF model of six power states although the DMTF focusing on network
management is much closer to the IETF network management issues than
ACPI
focusing on PC motherboards.

> Below are some detailed comments, but my view is that this document
does
> nothing to advance the charter of the working group and will be a
> distraction.  Instead we should focus on furthering the  existing
drafts
>=20
> http://tools.ietf.org/html/draft-quittek-power-mib-02
>=20
> http://tools.ietf.org/html/draft-parello-eman-energy-aware-mib-00
>=20
>
http://ietfreport.isoc.org/all-ids/draft-claise-energy-monitoring-mib-06
> .txt

These are all MIB modules. Right, they are on the eman charter. But as
well
on the charter are drafts on requirements, framework, and applicability.
I think the draft you reviewed is much more related to these three
drafts
than to the one you refer to.
=20
> --------------------------------------------------
>=20
> 3. "Scope of Devices" section seems to misunderstand the nature of
SNMP.
> Only devices with a network connection AND a SNMP agent can implement
> these MIBs.

I do not see any relation between this section and SNMP at all. It
definitely does not mention MIBs or SNMP. Consequently, I cannot detect
any
misunderstanding of SNMP. Are you really referring to this section or do
you
have another one in mind?

> 4.1. The 'Terminology' section on power states don't align with
existing
> standards for networked equipment (DMTF and ACPI).  The authors need
to
> clarify why they believe these pre-existing standards are in error or
> not applicable.

The drafts argues for introducing "power state categories" on, off, and
sleep. I see not problem with mapping power states defined by DMTF, ACPI
or
other bodies to these categories. Do you?

But yes, I agree that if we adopt this proposal we should elaborate on
the
mapping between these categories and the power states defined by other
bodies.

> 5.1. Control "Device Considerations" also doesn't seem to understand
how
> SNMP management works " We should not forbid power state management of
> devices that is done externally/centrally.  Today, centralized
> management is the norm with SNMP.

There is no statement forbidding anything in this short section.
Particularly, I see no indication of anyone misunderstanding SNMP. After
working with SNMP for more than 10 years now and after editing a few
standard MIB modules I still cannot see your point. Can you help me
seeing
it?

> Also, the authors need to explain how this idea relates to the current
> marketplace of existing devices that in general are externally
> controlled and only occasionally have distributed intelligence.

Good point. But you are probably aware that, for example, for mobile
access
networks so-called "Self-Organizing Networks" (SON) for self-management
of
base stations is already included in 3GPP standards. And energy
management
functions is the next application area for SON.

> 5.2 The comment about URL's seems ignorant of SysObjectID and not
> relevant to the EMAN charter

Maybe. But so far, I do not consider the identification of energy
consumers
being solved by the eman WG. Proposals are still welcome. Whether the
eman
WG or another WG will solve this problem is to be discussed.

> 5.3 For "NMS Considerations", the authors need to clarify how this
> relates to existing energy management systems and existing standards
> such as IEC 61850 that define interval measurements.

Good point. IEC 61850 is important and should not be ignored.

> 5.7 "For the device power state, the following information is
considered
> to be relevant"...   This doesn't reference any existing standards and
> is therefore largely irrelevant.

A very strange argument. Issues not covered already by existing
standards
should not be dealt with by the IETF?

> 5.8 "Devices can report power for another device only if they are the
>=20
> entity providing the power"  This would rule out managing PC's which
> typically don't have a SNMP agent.   We probably don't want to forbid
> this.

No, it rules out PCs that do not report their own power consumption. If
no
device is connected to the PCs power line then the PC has to report
power on
its own, because no other device will know its current power. This is
quite
obvious. But I agree with you, that the authors should think about
including
relaying of information from such PCs into their considerations.

> 6.o "Use Case: A house... A vehicle"  This further ignores basics
about
> SNMP.  Existing use cases for SNMP are not homes or vehicles.

You talk about "basics". Do you claim that a "basic" property of SNMP is
that it cannot be applied in homes?

Let's try to be more constructive next time.

    Juergen


> Brad Schoening
> Consultant
> Product Development
> braschoe@cisco.com <mailto:braschoe@cisco.com>
> Phone: +1 408 424 0363
> Mobile: +1 917 304 7190
>=20
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
> <http://www.cisco.com/web/about/doing_business/legal/cri/index.html>
>=20
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman

From Quittek@neclab.eu  Mon Nov  8 13:19:27 2010
Return-Path: <Quittek@neclab.eu>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9C1F13A68D5 for <eman@core3.amsl.com>; Mon,  8 Nov 2010 13:19:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.751
X-Spam-Level: 
X-Spam-Status: No, score=-101.751 tagged_above=-999 required=5 tests=[AWL=0.183, BAYES_00=-2.599, HELO_EQ_DE=0.35, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iBNyR4yp1bCO for <eman@core3.amsl.com>; Mon,  8 Nov 2010 13:19:26 -0800 (PST)
Received: from smtp0.netlab.nec.de (smtp0.netlab.nec.de [195.37.70.40]) by core3.amsl.com (Postfix) with ESMTP id 9F7E53A68CF for <eman@ietf.org>; Mon,  8 Nov 2010 13:19:25 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.netlab.nec.de (Postfix) with ESMTP id 8C3522800017D; Mon,  8 Nov 2010 22:19:47 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas1.office.hd)
Received: from smtp0.netlab.nec.de ([127.0.0.1]) by localhost (atlas1.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Eo-erxfN25V3; Mon,  8 Nov 2010 22:19:47 +0100 (CET)
Received: from METHONE.office.hd (Methone.office.hd [192.168.24.54]) by smtp0.netlab.nec.de (Postfix) with ESMTP id 627AA2800015D; Mon,  8 Nov 2010 22:19:37 +0100 (CET)
Received: from DAPHNIS.office.hd ([169.254.2.19]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0255.000; Mon, 8 Nov 2010 22:19:37 +0100
From: Juergen Quittek <Quittek@neclab.eu>
To: "Brad Schoening -X (braschoe - Piepeople Consulting,Inc. at Cisco)" <braschoe@cisco.com>, eman mailing list <eman@ietf.org>
Thread-Topic: [eman]  Review of draft-norwin-energy-consider-01
Thread-Index: Act/Yk5gIDthfJvVQb+n7BqkZg+aCQAFi4HXAAHeJzAAAqoz1w==
Date: Mon, 8 Nov 2010 21:19:36 +0000
Message-ID: <C8FE8A5C.16D31%quittek@neclab.eu>
In-Reply-To: <308743659A7CB142B28029FB77F1128E018FF3FE@XMB-RCD-204.cisco.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.7.0.100913
x-originating-ip: [10.7.0.92]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3372124764_29782299"
MIME-Version: 1.0
Subject: Re: [eman] Review of draft-norwin-energy-consider-01
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 21:19:27 -0000

--B_3372124764_29782299
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Hi Brad,

Wow, again. 

I objected almost every point you made and you see us in basic agreement.
Are you now fine with the draft that you reviewed?
No problems with it anymore?

Great!

    Juergen


On 09.11.10 04:19  "Brad Schoening -X (braschoe - Piepeople Consulting,Inc.
at Cisco)" <braschoe@cisco.com> wrote:

> Juergen,
> 
> It seems like we're in basic agreement here, that drafts and comments
> should take into account existing standards.  Then, we can have an
> honest debate about which standards are most relevant to our work.
> 
> -----Original Message-----
> From: Juergen Quittek [mailto:Quittek@neclab.eu]
> Sent: Monday, November 08, 2010 2:10 PM
> To: Brad Schoening -X (braschoe - Piepeople Consulting,Inc. at Cisco);
> eman mailing list
> Subject: Re: [eman] Review of draft-norwin-energy-consider-01
> 
> Wow, what a review ...
> 
> Dear Brad,
> 
> Below please find some replies on your comments inline.
> Please cool down before you reply again and read carefully what you
> write.
> 
> Thanks,
> 
>     Juergen
> 
> 
> On 09.11.10 00:30  "Brad Schoening -X (braschoe - Piepeople Consulting,
> Inc.
> at Cisco)" <braschoe@cisco.com> wrote:
> 
>> This document is inconsistent with the EMAN charter and should be
> tabled
>> or withdrawn. 
> 
> As a general comment since you do not seem to be familiar with the IETF:
> Internet drafts are preferred means to contribute discussion items and
> opinions to the IETF. Asking someone to withdraw a draft is comparable
> to
> asking someone to withdraw her or his opinion. This is not what we do in
> the
> IETF, at least as long as it is a technical opinion. Anyway, I would not
> know means for removing a draft from the Internet draft repository.
> 
> More specifically: I am not sure what you mean with "inconsistent with
> the
> EMAN charter". It is indeed not one of the documents that we envision to
> produce in the eman WG. But so far nobody claimed that this draft would
> match any of the envisioned drafts. In contrary, Bruce stated in his
> message
> on this draft that this document should "reflect conclusions", "clarify
> issues" and "drive decisions". No one is talking about making it an RFC.
> Please find and read Bruce's announcement in the eman mailing list
> archive
> at http://www.ietf.org/mail-archive/web/eman/current/msg00071.html
> 
>>               It is deeply flawed in several areas.
> 
> I don't see that it even slightly flawed. Please see my replies below to
> all
> issues that you consider to be a flaw.
> 
>>                                                     First, it ignores
>> the basic concepts of SNMP MIB management.
> 
> You are right in the sense that it ignores SNMP by not mentioning it.
> But
> that is all ignorance I can find. Nothing in this document is in
> conflict
> with any concept of SNMP.
> 
>>                                            Secondly, without
>> explaining why, it ought right opposes the power models presented in
>> several widely used standards such as ACPI,  DMTF's Power State and
> IEC
>> 61850. 
> 
> There is no statement opposing any other standard. None of the draft we
> have
> received for eman uses exactly ACPI or DMTF (see my next comment below).
> They don't even argue why they don't do so. Are they all deeply flawed?
> 
>> These three standards for power management are well established and
>> supported on millions of devices.
>> 
>> *         The ACPI standard for CPU power management was released in
>> 1996 and  is ubiquitous today.  It defines seven power levels.
> 
> So far, none of the existing draft suggested using exactly the ACPI
> model
> for power states. draft-claise-power-management-arch-02 is close to
> ACPI,
> but it compresses the three stage model of ACPI (G,S,P) into a single
> stage
> model of 12 power states. No other document that I have seen for eman
> suggests ignoring ACPI or does not provides means for supporting it.
> Still,
> the existing drafts differ in how far they limit themselves to ACPI that
> was
> defined specifically for PCs.
> 
>> *         IEC 61850 is supported by utilities worldwide and power
>> equipment  manufacturers.   IEC 61850 has an extensive Common
>> Information Model (CIM) that is the basis for many smart grid
> standards.
> 
> This is correct. Where do you see the draft you have reviewed opposing
> IEC 61850?
> 
>> *          The DMTF Power State Management Profile was adopted in 2008
>> and defines an information model over web services.  It defines six
>> power levels and aligns them with the ACPI power levels.
> 
> The DMTF has only 6 power states, 5 of them non-operational. They merged
> all
> operational power states into a single one: "on". This way it deviates
> from
> ACPI providing means for several more states. It looks like Bruce's and
> Rolf's draft is going into the same direction.
> 
> BTW, so far none of the drafts contributing to eman has suggested to
> adopt
> the DMTF model of six power states although the DMTF focusing on network
> management is much closer to the IETF network management issues than
> ACPI
> focusing on PC motherboards.
> 
>> Below are some detailed comments, but my view is that this document
> does
>> nothing to advance the charter of the working group and will be a
>> distraction.  Instead we should focus on furthering the  existing
> drafts
>> 
>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>> 
>> http://tools.ietf.org/html/draft-parello-eman-energy-aware-mib-00
>> 
>> 
> http://ietfreport.isoc.org/all-ids/draft-claise-energy-monitoring-mib-06
>> .txt
> 
> These are all MIB modules. Right, they are on the eman charter. But as
> well
> on the charter are drafts on requirements, framework, and applicability.
> I think the draft you reviewed is much more related to these three
> drafts
> than to the one you refer to.
>  
>> --------------------------------------------------
>> 
>> 3. "Scope of Devices" section seems to misunderstand the nature of
> SNMP.
>> Only devices with a network connection AND a SNMP agent can implement
>> these MIBs.
> 
> I do not see any relation between this section and SNMP at all. It
> definitely does not mention MIBs or SNMP. Consequently, I cannot detect
> any
> misunderstanding of SNMP. Are you really referring to this section or do
> you
> have another one in mind?
> 
>> 4.1. The 'Terminology' section on power states don't align with
> existing
>> standards for networked equipment (DMTF and ACPI).  The authors need
> to
>> clarify why they believe these pre-existing standards are in error or
>> not applicable.
> 
> The drafts argues for introducing "power state categories" on, off, and
> sleep. I see not problem with mapping power states defined by DMTF, ACPI
> or
> other bodies to these categories. Do you?
> 
> But yes, I agree that if we adopt this proposal we should elaborate on
> the
> mapping between these categories and the power states defined by other
> bodies.
> 
>> 5.1. Control "Device Considerations" also doesn't seem to understand
> how
>> SNMP management works " We should not forbid power state management of
>> devices that is done externally/centrally.  Today, centralized
>> management is the norm with SNMP.
> 
> There is no statement forbidding anything in this short section.
> Particularly, I see no indication of anyone misunderstanding SNMP. After
> working with SNMP for more than 10 years now and after editing a few
> standard MIB modules I still cannot see your point. Can you help me
> seeing
> it?
> 
>> Also, the authors need to explain how this idea relates to the current
>> marketplace of existing devices that in general are externally
>> controlled and only occasionally have distributed intelligence.
> 
> Good point. But you are probably aware that, for example, for mobile
> access
> networks so-called "Self-Organizing Networks" (SON) for self-management
> of
> base stations is already included in 3GPP standards. And energy
> management
> functions is the next application area for SON.
> 
>> 5.2 The comment about URL's seems ignorant of SysObjectID and not
>> relevant to the EMAN charter
> 
> Maybe. But so far, I do not consider the identification of energy
> consumers
> being solved by the eman WG. Proposals are still welcome. Whether the
> eman
> WG or another WG will solve this problem is to be discussed.
> 
>> 5.3 For "NMS Considerations", the authors need to clarify how this
>> relates to existing energy management systems and existing standards
>> such as IEC 61850 that define interval measurements.
> 
> Good point. IEC 61850 is important and should not be ignored.
> 
>> 5.7 "For the device power state, the following information is
> considered
>> to be relevant"...   This doesn't reference any existing standards and
>> is therefore largely irrelevant.
> 
> A very strange argument. Issues not covered already by existing
> standards
> should not be dealt with by the IETF?
> 
>> 5.8 "Devices can report power for another device only if they are the
>> 
>> entity providing the power"  This would rule out managing PC's which
>> typically don't have a SNMP agent.   We probably don't want to forbid
>> this.
> 
> No, it rules out PCs that do not report their own power consumption. If
> no
> device is connected to the PCs power line then the PC has to report
> power on
> its own, because no other device will know its current power. This is
> quite
> obvious. But I agree with you, that the authors should think about
> including
> relaying of information from such PCs into their considerations.
> 
>> 6.o "Use Case: A house... A vehicle"  This further ignores basics
> about
>> SNMP.  Existing use cases for SNMP are not homes or vehicles.
> 
> You talk about "basics". Do you claim that a "basic" property of SNMP is
> that it cannot be applied in homes?
> 
> Let's try to be more constructive next time.
> 
>     Juergen
> 
> 
>> Brad Schoening
>> Consultant
>> Product Development
>> braschoe@cisco.com <mailto:braschoe@cisco.com>
>> Phone: +1 408 424 0363
>> Mobile: +1 917 304 7190
>> 
>> For corporate legal information go to:
>> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>> <http://www.cisco.com/web/about/doing_business/legal/cri/index.html>
>> 
>> _______________________________________________
>> eman mailing list
>> eman@ietf.org
>> https://www.ietf.org/mailman/listinfo/eman

--B_3372124764_29782299
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIQ5wYJKoZIhvcNAQcCoIIQ2DCCENQCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
Do8wggUzMIIEG6ADAgECAgQP7R53MA0GCSqGSIb3DQEBBQUAMIGQMQswCQYDVQQGEwJERTEY
MBYGA1UEChMPTkVDIEV1cm9wZSBMdGQuMSAwHgYDVQQLExdORUMgTGFib3JhdG9yaWVzIEV1
cm9wZTESMBAGA1UEAxMJTkVDTEFCLUNBMTEwLwYJKoZIhvcNAQkBFiJ6ZXJ0aWZpemllcnVu
Z3NzdGVsbGVAbncubmVjbGFiLmV1MB4XDTEwMDQyMDEyNDExMloXDTEzMDQxOTEyNDExMlow
YzELMAkGA1UEBhMCREUxGDAWBgNVBAoTD05FQyBFdXJvcGUgTHRkLjEgMB4GA1UECxMXTkVD
IExhYm9yYXRvcmllcyBFdXJvcGUxGDAWBgNVBAMTD0p1ZXJnZW4gUXVpdHRlazCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBANga4Hf5iSjDiva8/BTlatnXFlOWPfqZvY7AU6bt
CUKFiaGwytFar7XCwRggHcCeodYaMZoDRSEGY+bRUDvayjNvFTkhL19Fmzxg4MPmQA92tcIb
/+IylZD5YkVkw88/6zb6k+T+o875LlLAR79f8gvloaPMbxiB8KwQtdlGB9OiN1k3+7NiESpW
myT8WWrWw4F7qc0WLXaWuqv6/3vRo+jJSxyOwefEnzrRojCePJ2ZD4mgPMQvMHPqodDhTvIB
BupYoAtW53024WnL/PHH34pQ0Zmclz8u/YocnfMEYoyLDVuJKnQowDF75LVbnKmpXfCscKeb
SndFpSANP2TiI2cCAwEAAaOCAb8wggG7MAkGA1UdEwQCMAAwCwYDVR0PBAQDAgXgMCkGA1Ud
JQQiMCAGCCsGAQUFBwMCBggrBgEFBQcDBAYKKwYBBAGCNxQCAjAdBgNVHQ4EFgQU9WUPxjFB
AtJOXxJ7agqXozHDy9gwHwYDVR0jBBgwFoAUTxyHeh3gL5n2vhWq0TWdDkrmujYwHAYDVR0R
BBUwE4ERUXVpdHRla0BuZWNsYWIuZXUwfQYDVR0fBHYwdDA4oDagNIYyaHR0cDovL2NkcDEu
cGNhLmRmbi5kZS9uZWNsYWItY2EvcHViL2NybC9jYWNybC5jcmwwOKA2oDSGMmh0dHA6Ly9j
ZHAyLnBjYS5kZm4uZGUvbmVjbGFiLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGYBggrBgEFBQcB
AQSBizCBiDBCBggrBgEFBQcwAoY2aHR0cDovL2NkcDEucGNhLmRmbi5kZS9uZWNsYWItY2Ev
cHViL2NhY2VydC9jYWNlcnQuY3J0MEIGCCsGAQUFBzAChjZodHRwOi8vY2RwMi5wY2EuZGZu
LmRlL25lY2xhYi1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQEFBQADggEB
AH9VRaZ978LNoc+eM/2k/OQafNJl4UjKLjiEnH8FCuqnuNXZMAOdcfnMrRKK1bl+FhCy3sjg
gsuP4Nam2oSy7RDYWYjLY/MKMPO/MD/PpNSe6gox4948wfjWGmj4Uz3gqgDovQEC2H03jcPX
etJqBTipqmfnvMFqozoN5zjiEzJuuLpLMYNPM+E+4pQnLtRAhN94C1e9C7oP66b7as6OgVVC
CplE5llnoKM5ngtAFL5G3ygm/rZtptdmaNgRO6jDX1w9AOrsmSPGp+S+YRNonKGEqTolJpul
EJB7rMdAUimsUp/qdzvWrhIZ6A3fgzHwFhrIHqVBlDLmu7cQHu/QMUEwggUvMIIEF6ADAgEC
AgQNIQpHMA0GCSqGSIb3DQEBBQUAMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVy
ZWluMRAwDgYDVQQLEwdERk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwg
LSBHMDEwHhcNMDgxMDI0MDg1MjA4WhcNMTkwNjMwMDAwMDAwWjCBkDELMAkGA1UEBhMCREUx
GDAWBgNVBAoTD05FQyBFdXJvcGUgTHRkLjEgMB4GA1UECxMXTkVDIExhYm9yYXRvcmllcyBF
dXJvcGUxEjAQBgNVBAMTCU5FQ0xBQi1DQTExMC8GCSqGSIb3DQEJARYiemVydGlmaXppZXJ1
bmdzc3RlbGxlQG53Lm5lY2xhYi5ldTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB
AJ7yFbG1EaoyDnG5367mJEXHljmacrzNnm52KW3dXD/s3Vpuskex0jvaaTntWWRSGrAK6kKX
nTxBb3J3EhveBUbltzQ+K0XKtPJm6VE5qVpl33WJSaUHs27Dhwlke+DV6BBGyukz2SDBaSa+
nc0AwMZ0XO1DoDuiUNVeNmd/QT4SGzyFs+uLfLL2n8WzkZsbpSZ+xecwyw3EdQBBsp/i/W+u
OQBsGqaCjYe3EkBU6nW+pBsj0Iy1n7b9PXb5gQynrK3Mi2V7g1idSzHos0o1BMoHUrMzVw94
Hj4CWlWmQ0t6Pdt1uYAMjwk0saQBY/Fyfv+wKeYycGIYyYCfJIRUeyUCAwEAAaOCAcQwggHA
MBIGA1UdEwEB/wQIMAYBAf8CAQEwCwYDVR0PBAQDAgEGMB0GA1UdDgQWBBRPHId6HeAvmfa+
FarRNZ0OSua6NjAfBgNVHSMEGDAWgBRJt8bP6D0ff+pEexMp9/EKcD7eZDAtBgNVHREEJjAk
gSJ6ZXJ0aWZpemllcnVuZ3NzdGVsbGVAbncubmVjbGFiLmV1MIGIBgNVHR8EgYAwfjA9oDug
OYY3aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY3JsL2NhY3Js
LmNybDA9oDugOYY3aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIv
Y3JsL2NhY3JsLmNybDCBogYIKwYBBQUHAQEEgZUwgZIwRwYIKwYBBQUHMAKGO2h0dHA6Ly9j
ZHAxLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MEcG
CCsGAQUFBzAChjtodHRwOi8vY2RwMi5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWNhL3B1Yi9j
YWNlcnQvY2FjZXJ0LmNydDANBgkqhkiG9w0BAQUFAAOCAQEAbDEPnQ9JpouPHYA1OEekP3l3
GNM0HBzadVbtbN5MDtFmoVgdLYqlQaHb30wFhuOMbsNCOzV0k8EOvBVOT9BiEJ70RWclSZQ4
60jZS2MY6n5oG/ilZuu6N/N3GSLg2pBBNH9vZFCyBJ9n4Px7A4gQF07G+CNfV2jdE1yyPjzI
VPhg6bBgia8nXroBFe6oteavMspo0gLGIJ63NsCbl6ckPa96grT+mnnQD0h6jk/IGtXS09mE
WRbN7zZu0x0q+SScpljG36Q+jnG0U5zQI0jAx8CcYEQQH5QOlsw1Zu35OI4lsi7ycFkzJNfb
fEC4ihuw9J2L43BFGMojkhPkhVExHTCCBCEwggMJoAMCAQICAgDHMA0GCSqGSIb3DQEBBQUA
MHExCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQL
ExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMwIQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJv
b3QgQ0EgMjAeFw0wNjEyMTkxMDI5MDBaFw0xOTA2MzAyMzU5MDBaMFoxCzAJBgNVBAYTAkRF
MRMwEQYDVQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdERk4tUEtJMSQwIgYDVQQDExtERk4t
VmVyZWluIFBDQSBHbG9iYWwgLSBHMDEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB
AQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U1wBblSJ01CDrNI/W7MAxBAuZgeKmFNJSoCgjhIt0
iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6fL9KDhsAw4bpXCsxEXsM84IkQ4wcOItqaACa7txP
eKvSxhObdq3u3ibo7wGvdA/BCaL2a869080UME/15eOkyGKbghoDJzANAmVgTe3RCSMqljVY
J9N2xnG2kB3E7f81hn1vM7PbD8URwoqDoZRdQWvY0hD1TP3KUazZve+Sg7va64sWVlZDz+HV
Ez2mHycwzUlU28kTNJpxdcVs6qcLmPkhnSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjgdkwgdYw
cAYDVR0fBGkwZzBloGOgYYZfaHR0cDovL3BraS50ZWxlc2VjLmRlL2NnaS1iaW4vc2Vydmlj
ZS9hZl9Eb3dubG9hZEFSTC5jcmw/LWNybF9mb3JtYXQ9WF81MDkmLWlzc3Vlcj1EVF9ST09U
X0NBXzIwHQYDVR0OBBYEFEm3xs/oPR9/6kR7Eyn38QpwPt5kMB8GA1UdIwQYMBaAFDHDeRu6
9VPXF+CJei0XbAqzK50zMA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgECMA0G
CSqGSIb3DQEBBQUAA4IBAQA74Vp3wEgX3KkY7IGvWonwvSiSpspZGBJw7Cjy565/lizn8l0Z
MfYTK3S9vYCyufdnyTmieTvhERHua3iRM347XyYndVNljjNj7s9zw7CSI0khUHUjoR8Y4pSF
PT8z6XcgjaK95qGFKUD2P3MyWA0Ja6bahWzAP7uNZmRWJE6uDT8yNQFb6YyC2XJZT7GGhfF0
hVblw/hc843uR7NTBXDn5U2KaYMo4RMJhp5eyOpYHgwf+aTUWgRo/Sg+iwK2WLX2oSw3VwBn
qyNojWOl75lrXP1LVvarQIc01BGSbOyHxQoLBzNytG8MHVQs2FHHzL8w00Ny8TK/jM5JY6gA
9/IcMYICIDCCAhwCAQEwgZkwgZAxCzAJBgNVBAYTAkRFMRgwFgYDVQQKEw9ORUMgRXVyb3Bl
IEx0ZC4xIDAeBgNVBAsTF05FQyBMYWJvcmF0b3JpZXMgRXVyb3BlMRIwEAYDVQQDEwlORUNM
QUItQ0ExMTAvBgkqhkiG9w0BCQEWInplcnRpZml6aWVydW5nc3N0ZWxsZUBudy5uZWNsYWIu
ZXUCBA/tHncwCQYFKw4DAhoFAKBdMCMGCSqGSIb3DQEJBDEWBBTn4Swsm62+n2TSpGz2HtBn
+f+jgjAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMDExMDgy
MTE5MjRaMA0GCSqGSIb3DQEBAQUABIIBAM9rD1rHua9nV7RAzQLRztQW2UDQmRNQSc1atl7o
SKAaYRUUe0S8G6qwK/6Jo7rAI3GZEalE3SzWVu2U91Avj6zZRlwo3Aq41J91IjK90+G8J364
z1vwWB5c65n02OYGIaeJppsSAYedg1U/KdDmAXf6iExBb0eyl4IX8RpDXa7ENAepcOKCqgNT
boxJTgXyEelrLO7RIBryJ13tbP0npx10Rj8d9jM3dUs+5kAJbZ3vwN5LdOVqHopylTItPI0X
9rQ/VbvGkrYGoQHFyHRh7pHaFHTGXs2qKv8bPkzgGgZWWc2q72xRMOS8vdsKaQQw5KGR10CT
fQhytzc2GQG7U/E=

--B_3372124764_29782299--

From Quittek@neclab.eu  Mon Nov  8 15:24:50 2010
Return-Path: <Quittek@neclab.eu>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 61DE428C0E7 for <eman@core3.amsl.com>; Mon,  8 Nov 2010 15:24:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.145
X-Spam-Level: 
X-Spam-Status: No, score=-102.145 tagged_above=-999 required=5 tests=[AWL=0.454, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ifwxcTghmwoS for <eman@core3.amsl.com>; Mon,  8 Nov 2010 15:24:49 -0800 (PST)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41]) by core3.amsl.com (Postfix) with ESMTP id BED4F28C0E3 for <eman@ietf.org>; Mon,  8 Nov 2010 15:24:48 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.neclab.eu (Postfix) with ESMTP id EFDAB2C0001B0 for <eman@ietf.org>; Tue,  9 Nov 2010 00:25:08 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office.hd)
Received: from smtp0.neclab.eu ([127.0.0.1]) by localhost (atlas2.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4OcIkSTMfQeC for <eman@ietf.org>; Tue,  9 Nov 2010 00:25:08 +0100 (CET)
Received: from METHONE.office.hd (Methone.office.hd [192.168.24.54]) by smtp0.neclab.eu (Postfix) with ESMTP id D27612C0001AF for <eman@ietf.org>; Tue,  9 Nov 2010 00:25:03 +0100 (CET)
Received: from DAPHNIS.office.hd ([169.254.2.19]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0255.000; Tue, 9 Nov 2010 00:25:03 +0100
From: Juergen Quittek <Quittek@neclab.eu>
To: eman mailing list <eman@ietf.org>
Thread-Topic: New draft draft-quittek-eman-reference-model-00 
Thread-Index: AQHLf5wrW8er+/feZEiYYleDjPOCsQ==
Date: Mon, 8 Nov 2010 23:25:03 +0000
Message-ID: <C8FEA7BA.16D4A%quittek@neclab.eu>
In-Reply-To: <20101108224927.6B96728C0DB@core3.amsl.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.7.0.100913
x-originating-ip: [10.7.0.92]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3372132282_30211805"
MIME-Version: 1.0
Subject: [eman] New draft draft-quittek-eman-reference-model-00
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Nov 2010 23:24:50 -0000

--B_3372132282_30211805
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Dear all,

The discussions on this list during the last days and in restaurants at the
last nights have been quite inspiring. Particularly my understanding of the
fundamental steps of energy management has improved.

I tried to record some of the new insights in an Internet draft that I just
posted. It suggests a more detailed reference model for energy management
than we have it so far. Please find it at
http://datatracker.ietf.org/doc/draft-quittek-eman-reference-model/

This is just a contribution to the ongoing discussion. I have no intention
of adding another document to our charter. The content of this draft will
hopefully help understanding better what energy management is or could be.

I know this draft arrives too late for discussing it during the session
tomorrow. But we can do this on the list. Comments are highly appreciated.

Thanks,

    Juergen


------ Forwarded message
From: IETF I-D Submission Tool <idsubmission@ietf.org>
Date: Mon, 8 Nov 2010 14:49:27 -0800
To: <quittek@neclab.eu>
Subject: New Version Notification for  draft-quittek-eman-reference-model-00


A new version of I-D, draft-quittek-eman-reference-model-00.txt has been
successfully submitted by Juergen Quittek and posted to the IETF repository.

Filename:  draft-quittek-eman-reference-model
Revision:  00
Title:   Reference Model for Energy Management
Creation_date:  2010-11-08
WG ID:   Independent Submission
Number_of_pages: 15

Abstract:
This memo discusses suggest a reference model for energy consumption
monitoring and control.  It defines entities involved in energy
management, their roles, and relationships between them.  Considered
entities include energy consumers, energy consumption meters, energy
consumption reporters, energy consumption controllers, and energy
consumption management systems.

The IETF Secretariat.

------ end of forwarded message

--B_3372132282_30211805
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIQ5wYJKoZIhvcNAQcCoIIQ2DCCENQCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
Do8wggUzMIIEG6ADAgECAgQP7R53MA0GCSqGSIb3DQEBBQUAMIGQMQswCQYDVQQGEwJERTEY
MBYGA1UEChMPTkVDIEV1cm9wZSBMdGQuMSAwHgYDVQQLExdORUMgTGFib3JhdG9yaWVzIEV1
cm9wZTESMBAGA1UEAxMJTkVDTEFCLUNBMTEwLwYJKoZIhvcNAQkBFiJ6ZXJ0aWZpemllcnVu
Z3NzdGVsbGVAbncubmVjbGFiLmV1MB4XDTEwMDQyMDEyNDExMloXDTEzMDQxOTEyNDExMlow
YzELMAkGA1UEBhMCREUxGDAWBgNVBAoTD05FQyBFdXJvcGUgTHRkLjEgMB4GA1UECxMXTkVD
IExhYm9yYXRvcmllcyBFdXJvcGUxGDAWBgNVBAMTD0p1ZXJnZW4gUXVpdHRlazCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBANga4Hf5iSjDiva8/BTlatnXFlOWPfqZvY7AU6bt
CUKFiaGwytFar7XCwRggHcCeodYaMZoDRSEGY+bRUDvayjNvFTkhL19Fmzxg4MPmQA92tcIb
/+IylZD5YkVkw88/6zb6k+T+o875LlLAR79f8gvloaPMbxiB8KwQtdlGB9OiN1k3+7NiESpW
myT8WWrWw4F7qc0WLXaWuqv6/3vRo+jJSxyOwefEnzrRojCePJ2ZD4mgPMQvMHPqodDhTvIB
BupYoAtW53024WnL/PHH34pQ0Zmclz8u/YocnfMEYoyLDVuJKnQowDF75LVbnKmpXfCscKeb
SndFpSANP2TiI2cCAwEAAaOCAb8wggG7MAkGA1UdEwQCMAAwCwYDVR0PBAQDAgXgMCkGA1Ud
JQQiMCAGCCsGAQUFBwMCBggrBgEFBQcDBAYKKwYBBAGCNxQCAjAdBgNVHQ4EFgQU9WUPxjFB
AtJOXxJ7agqXozHDy9gwHwYDVR0jBBgwFoAUTxyHeh3gL5n2vhWq0TWdDkrmujYwHAYDVR0R
BBUwE4ERUXVpdHRla0BuZWNsYWIuZXUwfQYDVR0fBHYwdDA4oDagNIYyaHR0cDovL2NkcDEu
cGNhLmRmbi5kZS9uZWNsYWItY2EvcHViL2NybC9jYWNybC5jcmwwOKA2oDSGMmh0dHA6Ly9j
ZHAyLnBjYS5kZm4uZGUvbmVjbGFiLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGYBggrBgEFBQcB
AQSBizCBiDBCBggrBgEFBQcwAoY2aHR0cDovL2NkcDEucGNhLmRmbi5kZS9uZWNsYWItY2Ev
cHViL2NhY2VydC9jYWNlcnQuY3J0MEIGCCsGAQUFBzAChjZodHRwOi8vY2RwMi5wY2EuZGZu
LmRlL25lY2xhYi1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQEFBQADggEB
AH9VRaZ978LNoc+eM/2k/OQafNJl4UjKLjiEnH8FCuqnuNXZMAOdcfnMrRKK1bl+FhCy3sjg
gsuP4Nam2oSy7RDYWYjLY/MKMPO/MD/PpNSe6gox4948wfjWGmj4Uz3gqgDovQEC2H03jcPX
etJqBTipqmfnvMFqozoN5zjiEzJuuLpLMYNPM+E+4pQnLtRAhN94C1e9C7oP66b7as6OgVVC
CplE5llnoKM5ngtAFL5G3ygm/rZtptdmaNgRO6jDX1w9AOrsmSPGp+S+YRNonKGEqTolJpul
EJB7rMdAUimsUp/qdzvWrhIZ6A3fgzHwFhrIHqVBlDLmu7cQHu/QMUEwggUvMIIEF6ADAgEC
AgQNIQpHMA0GCSqGSIb3DQEBBQUAMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVy
ZWluMRAwDgYDVQQLEwdERk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwg
LSBHMDEwHhcNMDgxMDI0MDg1MjA4WhcNMTkwNjMwMDAwMDAwWjCBkDELMAkGA1UEBhMCREUx
GDAWBgNVBAoTD05FQyBFdXJvcGUgTHRkLjEgMB4GA1UECxMXTkVDIExhYm9yYXRvcmllcyBF
dXJvcGUxEjAQBgNVBAMTCU5FQ0xBQi1DQTExMC8GCSqGSIb3DQEJARYiemVydGlmaXppZXJ1
bmdzc3RlbGxlQG53Lm5lY2xhYi5ldTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB
AJ7yFbG1EaoyDnG5367mJEXHljmacrzNnm52KW3dXD/s3Vpuskex0jvaaTntWWRSGrAK6kKX
nTxBb3J3EhveBUbltzQ+K0XKtPJm6VE5qVpl33WJSaUHs27Dhwlke+DV6BBGyukz2SDBaSa+
nc0AwMZ0XO1DoDuiUNVeNmd/QT4SGzyFs+uLfLL2n8WzkZsbpSZ+xecwyw3EdQBBsp/i/W+u
OQBsGqaCjYe3EkBU6nW+pBsj0Iy1n7b9PXb5gQynrK3Mi2V7g1idSzHos0o1BMoHUrMzVw94
Hj4CWlWmQ0t6Pdt1uYAMjwk0saQBY/Fyfv+wKeYycGIYyYCfJIRUeyUCAwEAAaOCAcQwggHA
MBIGA1UdEwEB/wQIMAYBAf8CAQEwCwYDVR0PBAQDAgEGMB0GA1UdDgQWBBRPHId6HeAvmfa+
FarRNZ0OSua6NjAfBgNVHSMEGDAWgBRJt8bP6D0ff+pEexMp9/EKcD7eZDAtBgNVHREEJjAk
gSJ6ZXJ0aWZpemllcnVuZ3NzdGVsbGVAbncubmVjbGFiLmV1MIGIBgNVHR8EgYAwfjA9oDug
OYY3aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY3JsL2NhY3Js
LmNybDA9oDugOYY3aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIv
Y3JsL2NhY3JsLmNybDCBogYIKwYBBQUHAQEEgZUwgZIwRwYIKwYBBQUHMAKGO2h0dHA6Ly9j
ZHAxLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MEcG
CCsGAQUFBzAChjtodHRwOi8vY2RwMi5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWNhL3B1Yi9j
YWNlcnQvY2FjZXJ0LmNydDANBgkqhkiG9w0BAQUFAAOCAQEAbDEPnQ9JpouPHYA1OEekP3l3
GNM0HBzadVbtbN5MDtFmoVgdLYqlQaHb30wFhuOMbsNCOzV0k8EOvBVOT9BiEJ70RWclSZQ4
60jZS2MY6n5oG/ilZuu6N/N3GSLg2pBBNH9vZFCyBJ9n4Px7A4gQF07G+CNfV2jdE1yyPjzI
VPhg6bBgia8nXroBFe6oteavMspo0gLGIJ63NsCbl6ckPa96grT+mnnQD0h6jk/IGtXS09mE
WRbN7zZu0x0q+SScpljG36Q+jnG0U5zQI0jAx8CcYEQQH5QOlsw1Zu35OI4lsi7ycFkzJNfb
fEC4ihuw9J2L43BFGMojkhPkhVExHTCCBCEwggMJoAMCAQICAgDHMA0GCSqGSIb3DQEBBQUA
MHExCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQL
ExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMwIQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJv
b3QgQ0EgMjAeFw0wNjEyMTkxMDI5MDBaFw0xOTA2MzAyMzU5MDBaMFoxCzAJBgNVBAYTAkRF
MRMwEQYDVQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdERk4tUEtJMSQwIgYDVQQDExtERk4t
VmVyZWluIFBDQSBHbG9iYWwgLSBHMDEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB
AQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U1wBblSJ01CDrNI/W7MAxBAuZgeKmFNJSoCgjhIt0
iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6fL9KDhsAw4bpXCsxEXsM84IkQ4wcOItqaACa7txP
eKvSxhObdq3u3ibo7wGvdA/BCaL2a869080UME/15eOkyGKbghoDJzANAmVgTe3RCSMqljVY
J9N2xnG2kB3E7f81hn1vM7PbD8URwoqDoZRdQWvY0hD1TP3KUazZve+Sg7va64sWVlZDz+HV
Ez2mHycwzUlU28kTNJpxdcVs6qcLmPkhnSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjgdkwgdYw
cAYDVR0fBGkwZzBloGOgYYZfaHR0cDovL3BraS50ZWxlc2VjLmRlL2NnaS1iaW4vc2Vydmlj
ZS9hZl9Eb3dubG9hZEFSTC5jcmw/LWNybF9mb3JtYXQ9WF81MDkmLWlzc3Vlcj1EVF9ST09U
X0NBXzIwHQYDVR0OBBYEFEm3xs/oPR9/6kR7Eyn38QpwPt5kMB8GA1UdIwQYMBaAFDHDeRu6
9VPXF+CJei0XbAqzK50zMA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgECMA0G
CSqGSIb3DQEBBQUAA4IBAQA74Vp3wEgX3KkY7IGvWonwvSiSpspZGBJw7Cjy565/lizn8l0Z
MfYTK3S9vYCyufdnyTmieTvhERHua3iRM347XyYndVNljjNj7s9zw7CSI0khUHUjoR8Y4pSF
PT8z6XcgjaK95qGFKUD2P3MyWA0Ja6bahWzAP7uNZmRWJE6uDT8yNQFb6YyC2XJZT7GGhfF0
hVblw/hc843uR7NTBXDn5U2KaYMo4RMJhp5eyOpYHgwf+aTUWgRo/Sg+iwK2WLX2oSw3VwBn
qyNojWOl75lrXP1LVvarQIc01BGSbOyHxQoLBzNytG8MHVQs2FHHzL8w00Ny8TK/jM5JY6gA
9/IcMYICIDCCAhwCAQEwgZkwgZAxCzAJBgNVBAYTAkRFMRgwFgYDVQQKEw9ORUMgRXVyb3Bl
IEx0ZC4xIDAeBgNVBAsTF05FQyBMYWJvcmF0b3JpZXMgRXVyb3BlMRIwEAYDVQQDEwlORUNM
QUItQ0ExMTAvBgkqhkiG9w0BCQEWInplcnRpZml6aWVydW5nc3N0ZWxsZUBudy5uZWNsYWIu
ZXUCBA/tHncwCQYFKw4DAhoFAKBdMCMGCSqGSIb3DQEJBDEWBBSCRw5vbgF5Zz4Iv1lsMPcE
CkijajAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMDExMDgy
MzI0NDJaMA0GCSqGSIb3DQEBAQUABIIBACyzn6XjnN+RDGxXqDWZffne9mwGZu2uvpE0TFJt
ifm8/QjMkzoaYVTZkv2Pm35qYTXxvo8VWvjSSRK4s0gHJbB8uRzPEZ8YoFt27biNviprw4Bo
SUpXcuQ2cRNgrMnslrKWk+D4wXfPWpuppVGO3HHurosb/vyQ/Gzdrw00UKPHj9iJf6tmcMy6
v7URLo85eLei1Obx6qMwktoDYRlT2Sr+9/gg533sfdpAtaydqs0qK/ylbkBTdx/3mN52HasU
FLBysBfILlInsvWhthDKpsn5UwKcZzeDCzR8b4QuOLSyC5jjueYCUVDxgHAbKv8/i3KdYOHF
zsWYltGh8vYU5e0=

--B_3372132282_30211805--

From Rolf.Winter@neclab.eu  Mon Nov  8 16:53:31 2010
Return-Path: <Rolf.Winter@neclab.eu>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0116B28C0F5 for <eman@core3.amsl.com>; Mon,  8 Nov 2010 16:53:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.908
X-Spam-Level: 
X-Spam-Status: No, score=-101.908 tagged_above=-999 required=5 tests=[AWL=0.376, BAYES_00=-2.599, SARE_MILLIONSOF=0.315, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cA3J-7nO-2ec for <eman@core3.amsl.com>; Mon,  8 Nov 2010 16:53:29 -0800 (PST)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41]) by core3.amsl.com (Postfix) with ESMTP id 1955C3A690E for <eman@ietf.org>; Mon,  8 Nov 2010 16:53:29 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.neclab.eu (Postfix) with ESMTP id 6ED5B2C0001AD; Tue,  9 Nov 2010 01:53:51 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office.hd)
Received: from smtp0.neclab.eu ([127.0.0.1]) by localhost (atlas2.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d7z3b2YDYTUk; Tue,  9 Nov 2010 01:53:51 +0100 (CET)
Received: from METHONE.office.hd (Methone.office.hd [192.168.24.54]) by smtp0.neclab.eu (Postfix) with ESMTP id 4496B2C0001AF; Tue,  9 Nov 2010 01:53:41 +0100 (CET)
Received: from PALLENE.office.hd ([169.254.1.152]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0255.000; Tue, 9 Nov 2010 01:53:41 +0100
From: Rolf Winter <Rolf.Winter@neclab.eu>
To: Juergen Quittek <Quittek@neclab.eu>, "Brad Schoening -X (braschoe - Piepeople Consulting, Inc. at Cisco)" <braschoe@cisco.com>, eman mailing list <eman@ietf.org>
Thread-Topic: [eman] Review of draft-norwin-energy-consider-01
Thread-Index: AQHLf3iYfx0dv0f+yEybLei00kP9zpNoURgA
Date: Tue, 9 Nov 2010 00:53:40 +0000
Message-ID: <791AD3077F94194BB2BDD13565B6295D836F79@PALLENE.office.hd>
References: <308743659A7CB142B28029FB77F1128E0185D828@XMB-RCD-204.cisco.com> <C8FE6BF1.16D1D%quittek@neclab.eu>
In-Reply-To: <C8FE6BF1.16D1D%quittek@neclab.eu>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.7.0.197]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [eman] Review of draft-norwin-energy-consider-01
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Nov 2010 00:53:31 -0000

Wow, what an excellent reply :) I have nothing to add to that. Thanks Juerg=
en!

NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London =
W3 6BL | Registered in England 2832014=20


> -----Original Message-----
> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of
> Juergen Quittek
> Sent: Montag, 8. November 2010 20:10
> To: Brad Schoening -X (braschoe - Piepeople Consulting, Inc. at Cisco);
> eman mailing list
> Subject: Re: [eman] Review of draft-norwin-energy-consider-01
>=20
> Wow, what a review ...
>=20
> Dear Brad,
>=20
> Below please find some replies on your comments inline.
> Please cool down before you reply again and read carefully what you
> write.
>=20
> Thanks,
>=20
>     Juergen
>=20
>=20
> On 09.11.10 00:30  "Brad Schoening -X (braschoe - Piepeople Consulting,
> Inc.
> at Cisco)" <braschoe@cisco.com> wrote:
>=20
> > This document is inconsistent with the EMAN charter and should be
> > tabled or withdrawn.
>=20
> As a general comment since you do not seem to be familiar with the
> IETF:
> Internet drafts are preferred means to contribute discussion items and
> opinions to the IETF. Asking someone to withdraw a draft is comparable
> to asking someone to withdraw her or his opinion. This is not what we
> do in the IETF, at least as long as it is a technical opinion. Anyway,
> I would not know means for removing a draft from the Internet draft
> repository.
>=20
> More specifically: I am not sure what you mean with "inconsistent with
> the EMAN charter". It is indeed not one of the documents that we
> envision to produce in the eman WG. But so far nobody claimed that this
> draft would match any of the envisioned drafts. In contrary, Bruce
> stated in his message on this draft that this document should "reflect
> conclusions", "clarify issues" and "drive decisions". No one is talking
> about making it an RFC.
> Please find and read Bruce's announcement in the eman mailing list
> archive at http://www.ietf.org/mail-
> archive/web/eman/current/msg00071.html
>=20
> >               It is deeply flawed in several areas.
>=20
> I don't see that it even slightly flawed. Please see my replies below
> to all issues that you consider to be a flaw.
>=20
> >                                                     First, it ignores
> > the basic concepts of SNMP MIB management.
>=20
> You are right in the sense that it ignores SNMP by not mentioning it.
> But that is all ignorance I can find. Nothing in this document is in
> conflict with any concept of SNMP.
>=20
> >                                            Secondly, without
> > explaining why, it ought right opposes the power models presented in
> > several widely used standards such as ACPI,  DMTF's Power State and
> > IEC 61850.
>=20
> There is no statement opposing any other standard. None of the draft we
> have received for eman uses exactly ACPI or DMTF (see my next comment
> below).
> They don't even argue why they don't do so. Are they all deeply flawed?
>=20
> > These three standards for power management are well established and
> > supported on millions of devices.
> >
> > *         The ACPI standard for CPU power management was released in
> > 1996 and  is ubiquitous today.  It defines seven power levels.
>=20
> So far, none of the existing draft suggested using exactly the ACPI
> model for power states. draft-claise-power-management-arch-02 is close
> to ACPI, but it compresses the three stage model of ACPI (G,S,P) into a
> single stage model of 12 power states. No other document that I have
> seen for eman suggests ignoring ACPI or does not provides means for
> supporting it. Still, the existing drafts differ in how far they limit
> themselves to ACPI that was defined specifically for PCs.
>=20
> > *         IEC 61850 is supported by utilities worldwide and power
> > equipment  manufacturers.   IEC 61850 has an extensive Common
> > Information Model (CIM) that is the basis for many smart grid
> standards.
>=20
> This is correct. Where do you see the draft you have reviewed opposing
> IEC 61850?
>=20
> > *          The DMTF Power State Management Profile was adopted in
> 2008
> > and defines an information model over web services.  It defines six
> > power levels and aligns them with the ACPI power levels.
>=20
> The DMTF has only 6 power states, 5 of them non-operational. They
> merged all operational power states into a single one: "on". This way
> it deviates from ACPI providing means for several more states. It looks
> like Bruce's and Rolf's draft is going into the same direction.
>=20
> BTW, so far none of the drafts contributing to eman has suggested to
> adopt the DMTF model of six power states although the DMTF focusing on
> network management is much closer to the IETF network management issues
> than ACPI focusing on PC motherboards.
>=20
> > Below are some detailed comments, but my view is that this document
> > does nothing to advance the charter of the working group and will be
> a
> > distraction.  Instead we should focus on furthering the  existing
> > drafts
> >
> > http://tools.ietf.org/html/draft-quittek-power-mib-02
> >
> > http://tools.ietf.org/html/draft-parello-eman-energy-aware-mib-00
> >
> > http://ietfreport.isoc.org/all-ids/draft-claise-energy-monitoring-
> mib-
> > 06
> > .txt
>=20
> These are all MIB modules. Right, they are on the eman charter. But as
> well on the charter are drafts on requirements, framework, and
> applicability.
> I think the draft you reviewed is much more related to these three
> drafts than to the one you refer to.
>=20
> > --------------------------------------------------
> >
> > 3. "Scope of Devices" section seems to misunderstand the nature of
> SNMP.
> > Only devices with a network connection AND a SNMP agent can implement
> > these MIBs.
>=20
> I do not see any relation between this section and SNMP at all. It
> definitely does not mention MIBs or SNMP. Consequently, I cannot detect
> any misunderstanding of SNMP. Are you really referring to this section
> or do you have another one in mind?
>=20
> > 4.1. The 'Terminology' section on power states don't align with
> > existing standards for networked equipment (DMTF and ACPI).  The
> > authors need to clarify why they believe these pre-existing standards
> > are in error or not applicable.
>=20
> The drafts argues for introducing "power state categories" on, off, and
> sleep. I see not problem with mapping power states defined by DMTF,
> ACPI or other bodies to these categories. Do you?
>=20
> But yes, I agree that if we adopt this proposal we should elaborate on
> the mapping between these categories and the power states defined by
> other bodies.
>=20
> > 5.1. Control "Device Considerations" also doesn't seem to understand
> > how SNMP management works " We should not forbid power state
> > management of devices that is done externally/centrally.  Today,
> > centralized management is the norm with SNMP.
>=20
> There is no statement forbidding anything in this short section.
> Particularly, I see no indication of anyone misunderstanding SNMP.
> After working with SNMP for more than 10 years now and after editing a
> few standard MIB modules I still cannot see your point. Can you help me
> seeing it?
>=20
> > Also, the authors need to explain how this idea relates to the
> current
> > marketplace of existing devices that in general are externally
> > controlled and only occasionally have distributed intelligence.
>=20
> Good point. But you are probably aware that, for example, for mobile
> access networks so-called "Self-Organizing Networks" (SON) for self-
> management of base stations is already included in 3GPP standards. And
> energy management functions is the next application area for SON.
>=20
> > 5.2 The comment about URL's seems ignorant of SysObjectID and not
> > relevant to the EMAN charter
>=20
> Maybe. But so far, I do not consider the identification of energy
> consumers being solved by the eman WG. Proposals are still welcome.
> Whether the eman WG or another WG will solve this problem is to be
> discussed.
>=20
> > 5.3 For "NMS Considerations", the authors need to clarify how this
> > relates to existing energy management systems and existing standards
> > such as IEC 61850 that define interval measurements.
>=20
> Good point. IEC 61850 is important and should not be ignored.
>=20
> > 5.7 "For the device power state, the following information is
> considered
> > to be relevant"...   This doesn't reference any existing standards
> and
> > is therefore largely irrelevant.
>=20
> A very strange argument. Issues not covered already by existing
> standards should not be dealt with by the IETF?
>=20
> > 5.8 "Devices can report power for another device only if they are the
> >
> > entity providing the power"  This would rule out managing PC's which
> > typically don't have a SNMP agent.   We probably don't want to forbid
> > this.
>=20
> No, it rules out PCs that do not report their own power consumption. If
> no device is connected to the PCs power line then the PC has to report
> power on its own, because no other device will know its current power.
> This is quite obvious. But I agree with you, that the authors should
> think about including relaying of information from such PCs into their
> considerations.
>=20
> > 6.o "Use Case: A house... A vehicle"  This further ignores basics
> > about SNMP.  Existing use cases for SNMP are not homes or vehicles.
>=20
> You talk about "basics". Do you claim that a "basic" property of SNMP
> is that it cannot be applied in homes?
>=20
> Let's try to be more constructive next time.
>=20
>     Juergen
>=20
>=20
> > Brad Schoening
> > Consultant
> > Product Development
> > braschoe@cisco.com <mailto:braschoe@cisco.com>
> > Phone: +1 408 424 0363
> > Mobile: +1 917 304 7190
> >
> > For corporate legal information go to:
> > http://www.cisco.com/web/about/doing_business/legal/cri/index.html
> > <http://www.cisco.com/web/about/doing_business/legal/cri/index.html>
> >
> > _______________________________________________
> > eman mailing list
> > eman@ietf.org
> > https://www.ietf.org/mailman/listinfo/eman

From bnordman@lbl.gov  Mon Nov  8 17:47:47 2010
Return-Path: <bnordman@lbl.gov>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0A5BF3A68A9 for <eman@core3.amsl.com>; Mon,  8 Nov 2010 17:47:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.527
X-Spam-Level: 
X-Spam-Status: No, score=-5.527 tagged_above=-999 required=5 tests=[AWL=0.449,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RUj74YUrW1o7 for <eman@core3.amsl.com>; Mon,  8 Nov 2010 17:47:20 -0800 (PST)
Received: from ironport1.lbl.gov (ironport1.lbl.gov [128.3.41.47]) by core3.amsl.com (Postfix) with ESMTP id 7D7973A67EC for <eman@ietf.org>; Mon,  8 Nov 2010 17:47:11 -0800 (PST)
X-Ironport-SBRS: 4.4
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AucBAC822EzRVdQ0kGdsb2JhbACBbpgfAYgHCBUBAQEBCQkMBxEDH4glmXmaa4JyGYI9BIRWhX8
X-IronPort-AV: E=Sophos;i="4.59,172,1288594800"; d="scan'208";a="136406850"
Received: from mail-vw0-f52.google.com ([209.85.212.52]) by ironport1.lbl.gov with ESMTP; 08 Nov 2010 17:47:33 -0800
Received: by vws20 with SMTP id 20so779984vws.39 for <eman@ietf.org>; Mon, 08 Nov 2010 17:47:32 -0800 (PST)
MIME-Version: 1.0
Received: by 10.224.195.1 with SMTP id ea1mr2088113qab.304.1289267252590; Mon, 08 Nov 2010 17:47:32 -0800 (PST)
Received: by 10.229.105.8 with HTTP; Mon, 8 Nov 2010 17:47:32 -0800 (PST)
In-Reply-To: <E9B25823FA871E4AA9EDA7B163E5D8A903503FAF@XMB-RCD-106.cisco.com>
References: <AANLkTikFy7hzFSFtQonWZRXe_WAMbpZLLAGWrNjOVcFw@mail.gmail.com> <68FBE0F3CE97264395875AC1C468F22C514A74@mail03.cyberswitching.local> <E9B25823FA871E4AA9EDA7B163E5D8A903503FAF@XMB-RCD-106.cisco.com>
Date: Tue, 9 Nov 2010 09:47:32 +0800
Message-ID: <AANLkTikNxt5db2nG1d8ML3EGJt5wkBnzT8rwN3RiN8Tj@mail.gmail.com>
From: Bruce Nordman <bnordman@lbl.gov>
To: "Mouli Chandramouli (moulchan)" <moulchan@cisco.com>
Content-Type: multipart/alternative; boundary=20cf300fab819c7d1b049494ecfd
Cc: eman@ietf.org
Subject: Re: [eman] Review of draft-norwin-energy-consider-01
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Nov 2010 01:47:48 -0000

--20cf300fab819c7d1b049494ecfd
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

My comments inline below.

On Mon, Nov 8, 2010 at 3:02 PM, Mouli Chandramouli (moulchan) <
moulchan@cisco.com> wrote:

>  Hello,
>
> Here are my comments on norwin-energy-consider-01.
>
> 1.  Section 3 - Scope of energy management is already covered in
> requirements draft. There are no additional requirements in this draft.
>
There are differences.  I would be happy to provide proposed edits to
the requirements draft to harmonize the two.

> 2.  Section 4 =96 Terminology - The purpose is to have common terminology
> understood by all =96 I agree this is import and is sort of similar to th=
e
> work in other WG; for e.g.
> http://tools.ietf.org/html/draft-ietf-roll-terminology-04  for RPL.
>
If Terminology is the focus, then this draft should explain/clarify lot of
> other commonly used terminology =96 perhaps, from the basics =96 what is =
energy,
> what is power, devices,  what are the methods of power/energy measurement=
,
> then moving on to monitoring, power states, configuration  =85.
>
Thank you for the reference.  Which draft would a terminology section
 be added to?

>  In terms of power states, my thought is it will take some time to evolve
> to precise definitions for the devices. It may be useful if we can focus =
on
> the devices in consideration - network devices, devices attached to the
> network;  building devices and then perhaps, we can converge on this
> discussion soon.
>
The key to me is that the more power states that are defined, the more that
this becomes product-dependent and implementation-dependent, and the
power state becomes a proxy for other characteristics.  An alternative is t=
o
simply report the other characteristic directly, and thus relax the need fo=
r
many power states.  I do agree that a listing of relevant states for variou=
s
classes of devices would be highly informative.  For a past example of this=
,
see:

http://www.energy.ca.gov/publications/displayOneReport.php?pubNum=3DCEC-500=
-2008-035
On page 21 (page 40 of the PDF), there is a table of power states for
various devices, and average power levels.  This just for illustration.

>  I do not agree Power Levels should be equivalent to measured value of
> power.
>
My concern is that in many audiences, particularly for energy contexts, the
term "power level" will be interpreted as the numeric level in watts.  If w=
e
use
the same term to mean something else, confusion will result.

> 3.  Section 5.1 Control  - This section calls for distributed control
> instead of restricting to policy based control only. This is a valid and
> interesting point to be considered.
>
Facilitating distributed control (and most important, hybrids of central an=
d
distributed)
should have minimal impact on eman.  I think only one feature is required
for distributed
control (though some should be optional as not needed for the distributed
case) -- the
concept of a named electricity domain.

>     Section 5.2 - Identity - calls for recognizing a Universal Product Co=
de
> (UPC) and discovering if the device is a TV.  Firstly, this requires that
> TV, MicroWave has a network connection (IPV6, 6lowPAN, ...). Protocols
> developed in WG such CORE can be be used in that scenario. Refer to
> http://tools.ietf.org/html/rfc5826
>
Goal here is for IP-connected devices.  About 1/3 of TVs sold this year in
the U.S. are
to have IP connections, and the share will certainly rise quickly.  UPC is =
a
possible solution
for illustration.   The CORE work seems very important, but designed for
specific application
contexts.  EMAN is not context-specific so the mechanism needs to be
generic.

>  Section 5.3 - NMS considerations =96 This section the describes how NMS
> would work for energy management.
> Section 5.6 =96 Power considerations - There is an interesting point on p=
ower
> source - internal or external - (powered by outlet of powered by battery)=
. I
> think this can be useful.
>
>     Section 5.7 =96 Power state monitoring =96 this material is covered i=
n the
> requirements doc.
>
The goal here was to define basic functionalities that all devices should
support, to distinguish
those from optional features.

>     Section 5.8 - Use cases =96 There many use cases presented in the
> requirements doc.  I am not sure if the use case on =96 Vehicles is relev=
ant
> to energy monitoring =96 Vehicle energy is fuel or battery ?
>
Only electricity use, principally for non-motive-power consumption, though
nothing should
be excluded.  Vehicles have long provided power to both built-in and
dynamically added
devices, just as other building types do.  Regardless of motive power,
vehicles can have
high costs for on-board power (I've seen $1/kWh as typical for the
U.S.--presumably higher
in many other countries) as well as frequent times of constrained capacity,
so monitoring
and controlling these loads is key to ensure good user experience.

> 4.  Section 7 - Outstanding questions - Units of measurement - I thought
> this question was settled and there is rough consensus on the IEC
> measurement model ?
>
Does that specify J or Wh as the basic unit of energy for reporting?
Wh is not an SI unit but certainly much more common for electricity use.
I think we need to explicitly compare the uses the IEC standard is
intended for and compare it to ours.  There is another IEC standard,
62301 on Standby Power, that is also quite relevant for measurement
(though it does not speak to the Wh or J question as it focuses on
power values, not energy).

>                                         Multiple power sources =96is an
> interesting point.
>
One we cannot ignore, even if we don't immediately address.

>
>
>
>
> In conclusion, this draft is a combination of some requirements, some
> terminology, and some open issues.
>
>
>
> Thanks
>
Thank you,

--Bruce

> Mouli
>
>
>
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman
>
>


--=20
*Bruce Nordman*
Lawrence Berkeley National Laboratory
eetd.lbl.gov/ea/nordman
BNordman@LBL.gov
510-486-7089
m: 510-501-7943

--20cf300fab819c7d1b049494ecfd
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

My comments inline below.<br><br><div class=3D"gmail_quote">On Mon, Nov 8, =
2010 at 3:02 PM, Mouli Chandramouli (moulchan) <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:moulchan@cisco.com">moulchan@cisco.com</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; bord=
er-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">









<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US">

<div>

<p>Hello,</p>



<p>Here are my comments on norwin-energy-consider-01.</p>



<p>1.=A0 Section 3 - Scope of energy management is
already covered in requirements draft. There are no additional requirements=
 in
this draft. </p></div></div></blockquote><div>There are differences.=A0 I w=
ould be happy to provide proposed edits to<br>the requirements draft to har=
monize the two. <br></div><blockquote class=3D"gmail_quote" style=3D"margin=
: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-lef=
t: 1ex;">
<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US"><div>



<p>2.=A0 Section 4 =96 Terminology - The purpose is
to have common terminology understood by all =96 I agree this is import and
is sort of similar to the work in other WG; for e.g. =A0=A0<a href=3D"http:=
//tools.ietf.org/html/draft-ietf-roll-terminology-04" target=3D"_blank">htt=
p://tools.ietf.org/html/draft-ietf-roll-terminology-04</a>=A0
for RPL. <br></p></div></div></blockquote><blockquote class=3D"gmail_quote"=
 style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 2=
04); padding-left: 1ex;"><div link=3D"blue" vlink=3D"purple" lang=3D"EN-US"=
><div>


<p>If Terminology is the focus, then this draft should
explain/clarify lot of other commonly used terminology =96 perhaps, from
the basics =96 what is energy, what is power, devices,=A0 what are the
methods of power/energy measurement, then moving on to monitoring, power
states, configuration =A0=85.</p></div></div></blockquote><div>Thank you fo=
r the reference.=A0 Which draft would a terminology section<br>
=A0be added to? <br></div><blockquote class=3D"gmail_quote" style=3D"margin=
: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-lef=
t: 1ex;"><div link=3D"blue" vlink=3D"purple" lang=3D"EN-US"><div>



<p>=A0In terms of power states, my thought is it will take some
time to evolve to precise definitions for the devices. It may be useful if =
we
can focus on the devices in consideration - network devices, devices attach=
ed
to the network;=A0 building devices and then perhaps, we can converge on
this discussion soon. </p></div></div></blockquote><div>The key to me is th=
at the more power states that are defined, the more that<br>this becomes pr=
oduct-dependent and implementation-dependent, and the<br>power state become=
s a proxy for other characteristics.=A0 An alternative is to<br>
simply report the other characteristic directly, and thus relax the need fo=
r<br>many power states.=A0 I do agree that a listing of relevant states for=
 various<br>classes of devices would be highly informative.=A0 For a past e=
xample of this, see:<br>
=A0=A0 <a href=3D"http://www.energy.ca.gov/publications/displayOneReport.ph=
p?pubNum=3DCEC-500-2008-035">http://www.energy.ca.gov/publications/displayO=
neReport.php?pubNum=3DCEC-500-2008-035</a><br>On page 21 (page 40 of the PD=
F), there is a table of power states for <br>
various devices, and average power levels.=A0 This just for illustration. <=
br></div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8=
ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div lin=
k=3D"blue" vlink=3D"purple" lang=3D"EN-US">
<div>



<p>=A0I do not agree Power Levels should be equivalent to measured
value of power. </p></div></div></blockquote><div>My concern is that in man=
y audiences, particularly for energy contexts, the<br>term &quot;power leve=
l&quot; will be interpreted as the numeric level in watts.=A0 If we use<br>
the same term to mean something else, confusion will result. <br></div><blo=
ckquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-le=
ft: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div link=3D"blue" vl=
ink=3D"purple" lang=3D"EN-US">
<div>





<p>3.=A0 Section 5.1 Control=A0 - This section calls
for distributed control instead of restricting to policy based control only=
.
This is a valid and interesting point to be considered. </p></div></div></b=
lockquote><div>Facilitating distributed control (and most important, hybrid=
s of central and distributed)<br>should have minimal impact on eman.=A0 I t=
hink only one feature is required for distributed<br>
control (though some should be optional as not needed for the distributed c=
ase) -- the<br>concept of a named electricity domain.<br></div><blockquote =
class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px =
solid rgb(204, 204, 204); padding-left: 1ex;">
<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US"><div>



<p>=A0=A0=A0 Section 5.2 - Identity - calls for
recognizing a Universal Product Code (UPC) and discovering if the device is=
 a
TV.=A0 Firstly, this requires that TV, MicroWave has a network connection
(IPV6, 6lowPAN, ...). Protocols developed in WG such CORE can be be used in
that scenario. Refer to=A0 <a href=3D"http://tools.ietf.org/html/rfc5826" t=
arget=3D"_blank">http://tools.ietf.org/html/rfc5826</a></p></div></div></bl=
ockquote><div>Goal here is for IP-connected devices.=A0 About 1/3 of TVs so=
ld this year in the U.S. are<br>
to have IP connections, and the share will certainly rise quickly.=A0 UPC i=
s a possible solution<br>for illustration.=A0=A0 The CORE work seems very i=
mportant, but designed for specific application<br>contexts.=A0 EMAN is not=
 context-specific so the mechanism needs to be generic.<br>
</div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex;=
 border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div link=
=3D"blue" vlink=3D"purple" lang=3D"EN-US"><div>



<p>=A0Section 5.3 - NMS considerations =96
This section the describes how NMS would work for energy management. </p> S=
ection 5.6 =96 Power considerations
- There is an interesting point on power source - internal or external -
(powered by outlet of powered by battery). I think this can be useful.=20

<p>=A0=A0=A0 Section 5.7 =96 Power state
monitoring =96 this material is covered in the requirements doc. </p></div>=
</div></blockquote><div>The goal here was to define basic functionalities t=
hat all devices should support, to distinguish<br>those from optional featu=
res. <br>
</div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex;=
 border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div link=
=3D"blue" vlink=3D"purple" lang=3D"EN-US"><div>

<p>=A0=A0=A0 Section 5.8 - Use cases =96 There many
use cases presented in the requirements doc.=A0 I am not sure if the use
case on =96 Vehicles is relevant to energy monitoring =96 Vehicle energy
is fuel or battery ? =A0</p></div></div></blockquote><div>Only electricity =
use, principally for non-motive-power consumption, though nothing should<br=
>be excluded.=A0 Vehicles have long provided power to both built-in and dyn=
amically added<br>
devices, just as other building types do.=A0 Regardless of motive power, ve=
hicles can have<br>high costs for on-board power (I&#39;ve seen $1/kWh as t=
ypical for the U.S.--presumably higher<br>in many other countries) as well =
as frequent times of constrained capacity, so monitoring<br>
and controlling these loads is key to ensure good user experience.<br></div=
><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; bord=
er-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div link=3D"blu=
e" vlink=3D"purple" lang=3D"EN-US">
<div>



<p>4.=A0 Section 7 - Outstanding questions - Units of
measurement - I thought this question was settled and there is rough consen=
sus
on the IEC measurement model ? </p></div></div></blockquote><div>Does that =
specify J or Wh as the basic unit of energy for reporting?<br>Wh is not an =
SI unit but certainly much more common for electricity use.<br>I think we n=
eed to explicitly compare the uses the IEC standard is<br>
intended for and compare it to ours.=A0 There is another IEC standard,<br>6=
2301 on Standby Power, that is also quite relevant for measurement<br>(thou=
gh it does not speak to the Wh or J question as it focuses on<br>power valu=
es, not energy). <br>
</div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex;=
 border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div link=
=3D"blue" vlink=3D"purple" lang=3D"EN-US"><div>

<p>=A0=A0=A0=A0=A0 =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0Multiple
power sources =96is an interesting point. </p></div></div></blockquote><div=
>One we cannot ignore, even if we don&#39;t immediately address. <br></div>=
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div link=3D"blue" vlink=3D"purple" lang=3D"EN-US"><div>

<p>=A0</p>

<p>=A0</p>

<p>In conclusion, this draft is a combination of some
requirements, some terminology, and some open issues. </p>

<p>=A0</p>

<p>Thanks</p></div></div></blockquote><div>Thank you,<br><br>--Bruce <br></=
div><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; b=
order-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div link=3D"=
blue" vlink=3D"purple" lang=3D"EN-US">
<div>

<p>Mouli</p>

<p class=3D"MsoNormal"><span style=3D"font-size: 11pt; color: rgb(31, 73, 1=
25);">=A0</span></p>

</div>

</div>


<br>_______________________________________________<br>
eman mailing list<br>
<a href=3D"mailto:eman@ietf.org">eman@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/eman" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/eman</a><br>
<br></blockquote></div><br><br clear=3D"all"><br>-- <br><font size=3D"4"><b=
>Bruce Nordman</b></font><br><span style=3D"color: rgb(0, 0, 153);">Lawrenc=
e Berkeley National Laboratory</span><br><a href=3D"http://eetd.lbl.gov/ea/=
nordman" target=3D"_blank">eetd.lbl.gov/ea/nordman</a><br>
BNordman@LBL.gov<br>510-486-7089<br>m: 510-501-7943<br><br>

--20cf300fab819c7d1b049494ecfd--

From braschoe@cisco.com  Mon Nov  8 17:55:35 2010
Return-Path: <braschoe@cisco.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 85B7E3A68EF for <eman@core3.amsl.com>; Mon,  8 Nov 2010 17:55:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.933
X-Spam-Level: 
X-Spam-Status: No, score=-9.933 tagged_above=-999 required=5 tests=[AWL=0.351,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Jhipd17PtIDY for <eman@core3.amsl.com>; Mon,  8 Nov 2010 17:55:34 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 96E373A6898 for <eman@ietf.org>; Mon,  8 Nov 2010 17:55:33 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAMM42EytJXG8/2dsb2JhbACiHHGhBZt2AoMCBwGCPASEWIkN
X-IronPort-AV: E=Sophos;i="4.59,172,1288569600"; d="scan'208";a="179984770"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rtp-iport-2.cisco.com with ESMTP; 09 Nov 2010 01:55:55 +0000
Received: from xbh-rcd-201.cisco.com (xbh-rcd-201.cisco.com [72.163.62.200]) by rcdn-core2-1.cisco.com (8.14.3/8.14.3) with ESMTP id oA91ttKZ021039;  Tue, 9 Nov 2010 01:55:55 GMT
Received: from xmb-rcd-204.cisco.com ([72.163.62.211]) by xbh-rcd-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 8 Nov 2010 19:55:55 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 8 Nov 2010 19:55:53 -0600
Message-ID: <308743659A7CB142B28029FB77F1128E018FF5CD@XMB-RCD-204.cisco.com>
In-Reply-To: <C8FE8A5C.16D31%quittek@neclab.eu>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [eman]  Review of draft-norwin-energy-consider-01
Thread-Index: Act/Yk5gIDthfJvVQb+n7BqkZg+aCQAFi4HXAAHeJzAAAqoz1wAIcuqg
References: <308743659A7CB142B28029FB77F1128E018FF3FE@XMB-RCD-204.cisco.com> <C8FE8A5C.16D31%quittek@neclab.eu>
From: "Brad Schoening -X (braschoe - Piepeople Consulting, Inc. at Cisco)" <braschoe@cisco.com>
To: "Juergen Quittek" <Quittek@neclab.eu>, "eman mailing list" <eman@ietf.org>
X-OriginalArrivalTime: 09 Nov 2010 01:55:55.0706 (UTC) FILETIME=[3F3C81A0:01CB7FB1]
Subject: Re: [eman] Review of draft-norwin-energy-consider-01
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Nov 2010 01:55:35 -0000

Juergen,

Looking at the big picture, if we agree that the EMAN working group must
take into consideration the existing standards for energy management,
then, yes, I'd say we're in basic agreement.  Bruce and Rolf's document
did not do that.

You stated the following which gives me confidence we're on the same
page...

	"Good point. IEC 61850 is important and should not be ignored."

	"But yes, I agree that if we adopt this proposal we should
elaborate on the mapping=20
	between these categories and the power states defined by other
bodies."

	"No other document that I have seen for eman suggests ignoring
ACPI or does not=20
	provides means for supporting it"


-----Original Message-----
From: Juergen Quittek [mailto:Quittek@neclab.eu]=20
Sent: Monday, November 08, 2010 4:20 PM
To: Brad Schoening -X (braschoe - Piepeople Consulting,Inc. at Cisco);
eman mailing list
Subject: Re: [eman] Review of draft-norwin-energy-consider-01

Hi Brad,

Wow, again.=20

I objected almost every point you made and you see us in basic
agreement.
Are you now fine with the draft that you reviewed?
No problems with it anymore?

Great!

    Juergen


On 09.11.10 04:19  "Brad Schoening -X (braschoe - Piepeople
Consulting,Inc.
at Cisco)" <braschoe@cisco.com> wrote:

> Juergen,
>=20
> It seems like we're in basic agreement here, that drafts and comments
> should take into account existing standards.  Then, we can have an
> honest debate about which standards are most relevant to our work.
>=20
> -----Original Message-----
> From: Juergen Quittek [mailto:Quittek@neclab.eu]
> Sent: Monday, November 08, 2010 2:10 PM
> To: Brad Schoening -X (braschoe - Piepeople Consulting,Inc. at Cisco);
> eman mailing list
> Subject: Re: [eman] Review of draft-norwin-energy-consider-01
>=20
> Wow, what a review ...
>=20
> Dear Brad,
>=20
> Below please find some replies on your comments inline.
> Please cool down before you reply again and read carefully what you
> write.
>=20
> Thanks,
>=20
>     Juergen
>=20
>=20
> On 09.11.10 00:30  "Brad Schoening -X (braschoe - Piepeople
Consulting,
> Inc.
> at Cisco)" <braschoe@cisco.com> wrote:
>=20
>> This document is inconsistent with the EMAN charter and should be
> tabled
>> or withdrawn.=20
>=20
> As a general comment since you do not seem to be familiar with the
IETF:
> Internet drafts are preferred means to contribute discussion items and
> opinions to the IETF. Asking someone to withdraw a draft is comparable
> to
> asking someone to withdraw her or his opinion. This is not what we do
in
> the
> IETF, at least as long as it is a technical opinion. Anyway, I would
not
> know means for removing a draft from the Internet draft repository.
>=20
> More specifically: I am not sure what you mean with "inconsistent with
> the
> EMAN charter". It is indeed not one of the documents that we envision
to
> produce in the eman WG. But so far nobody claimed that this draft
would
> match any of the envisioned drafts. In contrary, Bruce stated in his
> message
> on this draft that this document should "reflect conclusions",
"clarify
> issues" and "drive decisions". No one is talking about making it an
RFC.
> Please find and read Bruce's announcement in the eman mailing list
> archive
> at http://www.ietf.org/mail-archive/web/eman/current/msg00071.html
>=20
>>               It is deeply flawed in several areas.
>=20
> I don't see that it even slightly flawed. Please see my replies below
to
> all
> issues that you consider to be a flaw.
>=20
>>                                                     First, it ignores
>> the basic concepts of SNMP MIB management.
>=20
> You are right in the sense that it ignores SNMP by not mentioning it.
> But
> that is all ignorance I can find. Nothing in this document is in
> conflict
> with any concept of SNMP.
>=20
>>                                            Secondly, without
>> explaining why, it ought right opposes the power models presented in
>> several widely used standards such as ACPI,  DMTF's Power State and
> IEC
>> 61850.=20
>=20
> There is no statement opposing any other standard. None of the draft
we
> have
> received for eman uses exactly ACPI or DMTF (see my next comment
below).
> They don't even argue why they don't do so. Are they all deeply
flawed?
>=20
>> These three standards for power management are well established and
>> supported on millions of devices.
>>=20
>> *         The ACPI standard for CPU power management was released in
>> 1996 and  is ubiquitous today.  It defines seven power levels.
>=20
> So far, none of the existing draft suggested using exactly the ACPI
> model
> for power states. draft-claise-power-management-arch-02 is close to
> ACPI,
> but it compresses the three stage model of ACPI (G,S,P) into a single
> stage
> model of 12 power states. No other document that I have seen for eman
> suggests ignoring ACPI or does not provides means for supporting it.
> Still,
> the existing drafts differ in how far they limit themselves to ACPI
that
> was
> defined specifically for PCs.
>=20
>> *         IEC 61850 is supported by utilities worldwide and power
>> equipment  manufacturers.   IEC 61850 has an extensive Common
>> Information Model (CIM) that is the basis for many smart grid
> standards.
>=20
> This is correct. Where do you see the draft you have reviewed opposing
> IEC 61850?
>=20
>> *          The DMTF Power State Management Profile was adopted in
2008
>> and defines an information model over web services.  It defines six
>> power levels and aligns them with the ACPI power levels.
>=20
> The DMTF has only 6 power states, 5 of them non-operational. They
merged
> all
> operational power states into a single one: "on". This way it deviates
> from
> ACPI providing means for several more states. It looks like Bruce's
and
> Rolf's draft is going into the same direction.
>=20
> BTW, so far none of the drafts contributing to eman has suggested to
> adopt
> the DMTF model of six power states although the DMTF focusing on
network
> management is much closer to the IETF network management issues than
> ACPI
> focusing on PC motherboards.
>=20
>> Below are some detailed comments, but my view is that this document
> does
>> nothing to advance the charter of the working group and will be a
>> distraction.  Instead we should focus on furthering the  existing
> drafts
>>=20
>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>>=20
>> http://tools.ietf.org/html/draft-parello-eman-energy-aware-mib-00
>>=20
>>=20
>
http://ietfreport.isoc.org/all-ids/draft-claise-energy-monitoring-mib-06
>> .txt
>=20
> These are all MIB modules. Right, they are on the eman charter. But as
> well
> on the charter are drafts on requirements, framework, and
applicability.
> I think the draft you reviewed is much more related to these three
> drafts
> than to the one you refer to.
> =20
>> --------------------------------------------------
>>=20
>> 3. "Scope of Devices" section seems to misunderstand the nature of
> SNMP.
>> Only devices with a network connection AND a SNMP agent can implement
>> these MIBs.
>=20
> I do not see any relation between this section and SNMP at all. It
> definitely does not mention MIBs or SNMP. Consequently, I cannot
detect
> any
> misunderstanding of SNMP. Are you really referring to this section or
do
> you
> have another one in mind?
>=20
>> 4.1. The 'Terminology' section on power states don't align with
> existing
>> standards for networked equipment (DMTF and ACPI).  The authors need
> to
>> clarify why they believe these pre-existing standards are in error or
>> not applicable.
>=20
> The drafts argues for introducing "power state categories" on, off,
and
> sleep. I see not problem with mapping power states defined by DMTF,
ACPI
> or
> other bodies to these categories. Do you?
>=20
> But yes, I agree that if we adopt this proposal we should elaborate on
> the
> mapping between these categories and the power states defined by other
> bodies.
>=20
>> 5.1. Control "Device Considerations" also doesn't seem to understand
> how
>> SNMP management works " We should not forbid power state management
of
>> devices that is done externally/centrally.  Today, centralized
>> management is the norm with SNMP.
>=20
> There is no statement forbidding anything in this short section.
> Particularly, I see no indication of anyone misunderstanding SNMP.
After
> working with SNMP for more than 10 years now and after editing a few
> standard MIB modules I still cannot see your point. Can you help me
> seeing
> it?
>=20
>> Also, the authors need to explain how this idea relates to the
current
>> marketplace of existing devices that in general are externally
>> controlled and only occasionally have distributed intelligence.
>=20
> Good point. But you are probably aware that, for example, for mobile
> access
> networks so-called "Self-Organizing Networks" (SON) for
self-management
> of
> base stations is already included in 3GPP standards. And energy
> management
> functions is the next application area for SON.
>=20
>> 5.2 The comment about URL's seems ignorant of SysObjectID and not
>> relevant to the EMAN charter
>=20
> Maybe. But so far, I do not consider the identification of energy
> consumers
> being solved by the eman WG. Proposals are still welcome. Whether the
> eman
> WG or another WG will solve this problem is to be discussed.
>=20
>> 5.3 For "NMS Considerations", the authors need to clarify how this
>> relates to existing energy management systems and existing standards
>> such as IEC 61850 that define interval measurements.
>=20
> Good point. IEC 61850 is important and should not be ignored.
>=20
>> 5.7 "For the device power state, the following information is
> considered
>> to be relevant"...   This doesn't reference any existing standards
and
>> is therefore largely irrelevant.
>=20
> A very strange argument. Issues not covered already by existing
> standards
> should not be dealt with by the IETF?
>=20
>> 5.8 "Devices can report power for another device only if they are the
>>=20
>> entity providing the power"  This would rule out managing PC's which
>> typically don't have a SNMP agent.   We probably don't want to forbid
>> this.
>=20
> No, it rules out PCs that do not report their own power consumption.
If
> no
> device is connected to the PCs power line then the PC has to report
> power on
> its own, because no other device will know its current power. This is
> quite
> obvious. But I agree with you, that the authors should think about
> including
> relaying of information from such PCs into their considerations.
>=20
>> 6.o "Use Case: A house... A vehicle"  This further ignores basics
> about
>> SNMP.  Existing use cases for SNMP are not homes or vehicles.
>=20
> You talk about "basics". Do you claim that a "basic" property of SNMP
is
> that it cannot be applied in homes?
>=20
> Let's try to be more constructive next time.
>=20
>     Juergen
>=20
>=20
>> Brad Schoening
>> Consultant
>> Product Development
>> braschoe@cisco.com <mailto:braschoe@cisco.com>
>> Phone: +1 408 424 0363
>> Mobile: +1 917 304 7190
>>=20
>> For corporate legal information go to:
>> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>> <http://www.cisco.com/web/about/doing_business/legal/cri/index.html>
>>=20
>> _______________________________________________
>> eman mailing list
>> eman@ietf.org
>> https://www.ietf.org/mailman/listinfo/eman

From bnordman@lbl.gov  Mon Nov  8 18:31:29 2010
Return-Path: <bnordman@lbl.gov>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 608DF28C115 for <eman@core3.amsl.com>; Mon,  8 Nov 2010 18:31:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.102
X-Spam-Level: 
X-Spam-Status: No, score=-4.102 tagged_above=-999 required=5 tests=[AWL=-1.126, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tO0I30vBgElg for <eman@core3.amsl.com>; Mon,  8 Nov 2010 18:31:21 -0800 (PST)
Received: from ironport4.lbl.gov (ironport4.lbl.gov [128.3.41.45]) by core3.amsl.com (Postfix) with ESMTP id E628D3A6A12 for <eman@ietf.org>; Mon,  8 Nov 2010 18:30:56 -0800 (PST)
X-Ironport-SBRS: 4.7
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap0BAG9B2EzRVaC0k2dsb2JhbACBbpgeAYgHCBUBAQEBCQkKCREDH6Ikmm2DBAcBgjwEhFaFfw
X-IronPort-AV: E=Sophos;i="4.59,172,1288594800"; d="scan'208";a="28409109"
Received: from mail-gy0-f180.google.com ([209.85.160.180]) by ironport4.lbl.gov with ESMTP; 08 Nov 2010 18:31:19 -0800
Received: by mail-gy0-f180.google.com with SMTP id 8so3959587gyg.39 for <eman@ietf.org>; Mon, 08 Nov 2010 18:31:19 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.87.13 with SMTP id u13mr5771699qcl.202.1289269879240; Mon, 08 Nov 2010 18:31:19 -0800 (PST)
Received: by 10.229.105.8 with HTTP; Mon, 8 Nov 2010 18:31:19 -0800 (PST)
In-Reply-To: <308743659A7CB142B28029FB77F1128E018FF5CD@XMB-RCD-204.cisco.com>
References: <308743659A7CB142B28029FB77F1128E018FF3FE@XMB-RCD-204.cisco.com> <C8FE8A5C.16D31%quittek@neclab.eu> <308743659A7CB142B28029FB77F1128E018FF5CD@XMB-RCD-204.cisco.com>
Date: Tue, 9 Nov 2010 10:31:19 +0800
Message-ID: <AANLkTinmxX+=8WbRmKOW3FxzNfakfaaA6WvQbJgJXOhP@mail.gmail.com>
From: Bruce Nordman <bnordman@lbl.gov>
To: "Brad Schoening -X (braschoe - Piepeople Consulting, Inc. at Cisco)" <braschoe@cisco.com>
Content-Type: multipart/alternative; boundary=0016364ee0342bf72c04949589db
Cc: eman mailing list <eman@ietf.org>
Subject: Re: [eman] Review of draft-norwin-energy-consider-01
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Nov 2010 02:31:29 -0000

--0016364ee0342bf72c04949589db
Content-Type: text/plain; charset=ISO-8859-1

Brad--

There are MANY potentially relevant standards with definitions of power
states.  ACPI is certainly one of the most important for a certain category
of devices.  Some aspects of ACPI are extremely relevant to eman - some
are not.  While we need to take into account all relevant standards, there
is generally considerable difference between their origins, goals, concerns,
and scopes, and those of eman  -- which is where the "consideration"
process comes in.

I have not read IEC 61850, but the description of it being intended for
substation automation seems to make it at least one step removed from
the eman focus.  I do look forward though to seeing what it has to offer.

The norwin draft was not intended to repeat information already in the
other drafts, so it was not felt necessary to cite the importance of ACPI
(or SNMP or IP for that matter).

--Bruce

On Tue, Nov 9, 2010 at 9:55 AM, Brad Schoening -X (braschoe - Piepeople
Consulting, Inc. at Cisco) <braschoe@cisco.com> wrote:

> Juergen,
>
> Looking at the big picture, if we agree that the EMAN working group must
> take into consideration the existing standards for energy management,
> then, yes, I'd say we're in basic agreement.  Bruce and Rolf's document
> did not do that.
>
> You stated the following which gives me confidence we're on the same
> page...
>
>        "Good point. IEC 61850 is important and should not be ignored."
>
>         "But yes, I agree that if we adopt this proposal we should
> elaborate on the mapping
>        between these categories and the power states defined by other
> bodies."
>
>         "No other document that I have seen for eman suggests ignoring
> ACPI or does not
>        provides means for supporting it"
>
>
>
> --
*Bruce Nordman*
Lawrence Berkeley National Laboratory
eetd.lbl.gov/ea/nordman
BNordman@LBL.gov
510-486-7089
m: 510-501-7943

--0016364ee0342bf72c04949589db
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Brad--<br><br>There are MANY potentially relevant standards with definition=
s of power<br>states.=A0 ACPI is certainly one of the most important for a =
certain category<br>of devices.=A0 Some aspects of ACPI are extremely relev=
ant to eman - some<br>
are not.=A0 While we need to take into account all relevant standards, ther=
e<br>is generally considerable difference between their origins, goals, con=
cerns,<br>and scopes, and those of eman=A0 -- which is where the &quot;cons=
ideration&quot; <br>
process comes in.<br><br>I have not read IEC 61850, but the description of =
it being intended for<br>substation automation seems to make it at least on=
e step removed from<br>the eman focus.=A0 I do look forward though to seein=
g what it has to offer.<br>
<br>The norwin draft was not intended to repeat information already in the<=
br>other drafts, so it was not felt necessary to cite the importance of ACP=
I<br>(or SNMP or IP for that matter).<br><br>--Bruce<br><br><div class=3D"g=
mail_quote">
On Tue, Nov 9, 2010 at 9:55 AM, Brad Schoening -X (braschoe - Piepeople Con=
sulting, Inc. at Cisco) <span dir=3D"ltr">&lt;<a href=3D"mailto:braschoe@ci=
sco.com">braschoe@cisco.com</a>&gt;</span> wrote:<br><blockquote class=3D"g=
mail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(=
204, 204, 204); padding-left: 1ex;">
Juergen,<br>
<br>
Looking at the big picture, if we agree that the EMAN working group must<br=
>
take into consideration the existing standards for energy management,<br>
then, yes, I&#39;d say we&#39;re in basic agreement. =A0Bruce and Rolf&#39;=
s document<br>
did not do that.<br>
<br>
You stated the following which gives me confidence we&#39;re on the same<br=
>
page...<br>
<div class=3D"im"><br>
 =A0 =A0 =A0 =A0&quot;Good point. IEC 61850 is important and should not be =
ignored.&quot;<br>
<br>
</div><div class=3D"im"> =A0 =A0 =A0 =A0&quot;But yes, I agree that if we a=
dopt this proposal we should<br>
elaborate on the mapping<br>
 =A0 =A0 =A0 =A0between these categories and the power states defined by ot=
her<br>
bodies.&quot;<br>
<br>
</div><div class=3D"im"> =A0 =A0 =A0 =A0&quot;No other document that I have=
 seen for eman suggests ignoring<br>
ACPI or does not<br>
 =A0 =A0 =A0 =A0provides means for supporting it&quot;<br>
<br>
<br>
</div><br></blockquote></div>-- <br><font size=3D"4"><b>Bruce Nordman</b></=
font><br><span style=3D"color: rgb(0, 0, 153);">Lawrence Berkeley National =
Laboratory</span><br><a href=3D"http://eetd.lbl.gov/ea/nordman" target=3D"_=
blank">eetd.lbl.gov/ea/nordman</a><br>
BNordman@LBL.gov<br>510-486-7089<br>m: 510-501-7943<br><br>

--0016364ee0342bf72c04949589db--

From bclaise@cisco.com  Mon Nov  8 18:53:45 2010
Return-Path: <bclaise@cisco.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C37A28C176 for <eman@core3.amsl.com>; Mon,  8 Nov 2010 18:53:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.394
X-Spam-Level: 
X-Spam-Status: No, score=-2.394 tagged_above=-999 required=5 tests=[AWL=-0.111, BAYES_00=-2.599, HTML_MESSAGE=0.001, SARE_MILLIONSOF=0.315]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V3DqoKe0kXFI for <eman@core3.amsl.com>; Mon,  8 Nov 2010 18:53:37 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id 6A62B3A6A1A for <eman@ietf.org>; Mon,  8 Nov 2010 18:53:32 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oA92o92S026348 for <eman@ietf.org>; Tue, 9 Nov 2010 03:50:10 +0100 (CET)
Received: from [10.68.17.151] (sin-vpn-client-17-151.cisco.com [10.68.17.151]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oA92nvge012343; Tue, 9 Nov 2010 03:50:02 +0100 (CET)
Message-ID: <4CD8B6D4.80804@cisco.com>
Date: Tue, 09 Nov 2010 10:49:56 +0800
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: "Brad Schoening -X (braschoe - Piepeople Consulting, Inc. at Cisco)" <braschoe@cisco.com>
References: <308743659A7CB142B28029FB77F1128E0185D828@XMB-RCD-204.cisco.com>
In-Reply-To: <308743659A7CB142B28029FB77F1128E0185D828@XMB-RCD-204.cisco.com>
Content-Type: multipart/alternative; boundary="------------090302050508020401040806"
Cc: eman@ietf.org
Subject: Re: [eman] Review of draft-norwin-energy-consider-01
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Nov 2010 02:53:45 -0000

This is a multi-part message in MIME format.
--------------090302050508020401040806
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Brad,

<Working Chair hats on>
Energy Management is a new work area at the IETF.
This implies that there are a couple of a newcomers at the IETF. This is 
a good thing!
Many of us are passionate. This is also a good thing!

"Internet drafts are preferred means to contribute discussion items and 
opinions to the IETF. Asking someone to withdraw a draft is comparable 
to asking someone to withdraw her or his opinion. This is not what we do 
in the IETF, at least as long as it is a technical opinion. Anyway, I 
would not know means for removing a draft from the Internet draft 
repository."
Juergen wrote this, but I could have written that myself

Without abandoning our passion, let's bring back the discussions to 
technical arguments and facts.

If deem useful, Bruce and I are available for any private or public 
discussions (this is valid for anybody in the WG)

</Working Chair hats off>

Regards, Bruce & Benoit.
>
> This document is inconsistent with the EMAN charter and should be 
> tabled or withdrawn.  It is deeply flawed in several areas.  First, it 
> ignores the basic concepts of SNMP MIB management.   Secondly, without 
> explaining why, it ought right opposes the power models presented in 
> several widely used standards such as ACPI,  DMTF's Power State and 
> IEC 61850.
>
> These three standards for power management are well established and 
> supported on millions of devices.
>
> ·The ACPI standard for CPU power management was released in 1996 and 
>  is ubiquitous today.  It defines seven power levels.
>
> ·IEC 61850 is supported by utilities worldwide and power equipment  
> manufacturers.   IEC 61850 has an extensive Common Information Model 
> (CIM) that is the basis for many smart grid standards.
>
> · The DMTF Power State Management Profile was adopted in 2008 and 
> defines an information model over web services.  It defines six power 
> levels and aligns them with the ACPI power levels.
>
> Below are some detailed comments, but my view is that this document 
> does nothing to advance the charter of the working group and will be a 
> distraction.  Instead we should focus on furthering the  existing drafts
>
> http://tools.ietf.org/html/draft-quittek-power-mib-02
>
> http://tools.ietf.org/html/draft-parello-eman-energy-aware-mib-00
>
> http://ietfreport.isoc.org/all-ids/draft-claise-energy-monitoring-mib-06.txt
>
> --------------------------------------------------
>
> 3. "Scope of Devices" section seems to misunderstand the nature of 
> SNMP.   Only devices with a network connection AND a SNMP agent can 
> implement these MIBs.
>
> 4.1. The 'Terminology' section on power states don't align with 
> existing standards for networked equipment (DMTF and ACPI).  The 
> authors need to clarify why they believe these pre-existing standards 
> are in error or not applicable.
>
> 5.1. Control "Device Considerations" also doesn't seem to understand 
> how SNMP management works " We should not forbid power state 
> management of devices that is done externally/centrally.  Today, 
> centralized management is the norm with SNMP.
>
> Also, the authors need to explain how this idea relates to the current 
> marketplace of existing devices that in general are externally 
> controlled and only occasionally have distributed intelligence.
>
> 5.2 The comment about URL's seems ignorant of SysObjectID and not 
> relevant to the EMAN charter
>
> 5.3 For "NMS Considerations", the authors need to clarify how this 
> relates to existing energy management systems and existing standards 
> such as IEC 61850 that define interval measurements.
>
> 5.7 "For the device power state, the following information is 
> considered to be relevant"...   This doesn't reference any existing 
> standards and is therefore largely irrelevant.
>
> 5.8 "Devices can report power for another device only if they are the
>
> entity providing the power"  This would rule out managing PC's which 
> typically don't have a SNMP agent.   We probably don't want to forbid 
> this.
>
> 6.o "Use Case: A house... A vehicle"  This further ignores basics 
> about SNMP.  Existing use cases for SNMP are not homes or vehicles.
>
> http://www.cisco.com/swa/i/logo.gif
>
> *Brad Schoening*
> *Consultant*
> *Product Development*
> braschoe@cisco.com <mailto:braschoe@cisco.com>
> Phone: *+1 408 424 0363*
> Mobile: *+1 917 304 7190***
>
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>
> 	
> 	
>
>
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman


--------------090302050508020401040806
Content-Type: multipart/related;
 boundary="------------060200050609050002060601"


--------------060200050609050002060601
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#ffffff">
    Brad,<br>
    <br>
    &lt;Working Chair hats on&gt;<br>
    Energy Management is a new work area at the IETF. <br>
    This implies that there are a couple of a newcomers at the IETF.
    This is a good thing!<br>
    Many of us are passionate. This is also a good thing!<br>
    <br>
    "Internet drafts are preferred means to contribute discussion items
    and opinions to the IETF. Asking someone to withdraw a draft is
    comparable to asking someone to withdraw her or his opinion. This is
    not what we do in the IETF, at least as long as it is a technical
    opinion. Anyway, I would not know means for removing a draft from
    the Internet draft repository."<br>
    Juergen wrote this, but I could have written that myself<br>
    <br>
    Without abandoning our passion, let's bring back the discussions to
    technical arguments and facts.<br>
    <br>
    If deem useful, Bruce and I are available for any private or public
    discussions (this is valid for anybody in the WG)<br>
    <br>
    &lt;/Working Chair hats off&gt;<br>
    <br>
    Regards, Bruce &amp; Benoit.<br>
    <blockquote
cite="mid:308743659A7CB142B28029FB77F1128E0185D828@XMB-RCD-204.cisco.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="Generator" content="Microsoft Word 12 (filtered
        medium)">
      <!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
      <style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
 /* List Definitions */
 @list l0
	{mso-list-id:1157647374;
	mso-list-type:hybrid;
	mso-list-template-ids:430717940 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style><!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext="edit" spidmax="2050" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext="edit">
  <o:idmap v:ext="edit" data="1" />
 </o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal">This document is inconsistent with the EMAN
          charter and
          should be tabled or withdrawn.&nbsp; It is deeply flawed in several
          areas. &nbsp;First,
          it ignores the basic concepts of SNMP MIB management.&nbsp;&nbsp;
          Secondly, without
          explaining why, it ought right opposes the power models
          presented in several widely
          used standards such as ACPI, &nbsp;DMTF&#8217;s Power State and IEC
          61850. <o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">These three standards for power management
          are well established
          and supported on millions of devices.&nbsp; <o:p></o:p></p>
        <p class="MsoListParagraph" style="text-indent: -0.25in;"><!--[if !supportLists]--><span
            style="font-family: Symbol;"><span style="">&middot;<span
                style="font: 7pt &quot;Times New Roman&quot;;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
              </span></span></span><!--[endif]-->The ACPI standard for
          CPU power management was released
          in 1996 and &nbsp;is ubiquitous today.&nbsp; It defines seven power
          levels.&nbsp; <o:p></o:p></p>
        <p class="MsoListParagraph" style="text-indent: -0.25in;"><!--[if !supportLists]--><span
            style="font-family: Symbol;"><span style="">&middot;<span
                style="font: 7pt &quot;Times New Roman&quot;;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
              </span></span></span><!--[endif]-->IEC 61850 is supported
          by utilities worldwide and
          power equipment&nbsp; manufacturers.&nbsp;&nbsp; IEC 61850 has an extensive
          Common Information Model (CIM) that is the basis for many
          smart grid standards.&nbsp;
          <o:p></o:p></p>
        <p class="MsoListParagraph" style="text-indent: -0.25in;"><!--[if !supportLists]--><span
            style="font-family: Symbol;"><span style="">&middot;<span
                style="font: 7pt &quot;Times New Roman&quot;;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
              </span></span></span><!--[endif]-->&nbsp;The DMTF Power State
          Management Profile was
          adopted in 2008 and defines an information model over web
          services.&nbsp; It
          defines six power levels and aligns them with the ACPI power
          levels. <o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">Below are some detailed comments, but my
          view is that this document
          does nothing to advance the charter of the working group and
          will be a
          distraction.&nbsp; Instead we should focus on furthering the
          &nbsp;existing
          drafts <o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal" style="text-indent: 0.5in;"><a
            moz-do-not-send="true"
            href="http://tools.ietf.org/html/draft-quittek-power-mib-02">http://tools.ietf.org/html/draft-quittek-power-mib-02</a><o:p></o:p></p>
        <p class="MsoNormal" style="text-indent: 0.5in;"><a
            moz-do-not-send="true"
            href="http://tools.ietf.org/html/draft-parello-eman-energy-aware-mib-00">http://tools.ietf.org/html/draft-parello-eman-energy-aware-mib-00</a><o:p></o:p></p>
        <p class="MsoNormal" style="text-indent: 0.5in;"><a
            moz-do-not-send="true"
href="http://ietfreport.isoc.org/all-ids/draft-claise-energy-monitoring-mib-06.txt">http://ietfreport.isoc.org/all-ids/draft-claise-energy-monitoring-mib-06.txt</a><o:p></o:p></p>
        <p class="MsoNormal" style="text-indent: 0.5in;"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal">--------------------------------------------------<o:p></o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal" style=""><span style="font-size: 10.5pt;
            font-family: Consolas;">3. "Scope of Devices" section seems
            to misunderstand
            the nature of SNMP.&nbsp;&nbsp; Only devices with a network connection
            AND a
            SNMP agent can implement these MIBs.<o:p></o:p></span></p>
        <p class="MsoNormal" style=""><span style="font-size: 10.5pt;
            font-family: Consolas;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal" style=""><span style="font-size: 10.5pt;
            font-family: Consolas;">4.1. The 'Terminology' section on
            power states don't
            align with existing standards for networked equipment (DMTF
            and ACPI).&nbsp;
            The authors need to clarify why they believe these
            pre-existing standards are
            in error or not applicable.<o:p></o:p></span></p>
        <p class="MsoNormal" style=""><span style="font-size: 10.5pt;
            font-family: Consolas;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal" style=""><span style="font-size: 10.5pt;
            font-family: Consolas;">5.1. Control "Device Considerations"
            also
            doesn't seem to understand how SNMP management works " We
            should not forbid
            power state management of devices that is done
            externally/centrally.&nbsp; Today,
            centralized management is the norm with SNMP.<o:p></o:p></span></p>
        <p class="MsoNormal" style=""><span style="font-size: 10.5pt;
            font-family: Consolas;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal" style=""><span style="font-size: 10.5pt;
            font-family: Consolas;">Also, the authors need to explain
            how this idea relates
            to the current marketplace of existing devices that in
            general are externally
            controlled and only occasionally have distributed
            intelligence.<o:p></o:p></span></p>
        <p class="MsoNormal" style=""><span style="font-size: 10.5pt;
            font-family: Consolas;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal" style=""><span style="font-size: 10.5pt;
            font-family: Consolas;">5.2 The comment about URL's seems
            ignorant of SysObjectID
            and not relevant to the EMAN charter <o:p></o:p></span></p>
        <p class="MsoNormal" style=""><span style="font-size: 10.5pt;
            font-family: Consolas;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal" style=""><span style="font-size: 10.5pt;
            font-family: Consolas;">5.3 For "NMS Considerations", the
            authors need
            to clarify how this relates to existing energy management
            systems and existing
            standards such as IEC 61850 that define interval
            measurements.&nbsp; <o:p></o:p></span></p>
        <p class="MsoNormal" style=""><span style="font-size: 10.5pt;
            font-family: Consolas;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal" style=""><span style="font-size: 10.5pt;
            font-family: Consolas;">5.7 "For the device power state, the
            following
            information is considered to be relevant"...&nbsp;&nbsp; This doesn't
            reference any existing standards and is therefore largely
            irrelevant.<o:p></o:p></span></p>
        <p class="MsoNormal" style=""><span style="font-size: 10.5pt;
            font-family: Consolas;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal" style=""><span style="font-size: 10.5pt;
            font-family: Consolas;">5.8 "Devices can report power for
            another device
            only if they are the<o:p></o:p></span></p>
        <p class="MsoNormal" style=""><span style="font-size: 10.5pt;
            font-family: Consolas;">entity providing the power"&nbsp; This
            would rule
            out managing PC's which typically don&#8217;t have a SNMP agent.
            &nbsp;&nbsp;We
            probably don&#8217;t want to forbid this.<o:p></o:p></span></p>
        <p class="MsoNormal" style=""><span style="font-size: 10.5pt;
            font-family: Consolas;"><o:p>&nbsp;</o:p></span></p>
        <p class="MsoNormal" style="margin-bottom: 10pt; line-height:
          115%;"><span style="font-size: 10.5pt; line-height: 115%;
            font-family: Consolas;">6.o
            "Use Case: A house... A vehicle"&nbsp; This further ignores
            basics
            about SNMP.&nbsp; Existing use cases for SNMP are not homes or
            vehicles.</span><span lang="EN"><o:p></o:p></span></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <table class="MsoNormalTable" style="width: 407.25pt;"
          width="543" border="0" cellpadding="0" cellspacing="0">
          <tbody>
            <tr>
              <td colspan="3" style="padding: 0in;">
                <p class="MsoNormal"><span style="font-size: 10pt;
                    font-family:
                    &quot;Arial&quot;,&quot;sans-serif&quot;; color:
                    rgb(34, 34, 34);"><img id="Picture_x0020_1"
                      src="cid:part1.07080307.05060401@cisco.com"
                      alt="http://www.cisco.com/swa/i/logo.gif"
                      width="110" border="0" height="73"></span><span
                    style="font-size: 10pt; font-family:
                    &quot;Arial&quot;,&quot;sans-serif&quot;; color:
                    rgb(34, 34, 34);"><o:p></o:p></span></p>
              </td>
            </tr>
            <tr>
              <td style="padding: 0in 0in 11.25pt 0.25in;" valign="top"
                nowrap="nowrap">
                <p class="MsoNormal" style="margin-bottom: 12pt;"><b><span
                      style="font-size: 8.5pt; font-family:
                      &quot;Arial&quot;,&quot;sans-serif&quot;; color:
                      rgb(102, 102, 102);">Brad Schoening</span></b><span
                    style="font-size: 8.5pt; font-family:
                    &quot;Arial&quot;,&quot;sans-serif&quot;; color:
                    rgb(102, 102, 102);"><br>
                    <b>Consultant</b><br>
                    <b>Product Development</b><br>
                    <a moz-do-not-send="true"
                      href="mailto:braschoe@cisco.com"><span
                        style="color: rgb(102, 102, 102);">braschoe@cisco.com</span></a><br>
                    Phone: <b>+1 408 424 0363</b><br>
                    Mobile: <b>+1 917 304 7190</b></span><b><span
                      style="font-size: 8.5pt; font-family:
                      &quot;Arial&quot;,&quot;sans-serif&quot;; color:
                      rgb(102, 102, 102);"><o:p></o:p></span></b></p>
                <p class="MsoNormal" style="margin-bottom: 12pt;"><span
                    style="font-size: 7.5pt; font-family:
                    &quot;Arial&quot;,&quot;sans-serif&quot;; color:
                    rgb(153, 153, 153);">For corporate legal information
                    go to:<br>
                    <a moz-do-not-send="true"
href="http://www.cisco.com/web/about/doing_business/legal/cri/index.html"><span
                        style="color: rgb(14, 88, 160);">http://www.cisco.com/web/about/doing_business/legal/cri/index.html</span></a></span><o:p></o:p></p>
              </td>
              <td style="padding: 0in;"><br>
              </td>
              <td style="padding: 0in;"><br>
              </td>
            </tr>
          </tbody>
        </table>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
        <p class="MsoNormal"><o:p>&nbsp;</o:p></p>
      </div>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
eman mailing list
<a class="moz-txt-link-abbreviated" href="mailto:eman@ietf.org">eman@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/eman">https://www.ietf.org/mailman/listinfo/eman</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------060200050609050002060601
Content-Type: image/gif
Content-Transfer-Encoding: base64
Content-ID: <part1.07080307.05060401@cisco.com>

R0lGODlhbgBJAMQAAP///3OXqtapqq1MTcmRki9mgZkAALpqbMl/f6g5O/Xq6+vX2OTIyaMq
K/nz9OW/v5sVFsbV3Nfh5p0PD5kFBf78/P38/Pz6+v/+/rZdXpcKDKAhIvv396QvMO/g4Ny4
uSH5BAAAAAAALAAAAABuAEkAQAX/ICCOZGmeaKqubOu+cCzPdG3feK6nkln8pp5LSPoVgruc
sbQsAp1HKPM5alapImtyy+16SwKDmJBCiBEWgMUsPgg8JMHEQCGTMACP2HDgiBQZYglfOQ+G
Dy2HhiqKKI2EkJGSk5SVlpeYmZpfWkpYmypEV1GjU6QjolmfnZ0AqZWvrj6fski2UiWxsZkc
HxkNYg0IABUibAjFIgsHwAYNBwokvb8QEMIOJAwICQYQCQgLoCgLHWIdHwoKCwzExmdpGBwc
xRgDYhkXAOTm6OoMfg4CiRGgwAOBOXzEKVzIsKHDhxAjSpxIsaKNCAEibMGo0WKLVjdAVgxQ
IICpEiRN/7JIeZIEy4WsVsk8BSAmTZstLb0csVMVzZ4AgALtJLQkRY4bM3pcupDAHgMduA1Q
484AGmJO7x04kCCaCAIaxFCISmGAVwZPu+1pEK5hVgPYUBxLQ4yBvacfvlIwMCFuCbRi2I34
sHfDQ0BpDUyFNxfABTZPGwgGACjsU7MiLLx9ukEA08+gQ4seTbq06dOoU6tezbq169evd92Q
HRooDtujRdbQDZr3DN8RkeIaIXxFcZ8ljkPEOVwF81ILlT9HTkL6zJwilE+aXvN68+43vUO3
xL28eOrj0VdSbp0me6XV4acH8L6jRNw28IumXYM/7P8kPJLIISkIWIKBD3GwmcIYiwGAQWP6
cJMWHCIoCEFamInwQTNPdYCIQwqUM8YCC3zgWTKNOXAAg14pkA9lIkJAAIkmYsPBim0YcsBe
Vjn0llcnQAjYHh14phdfQGazx2QAEGaAYQ2FMVAZ75BggTZ7HFCMHHQYWcICeyAjgormPASZ
YgN00CAAjV0gwAEEEACZlsbwCMEAaWb4wFMJJMDjBkwypAABErbRzoNnFFPBghnkRcKgCVim
wQF+VSDAXXw1CuCmnHbq6aeghirqqDiEAAA7
--------------060200050609050002060601--

--------------090302050508020401040806--

From braschoe@cisco.com  Mon Nov  8 19:34:11 2010
Return-Path: <braschoe@cisco.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 20B8028C2FF for <eman@core3.amsl.com>; Mon,  8 Nov 2010 19:34:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.178
X-Spam-Level: 
X-Spam-Status: No, score=-10.178 tagged_above=-999 required=5 tests=[AWL=0.420, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nrWHt6jvo5Tc for <eman@core3.amsl.com>; Mon,  8 Nov 2010 19:34:00 -0800 (PST)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id 5EE6528C247 for <eman@ietf.org>; Mon,  8 Nov 2010 19:33:59 -0800 (PST)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkMJAPlP2EytJV2Z/2dsb2JhbACBbpgeAYgPcaBvm3iDBAcBgjwEgVqCfokN
X-IronPort-AV: E=Sophos;i="4.59,173,1288569600";  d="scan'208,217";a="180009339"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rtp-iport-2.cisco.com with ESMTP; 09 Nov 2010 03:34:20 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id oA93YKS3008429;  Tue, 9 Nov 2010 03:34:20 GMT
Received: from xmb-rcd-204.cisco.com ([72.163.62.211]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 8 Nov 2010 21:34:20 -0600
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB7FBE.FEC1E492"
Date: Mon, 8 Nov 2010 21:34:19 -0600
Message-ID: <308743659A7CB142B28029FB77F1128E018FF5E2@XMB-RCD-204.cisco.com>
In-Reply-To: <AANLkTinmxX+=8WbRmKOW3FxzNfakfaaA6WvQbJgJXOhP@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [eman] Review of draft-norwin-energy-consider-01
Thread-Index: Act/tjKVSCTPn7/qQ8OXBuyBMbRkngAAiRGA
References: <308743659A7CB142B28029FB77F1128E018FF3FE@XMB-RCD-204.cisco.com><C8FE8A5C.16D31%quittek@neclab.eu><308743659A7CB142B28029FB77F1128E018FF5CD@XMB-RCD-204.cisco.com> <AANLkTinmxX+=8WbRmKOW3FxzNfakfaaA6WvQbJgJXOhP@mail.gmail.com>
From: "Brad Schoening -X (braschoe - Piepeople Consulting, Inc. at Cisco)" <braschoe@cisco.com>
To: "Bruce Nordman" <bnordman@lbl.gov>
X-OriginalArrivalTime: 09 Nov 2010 03:34:20.0952 (UTC) FILETIME=[FF098980:01CB7FBE]
Cc: eman mailing list <eman@ietf.org>
Subject: Re: [eman] Review of draft-norwin-energy-consider-01
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Nov 2010 03:34:11 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB7FBE.FEC1E492
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Bruce,

=20

There are probably only a few standards that are highly relevant for
EMAN.  I would think these are ones from ACPI, DMTF and IEC, but I'm
open to hearing how others are relevant.   As Juergen suggests, it would
be helpful if you could elaborate on the mapping between your proposed
power states and those used in the DMTF and ACPI standards.  I wouldn't
really be worried that you're repeating information, because its highly
relevant how your consideration draft  ties in with these other
standards.  That's not something found in the mib drafts, since you have
suggested a new model.

=20

I agree, "Substation Automation" sounds odd, but its relevant to power
quality and interval reporting .  There is also IEC 61970 which is the
Common Information Model (CIM) / Energy Management which is in turn
related to 61850.  You should already have short excerpts of 61850 which
I previously sent you, but I can resend.

=20

Regards,

=20

Brad

=20

References

=20

http://www.dmtf.org/sites/default/files/standards/documents/DSP1027_2.0.
0.pdf

http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Interface



=20

=20

From: Bruce Nordman [mailto:bnordman@lbl.gov]=20
Sent: Monday, November 08, 2010 9:31 PM
To: Brad Schoening -X (braschoe - Piepeople Consulting,Inc. at Cisco)
Cc: eman mailing list
Subject: Re: [eman] Review of draft-norwin-energy-consider-01

=20

Brad--

There are MANY potentially relevant standards with definitions of power
states.  ACPI is certainly one of the most important for a certain
category
of devices.  Some aspects of ACPI are extremely relevant to eman - some
are not.  While we need to take into account all relevant standards,
there
is generally considerable difference between their origins, goals,
concerns,
and scopes, and those of eman  -- which is where the "consideration"=20
process comes in.

I have not read IEC 61850, but the description of it being intended for
substation automation seems to make it at least one step removed from
the eman focus.  I do look forward though to seeing what it has to
offer.

The norwin draft was not intended to repeat information already in the
other drafts, so it was not felt necessary to cite the importance of
ACPI
(or SNMP or IP for that matter).

--Bruce

On Tue, Nov 9, 2010 at 9:55 AM, Brad Schoening -X (braschoe - Piepeople
Consulting, Inc. at Cisco) <braschoe@cisco.com> wrote:

Juergen,

Looking at the big picture, if we agree that the EMAN working group must
take into consideration the existing standards for energy management,
then, yes, I'd say we're in basic agreement.  Bruce and Rolf's document
did not do that.

You stated the following which gives me confidence we're on the same
page...


       "Good point. IEC 61850 is important and should not be ignored."

       "But yes, I agree that if we adopt this proposal we should
elaborate on the mapping
       between these categories and the power states defined by other
bodies."

       "No other document that I have seen for eman suggests ignoring
ACPI or does not
       provides means for supporting it"



=20

--=20
Bruce Nordman
Lawrence Berkeley National Laboratory
eetd.lbl.gov/ea/nordman
BNordman@LBL.gov
510-486-7089
m: 510-501-7943


------_=_NextPart_001_01CB7FBE.FEC1E492
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DWordSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Bruce,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>There are probably only a few standards that are highly =
relevant
for EMAN.&nbsp; I would think these are ones from ACPI, DMTF and IEC, =
but I&#8217;m
open to hearing how others are relevant.&nbsp;&nbsp; As Juergen =
suggests, it
would be helpful if you could elaborate on the mapping between your =
proposed power
states and those used in the DMTF and ACPI standards.&nbsp; I =
wouldn&#8217;t
really be worried that you&#8217;re repeating information, because its =
highly
relevant how your consideration draft &nbsp;ties in with these other
standards.&nbsp; That&#8217;s not something found in the mib drafts, =
since you
have suggested a new model.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I agree, &#8220;Substation Automation&#8221; sounds odd, =
but its
relevant to power quality and interval reporting .&nbsp; There is also =
IEC
61970 which is the Common Information Model (CIM) / Energy Management =
which is
in turn related to 61850.&nbsp; You should already have short excerpts =
of 61850
which I previously sent you, but I can resend.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Regards,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Brad<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>References<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><a
href=3D"http://www.dmtf.org/sites/default/files/standards/documents/DSP10=
27_2.0.0.pdf">http://www.dmtf.org/sites/default/files/standards/documents=
/DSP1027_2.0.0.pdf</a><o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><a
href=3D"http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Int=
erface">http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_Int=
erface</a><br>
<br>
<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Bruce =
Nordman
[mailto:bnordman@lbl.gov] <br>
<b>Sent:</b> Monday, November 08, 2010 9:31 PM<br>
<b>To:</b> Brad Schoening -X (braschoe - Piepeople Consulting,Inc. at =
Cisco)<br>
<b>Cc:</b> eman mailing list<br>
<b>Subject:</b> Re: [eman] Review of =
draft-norwin-energy-consider-01<o:p></o:p></span></p>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>Brad--<br>
<br>
There are MANY potentially relevant standards with definitions of =
power<br>
states.&nbsp; ACPI is certainly one of the most important for a certain
category<br>
of devices.&nbsp; Some aspects of ACPI are extremely relevant to eman - =
some<br>
are not.&nbsp; While we need to take into account all relevant =
standards, there<br>
is generally considerable difference between their origins, goals, =
concerns,<br>
and scopes, and those of eman&nbsp; -- which is where the
&quot;consideration&quot; <br>
process comes in.<br>
<br>
I have not read IEC 61850, but the description of it being intended =
for<br>
substation automation seems to make it at least one step removed =
from<br>
the eman focus.&nbsp; I do look forward though to seeing what it has to =
offer.<br>
<br>
The norwin draft was not intended to repeat information already in =
the<br>
other drafts, so it was not felt necessary to cite the importance of =
ACPI<br>
(or SNMP or IP for that matter).<br>
<br>
--Bruce<o:p></o:p></p>

<div>

<p class=3DMsoNormal>On Tue, Nov 9, 2010 at 9:55 AM, Brad Schoening -X =
(braschoe
- Piepeople Consulting, Inc. at Cisco) &lt;<a =
href=3D"mailto:braschoe@cisco.com">braschoe@cisco.com</a>&gt;
wrote:<o:p></o:p></p>

<p class=3DMsoNormal>Juergen,<br>
<br>
Looking at the big picture, if we agree that the EMAN working group =
must<br>
take into consideration the existing standards for energy =
management,<br>
then, yes, I'd say we're in basic agreement. &nbsp;Bruce and Rolf's =
document<br>
did not do that.<br>
<br>
You stated the following which gives me confidence we're on the same<br>
page...<o:p></o:p></p>

<div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><br>
&nbsp; &nbsp; &nbsp; &nbsp;&quot;Good point. IEC 61850 is important and =
should
not be ignored.&quot;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>&nbsp; &nbsp; &nbsp;
&nbsp;&quot;But yes, I agree that if we adopt this proposal we =
should<br>
elaborate on the mapping<br>
&nbsp; &nbsp; &nbsp; &nbsp;between these categories and the power states
defined by other<br>
bodies.&quot;<o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>&nbsp; &nbsp; &nbsp;
&nbsp;&quot;No other document that I have seen for eman suggests =
ignoring<br>
ACPI or does not<br>
&nbsp; &nbsp; &nbsp; &nbsp;provides means for supporting it&quot;<br>
<br>
<o:p></o:p></p>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>-- <br>
<b><span style=3D'font-size:13.5pt'>Bruce Nordman</span></b><br>
<span style=3D'color:#000099'>Lawrence Berkeley National =
Laboratory</span><br>
<a href=3D"http://eetd.lbl.gov/ea/nordman" =
target=3D"_blank">eetd.lbl.gov/ea/nordman</a><br>
BNordman@LBL.gov<br>
510-486-7089<br>
m: 510-501-7943<o:p></o:p></p>

</div>

</body>

</html>

------_=_NextPart_001_01CB7FBE.FEC1E492--

From jparello@cisco.com  Mon Nov  8 21:26:56 2010
Return-Path: <jparello@cisco.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 102EF28C0E8 for <eman@core3.amsl.com>; Mon,  8 Nov 2010 21:26:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S85knJU4mPz7 for <eman@core3.amsl.com>; Mon,  8 Nov 2010 21:26:53 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 8D10E3A68D8 for <eman@ietf.org>; Mon,  8 Nov 2010 21:26:53 -0800 (PST)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAHNq2EyrR7Hu/2dsb2JhbACiHXGgbpt1AoJwEgcBgjwEhFhVhSiDCg
X-IronPort-AV: E=Sophos;i="4.59,173,1288569600"; d="scan'208";a="213950175"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 09 Nov 2010 05:27:13 +0000
Received: from [130.129.64.91] (sjc-vpn7-777.cisco.com [10.21.147.9]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id oA95RBMs029241; Tue, 9 Nov 2010 05:27:11 GMT
Message-ID: <4CD8DBAD.8080405@cisco.com>
Date: Mon, 08 Nov 2010 21:27:09 -0800
From: john parello <jparello@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: "Mielke, William F (Bill)" <bill.mielke@alcatel-lucent.com>
References: <AANLkTikFy7hzFSFtQonWZRXe_WAMbpZLLAGWrNjOVcFw@mail.gmail.com> <0DEE3BCEE44BFD4EBC3B7DC009C8E79225064C324D@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
In-Reply-To: <0DEE3BCEE44BFD4EBC3B7DC009C8E79225064C324D@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "eman@ietf.org" <eman@ietf.org>
Subject: Re: [eman] Proposed alternation of framework
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Nov 2010 05:26:56 -0000

Hi William,

Looking forward to meeting you at the session!

I agree with your comments especially w.r.t to the power usage over 
time. For the implementation that I have of power monitoring I have been 
getting requests for the historical tracking on devices from both device 
manufacturers and NMS vendors.

Especially PDU manufacturers who have this capability but have no 
standard/common way of reporting it.

If you look at the optional historical power reporting in 
draft-claise-energy-monitoring-mib-05 you'll see that we have modeled it 
based upon the existing standards and with input from power meter and 
control manufacturers.

See you at the session!
John



On 11/7/10 8:51 PM, Mielke, William F (Bill) wrote:
> Hello all.  Being new to the IETF I have been mainly lurking on the EMAN
> list until now.  I am in Beijing and will be attending the EMAN WG meeting
> on Wednesday and look forward to meeting those who can attend face-to-face.
> I am in the process of reading through the current drafts and should be
> prepared to offer any insights or thoughts by the Wednesday meeting.
>
> I want to thank everyone for their thought provoking contributions thus far
> and look forward to working with you in this important area.
>
> With that as an introduction I have provided some informal thoughts on
> Bruce's comments in-line below.
>
> Sincerely,
>
> William F. Mielke
> Alcatel-Lucent
> Distinguished Member of Technical Staff
> 6200 East Broad Street
> Room: 4B01-1V
> Columbus, OH  43213-1530
> Email:<mailto:mielke@alcatel-lucent.com>  Bill.Mielke@alcatel-lucent.com
> Phone: 614 367 5628
> Fax: 614 367 5965
>
> "Live like you're going to die tomorrow.
>   Learn like you're going to live forever."
>
>      - Albert Einstein
>
>
>
>    _____
>
> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of
> Bruce Nordman
> Sent: Sunday, November 07, 2010 6:10 PM
> To: eman@ietf.org
> Subject: [eman] Proposed alternation of framework
>
>
> <<  warning: long email>>
>
>
>
> eman proposal for adjusting framework in current I-Ds
>
> Bruce Nordman
>
> November 7, 2010
>
>
>
> The following takes the basic principles from the current I-Ds, and
>
> makes a few changes that I see as making the framework simpler
>
> and more transparent, and also provides some additional features.
>
> It does not address control, nor many (future) optional features.
>
>
>
> As an observation, power state is a property of an individual device
>
> and cannot be aggregated.  Power level (W) and energy use can be
>
> readily aggregated.
>
>
>
> [WFM] As Chris Verges has pointed out there may be some reasonable
> approaches to state aggregation.  The ability to do so will depend to some
> degree on the semantics and definition that are assigned to the term power
> state. For example, a generic set of power states could be defined (along
> with some concept of extensibility thereof) which each device is free to map
> to a rough percentage of the total potential power consumption of that
> device.  These values could be device specific and exposed through a MIB.
> By mapping these values to a unitless quantity like a percentage we could
> enable a useful form of aggregation for power states which can remain device
> specific.
>
>
>
> I am not advocating anything here, merely observing the possibility.
>
>
>
> There are a number of complications that I would propose deferring
>
> from our initial product.  These include transition states, support for
>
> reporting intervals, and reporting on components within a host.
>
> As noted above, we could be making progress on these in parallel to
>
> the more basic work, particularly if the content was in separate I-Ds.
>
>
>
> [WFM] I agree that we need to have some discussion of the first set of work
> products from this group and a potential rollout of functions across those.
> Reporting is a logical first step which could be addressed in isolation but
> from my perspective power states and control mechanisms are key features of
> any final working products this group must address.  I personally am
> agnostic, however, on the specific timing of how these features are to be
> rolled out across formal WG outputs.
>
>
>
> There is nothing magic about the terminology used below and I am
>
> sure it can be improved.
>
>
>
> Basic concepts I propose are:
>
>
>
> Powered Device
>
>
>
> An electricity-using device that is almost always "atomic" - not
>
> separated into constituent parts that can be powered and function
>
> autonomously in normal use.  They may have IP connectivity or lack it.
>
> They may be able to report energy/power information themselves,
>
> or rely on a power proxy to do this.
>
>
>
> Most devices have a single power source, no battery, and do not power
>
> other devices, so these just report a unitary notion of energy/power.
>
> Other devices have multiple power sources (from different electricity
>
> "domains"), an internal battery (which is functionally an additional
> source),
>
> and/or downstream power loads (other devices; a battery that is charging
>
> is effectively an additional load).  Thus, these have the total net
> consumption
>
> of the device itself, the power input from each source, and the power output
>
> to each load.  The complexity required for these more complex devices
>
> should not be burdensome on the simpler devices.  We need terms that
>
> distinguish simple from complex devices; whether having a battery always
>
> makes a device complex I am not sure.
>
>
>
> In addition to the information noted in the current I-Ds, a device is also a
>
> member of a "Power Domain" (or more specifically, each power source is).
>
>
>
> Power Proxy
>
>
>
> A power proxy reports power/energy data on behalf of a second device.
>
> For purposes of energy management, it IS the device.  The second device
>
> may or may not have IP connectivity, but in either case, all energy/power
>
> information (including any subsidiary notion of identity) should come from
>
> the proxy to the rest of the IP network.  In the long run, we should hope
> that
>
> fewer and fewer devices require a proxy, but for a considerable time we will
>
> have devices that lack IP connectivity, or that have it but lack ability to
> report
>
> on their own power/energy status.
>
>
>
> Note that a host may implement many power proxies; each proxy is logically
>
> independent of the others.  It seems likely that any device that provides
> proxy
>
> services can report on its own power/energy status.  A proxy will almost
> always
>
> (perhaps always) be implemented by a Power Distributor, but proxying a
> distinct
>
> function.
>
>
>
> The proxy may be in the same domain as the second device, or a different
> domain.
>
> If in the same domain, the proxy may be in a device that distributes power
> to the
>
> second device, or not.  Thus, there are three possible relationships:
> different domain,
>
> powering (consequently same domain), not powering (but same domain).
>
>
>
> Power Distributor
>
>
>
> These consumes power themselves and distribute power to other devices, which
>
> may include further distributors.  A distributor may have incomplete
> information
>
> about downstream devices and their power consumption, missing identity,
> power
>
> consumption, or both, from some devices.  A distributor is a device, so may
> have
>
> more than one power source, and may include a battery.
>
>
>
> It is helpful to first think of power being distributed along a tree
> structure, with
>
> parent and child controllers, but the structure need not be limited to
> classic trees.
>
> Other than batteries, at this time power flow is only in one direction (that
> is, all
>
> flows are either sources into a device, or sinks out of it).
>
>
>
> [WFM] While the concept of uni-directional flow is a nice simplifying
> concept, and indeed it may be true at any particular instant in time, it is
> not clear that this would be true in general for a given device over time.
> The example that I am thinking of is a house with solar panels installed.
> During the daytime on a sunny day these systems can produce more power than
> is required which can then flow backwards through the main electric meter
> and is thus "sold" back to the power utility on the main grid.  At night the
> house then operates as normal with respect to the grid, or it may also
> supplement its power needs via battery reserves which are typically
> recharged via the solar panels during the day as well.
>
>
>
> Whether this concept extends to other devices or uses in other alternative
> energy scenarios remains to be seen.
>
>
>
> This does raise the issue that the power flow on a given metering point may
> actually be negative, something that may not be immediately obvious.  Using
> the example of the house described above, the power meter provided by the
> utility may actually report "negative KW" during the day and "positive KW"
> at night.
>
>
>
> A distributor may be in one power domain, but more commonly the downstream
>
> powered devices will be in a different domain; a Power over Ethernet switch
> is a
>
> prime example of this.  Most commonly, each domain will have a single source
> of
>
> power (ignoring batteries), but this may not be required.
>
>
>
> [WFM] Interestingly, batteries are actually an interesting case.  In this
> context I am speaking of rechargable batteries (not single use chemical
> batteries which I suppose could be considered a specialized power
> source/domain in their own right with their own environmental impacts).
> Rechargable batteries have an internal resistance which will cause them to
> discharge over time.  As such they are a load to the overall system.  When
> they are being utilized as a temporary power source they are depleting their
> internal reserves which must ultimately be restored from some other primary
> power source.  So the environmental footprint of a battery is ultimately
> tied to the primary energy source which is used to charge it.  Solar cells
> would have one carbon footprint, whereas a coal burning power plant would
> have another.  This suggests to me that carbon footprint of a battery is
> ultimately tied back to the primary source used to charge it, which could
> vary over time (i.e. it may typically be recharged from solar cells when
> they are available and producing power, or from the power utility
> otherwise).
>
>
>
> So if on one day they happen to be recharged via the solar cells their
> instantaneous carbon footprint at that point in time would be zero, whereas
> if on a differnt day they happened to be recharged from utility power their
> carbon footprint would be a function of the utility's carbon load.
>
>
>
> Whether we need or indeed want to produce a standard which can reasonably
> account for such cases or not is something that we will need to decide.
> Perhaps initially not, but as alternative energy sources become a larger
> part of every day life these may become important.
>
>
>
> This then raises the question of whether our power reporting mechanism can
> or should account for allowing each device to report it's own carbon impact
> to facilitate a more meaningful form of aggregation.  This in turn raises
> the question of how a given device would even know what it's carbon impact
> was since this is a function/attribute of the source.
>
>
>
> I am not personally at a point of advocating any particular position on
> these issues.  I am merely raising them for consideration.  The direction we
> take will have downstream consequences.
>
>
>
>
>
> Power Domain
>
>
>
> A system of power distribution with a common technology and fate.
> Technologies
>
> are usually distinguished by voltages and whether AC or DC.  AC examples
> include
>
> 100V, 115V, 200V, and 230V.  DC examples include 380V, 48V, 24V, 12V, and 5V
>
> (variously including eMerge, PoE, USB, and vehicle standards).  Increasingly
>
> communications go along with power, but this is incidental to power
> reporting.
>
>
>
> Power domains are often in trees, but this is not strictly required.  A
> domain with
>
> a single source may have a controller at its root (e.g. a PoE switch), or
> not (e.g.
>
> a circuit breaker in a building).  At this time, we should consider domains
> as having
>
> a single source of power; later we could relax that requirement.
>
>
>
> Common fate includes quality, reliability, availability, total capacity, and
> price.
>
> How devices learn what domain they are in is out of our scope.
>
>
>
> [WFM] This seems a reason simplifying assumption for a first version of the
> standard but long term we may wish to consider scenarios where the devices
> query their sources as well as vice versa.
>
>
>
> Power Manager
>
>
>
> This concept is NOT defined in our standard, but is a key expected user of
>
> the facility.  It is an interested entity and has no specific relation to
> device.
>
> It may be in the same power domain, or not.
>
>
>
> A power manager will commonly send out a broadcast request to all devices
>
> in a power domain and ask for current information.  In this case, a
> distributor is
>
> not involved in the request for that function, though a device which is a
> distributor
>
> will report its own (net) consumption, and may implement proxies that
> respond
>
> to this request.
>
>
>
> [WFM] I agree that discovery mechanisms such as the one you describe are
> something that we will need to take account of.  This is true even for
> common reporting use cases.
>
>
>
> To avoid double-counting, the manager needs to know what domains provide
>
> power to others).  A manager may use distributors that are gateways between
>
> domains as aggregators, and so not bothering to query devices in the second
>
> domain at all, or as often.  For example, the domain that a PoE switch is in
> may
>
> be queried more often than the domain of devices powered by that switch.
>
>
>
> Other Notes
>
>
>
> This system has no concept of a meter.  Rather, a meter is a distributor,
> and
>
> today's meters don't have direct knowledge of what they are providing power
> to
>
> (remember that a distributor can have incomplete knowledge, including none).
>
>
>
> A key point is that there is no assumed relationship between the power
> distribution
>
> topology and the communications topology.
>
>
>
> [WFM] Agreed.  The two are completely distinct.  To the extent that
> management systems will need to understand both we may wish to consider
> whether the power reporting capabilities we define are capable of providing
> the information necessary to enable them to discern the structure of the
> power distribution topology when devices have been configured with such
> information.
>
>
>
> This is also something that we will need to decide if it is in or out of
> scope for our efforts.
>
>
>
> Somewhere, attention needs to be paid to wire losses - there is a difference
>
> between power supplied to a device, and power consumed by one.   When
>
> measurement is done at both ends of the wire, it can be calculated, but more
>
> commonly, the measurement is done at only one end so just needs to have a
>
> flag for which it is.
>
>
>
> Power data are allowed to be estimated by a device from knowledge it has
>
> rather than directly measured.  This is then noted in accuracy reporting.
>
> Power estimation may be as important as proxying in the coming years.
>
>
>
> Communication
>
>
>
> The core definition is what information a device provides when queried.
>
> A proxy IS the device for these purposes, so responds the same as a direct
>
> device (with a flag somewhere noting it is a proxy in case someone cares).
>
> A distributor is a device so responds the same way as a simple device
> (albeit
>
> with more complexity to the response).
>
>
>
> Distributors may find it helpful to query devices they supply power to, but
>
> this is simply a usage of our facility, not a separate mechanism.
>
>
>
> Because control and intervals are not implemented, communication is only
>
> in one direction.
>
>
>
> [WFM] I understand your comment and why you make it given your stated
> assumptions regarding scope.  I would hope that intervals might actually
> still be addressed from a reporting perspective even if only based on
> default intervals defined by the standard, or by enabling device specific
> default intervals coupled with a means of reporting the durations thereof.
> Without some device maintained means of reporting historical information the
> per device polling overhead introduced on the communications network is
> likely to be far greater than is actually required for efficient operations.
> In addition, enabling the devices to report historical information
> decentralizes the collection of the raw data and removes the need for
> "tight" timing constraints on the actual polling of the devices making the
> system more tolerant of network outages and delays.
>
>
>
> Usage examples
>
>
>
> Most common today is devices on mains AC power in which a domain is
>
> a circuit breaker, a larger area (e.g. zone or floor of a building), or an
> entire
>
> building.  A vehicle is a building on wheels (and always its own domain).
>
>
>
> PoE necessarily creates a different domain.   Usually all devices powered
>
> from a PoE switch are in the same domain.  PoE switches usually have a
>
> capacity constraint distinct from that of the domain it is part of.
>
>
>
> A UPS has a distinct domain downstream of it from its mains power source,
>
> as the fate of these devices is different from what the UPS sees from its
> primary
>
> source.
>
>
>
> Other Other Notes
>
>
>
> There is no distinction by building type (home, commercial, vehicle) in any
>
> of this.
>
>
>
> Likely none of this affects the battery MIB proposal.
>
>
>
> Many control approaches will include distribution a price (and price
> forecast)
>
> to devices.  Prices will be by domain, as they may vary.  For example, UPS
> will
>
> have its own price when off-grid.  PoE devices may get higher price if
> switch
>
> is near capacity.  People in charge of a domain may want to impose their own
>
> carbon taxes implicitly.  Local batteries/generation may raise or lower the
> price
>
> otherwise seen on a domain.  Price distribution NOT part of the energy/power
>
> reporting mechanism, though will use the same domain concept.  There is a
>
> standard for getting a price to a building - my concern is only local
> distribution
>
> of a price within a building or a domain.
>
>
>
> [WFM] In addition to pricing a parallel concept exists for reporting of the
> carbon loading.  Agreed?  From a reporting perspective enabling a reasonable
> ability to distribute such cost and environmental data from the sources to
> the ultimate sinks would seem to be a significant goal of this work.
>
>
>
>
>
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman

From jparello@cisco.com  Mon Nov  8 21:37:12 2010
Return-Path: <jparello@cisco.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7A87A3A68F9 for <eman@core3.amsl.com>; Mon,  8 Nov 2010 21:37:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l0gOGMD4Ym+1 for <eman@core3.amsl.com>; Mon,  8 Nov 2010 21:37:11 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id C73E63A690A for <eman@ietf.org>; Mon,  8 Nov 2010 21:37:08 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAMps2EyrR7Ht/2dsb2JhbACiHXGgcptygwQIgjwEhFiFfYMK
X-IronPort-AV: E=Sophos;i="4.59,173,1288569600"; d="scan'208";a="282955517"
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-5.cisco.com with ESMTP; 09 Nov 2010 05:37:31 +0000
Received: from [130.129.64.91] (sjc-vpn7-559.cisco.com [10.21.146.47]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id oA95bUSt010196; Tue, 9 Nov 2010 05:37:30 GMT
Message-ID: <4CD8DD96.6050507@cisco.com>
Date: Mon, 08 Nov 2010 21:35:18 -0800
From: john parello <jparello@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: Chris Verges <chrisv@cyberswitching.com>
References: <AANLkTikFy7hzFSFtQonWZRXe_WAMbpZLLAGWrNjOVcFw@mail.gmail.com> <68FBE0F3CE97264395875AC1C468F22C514A74@mail03.cyberswitching.local>
In-Reply-To: <68FBE0F3CE97264395875AC1C468F22C514A74@mail03.cyberswitching.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: eman@ietf.org
Subject: Re: [eman] Proposed alternation of framework
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Nov 2010 05:37:12 -0000

Hi Chris,

Thanks for the replies I agree with your assessments as well. Also with 
respect to initial products I think we are past that.

Both you and I have products which deliver the features that Bruce is 
talking about. So I think we are past initial product and down to 
setting common data modeling between them.

What we need is the common standard that we have expressed in the drafts.

w.r.t to the power domain the metering domain described in both

draft-claise-power-management-arch-02

and

draft-parello-eman-energy-aware-mib-00

have the flexibility to be specified based upon the physical metered 
topology but with the context information and tagging the different 
aggregation and reporting you asked for can be obtained.

This is very much analogous to what we do in IP networking with physical 
topology versus vlan etc.

Thanks
Jp

On 11/7/10 5:15 PM, Chris Verges wrote:
> Hi Bruce,
>
>
>
> Questions and comments inline:
>
>
>
> [BN] As an observation, power state is a property of an individual
> device and cannot be aggregated.  Power level (W) and energy use can be
> readily aggregated.
>
>
>
> [CV] With respect, I think power state can be aggregated.  For example,
> please consider a standard datacenter.  When all servers are turned on
> in the datacenter, it is at 100% "on" state.  If 30% of the servers are
> turned off, the datacenter's state has reduced to 70%.  This is fairly
> congruous with the ACPI model, where a server can be in different
> states, and each state represents a power usage level.
>
>
>
> [CV] How such aggregated state is determined is beyond the scope of any
> MIB, but the ability to report such information can offer a hook for
> innovation in the industry.
>
>
>
> [CV] I agree that power state, like reporting meter data, could be
> pushed off to a later release, as enumerating the entities themselves is
> far more critical (core?) to establishing anything more complex.
>
>
>
> [BN] There are a number of complications that I would propose deferring
> from our initial product.  These include transition states, support for
>
> reporting intervals, and reporting on components within a host.  As
> noted above, we could be making progress on these in parallel to the
> more basic work, particularly if the content was in separate I-Ds.
>
>
>
> [CV] What would now be in the initial product?  After reading your two
> recent threads, I'm a little confused over what the "initial product"
> is, as a definition and in its scope.
>
>
>
> [BN] Power Domain
>
>
>
> [BN] A system of power distribution with a common technology and fate.
> Technologies are usually distinguished by voltages and whether AC or DC.
> AC examples include 100V, 115V, 200V, and 230V.  DC examples include
> 380V, 48V, 24V, 12V, and 5V (variously including eMerge, PoE, USB, and
> vehicle standards).  Increasingly communications go along with power,
> but this is incidental to power reporting.
>
>
>
> [BN] Power domains are often in trees, but this is not strictly
> required.  A domain with a single source may have a controller at its
> root (e.g. a PoE switch), or not (e.g. a circuit breaker in a building).
> At this time, we should consider domains as having a single source of
> power; later we could relax that requirement.
>
>
>
> [BN] Common fate includes quality, reliability, availability, total
> capacity, and price.  How devices learn what domain they are in is out
> of our scope.
>
>
>
> [CV] With respect, this concept of a "Power Domain" is very limited to
> the standard utility/facilities definition.  Given the advent of newer
> reporting models and systems, should we extend this concept to simply
> mean any logical grouping of power entities.  The mapping between power
> domains and power entities can be many-to-many, not just one-to-many.
>
>
>
> [CV] For example, consider a deployment where the "power domain" is
> segmented in two ways: (1) the physical infrastructure, taking into
> account branch circuit and transformer capacities; and (2) the billing
> structure, where entities are "grouped" according to who pays the costs.
> If the MIB model only handles a 1:N mapping, the administrator needs to
> choose only one.  If the MIB model handles a M:N mapping, more complex
> and useful systems can be built on top of this schema.
>
>
>
> Enjoy Beijing,
>
> Chris
>
>
>
>
>
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman

From jparello@cisco.com  Mon Nov  8 22:18:14 2010
Return-Path: <jparello@cisco.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A26F53A67FA for <eman@core3.amsl.com>; Mon,  8 Nov 2010 22:18:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mcKgMdoVG-GN for <eman@core3.amsl.com>; Mon,  8 Nov 2010 22:18:06 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 4466D28C10B for <eman@ietf.org>; Mon,  8 Nov 2010 22:15:06 -0800 (PST)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAP502EyrR7H+/2dsb2JhbACiHnGgXpttgnISCII8BIRYhX2DCg
X-IronPort-AV: E=Sophos;i="4.59,173,1288569600"; d="scan'208";a="213969484"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-4.cisco.com with ESMTP; 09 Nov 2010 06:13:19 +0000
Received: from [130.129.64.91] (sjc-vpn6-796.cisco.com [10.21.123.28]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id oA96DGRR017309; Tue, 9 Nov 2010 06:13:17 GMT
Message-ID: <4CD8E67C.6030502@cisco.com>
Date: Mon, 08 Nov 2010 22:13:16 -0800
From: john parello <jparello@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: Bruce Nordman <bnordman@lbl.gov>
References: <AANLkTikFy7hzFSFtQonWZRXe_WAMbpZLLAGWrNjOVcFw@mail.gmail.com>
In-Reply-To: <AANLkTikFy7hzFSFtQonWZRXe_WAMbpZLLAGWrNjOVcFw@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
Cc: eman@ietf.org
Subject: Re: [eman] Proposed alternation of framework
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Nov 2010 06:18:14 -0000

Hi Bruce,

Thanks for the feedback on the framework draft. I think in general I'm=20
pleased with the draft since after going through your proposed changes=20
my inner voice kept saying - that's covered, that's covered.

I think since this is a new group there's a bit of terminology that we=20
are familiar with since the drafts have been in the OPSAWG for a year=20
now. So we've converged on terms.

See inline and I think you'll see we are all seeing the same elephant...

(some deletia for readability)

On 11/7/10 3:09 PM, Bruce Nordman wrote:
<deletia>
>
>
> As an observation, power state is a property of an individual device
>
> and cannot be aggregated.  Power level (W) and energy use can be
>
> readily aggregated.
>
>

[jp] As we discussed I'd agree the state transitions are up to the=20
manufacturer/implementer. Having deployed the concept of levels we've=20
had a better acceptance with levels versus state transitions. I think=20
the issue we are dancing around is that other standards use the term=20
STATE like the DMTF and we need to reconcile with that.

>
> There are a number of complications that I would propose deferring
>
> from our initial product.  These include transition states, support for=

>
> reporting intervals, and reporting on components within a host.
>
> As noted above, we could be making progress on these in parallel to
>
> the more basic work, particularly if the content was in separate I-Ds.
>
>

[jp] See prior emails. We have a large contingency of folks that have=20
specifically asked and implement this type of interval. Having a=20
standard way to report that will help us all.

>

>
> Powered Device
>
>
>
> An electricity-using device that is almost always =93atomic=94 =96 not
>
> separated into constituent parts that can be powered and function
>
> autonomously in normal use.  They may have IP connectivity or lack it.
>
> They may be able to report energy/power information themselves,
>
> or rely on a power proxy to do this.
>
>

[jp] I don't see any difference between Power Device or the term Power=20
Monitor we defined.

>
> Most devices have a single power source, no battery, and do not power
>
> other devices, so these just report a unitary notion of energy/power.
>
> Other devices have multiple power sources (from different electricity
>
> =93domains=94), an internal battery (which is functionally an additiona=
l
> source),
>
> and/or downstream power loads (other devices; a battery that is chargin=
g
>

[jp] I disagree with your use of "most". That's relative. That depends=20
on who you talk to and context.  I'll take a leap here but I think you=20
are referring to consumer devices. If you ask a data center admin he=20
would say most devices run DC, have multiple power sources. We've seen=20
data centers where all devices had batteries.

> is effectively an additional load).  Thus, these have the total net
> consumption
>
> of the device itself, the power input from each source, and the power o=
utput
>
> to each load.  The complexity required for these more complex devices
>
> should not be burdensome on the simpler devices.  We need terms that
>
> distinguish simple from complex devices; whether having a battery alway=
s
>
> makes a device complex I am not sure.
>
>

[jp] Any solution should not hinder the simple path and I think we do=20
that wrt to parent child and simple, short variables for context and=20
reusing existing known standards in the space.

>
> Power Proxy
>
>
>
> A power proxy reports power/energy data on behalf of a second device.
>
> For purposes of energy management, it IS the device.  The second device=

>
> may or may not have IP connectivity, but in either case, all energy/pow=
er
>
> information (including any subsidiary notion of identity) should come f=
rom
>
> the proxy to the rest of the IP network.  In the long run, we should ho=
pe
> that
>
> fewer and fewer devices require a proxy, but for a considerable time we=
 will
>
> have devices that lack IP connectivity, or that have it but lack abilit=
y to
> report
>
> on their own power/energy status.
>

[jp] I think what you are trying to grok here is our notion of Parent=20
and Child. We specifically used the term Parent/Child to refer to a=20
generic type. I think what you are confusing is an "is type of" versus=20
"is capable of" relation ship.

In our implementation we specifically desired type to be Parent and=20
things like ability to proxy for a device to be a capability.

In network management we deal with this a lot. Is a a device a switch an =

power distribution unit or router. Or are those capabilities. Think=20
about a PoE switch and you'll see what we are talking about.

So in general I don't like the term Proxy for classifying a device as=20
that's more a capability.

The good thing is is that we cover this concept.

>
>
> Note that a host may implement many power proxies; each proxy is logica=
lly
>
> independent of the others.  It seems likely that any device that provid=
es
> proxy
>
> services can report on its own power/energy status.  A proxy will almos=
t
> always
>
> (perhaps always) be implemented by a Power Distributor, but proxying a
> distinct
>
> function.
>
>

[jp] again capability versus type

>
> The proxy may be in the same domain as the second device, or a differen=
t
> domain.
>
> If in the same domain, the proxy may be in a device that distributes po=
wer
> to the
>
> second device, or not.  Thus, there are three possible relationships:
> different domain,
>
> powering (consequently same domain), not powering (but same domain).
>
>

[jp] The notion of "in a domain" versus regrouping and categorization is =

something we have dealt with in network management for along time. Think =

of physical topology, SNMP domains etc. Our use of a Power Monitor=20
domain covers this and your reclassification can be done with our notion =

of keywords which allow for regrouping.


>
> Power Distributor
>
>
>
> These consumes power themselves and distribute power to other devices, =
which
>
> may include further distributors.  A distributor may have incomplete
> information
>
> about downstream devices and their power consumption, missing identity,=

> power
>
> consumption, or both, from some devices.  A distributor is a device, so=
 may
> have
>
> more than one power source, and may include a battery.
>
>

[jp] Again get familiar with is type of versus is capable of. There is=20
no clear line between a power distributor. Recall my example of a PoE=20
switch. From a power management point of view it's simple a Ethernet=20
based PDU.
>
> It is helpful to first think of power being distributed along a tree
> structure, with
>
> parent and child controllers, but the structure need not be limited to
> classic trees.
>
> Other than batteries, at this time power flow is only in one direction =
(that
> is, all
>
> flows are either sources into a device, or sinks out of it).
>
>

[jp] Not sure what you mean here.
>
> A distributor may be in one power domain, but more commonly the downstr=
eam
>
> powered devices will be in a different domain; a Power over Ethernet sw=
itch
> is a
>
> prime example of this.  Most commonly, each domain will have a single s=
ource
> of
>
> power (ignoring batteries), but this may not be required.
>

[jp] Again most is relevant to context

>
>
> Power Domain
>
>
>
> A system of power distribution with a common technology and fate.
> Technologies
>
> are usually distinguished by voltages and whether AC or DC.  AC example=
s
> include
>
> 100V, 115V, 200V, and 230V.  DC examples include 380V, 48V, 24V, 12V, a=
nd 5V
>
> (variously including eMerge, PoE, USB, and vehicle standards).  Increas=
ingly
>
> communications go along with power, but this is incidental to power
> reporting.
>
>
>
> Power domains are often in trees, but this is not strictly required.  A=

> domain with
>
> a single source may have a controller at its root (e.g. a PoE switch), =
or
> not (e.g.
>
> a circuit breaker in a building).  At this time, we should consider dom=
ains
> as having
>
> a single source of power; later we could relax that requirement.
>
>

[jp] For this we are in agreement. In fact our deployments of this=20
architecture we suggest mapping the data network to the power=20
distribution network and assume the same source of power for all devices =

in a domain. Lets get experience with this and then move on to the more=20
complex.

>

>
>
> Power Manager
>
>
>
> This concept is NOT defined in our standard, but is a key expected user=
 of
>
> the facility.  It is an interested entity and has no specific relation =
to
> device.
>
> It may be in the same power domain, or not.
>
>
[jp] I think the reason we don't call this our specifically is that is=20
taken as a given here amongst most members of the IETF that work on=20
SNMP. This would be the management station (NMS) and/or more=20
specifically the EMS.

>
> A power manager will commonly send out a broadcast request to all devic=
es
>
> in a power domain and ask for current information.  In this case, a
> distributor is
>
> not involved in the request for that function, though a device which is=
 a
> distributor
>
> will report its own (net) consumption, and may implement proxies that
> respond
>
> to this request.
>
>

[jp] I don't think you can make that assumption as devices will have=20
multiple capabilities.

>
> To avoid double-counting, the manager needs to know what domains provid=
e
>
> power to others).  A manager may use distributors that are gateways bet=
ween
>
> domains as aggregators, and so not bothering to query devices in the se=
cond
>
> domain at all, or as often.  For example, the domain that a PoE switch =
is in
> may
>
> be queried more often than the domain of devices powered by that switch=
=2E
>
>

[jp] again I think we cover this in the parent child aggregation

>
> Other Notes
>
>
>
> This system has no concept of a meter.  Rather, a meter is a distributo=
r,
> and
>
> today=92s meters don=92t have direct knowledge of what they are providi=
ng power
> to
>

[jp] We do have the notion of meter in the energy aware mib. Also more=20
devices will be considered meters wrt to their end devices. Take for=20
example a PDU. It is a power distributr but it is also a meter for the=20
device that is connected to it. Your last assumption on not knowing what =

is connected does not apply to all devices. A PoE switch for example is=20
a switch, a power distributer and a meter for the attached devices and=20
very much knows what is connected via LLDP/CDP etc.

> (remember that a distributor can have incomplete knowledge, including n=
one).
>
>
>
> A key point is that there is no assumed relationship between the power
> distribution
>
> topology and the communications topology.
>
>
>
> Somewhere, attention needs to be paid to wire losses =96 there is a dif=
ference
>
> between power supplied to a device, and power consumed by one.   When
>
> measurement is done at both ends of the wire, it can be calculated, but=
 more
>
> commonly, the measurement is done at only one end so just needs to have=
 a
>
> flag for which it is.
>
>

[jp] My opinion on wire loss is that it need not be specifically=20
accounted for. In general we are estimating power breakdowns that will=20
correlate to sub meters. Once you account for inaccuracy of reporting=20
and have to handle error you can account for line loss. In general we've =

found that the slopes of the curves of power usage once aggregate are=20
enough to correlate to actual readings from the source.
>
> Power data are allowed to be estimated by a device from knowledge it ha=
s
>
> rather than directly measured.  This is then noted in accuracy reportin=
g.
>
> Power estimation may be as important as proxying in the coming years.
>
>
>
> Communication
>
>
>
> The core definition is what information a device provides when queried.=

>
> A proxy IS the device for these purposes, so responds the same as a dir=
ect
>
> device (with a flag somewhere noting it is a proxy in case someone care=
s).
>
> A distributor is a device so responds the same way as a simple device
> (albeit
>
> with more complexity to the response).
>
>
>
> Distributors may find it helpful to query devices they supply power to,=
 but
>
> this is simply a usage of our facility, not a separate mechanism.
>
>
>
> Because control and intervals are not implemented, communication is onl=
y
>
> in one direction.
>
>

[jp] It seem like you have a specific system in mind here. Can you site=20
an implementation or working example. Without that I don't think we can=20
converge on the above.

>
> Usage examples
>
>
>
> Most common today is devices on mains AC power in which a domain is
>
> a circuit breaker, a larger area (e.g. zone or floor of a building), or=
 an
> entire
>
> building.  A vehicle is a building on wheels (and always its own domain=
).
>
>
>

[jp] again common is relative. DC in the datacenter :)

> PoE necessarily creates a different domain.   Usually all devices power=
ed
>
> from a PoE switch are in the same domain.  PoE switches usually have a
>
> capacity constraint distinct from that of the domain it is part of.
>
>
>
> A UPS has a distinct domain downstream of it from its mains power sourc=
e,
>
> as the fate of these devices is different from what the UPS sees from i=
ts
> primary
>
> source.
>
>
>
> Other Other Notes
>
>
>
> There is no distinction by building type (home, commercial, vehicle) in=
 any
>
> of this.
>
>
>
> Likely none of this affects the battery MIB proposal.
>
>
>
> Many control approaches will include distribution a price (and price
> forecast)
>
> to devices.  Prices will be by domain, as they may vary.  For example, =
UPS
> will
>
> have its own price when off-grid.  PoE devices may get higher price if
> switch
>
> is near capacity.  People in charge of a domain may want to impose thei=
r own
>
> carbon taxes implicitly.  Local batteries/generation may raise or lower=
 the
> price
>
> otherwise seen on a domain.  Price distribution NOT part of the energy/=
power
>
> reporting mechanism, though will use the same domain concept.  There is=
 a
>
> standard for getting a price to a building =96 my concern is only local=

> distribution
>
> of a price within a building or a domain.
>

[jp] We should have a longer discussion on price. I think for our group=20
we are taking a a more global view and can't assume price is the common=20
control point. you mention price as the control and also want to defer=20
control so I'm not sure where to take this.

In general my option on price is that it's constraint just like CO2e or=20
perhaps business need. Why it would be used as a control mechanism is a=20
topic we should discuss. Would price be fed to a device when an operator =

wants to shut if off for maintenance?

Also price is not applicable in every country. Our host country this=20
year for example has a yearly fee for some buildings and control is=20
arbitrary not based on price but on messages sent to facility managers.


In general thanks for the review and I think with a bit more discussion=20
we can converge. I see nothing that would amend our current draft.

Thanks!
Jp


From jinchoe@gmail.com  Mon Nov  8 23:29:46 2010
Return-Path: <jinchoe@gmail.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A8803A67A1 for <eman@core3.amsl.com>; Mon,  8 Nov 2010 23:29:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AR0oVJM9g+EI for <eman@core3.amsl.com>; Mon,  8 Nov 2010 23:29:45 -0800 (PST)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by core3.amsl.com (Postfix) with ESMTP id 2A3BD3A67AF for <eman@ietf.org>; Mon,  8 Nov 2010 23:29:45 -0800 (PST)
Received: by wwc33 with SMTP id 33so972858wwc.1 for <eman@ietf.org>; Mon, 08 Nov 2010 23:30:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=eErQUSiZoNYuEFsJ9EXfL54Kqt2si5WgNVYfLLpOHVI=; b=QoLl1BNZlF73bHVlsB5BcliYuLGyEedzUiq82RkxXwyJ3ntfcYgmsNEa4aQcEJ+HX6 bIuB5Th6iLUnM6j2GVHPDIKAOl5Ekk7nZ6JDeIwwL1lIC3GdkKK9O5aUGoMredlHXeN8 8Oo1mNgQIcYnnmENTP6NJ7T0/TfRBbn01mqGM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=tGUCKPDF+q1nXp9p0FODDLoiKenWewkRn5R65xnQmdLA6lQ+sZt747R9GWxmWRMY0M x94VcAJnhiSyW+OzlfASUqFAYS4PtYUHbkkqlJBYJQETBElok1kh7iOOST3y5IYvZWN2 7DpoksaBwHOhJe1TQTQQ4orIFU6AQLT28PMN0=
MIME-Version: 1.0
Received: by 10.227.155.66 with SMTP id r2mr6170838wbw.116.1289287807032; Mon, 08 Nov 2010 23:30:07 -0800 (PST)
Received: by 10.227.58.131 with HTTP; Mon, 8 Nov 2010 23:30:06 -0800 (PST)
In-Reply-To: <C8FEA7BA.16D4A%quittek@neclab.eu>
References: <20101108224927.6B96728C0DB@core3.amsl.com> <C8FEA7BA.16D4A%quittek@neclab.eu>
Date: Tue, 9 Nov 2010 16:30:06 +0900
Message-ID: <AANLkTik-fGiNo+qTnj0LMMvygp_rSZkKgEvgSukaTn0X@mail.gmail.com>
From: JinHyeock Choi <jinchoe@gmail.com>
To: Juergen Quittek <Quittek@neclab.eu>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: eman mailing list <eman@ietf.org>
Subject: Re: [eman] New draft draft-quittek-eman-reference-model-00
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Nov 2010 07:29:46 -0000

Dear Juergen

Thanks for the draft
which also improved my understanding of energy management,
especially about involving entities & their interactions.

Here are some quick comments.

First, the figure in Sec 3 gives an impression that
single =91Energy Management System=92 manages
1.Power Provisioning Controller &
2.Energy Consumption Reporter
3.Power Controller
but usually the first is managed by an electric power company
whereas 2nd & 3rd may by network operator (or else).

For example, even if a mobile operator builds
a management system to monitor & control its equipments,
I wonder whether the system can also control the power supply.

It may be better to divide Energy Management System into two entities
(as done for Power Provisioning Controller & Power Controller.)

Second, I wish the draft mentions more about the
relationship among entities such as
a single Energy Consumption Reporter can associate with
several Energy Consumers/ Energy Consumption meters
to aggregate the monitoring information
or which constitute power domain or meter domain,
(which still elude my understanding.)

In summary, the draft clarifies the overall energy management picture much
(surprised how quickly you turned out a draft from discussion)
and I wish the content would be integrated into eman work items
such as architecture draft.

Thanks for your kind consideration.

Best regards

JinHyeock Choi




On Tue, Nov 9, 2010 at 8:25 AM, Juergen Quittek <Quittek@neclab.eu> wrote:
> Dear all,
>
> The discussions on this list during the last days and in restaurants at t=
he
> last nights have been quite inspiring. Particularly my understanding of t=
he
> fundamental steps of energy management has improved.
>
> I tried to record some of the new insights in an Internet draft that I ju=
st
> posted. It suggests a more detailed reference model for energy management
> than we have it so far. Please find it at
> http://datatracker.ietf.org/doc/draft-quittek-eman-reference-model/
>
> This is just a contribution to the ongoing discussion. I have no intentio=
n
> of adding another document to our charter. The content of this draft will
> hopefully help understanding better what energy management is or could be=
.
>
> I know this draft arrives too late for discussing it during the session
> tomorrow. But we can do this on the list. Comments are highly appreciated=
.
>
> Thanks,
>
> =A0 =A0Juergen
>
>
> ------ Forwarded message
> From: IETF I-D Submission Tool <idsubmission@ietf.org>
> Date: Mon, 8 Nov 2010 14:49:27 -0800
> To: <quittek@neclab.eu>
> Subject: New Version Notification for =A0draft-quittek-eman-reference-mod=
el-00
>
>
> A new version of I-D, draft-quittek-eman-reference-model-00.txt has been
> successfully submitted by Juergen Quittek and posted to the IETF reposito=
ry.
>
> Filename: =A0draft-quittek-eman-reference-model
> Revision: =A000
> Title: =A0 Reference Model for Energy Management
> Creation_date: =A02010-11-08
> WG ID: =A0 Independent Submission
> Number_of_pages: 15
>
> Abstract:
> This memo discusses suggest a reference model for energy consumption
> monitoring and control. =A0It defines entities involved in energy
> management, their roles, and relationships between them. =A0Considered
> entities include energy consumers, energy consumption meters, energy
> consumption reporters, energy consumption controllers, and energy
> consumption management systems.
>
> The IETF Secretariat.
>
> ------ end of forwarded message
>
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman
>
>

From jparello@cisco.com  Tue Nov  9 00:40:30 2010
Return-Path: <jparello@cisco.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A3BDF3A696B for <eman@core3.amsl.com>; Tue,  9 Nov 2010 00:40:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K+0UQKoap6g4 for <eman@core3.amsl.com>; Tue,  9 Nov 2010 00:40:27 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id A08C53A680C for <eman@ietf.org>; Tue,  9 Nov 2010 00:40:26 -0800 (PST)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAK6X2EyrR7H+/2dsb2JhbACiHnGhQZtpgwQIgj4EhFiFfYMM
X-IronPort-AV: E=Sophos;i="4.59,174,1288569600"; d="scan'208";a="616929570"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-6.cisco.com with ESMTP; 09 Nov 2010 08:40:50 +0000
Received: from [130.129.64.91] (sjc-vpn3-811.cisco.com [10.21.67.43]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id oA98emcE002352; Tue, 9 Nov 2010 08:40:48 GMT
Message-ID: <4CD9090F.8000403@cisco.com>
Date: Tue, 09 Nov 2010 00:40:47 -0800
From: john parello <jparello@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: Chris Verges <chrisv@cyberswitching.com>
References: <C8EFF4A6.163CA%quittek@neclab.eu>	<4CCE3065.6050705@nteczone.com>	<68FBE0F3CE97264395875AC1C468F22C514765@mail03.cyberswitching.local>	<4CD0C560.7080907@nteczone.com>	<68FBE0F3CE97264395875AC1C468F22C5148AE@mail03.cyberswitching.local>	<4CD7A4AD.1040608@cisco.com> <68FBE0F3CE97264395875AC1C468F22C514A7F@mail03.cyberswitching.local>
In-Reply-To: <68FBE0F3CE97264395875AC1C468F22C514A7F@mail03.cyberswitching.local>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: eman@ietf.org
Subject: Re: [eman] Entity identification method
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Nov 2010 08:40:30 -0000

Hi Chris,

That is a very good point wrt the entity mib. Our draft calls for 
linking to the entity mib if present. You seem to be sayig that even if 
it is present you may do not want to link to it.

One question for the server power: would you want to report the 
aggragate or the remainder?

Example if you have 8 outlets and the server itself.  Wouldn't there be 
8 readings for the attached devices and then one reading for the server 
which is the draw of the PDU itself to function - albeit small.

For PoE switches that's our intent. We report the draw on each interface 
then the draw for the switch itself to operate.

Jp



On 11/8/10 7:10 AM, Chris Verges wrote:
> Hi Benoit,
>
> In Section 5.4, the "keywords" and/or "role" fields are perhaps the two
> that can *best* achieve the business context being described.  However,
> neither of these take into account the data reporting aspect.  For
> example:
>
> A server's redundant power supplies are connected to two different
> outlets on a smart power strip.  Each outlet is enumerated in the EMAN
> MIBs as separate entities, and the "role" is set to "server01",
> indicating that these outlets are linking in business context through
> the server's hostname.  (Use any other metric you want, the result is
> still the same.)  I know how much power each power supply is then
> drawing since the MIB splits the data out by outlet.  However, I do not
> know the aggregate power draw of the server itself, since there is no
> "server01" data entry.  There can't be, as there is no corresponding
> pmIndex for the server entity.  What's useful is to know all three
> datapoints: the power on supply A, the power on supply B, and the power
> on the server as a whole.  Yes, it should be a fairly straight-forward
> vector math calculation, but more complex scenarios could be crafted
> using three phase, automatic transfer switches, solar panels, etc.
>
> The point is that while the "role" and "keywords" fields can be used to
> establish business context for a particular entity in the MIB, I'm wary
> over whether they can be used to aggregate data or manage aggregated
> control over multiple entities being logically grouped together.  At
> least, given the current sparse table extension methodology behind the
> proposed set of MIBs.
>
> Perhaps mapping to ENTITY-MIB isn't required at this point.  What if
> power entities (POWER-ENTITY-MIB?) are separate from ENTITY-MIB
> entirely?  These two tables could later be mapped together through a
> separate set of tables to ENTITY-MIB, which would establish the ability
> for an M:N mapping between POWER-ENTITY-MIB and the physical and logical
> tables of ENTITY-MIB separately.  That would allow us to link the
> entities IF IT MAKES SENSE and in a way that makes sense.  But it's not
> part of the core definition of a power entity, in a more limited 1:1
> fashion.
>
> Thanks,
> Chris
>
> -----Original Message-----
> From: Benoit Claise [mailto:bclaise@cisco.com]
> Sent: Sunday, November 07, 2010 11:20 PM
> To: Chris Verges
> Cc: Christian Groves; eman@ietf.org
> Subject: Re: [eman] Entity identification method
>
> Hi Chris,
>
> Question: could the business context be used to achieve what you want
> to?
> See
> http://tools.ietf.org/html/draft-claise-power-management-arch-02#section
> -5.4
>
> Regards, Benoit
>> Hi Christian et al.,
>>
>> How about the following two use cases to augment the existing
>> power-allocation-per-virtual-machine scenario?
>>
>> 	1. "Grouped" outlets on a smart PDU
>>
>> 	2. Tenant submetering on a smart meter
>>
>> In the first scenario, several smart PDUs allow the user to create a
>> user-defined grouping that consists of several outlets.  Physical
>> outlets 1 and 7, for example, could be grouped together as logical
>> entity "server01".  This mapping could be created using the existing
>> ENTITY-MIB architecture.  The power data for both the physical and
>> logical entities are useful to facilities and IT managers to
>> understand power flow and usage.
>>
>> In the second scenario, a smart meter provides submetering for a
>> commercial rental building.  Such buildings often occur turnover in
>> tenants.  A submeter that meters each circuit in the building, for
>> example, could maintain that data in both granular and aggregate form.
>> When a tenant moves in, the facilities manager can create a new
>> logical entity for that tenant and map the physical circuit entries to
>
>> the tenant's logical entity.  This enables both real-time power usage
>> and management on an individual circuit basis (useful for
>> troubleshooting facilities problems) as well as on a customized
>> aggregate basis (useful for the bean counters who have to allocate
> costs).
>>
>> Here's an interesting question as far as implementation is concerned
> ...
>> why not implement pmPhysicalMap and pmLogicalMap tables (like
>> entLPMappingTable) to map the pmIndex entity to the appropriate
>> physical or logical entity (1:1 only?)
>>
>> Chris
>>
>>
>> -----Original Message-----
>> From: Christian Groves [mailto:Christian.Groves@nteczone.com]
>> Sent: Tuesday, November 02, 2010 7:14 PM
>> To: Chris Verges
>> Cc: eman@ietf.org
>> Subject: Re: [eman] Entity identification method
>>
>> Hello Chris,
>>
>> I don't have any concrete suggestions for implementing virtual entity
>> energy usage support. I'm still at the stage of trying to see what the
>
>> requirements and framework is for the work. There seems to be a focus
>> on the MIBs themselves, when without good requirements its hard to see
>
>> what needs they are meeting. The work of the eman WG could address IP
>> type servers only or the MIBs could also be used in other
>> telecommunication equipment i.e. those used in outside plant. I'm
>> encouraged to see Bruce's email on topics for discussion as think its
>> in important to get consensus/understanding on these before the MIBs
> are developed.
>>
>> Please see my comment below marked [CNG].
>>
>> Regards, Christian
>>
>> On 1/11/2010 11:39 PM, Chris Verges wrote:
>>> Hi Christian,
>>>
>>> Are you looking to allocate actual energy usage by a virtual entity,
>>> like the amount of energy used by a virtual machine running on a
>>> shared server? Certainly an interesting problem ... gives a lot of
>>> room for innovation for different vendors to find solutions.
>>>
>> [CNG] I agree its an interesting problem. In some instances it may be
>> possible to allocate the actual energy however in many cases it would
>> be very difficult/impossible. In these more difficult cases it may be
>> possible to simply report the identities of the virtual/logical
>> entities that are included in the physical measurement.
>>>    From a MIB standpoint, it seems like the requirement is to have a
>>> flexible power-related MIB that can either map to physical or logical
>
>>> entities. One question is, "where do you want those entities
>> enumerated?"
>>> Are virtual entities that need to be mapped to power usage normally
>>> enumerated in ENTITY-MIB in the "logical" table?
>>>
>>> If so, perhaps something like this would fit the bill:
>>>
>>> POWER-ENTITY-MIB:
>>>
>>> pwrEntityTable
>>>
>>> pwrEntityEntry
>>>
>>> pwrEntityIndex
>>>
>>> pwrEntityName
>>>
>>> pwrEntityType
>>>
>>> pwrEntityParent
>>>
>>> pwrEntityPhysical
>>>
>>> pwrEntityLogical
>>>
>>> The pwrEntity[Physical|Logical] objects would point to the
>>> appropriate index in ENTITY-MIB.
>>>
>>> However, if the virtual entities are not enumerated in ENTITY-MIB,
>>> the pwrEntityLogical column is probably overkill. The virtual
>>> entities can be enumerated in pwrEntityTable and linked to the
>>> Physical meter using the pwrEntityParent column, much like how
>>> ENTITY-MIB currently manages references between parent and component
>>> entities. It would just involve a new pwrEntityType being added for
>>> "virtual" or something similar.
>>>
>>> So what's the typical use case as these virtual entities relate to
>>> ENTITY-MIB?
>>>
>> [CNG] I'm not sure the typical case. Either of the approaches above
>> could be sufficient but I think it depends on what people agree on
>> with respect to virtual entities and how the data collected on them
>> would be used.
>>> Chris
>>>
>>> -----Original Message-----
>>> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf
>>> Of Christian Groves
>>> Sent: Sunday, October 31, 2010 8:14 PM
>>> To: eman@ietf.org
>>> Subject: Re: [eman] Entity identification method
>>>
>>> Hello Juergen,
>>>
>>> I think distinguishing the two cases is the correct way to go.
>>>
>>> I agree that reporting energy consumption for logical entities is a
>>> challenge and not straight forward. I guess there are a number of
>>> ways to look at this problem and how address the problem depends on
>>> the ambition level.
>>>
>>> As you rightly mention where there is partial use of a physical
>>> resource by a logical entity it is very difficult to have an exact
>>> figure.
>>>
>>> However I think the "grain size" of the measurement comes into play.
>>> For example if we have a large gateway implementing several virtual
>>> gateways if we take an overall measurement then we have the problem
>>> determining a figure. If the however the virtual gateways were each
>>> assigned a physical rack and the measurements were taken at a rack
>>> level then we have a more precise estimate of contribution of each
>>> virtual gateway to the overall picture.
>>>
>>> For me logical entities ultimately will be realised by physical
>>> hardware. The key is understanding the relationship between these
>>> entities. Thus I think virtualization can in some way be supported by
>
>>> allowing energy consumption reports for physical entities to indicate
>
>>> if/what logical entities they relate to. As they say information is
>>> power (pardon the pun :-) ).
>>>
>>> Regards, Christian
>>>
>>> On 29/10/2010 12:48 PM, Juergen Quittek wrote:
>>>
>>>> Hi Christian,
>>>> Thank you for this interesting comment.
>>>> It looks like we have to distinguish two cases: power state
>>>> monitoring and energy consumption monitoring.
>>>> For a logical entity and a virtual machine it may be well possible
>>>> to report on their power state. However, reporting their energy
>>>> consumption seems to be a tough challenge at least if be base it on
>>> real measurements.
>>>
>>>> It is well feasible to measure energy consumption of physical
>>>> entities, but if you have a logical entity that consumes only
>>>> partial resources of a physical entity, then precise measurement of
>>>> the energy consumption will be hardly possible. Estimations may be
>>>> possible based on a model of the logical entity, but I don't know
>>>> how good such
>>> models can be.
>>>
>>>> Thanks,
>>>> Juergen
>>>> On 29.10.10 03:25 "Christian Groves"<Christian.Groves@nteczone.com
>>> <mailto:Christian.Groves@nteczone.com>>   wrote:
>>>
>>>>> Hello
>>>>> I've just started to digest the various drafts of the eman wg and I
>>>>> see the comment below on logical entities. It's not clear to me
>>>>> how/if network virtualization is intended on being handled in the
>>> eman work.
>>>
>>>>> In networks there's now a trend towards network virtualization and
>>>>> cloud computing with the different "X" as a service models (i.e.
>>>>> Amazon EC2 "platform as a service" running different server
>>>>> instances). Even in today's networks we have physical gateways that
>>>>> are virtualized into different logical gateways. For example:
>>>>> H.248/Megaco virtual MG (VMG) concept.
>>>>> I think it would be advantageous to be able to assess the energy
>>>>> consumption of the VMGs or instances (which are logical entities)
>>>>> independent of the physical gateway so that a customers energy use
>>>>> may be recording. Will this sort of functionality be allowed?
>>>>> Regards, Christian
>>>>> On 29/10/2010 1:22 AM, Juergen Quittek wrote:
>>>>>> Hi Chris,
>>>>>> I think it may become very difficult if we want to assess energy
>>>>>> consumption of logical entities. It seems to be reasonable and
>>>>>> practical to limit energy consumption measurements to physical
>>>>>> entities. The ENERGY AWARE MIB module
>>>>>> (draft-parello-eman-energy-aware-mib) and the POWER MIB
>>>>>> (draft-quittek-power-mib-02) went this way.
>>>>>> Just using entPhysicalIndex solves some of the problem you
>> mentioned.
>>>>>> Particularly, you don't need a mapping table to entities if you
>>>>>> restrict Yourself to entPhysicalIndex.
>>>>>> Thanks,
>>>>>> Juergen
>>>>>> On 28.10.10 13:34 "Chris Verges"<chrisv@cyberswitching.com
>>> <mailto:chrisv@cyberswitching.com>>   wrote:
>>>
>>>>>>> Hi Jurgen and all,
>>>>>>> The more I've been thinking about these scenarios, the more
>>>>>>> something doesn't seem quite right. I'll try to explain my
>>>>>>> thought
>>>>>>> process behind this and see if my concerns/confusions get
>> captured.
>>>>>>> ENTITY-MIB provides enumerated lists of physical and logical
>>>>>>> entities on the system. The indices in both lists are maintained
>>>>>>> separately, so there is not a single, unique identifier provided.
>>>>>>> Because of this, the MIBs being discussed by the EMAN WG must
>>>>>>> only
>>>>>>> reference to one type (physical or logical) and are limited to
>>> that without additional work.
>>>
>>>>>>> At some point in my mind, I'm asking myself the question, "What's
>>>>>>> the point of linking to ENTITY-MIB?"
>>>>>>> More on that question in later scenarios below ...
>>>>>>> One possibility would be to create a separate mapping table that
>>>>>>> gives a guaranteed unique index based on all entities, regardless
>>>>>>> of type. The physical vs. logical extensions would then become
>>>>>>> sparse tables that augment this. For example:
>>>>>>> ENTITY-MIB : entityGeneral.entGeneralTable.entGeneralEntry
>>>>>>> +-----------------+-----------------+-----+
>>>>>>> | entGeneralIndex | entGeneralDescr | ... |
>>>>>>> +-----------------+-----------------+-----+
>>>>>>> | 1 | PDU Chassis | |
>>>>>>> +-----------------+-----------------+-----+
>>>>>>> | 2 | Meter #1 | |
>>>>>>> +-----------------+-----------------+-----+
>>>>>>> | 3 | Meter #2 | |
>>>>>>> +-----------------+-----------------+-----+
>>>>>>> | 4 | Remote Meter #1 | |
>>>>>>> +-----------------+-----------------+-----+
>>>>>>> ENTITY-MIB : entityPhysical.entPhysicalTable.entPhysicalEntry
>>>>>>> +-----------------+-----------------+-----+
>>>>>>> | entGeneralIndex | entVendorType | ... |
>>>>>>> +-----------------+-----------------+-----+
>>>>>>> | 1 | enterprises.foo | |
>>>>>>> +-----------------+-----------------+-----+
>>>>>>> | 2 | enterprises.foo | |
>>>>>>> +-----------------+-----------------+-----+
>>>>>>> | 3 | enterprises.foo | |
>>>>>>> +-----------------+-----------------+-----+
>>>>>>> ENTITY-MIB : entityLogical.entLogicalTable.entLogicalEntry
>>>>>>> +-----------------+----------------------+-----+
>>>>>>> | entGeneralIndex | entLogicalCommunity | ... |
>>>>>>> +-----------------+----------------------+-----+
>>>>>>> | 4 | remote-power-group-1 | |
>>>>>>> +-----------------+----------------------+-----+
>>>>>>> It seems like this 'entGeneralIndex' concept is what's missing
>>>>>>> from
>>>>>>> the current ENTITY-MIB, and is causing problems when thinking
>>>>>>> about
>>>>>>> local and remote power data being reported by the same agent.
>>>>>>> Another possibility would be to choose one -- entLogicalIndex,
>>>>>>> most
>>>>>>> likely -- and require that anyone who wants to implement the EMAN
>>>>>>> WG MIBs to always create an entLogicalEntry for the power data.
>>>>>>> In
>>>>>>> this context, the entLogicalTable fills the role of
>>>>>>> entGeneralTable
>>>>>>> as described above. For all entPhysicalTable entries, there would
>>>>>>> need to be a corresponding entry in entLogicalTable with a 1:1
>>>>>>> mapping between them. For all remote entries, there would be a
>>>>>>> unique entry in entLogicalTable. Of course, this would add some
>>>>>>> additional overhead on the part of the implementer, but isn't too
>>> overburdening.
>>>
>>>>>>> A third possibility is that ENTITY-MIB just doesn't do what we
>>>>>>> need
>>>>>>> in its present form and we need to think about enumerating power
>>>>>>> sensors separately from other components/sensors on the system.
>>>>>>> It
>>>>>>> seems like entPhysicalTable gives a good starting template for a
>>>>>>> new 'POWER-ENTITY-MIB', but can be extended to include support
>>>>>>> for
>>>>>>> remote agents. The difference would be a clean break from the
>>>>>>> legacy ENTITY-MIB structure.
>>>>>>> And with that, I look forward to others' feedback and ideas on
>>>>>>> solving this problem!
>>>>>>> Thanks,
>>>>>>> Chris
>>>>>>> -----Original Message-----
>>>>>>> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On
>>>>>>> Behalf Of Chris Verges
>>>>>>> Sent: Tuesday, October 26, 2010 9:26 PM
>>>>>>> To: Juergen Quittek; Benoit Claise; eman mailing list
>>>>>>> Subject: Re: [eman] Entity identification method (was: EMAN
>>>>>>> chartered itemsversus drafts)
>>>>>>> Hi Juergen and all,
>>>>>>> Agreed that a common ID method makes sense, and ENTITY-MIB seems
>>>>>>> to
>>>>>>> be a good choice. In case (c) from your list, wouldn't the remote
>>>>>>> agent condition be handled by ENTITY-MIB supporting a logical
>>>>>>> entity that is the remote agent iself? Since the logical entity
>>>>>>> is
>>>>>>> in the ENTITY-MIB table, it would be given a unique ID mixed
>>>>>>> amongst the other logical and physical entities.
>>>>>>> At that point, should all of the MIBs being discussed in the EMAN
>>>>>>> WG be sparse table augmentations of ENTITY-MIB?
>>>>>>> Thanks,
>>>>>>> Chris
>>>>>>> -----Original Message-----
>>>>>>> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On
>>>>>>> Behalf Of Juergen Quittek
>>>>>>> Sent: Tuesday, October 26, 2010 6:01 AM
>>>>>>> To: Benoit Claise; eman mailing list
>>>>>>> Subject: [eman] Entity identification method (was: EMAN chartered
>>>>>>> items versus drafts)
>>>>>>> Hi Benoit and all,
>>>>>>> I agree that we should find a common identification method for
>>>>>>> entities used by all MIB modules. This does not apply to the
>>>>>>> POWER
>>>>>>> MIB only, but to all MIB modules in the eman WG.
>>>>>>> The modules will use an entity ID as index for their tables.
>>>>>>> Which entity is identified by the index can be resolved by other
>>>>>>> MIB modules, such as the POWER AWARE MIB module
>>>>>>> (draft-parello-eman-energy-aware-mib) or the ENTITY MIB module
>>>>>>> (RFC
>>>>>>> 4133).
>>>>>>> I see three basic scenarios for the entity identification:
>>>>>>> a) a device just reports on its own power state and energy
>>>>>>> consumption and it reports on its own as a single unit.
>>>>>>> Then we have a single index only stating "it's me".
>>>>>>> Such a device usually does not need further identification
>>>>>>> of itself, because typically there are sufficient other
>>>>>>> MIB modules for this purpose running in the same SNMP engine,
>>>>>>> that provide information about the device's IP address,
>>>>>>> manufacturer, operating system, etc. In such a case a
>>>>>>> 'trivial' index, such as '0' should be used in order to
>>>>>>> keep it simple in this most simple case.
>>>>>>> b) a device reports on its own but not just as a single unit
>>>>>>> but it reports power states and energy consumption for its
>>>>>>> individual components, for example it may report separately
>>>>>>> on contained hard drives, line cards, back planes,
>>>>>>> processor boards, etc.
>>>>>>> In such a case, identification of these components as
>>>>>>> individual entities would be required. The ENTITY MIB
>>>>>>> module was designed for this purpose and would be a good
>>>>>>> choice here. Also the POWER AWARE MIB module would be
>>>>>>> useful in this case.
>>>>>>> c) a device reports on energy consumption of other, remote
>>>>>>> devices. Then remote devices (and potentially also their
>>>>>>> contained components need to be identified. For
>>>>>>> identifying remote components there is the POWER AWARE MIB
>>>>>>> module that has been designed for this purpose. As far as
>>>>>>> I understand, the ENTITY MIB module is not applicable to
>>>>>>> remote devices.
>>>>>>> In summary,
>>>>>>> - if you need to report on remote entities (case c)),
>>>>>>> you need the POWER AWARE MIB module,
>>>>>>> - if you report only on entities locally contained
>>>>>>> in the reporting device (case b)), you can use
>>>>>>> the POWER AWARE MIB or the ENTITY MIB
>>>>>>> - if you report just on your own as a single device
>>>>>>> (case a)), identification is trivial
>>>>>>> Hence, my recommendation (stated for POWER-STATE MIB and ENERGY
>>>>>>> MIB
>>>>>>> in
>>>>>>> draft-quittek-power-mib-02) would be:
>>>>>>> If there is an implementation of the POWER AWARE MIB module
>>>>>>> instantiated in the local SNMP engine, then you SHOULD (or MUST?)
>>>>>>> use it for indexing (pmIndex).
>>>>>>> If this is not the case but there is an ENTITY MIB instance
>>>>>>> available, then you SHOULD use this one (entPhysicalIndex).
>>>>>>> If neither of this MIB modules is available you should use index
>>>>>>> 0
>>>>>>> only and be limited to report on the local device as a single
>>> entity only.
>>>
>>>>>>> That's just my view. Certainly, there are more ways of entity
>>>>>>> identification. I look forward to discussing them.
>>>>>>> Thanks,
>>>>>>> Juergen
>>>>>>> On 26.10.10 11:44 "Benoit Claise"<bclaise@cisco.com
>>> <mailto:bclaise@cisco.com>>   wrote:
>>>
>>>>>>>> Hi Juergen,
>>>>>>>> Thanks for the clarification.
>>>>>>>> Something key is to agree on the Power Monitor index for all MIB
>>>>>>>> modules, which IMHO should be part of the Energy-aware Networks
>>>>>>>> and Devices MIB module, but reuse in the other MIB modules.
>>>>>>>> Regards, Benoit.
>>>>>>>>> Hi Benoit,
>>>>>>>>> Thanks for checking all drafts.
>>>>>>>>> I don't think that draft-quittek-power-mib-02 makes significant
>>>>>>>>> contributions to the Energy-aware Networks and Devices MIB.
>>>>>>>>> It just covers the Power and Energy Monitoring MIB and the
>>>>>>>>> Battery
>>>>>>> MIB.
>>>>>>>>> Thanks,
>>>>>>>>> Juergen
>>>>>>>>> On 26.10.10 08:22 "Benoit Claise"<bclaise@cisco.com
>>> <mailto:bclaise@cisco.com>>   wrote:
>>>
>>>>>>>>>> Dear all,
>>>>>>>>>> I went through the exercise of mapping the existing six
>>>>>>>>>> chartered items with the existing draft content.
>>>>>>>>>> _Energy Management Requirements_
>>>>>>>>>> http://tools.ietf.org/html/draft-quittek-power-monitoring-requ
>>>>>>>>>> ir
>>>>>>>>>> emen
>>>>>>>>>> ts-02
>>>>>>>>>> https://datatracker.ietf.org/doc/draft-norwin-energy-consider/
>>>>>>>>>> _
>>>>>>>>>> Energy Management Framework_
>>>>>>>>>> http://tools.ietf.org/html/draft-claise-power-management-arch-
>>>>>>>>>> 02
>>>>>>>>>> _Energy-aware Networks and Devices MIB_
>>>>>>>>>> http://tools.ietf.org/html/draft-parello-eman-energy-aware-mib
>>>>>>>>>> -0
>>>>>>>>>> 0
>>>>>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>>>>>>>>>> _Power and Energy Monitoring MIB_
>>>>>>>>>> http://tools.ietf.org/html/draft-claise-energy-monitoring-mib-
>>>>>>>>>> 06
>>>>>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>>>>>>>>>> _Battery MIB_
>>>>>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02
>>>>>>>>>> _Energy Management Applicability_
>>>>>>>>>> http://datatracker.ietf.org/doc/draft-tychon-eman-applicabilit
>>>>>>>>>> y-
>>>>>>>>>> stat
>>>>>>>>>> ement/
>>>>>>>>>> Please let me know if I made any mistakes or if I missed any
>>> draft?
>>>
>>>>>>>>>> Regards, Benoit.
>>>>>>>>>> _______________________________________________
>>>>>>>>>> eman mailing list
>>>>>>>>>> eman@ietf.org<mailto:eman@ietf.org>
>>>>>>>>>> https://www.ietf.org/mailman/listinfo/eman
>>>>>>> _______________________________________________
>>>>>>> eman mailing list
>>>>>>> eman@ietf.org<mailto:eman@ietf.org>
>>>>>>> https://www.ietf.org/mailman/listinfo/eman
>>>>>> _______________________________________________
>>>>>> eman mailing list
>>>>>> eman@ietf.org<mailto:eman@ietf.org>
>>>>>> https://www.ietf.org/mailman/listinfo/eman
>>>>> _______________________________________________
>>>>> eman mailing list
>>>>> eman@ietf.org<mailto:eman@ietf.org>
>>>>> https://www.ietf.org/mailman/listinfo/eman
>>>> _______________________________________________
>>>> eman mailing list
>>>> eman@ietf.org<mailto:eman@ietf.org>
>>>> https://www.ietf.org/mailman/listinfo/eman
>>> _______________________________________________
>>>
>>> eman mailing list
>>>
>>> eman@ietf.org<mailto:eman@ietf.org>
>>>
>>> https://www.ietf.org/mailman/listinfo/eman
>>>
>> _______________________________________________
>> eman mailing list
>> eman@ietf.org
>> https://www.ietf.org/mailman/listinfo/eman
>
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman
>

From chrisv@cyberswitching.com  Tue Nov  9 06:42:00 2010
Return-Path: <chrisv@cyberswitching.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6E8C13A69DE for <eman@core3.amsl.com>; Tue,  9 Nov 2010 06:41:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7zSZa9LwCUVn for <eman@core3.amsl.com>; Tue,  9 Nov 2010 06:40:38 -0800 (PST)
Received: from p01c12o142.mxlogic.net (p01c12o142.mxlogic.net [208.65.145.65]) by core3.amsl.com (Postfix) with ESMTP id 1AF993A69CE for <eman@ietf.org>; Tue,  9 Nov 2010 06:40:34 -0800 (PST)
Received: from unknown [64.81.28.110] (EHLO mail03.cyberswitching.local) by p01c12o142.mxlogic.net(mxl_mta-6.7.0-2) with ESMTP id b7d59dc4.0.072.00-385.143.p01c12o142.mxlogic.net (envelope-from <chrisv@cyberswitching.com>);  Tue, 09 Nov 2010 07:40:59 -0700 (MST)
X-MXL-Hash: 4cd95d7b7571bd92-1a67d494f138b3127506c1ea80c3fb50f97efd26
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB801B.FCBA3AF3"
Date: Tue, 9 Nov 2010 06:40:00 -0800
Message-ID: <68FBE0F3CE97264395875AC1C468F22C514B19@mail03.cyberswitching.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [eman] Entity identification method
Thread-Index: Act/6bTCY0tSnqaURb2ObUAPtq5s5AAMMrWg
References: <C8EFF4A6.163CA%quittek@neclab.eu>	<4CCE3065.6050705@nteczone.com>	<68FBE0F3CE97264395875AC1C468F22C514765@mail03.cyberswitching.local>	<4CD0C560.7080907@nteczone.com>	<68FBE0F3CE97264395875AC1C468F22C5148AE@mail03.cyberswitching.local>	<4CD7A4AD.1040608@cisco.com> <68FBE0F3CE97264395875AC1C468F22C514A7F@mail03.cyberswitching.local> <4CD9090F.8000403@cisco.com>
From: "Chris Verges" <chrisv@cyberswitching.com>
To: "john parello" <jparello@cisco.com>
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010110201)]
X-MAIL-FROM: <chrisv@cyberswitching.com>
X-SOURCE-IP: [64.81.28.110]
X-AnalysisOut: [v=1.0 c=1 a=aPxnrr7mnCkA:10 a=BLceEmwcHowA:10 a=4zsJQXJisS]
X-AnalysisOut: [Y22NXBO5KRuA==:17 a=AUd_NHdVAAAA:8 a=48vgC7mUAAAA:8 a=r3s3]
X-AnalysisOut: [_62XAAAA:8 a=wzgqfsuUAAAA:8 a=6FpkYD1kYuImA2NAn_AA:9 a=gGF]
X-AnalysisOut: [e1kwlWqPMCtmuAv4A:7 a=nmDqWX79CNUX0eZvI7nTYY47QmEA:4 a=wPN]
X-AnalysisOut: [LvfGTeEIA:10 a=JfD0Fch1gWkA:10 a=lZB815dzVvQA:10 a=3wXEbym]
X-AnalysisOut: [kWtoA:10 a=yvfu_RGVus0A:10 a=M-FevMlSht7c5fNo:21 a=MIe8rxT]
X-AnalysisOut: [sxi1JUOBb:21 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=NkCd_AtNj]
X-AnalysisOut: [MSHyXjua-8A:9 a=1s1AfUsn3ZD5JCZBnYYA:7 a=NadYz4YpmC0xfx0BR]
X-AnalysisOut: [fHD7MUG4OUA:4 a=s-P30tsjCp73QWuv:21 a=dfhbKnFPl8th8AV-:21]
Cc: eman@ietf.org
Subject: Re: [eman] Entity identification method
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Nov 2010 14:42:00 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB801B.FCBA3AF3
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi John,

=20

Here's an example of what I'd ideally report, indented to show =
parent/child relationships between the entities:

=20

POWER-ENTITY-MIB:

=B7         Cyber Switching ePower "Smart PDU"

o    Three Phase Input #1

=A7  Single Phase Bank #1

=B7         Single Phase Outlet #1

=B7         Single Phase Outlet #2

=B7         ...

=A7  Single Phase Bank #2

=B7         Single Phase Outlet #9

=B7         Single Phase Outlet #10

=B7         ...

=A7  ...

o    ...

=B7         Server01

=20

Note that "Server01" is a separate entity hierarchy from the ePower PDU =
itself.  In this example, let's say that Server01 points to Outlets #1 =
and #9, meaning the redundant power supplies on server01 are being =
powered by those physical outlets.  Server01 is, in effect, a "logical" =
entity from the perspective of the MIB that is representing a "physical" =
entity in the real world.

=20

To simplify management, I'd report actual power metered on the ePower =
PDU hierarchy (the PDU itself, the inputs, the banks, and the outlets) =
AND aggregated power metered on the Server01 entity.  So if Outlet 1 and =
Outlet 9 report 2.5 A each, I'd aggregate that to 5.0 A for the Server01 =
entity.  (I'm using Amperage as an example only; a solution should not =
be limited to only that data type.)

=20

There could even be a "logical-to-physical" mapping table like is in =
ENTITY-MIB.  The main difference, however, is that there wouldn't need =
to be a second table to separate logical and physical entities from each =
other.  That breakdown is just inane, I think.  Add a column that is the =
pmEntityType (or whatever name is appropriate) that distinguishes =
whether this entity is physical(1) or logical(2) or ....

=20

But yes, your initial summary is my main point.  With regards to linking =
to ENTITY-MIB, we should only link to it IF IT MAKES SENSE FOR OUR =
PRODUCT.  (Emphasis added, not meaning to "yell.")  By splitting this =
linkage out to tables, we can enhance the flexibility of the framework.

=20

Thanks,

Chris

=20

-----Original Message-----
From: john parello [mailto:jparello@cisco.com]=20
Sent: Tuesday, November 09, 2010 12:41 AM
To: Chris Verges
Cc: eman@ietf.org
Subject: Re: [eman] Entity identification method

=20

Hi Chris,

=20

That is a very good point wrt the entity mib. Our draft calls for =
linking to the entity mib if present. You seem to be sayig that even if =
it is present you may do not want to link to it.

=20

One question for the server power: would you want to report the =
aggragate or the remainder?

=20

Example if you have 8 outlets and the server itself.  Wouldn't there be

8 readings for the attached devices and then one reading for the server =
which is the draw of the PDU itself to function - albeit small.

=20

For PoE switches that's our intent. We report the draw on each interface =
then the draw for the switch itself to operate.

=20

Jp

=20

=20

=20

On 11/8/10 7:10 AM, Chris Verges wrote:

> Hi Benoit,

>=20

> In Section 5.4, the "keywords" and/or "role" fields are perhaps the=20

> two that can *best* achieve the business context being described. =20

> However, neither of these take into account the data reporting aspect. =
=20

> For

> example:

>=20

> A server's redundant power supplies are connected to two different=20

> outlets on a smart power strip.  Each outlet is enumerated in the EMAN =


> MIBs as separate entities, and the "role" is set to "server01",=20

> indicating that these outlets are linking in business context through=20

> the server's hostname.  (Use any other metric you want, the result is=20

> still the same.)  I know how much power each power supply is then=20

> drawing since the MIB splits the data out by outlet.  However, I do=20

> not know the aggregate power draw of the server itself, since there is =


> no "server01" data entry.  There can't be, as there is no=20

> corresponding pmIndex for the server entity.  What's useful is to know =


> all three

> datapoints: the power on supply A, the power on supply B, and the=20

> power on the server as a whole.  Yes, it should be a fairly=20

> straight-forward vector math calculation, but more complex scenarios=20

> could be crafted using three phase, automatic transfer switches, solar =
panels, etc.

>=20

> The point is that while the "role" and "keywords" fields can be used=20

> to establish business context for a particular entity in the MIB, I'm=20

> wary over whether they can be used to aggregate data or manage=20

> aggregated control over multiple entities being logically grouped=20

> together.  At least, given the current sparse table extension=20

> methodology behind the proposed set of MIBs.

>=20

> Perhaps mapping to ENTITY-MIB isn't required at this point.  What if=20

> power entities (POWER-ENTITY-MIB?) are separate from ENTITY-MIB=20

> entirely?  These two tables could later be mapped together through a=20

> separate set of tables to ENTITY-MIB, which would establish the=20

> ability for an M:N mapping between POWER-ENTITY-MIB and the physical=20

> and logical tables of ENTITY-MIB separately.  That would allow us to=20

> link the entities IF IT MAKES SENSE and in a way that makes sense. =20

> But it's not part of the core definition of a power entity, in a more=20

> limited 1:1 fashion.

>=20

> Thanks,

> Chris

>=20

> -----Original Message-----

> From: Benoit Claise [mailto:bclaise@cisco.com]

> Sent: Sunday, November 07, 2010 11:20 PM

> To: Chris Verges

> Cc: Christian Groves; eman@ietf.org

> Subject: Re: [eman] Entity identification method

>=20

> Hi Chris,

>=20

> Question: could the business context be used to achieve what you want=20

> to?

> See

> http://tools.ietf.org/html/draft-claise-power-management-arch-02#secti =
<http://tools.ietf.org/html/draft-claise-power-management-arch-02#secti> =


> on

> -5.4

>=20

> Regards, Benoit

>> Hi Christian et al.,

>>=20

>> How about the following two use cases to augment the existing=20

>> power-allocation-per-virtual-machine scenario?

>>=20

>>     1. "Grouped" outlets on a smart PDU

>>=20

>>     2. Tenant submetering on a smart meter

>>=20

>> In the first scenario, several smart PDUs allow the user to create a=20

>> user-defined grouping that consists of several outlets.  Physical=20

>> outlets 1 and 7, for example, could be grouped together as logical=20

>> entity "server01".  This mapping could be created using the existing=20

>> ENTITY-MIB architecture.  The power data for both the physical and=20

>> logical entities are useful to facilities and IT managers to=20

>> understand power flow and usage.

>>=20

>> In the second scenario, a smart meter provides submetering for a=20

>> commercial rental building.  Such buildings often occur turnover in=20

>> tenants.  A submeter that meters each circuit in the building, for=20

>> example, could maintain that data in both granular and aggregate =
form.

>> When a tenant moves in, the facilities manager can create a new=20

>> logical entity for that tenant and map the physical circuit entries=20

>> to

>=20

>> the tenant's logical entity.  This enables both real-time power usage =


>> and management on an individual circuit basis (useful for=20

>> troubleshooting facilities problems) as well as on a customized=20

>> aggregate basis (useful for the bean counters who have to allocate

> costs).

>>=20

>> Here's an interesting question as far as implementation is concerned

> ...

>> why not implement pmPhysicalMap and pmLogicalMap tables (like

>> entLPMappingTable) to map the pmIndex entity to the appropriate=20

>> physical or logical entity (1:1 only?)

>>=20

>> Chris

>>=20

>>=20

>> -----Original Message-----

>> From: Christian Groves [mailto:Christian.Groves@nteczone.com]

>> Sent: Tuesday, November 02, 2010 7:14 PM

>> To: Chris Verges

>> Cc: eman@ietf.org

>> Subject: Re: [eman] Entity identification method

>>=20

>> Hello Chris,

>>=20

>> I don't have any concrete suggestions for implementing virtual entity =


>> energy usage support. I'm still at the stage of trying to see what=20

>> the

>=20

>> requirements and framework is for the work. There seems to be a focus =


>> on the MIBs themselves, when without good requirements its hard to=20

>> see

>=20

>> what needs they are meeting. The work of the eman WG could address IP =


>> type servers only or the MIBs could also be used in other=20

>> telecommunication equipment i.e. those used in outside plant. I'm=20

>> encouraged to see Bruce's email on topics for discussion as think its =


>> in important to get consensus/understanding on these before the MIBs

> are developed.

>>=20

>> Please see my comment below marked [CNG].

>>=20

>> Regards, Christian

>>=20

>> On 1/11/2010 11:39 PM, Chris Verges wrote:

>>> Hi Christian,

>>>=20

>>> Are you looking to allocate actual energy usage by a virtual entity, =


>>> like the amount of energy used by a virtual machine running on a=20

>>> shared server? Certainly an interesting problem ... gives a lot of=20

>>> room for innovation for different vendors to find solutions.

>>>=20

>> [CNG] I agree its an interesting problem. In some instances it may be =


>> possible to allocate the actual energy however in many cases it would =


>> be very difficult/impossible. In these more difficult cases it may be =


>> possible to simply report the identities of the virtual/logical=20

>> entities that are included in the physical measurement.

>>>    From a MIB standpoint, it seems like the requirement is to have a =


>>> flexible power-related MIB that can either map to physical or=20

>>> logical

>=20

>>> entities. One question is, "where do you want those entities

>> enumerated?"

>>> Are virtual entities that need to be mapped to power usage normally=20

>>> enumerated in ENTITY-MIB in the "logical" table?

>>>=20

>>> If so, perhaps something like this would fit the bill:

>>>=20

>>> POWER-ENTITY-MIB:

>>>=20

>>> pwrEntityTable

>>>=20

>>> pwrEntityEntry

>>>=20

>>> pwrEntityIndex

>>>=20

>>> pwrEntityName

>>>=20

>>> pwrEntityType

>>>=20

>>> pwrEntityParent

>>>=20

>>> pwrEntityPhysical

>>>=20

>>> pwrEntityLogical

>>>=20

>>> The pwrEntity[Physical|Logical] objects would point to the=20

>>> appropriate index in ENTITY-MIB.

>>>=20

>>> However, if the virtual entities are not enumerated in ENTITY-MIB,=20

>>> the pwrEntityLogical column is probably overkill. The virtual=20

>>> entities can be enumerated in pwrEntityTable and linked to the=20

>>> Physical meter using the pwrEntityParent column, much like how=20

>>> ENTITY-MIB currently manages references between parent and component =


>>> entities. It would just involve a new pwrEntityType being added for=20

>>> "virtual" or something similar.

>>>=20

>>> So what's the typical use case as these virtual entities relate to=20

>>> ENTITY-MIB?

>>>=20

>> [CNG] I'm not sure the typical case. Either of the approaches above=20

>> could be sufficient but I think it depends on what people agree on=20

>> with respect to virtual entities and how the data collected on them=20

>> would be used.

>>> Chris

>>>=20

>>> -----Original Message-----

>>> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf =


>>> Of Christian Groves

>>> Sent: Sunday, October 31, 2010 8:14 PM

>>> To: eman@ietf.org

>>> Subject: Re: [eman] Entity identification method

>>>=20

>>> Hello Juergen,

>>>=20

>>> I think distinguishing the two cases is the correct way to go.

>>>=20

>>> I agree that reporting energy consumption for logical entities is a=20

>>> challenge and not straight forward. I guess there are a number of=20

>>> ways to look at this problem and how address the problem depends on=20

>>> the ambition level.

>>>=20

>>> As you rightly mention where there is partial use of a physical=20

>>> resource by a logical entity it is very difficult to have an exact=20

>>> figure.

>>>=20

>>> However I think the "grain size" of the measurement comes into play.

>>> For example if we have a large gateway implementing several virtual=20

>>> gateways if we take an overall measurement then we have the problem=20

>>> determining a figure. If the however the virtual gateways were each=20

>>> assigned a physical rack and the measurements were taken at a rack=20

>>> level then we have a more precise estimate of contribution of each=20

>>> virtual gateway to the overall picture.

>>>=20

>>> For me logical entities ultimately will be realised by physical=20

>>> hardware. The key is understanding the relationship between these=20

>>> entities. Thus I think virtualization can in some way be supported=20

>>> by

>=20

>>> allowing energy consumption reports for physical entities to=20

>>> indicate

>=20

>>> if/what logical entities they relate to. As they say information is=20

>>> power (pardon the pun :-) ).

>>>=20

>>> Regards, Christian

>>>=20

>>> On 29/10/2010 12:48 PM, Juergen Quittek wrote:

>>>=20

>>>> Hi Christian,

>>>> Thank you for this interesting comment.

>>>> It looks like we have to distinguish two cases: power state=20

>>>> monitoring and energy consumption monitoring.

>>>> For a logical entity and a virtual machine it may be well possible=20

>>>> to report on their power state. However, reporting their energy=20

>>>> consumption seems to be a tough challenge at least if be base it on

>>> real measurements.

>>>=20

>>>> It is well feasible to measure energy consumption of physical=20

>>>> entities, but if you have a logical entity that consumes only=20

>>>> partial resources of a physical entity, then precise measurement of =


>>>> the energy consumption will be hardly possible. Estimations may be=20

>>>> possible based on a model of the logical entity, but I don't know=20

>>>> how good such

>>> models can be.

>>>=20

>>>> Thanks,

>>>> Juergen

>>>> On 29.10.10 03:25 "Christian Groves"<Christian.Groves@nteczone.com

>>> <mailto:Christian.Groves@nteczone.com =
<mailto:Christian.Groves@nteczone.com> >>   wrote:

>>>=20

>>>>> Hello

>>>>> I've just started to digest the various drafts of the eman wg and=20

>>>>> I see the comment below on logical entities. It's not clear to me=20

>>>>> how/if network virtualization is intended on being handled in the

>>> eman work.

>>>=20

>>>>> In networks there's now a trend towards network virtualization and =


>>>>> cloud computing with the different "X" as a service models (i.e.

>>>>> Amazon EC2 "platform as a service" running different server=20

>>>>> instances). Even in today's networks we have physical gateways=20

>>>>> that are virtualized into different logical gateways. For example:

>>>>> H.248/Megaco virtual MG (VMG) concept.

>>>>> I think it would be advantageous to be able to assess the energy=20

>>>>> consumption of the VMGs or instances (which are logical entities)=20

>>>>> independent of the physical gateway so that a customers energy use =


>>>>> may be recording. Will this sort of functionality be allowed?

>>>>> Regards, Christian

>>>>> On 29/10/2010 1:22 AM, Juergen Quittek wrote:

>>>>>> Hi Chris,

>>>>>> I think it may become very difficult if we want to assess energy=20

>>>>>> consumption of logical entities. It seems to be reasonable and=20

>>>>>> practical to limit energy consumption measurements to physical=20

>>>>>> entities. The ENERGY AWARE MIB module

>>>>>> (draft-parello-eman-energy-aware-mib) and the POWER MIB

>>>>>> (draft-quittek-power-mib-02) went this way.

>>>>>> Just using entPhysicalIndex solves some of the problem you

>> mentioned.

>>>>>> Particularly, you don't need a mapping table to entities if you=20

>>>>>> restrict Yourself to entPhysicalIndex.

>>>>>> Thanks,

>>>>>> Juergen

>>>>>> On 28.10.10 13:34 "Chris Verges"<chrisv@cyberswitching.com

>>> <mailto:chrisv@cyberswitching.com <mailto:chrisv@cyberswitching.com> =
>>   wrote:

>>>=20

>>>>>>> Hi Jurgen and all,

>>>>>>> The more I've been thinking about these scenarios, the more=20

>>>>>>> something doesn't seem quite right. I'll try to explain my=20

>>>>>>> thought process behind this and see if my concerns/confusions=20

>>>>>>> get

>> captured.

>>>>>>> ENTITY-MIB provides enumerated lists of physical and logical=20

>>>>>>> entities on the system. The indices in both lists are maintained =


>>>>>>> separately, so there is not a single, unique identifier =
provided.

>>>>>>> Because of this, the MIBs being discussed by the EMAN WG must=20

>>>>>>> only reference to one type (physical or logical) and are limited =


>>>>>>> to

>>> that without additional work.

>>>=20

>>>>>>> At some point in my mind, I'm asking myself the question,=20

>>>>>>> "What's the point of linking to ENTITY-MIB?"

>>>>>>> More on that question in later scenarios below ...

>>>>>>> One possibility would be to create a separate mapping table that =


>>>>>>> gives a guaranteed unique index based on all entities,=20

>>>>>>> regardless of type. The physical vs. logical extensions would=20

>>>>>>> then become sparse tables that augment this. For example:

>>>>>>> ENTITY-MIB : entityGeneral.entGeneralTable.entGeneralEntry

>>>>>>> +-----------------+-----------------+-----+

>>>>>>> | entGeneralIndex | entGeneralDescr | ... |

>>>>>>> +-----------------+-----------------+-----+

>>>>>>> | 1 | PDU Chassis | |

>>>>>>> +-----------------+-----------------+-----+

>>>>>>> | 2 | Meter #1 | |

>>>>>>> +-----------------+-----------------+-----+

>>>>>>> | 3 | Meter #2 | |

>>>>>>> +-----------------+-----------------+-----+

>>>>>>> | 4 | Remote Meter #1 | |

>>>>>>> +-----------------+-----------------+-----+

>>>>>>> ENTITY-MIB : entityPhysical.entPhysicalTable.entPhysicalEntry

>>>>>>> +-----------------+-----------------+-----+

>>>>>>> | entGeneralIndex | entVendorType | ... |

>>>>>>> +-----------------+-----------------+-----+

>>>>>>> | 1 | enterprises.foo | |

>>>>>>> +-----------------+-----------------+-----+

>>>>>>> | 2 | enterprises.foo | |

>>>>>>> +-----------------+-----------------+-----+

>>>>>>> | 3 | enterprises.foo | |

>>>>>>> +-----------------+-----------------+-----+

>>>>>>> ENTITY-MIB : entityLogical.entLogicalTable.entLogicalEntry

>>>>>>> +-----------------+----------------------+-----+

>>>>>>> | entGeneralIndex | entLogicalCommunity | ... |

>>>>>>> +-----------------+----------------------+-----+

>>>>>>> | 4 | remote-power-group-1 | |

>>>>>>> +-----------------+----------------------+-----+

>>>>>>> It seems like this 'entGeneralIndex' concept is what's missing=20

>>>>>>> from the current ENTITY-MIB, and is causing problems when=20

>>>>>>> thinking about local and remote power data being reported by the =


>>>>>>> same agent.

>>>>>>> Another possibility would be to choose one -- entLogicalIndex,=20

>>>>>>> most likely -- and require that anyone who wants to implement=20

>>>>>>> the EMAN WG MIBs to always create an entLogicalEntry for the=20

>>>>>>> power data.

>>>>>>> In

>>>>>>> this context, the entLogicalTable fills the role of=20

>>>>>>> entGeneralTable as described above. For all entPhysicalTable=20

>>>>>>> entries, there would need to be a corresponding entry in=20

>>>>>>> entLogicalTable with a 1:1 mapping between them. For all remote=20

>>>>>>> entries, there would be a unique entry in entLogicalTable. Of=20

>>>>>>> course, this would add some additional overhead on the part of=20

>>>>>>> the implementer, but isn't too

>>> overburdening.

>>>=20

>>>>>>> A third possibility is that ENTITY-MIB just doesn't do what we=20

>>>>>>> need in its present form and we need to think about enumerating=20

>>>>>>> power sensors separately from other components/sensors on the=20

>>>>>>> system.

>>>>>>> It

>>>>>>> seems like entPhysicalTable gives a good starting template for a =


>>>>>>> new 'POWER-ENTITY-MIB', but can be extended to include support=20

>>>>>>> for remote agents. The difference would be a clean break from=20

>>>>>>> the legacy ENTITY-MIB structure.

>>>>>>> And with that, I look forward to others' feedback and ideas on=20

>>>>>>> solving this problem!

>>>>>>> Thanks,

>>>>>>> Chris

>>>>>>> -----Original Message-----

>>>>>>> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On=20

>>>>>>> Behalf Of Chris Verges

>>>>>>> Sent: Tuesday, October 26, 2010 9:26 PM

>>>>>>> To: Juergen Quittek; Benoit Claise; eman mailing list

>>>>>>> Subject: Re: [eman] Entity identification method (was: EMAN=20

>>>>>>> chartered itemsversus drafts) Hi Juergen and all, Agreed that a=20

>>>>>>> common ID method makes sense, and ENTITY-MIB seems to be a good=20

>>>>>>> choice. In case (c) from your list, wouldn't the remote agent=20

>>>>>>> condition be handled by ENTITY-MIB supporting a logical entity=20

>>>>>>> that is the remote agent iself? Since the logical entity is in=20

>>>>>>> the ENTITY-MIB table, it would be given a unique ID mixed=20

>>>>>>> amongst the other logical and physical entities.

>>>>>>> At that point, should all of the MIBs being discussed in the=20

>>>>>>> EMAN WG be sparse table augmentations of ENTITY-MIB?

>>>>>>> Thanks,

>>>>>>> Chris

>>>>>>> -----Original Message-----

>>>>>>> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On=20

>>>>>>> Behalf Of Juergen Quittek

>>>>>>> Sent: Tuesday, October 26, 2010 6:01 AM

>>>>>>> To: Benoit Claise; eman mailing list

>>>>>>> Subject: [eman] Entity identification method (was: EMAN=20

>>>>>>> chartered items versus drafts) Hi Benoit and all, I agree that=20

>>>>>>> we should find a common identification method for entities used=20

>>>>>>> by all MIB modules. This does not apply to the POWER MIB only,=20

>>>>>>> but to all MIB modules in the eman WG.

>>>>>>> The modules will use an entity ID as index for their tables.

>>>>>>> Which entity is identified by the index can be resolved by other =


>>>>>>> MIB modules, such as the POWER AWARE MIB module

>>>>>>> (draft-parello-eman-energy-aware-mib) or the ENTITY MIB module=20

>>>>>>> (RFC 4133).

>>>>>>> I see three basic scenarios for the entity identification:

>>>>>>> a) a device just reports on its own power state and energy=20

>>>>>>> consumption and it reports on its own as a single unit.

>>>>>>> Then we have a single index only stating "it's me".

>>>>>>> Such a device usually does not need further identification of=20

>>>>>>> itself, because typically there are sufficient other MIB modules =


>>>>>>> for this purpose running in the same SNMP engine, that provide=20

>>>>>>> information about the device's IP address, manufacturer,=20

>>>>>>> operating system, etc. In such a case a 'trivial' index, such as =


>>>>>>> '0' should be used in order to keep it simple in this most=20

>>>>>>> simple case.

>>>>>>> b) a device reports on its own but not just as a single unit but =


>>>>>>> it reports power states and energy consumption for its=20

>>>>>>> individual components, for example it may report separately on=20

>>>>>>> contained hard drives, line cards, back planes, processor=20

>>>>>>> boards, etc.

>>>>>>> In such a case, identification of these components as individual =


>>>>>>> entities would be required. The ENTITY MIB module was designed=20

>>>>>>> for this purpose and would be a good choice here. Also the POWER =


>>>>>>> AWARE MIB module would be useful in this case.

>>>>>>> c) a device reports on energy consumption of other, remote=20

>>>>>>> devices. Then remote devices (and potentially also their=20

>>>>>>> contained components need to be identified. For identifying=20

>>>>>>> remote components there is the POWER AWARE MIB module that has=20

>>>>>>> been designed for this purpose. As far as I understand, the=20

>>>>>>> ENTITY MIB module is not applicable to remote devices.

>>>>>>> In summary,

>>>>>>> - if you need to report on remote entities (case c)), you need=20

>>>>>>> the POWER AWARE MIB module,

>>>>>>> - if you report only on entities locally contained in the=20

>>>>>>> reporting device (case b)), you can use the POWER AWARE MIB or=20

>>>>>>> the ENTITY MIB

>>>>>>> - if you report just on your own as a single device (case a)),=20

>>>>>>> identification is trivial Hence, my recommendation (stated for=20

>>>>>>> POWER-STATE MIB and ENERGY MIB in

>>>>>>> draft-quittek-power-mib-02) would be:

>>>>>>> If there is an implementation of the POWER AWARE MIB module=20

>>>>>>> instantiated in the local SNMP engine, then you SHOULD (or=20

>>>>>>> MUST?) use it for indexing (pmIndex).

>>>>>>> If this is not the case but there is an ENTITY MIB instance=20

>>>>>>> available, then you SHOULD use this one (entPhysicalIndex).

>>>>>>> If neither of this MIB modules is available you should use index

>>>>>>> 0

>>>>>>> only and be limited to report on the local device as a single

>>> entity only.

>>>=20

>>>>>>> That's just my view. Certainly, there are more ways of entity=20

>>>>>>> identification. I look forward to discussing them.

>>>>>>> Thanks,

>>>>>>> Juergen

>>>>>>> On 26.10.10 11:44 "Benoit Claise"<bclaise@cisco.com

>>> <mailto:bclaise@cisco.com <mailto:bclaise@cisco.com> >>   wrote:

>>>=20

>>>>>>>> Hi Juergen,

>>>>>>>> Thanks for the clarification.

>>>>>>>> Something key is to agree on the Power Monitor index for all=20

>>>>>>>> MIB modules, which IMHO should be part of the Energy-aware=20

>>>>>>>> Networks and Devices MIB module, but reuse in the other MIB =
modules.

>>>>>>>> Regards, Benoit.

>>>>>>>>> Hi Benoit,

>>>>>>>>> Thanks for checking all drafts.

>>>>>>>>> I don't think that draft-quittek-power-mib-02 makes=20

>>>>>>>>> significant contributions to the Energy-aware Networks and =
Devices MIB.

>>>>>>>>> It just covers the Power and Energy Monitoring MIB and the=20

>>>>>>>>> Battery

>>>>>>> MIB.

>>>>>>>>> Thanks,

>>>>>>>>> Juergen

>>>>>>>>> On 26.10.10 08:22 "Benoit Claise"<bclaise@cisco.com

>>> <mailto:bclaise@cisco.com <mailto:bclaise@cisco.com> >>   wrote:

>>>=20

>>>>>>>>>> Dear all,

>>>>>>>>>> I went through the exercise of mapping the existing six=20

>>>>>>>>>> chartered items with the existing draft content.

>>>>>>>>>> _Energy Management Requirements_=20

>>>>>>>>>> http://tools.ietf.org/html/draft-quittek-power-monitoring-req =
<http://tools.ietf.org/html/draft-quittek-power-monitoring-req>=20

>>>>>>>>>> u

>>>>>>>>>> ir

>>>>>>>>>> emen

>>>>>>>>>> ts-02

>>>>>>>>>> https://datatracker.ietf.org/doc/draft-norwin-energy-consider =
<https://datatracker.ietf.org/doc/draft-norwin-energy-consider>=20

>>>>>>>>>> /

>>>>>>>>>> _

>>>>>>>>>> Energy Management Framework_

>>>>>>>>>> http://tools.ietf.org/html/draft-claise-power-management-arch =
<http://tools.ietf.org/html/draft-claise-power-management-arch>=20

>>>>>>>>>> -

>>>>>>>>>> 02

>>>>>>>>>> _Energy-aware Networks and Devices MIB_=20

>>>>>>>>>> http://tools.ietf.org/html/draft-parello-eman-energy-aware-mi =
<http://tools.ietf.org/html/draft-parello-eman-energy-aware-mi>=20

>>>>>>>>>> b

>>>>>>>>>> -0

>>>>>>>>>> 0

>>>>>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02 =
<http://tools.ietf.org/html/draft-quittek-power-mib-02>=20

>>>>>>>>>> _Power and Energy Monitoring MIB_

>>>>>>>>>> http://tools.ietf.org/html/draft-claise-energy-monitoring-mib =
<http://tools.ietf.org/html/draft-claise-energy-monitoring-mib>=20

>>>>>>>>>> -

>>>>>>>>>> 06

>>>>>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02 =
<http://tools.ietf.org/html/draft-quittek-power-mib-02>=20

>>>>>>>>>> _Battery MIB_

>>>>>>>>>> http://tools.ietf.org/html/draft-quittek-power-mib-02 =
<http://tools.ietf.org/html/draft-quittek-power-mib-02>=20

>>>>>>>>>> _Energy Management Applicability_=20

>>>>>>>>>> http://datatracker.ietf.org/doc/draft-tychon-eman-applicabili =
<http://datatracker.ietf.org/doc/draft-tychon-eman-applicabili>=20

>>>>>>>>>> t

>>>>>>>>>> y-

>>>>>>>>>> stat

>>>>>>>>>> ement/

>>>>>>>>>> Please let me know if I made any mistakes or if I missed any

>>> draft?

>>>=20

>>>>>>>>>> Regards, Benoit.

>>>>>>>>>> _______________________________________________

>>>>>>>>>> eman mailing list

>>>>>>>>>> eman@ietf.org<mailto:eman@ietf.org =
<mailto:eman@ietf.org%3cmailto:eman@ietf.org> >

>>>>>>>>>> https://www.ietf.org/mailman/listinfo/eman =
<https://www.ietf.org/mailman/listinfo/eman>=20

>>>>>>> _______________________________________________

>>>>>>> eman mailing list

>>>>>>> eman@ietf.org<mailto:eman@ietf.org =
<mailto:eman@ietf.org%3cmailto:eman@ietf.org> >

>>>>>>> https://www.ietf.org/mailman/listinfo/eman =
<https://www.ietf.org/mailman/listinfo/eman>=20

>>>>>> _______________________________________________

>>>>>> eman mailing list

>>>>>> eman@ietf.org<mailto:eman@ietf.org =
<mailto:eman@ietf.org%3cmailto:eman@ietf.org> >

>>>>>> https://www.ietf.org/mailman/listinfo/eman =
<https://www.ietf.org/mailman/listinfo/eman>=20

>>>>> _______________________________________________

>>>>> eman mailing list

>>>>> eman@ietf.org<mailto:eman@ietf.org =
<mailto:eman@ietf.org%3cmailto:eman@ietf.org> >

>>>>> https://www.ietf.org/mailman/listinfo/eman =
<https://www.ietf.org/mailman/listinfo/eman>=20

>>>> _______________________________________________

>>>> eman mailing list

>>>> eman@ietf.org<mailto:eman@ietf.org =
<mailto:eman@ietf.org%3cmailto:eman@ietf.org> >

>>>> https://www.ietf.org/mailman/listinfo/eman =
<https://www.ietf.org/mailman/listinfo/eman>=20

>>> _______________________________________________

>>>=20

>>> eman mailing list

>>>=20

>>> eman@ietf.org<mailto:eman@ietf.org =
<mailto:eman@ietf.org%3cmailto:eman@ietf.org> >

>>>=20

>>> https://www.ietf.org/mailman/listinfo/eman =
<https://www.ietf.org/mailman/listinfo/eman>=20

>>>=20

>> _______________________________________________

>> eman mailing list

>> eman@ietf.org <mailto:eman@ietf.org>=20

>> https://www.ietf.org/mailman/listinfo/eman =
<https://www.ietf.org/mailman/listinfo/eman>=20

>=20

> _______________________________________________

> eman mailing list

> eman@ietf.org <mailto:eman@ietf.org>=20

> https://www.ietf.org/mailman/listinfo/eman =
<https://www.ietf.org/mailman/listinfo/eman>=20

>=20


------_=_NextPart_001_01CB801B.FCBA3AF3
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DGenerator =
content=3D"Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:Consolas;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:270864285;
	mso-list-type:hybrid;
	mso-list-template-ids:1115868426 67698689 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1
	{mso-list-id:939070746;
	mso-list-type:hybrid;
	mso-list-template-ids:1987607470 67698689 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoPlainText>Hi =
John,<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Here's an example of what I'd ideally report, =
indented to show parent/child relationships between the =
entities:<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText =
style=3D'margin-left:.25in'><b>POWER-ENTITY-MIB:<o:p></o:p></b></p><p =
class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo1'><![if !supportLists]><span style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>Cyber Switching ePower &#8220;Smart =
PDU&#8221;<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 =
lfo1'><![if !supportLists]><span style=3D'font-family:"Courier =
New"'><span style=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp; </span></span></span><![endif]>Three =
Phase Input #1<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l1 level3 =
lfo1'><![if !supportLists]><span style=3D'font-family:Wingdings'><span =
style=3D'mso-list:Ignore'>=A7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]>Single Phase Bank =
#1<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:2.0in;text-indent:-.25in;mso-list:l1 level4 =
lfo1'><![if !supportLists]><span style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>Single Phase Outlet #1<o:p></o:p></p><p =
class=3DMsoPlainText =
style=3D'margin-left:2.0in;text-indent:-.25in;mso-list:l1 level4 =
lfo1'><![if !supportLists]><span style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>Single Phase Outlet #2<o:p></o:p></p><p =
class=3DMsoPlainText =
style=3D'margin-left:2.0in;text-indent:-.25in;mso-list:l1 level4 =
lfo1'><![if !supportLists]><span style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>...<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l1 level3 =
lfo1'><![if !supportLists]><span style=3D'font-family:Wingdings'><span =
style=3D'mso-list:Ignore'>=A7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]>Single Phase Bank =
#2<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:2.0in;text-indent:-.25in;mso-list:l1 level4 =
lfo1'><![if !supportLists]><span style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>Single Phase Outlet #9<o:p></o:p></p><p =
class=3DMsoPlainText =
style=3D'margin-left:2.0in;text-indent:-.25in;mso-list:l1 level4 =
lfo1'><![if !supportLists]><span style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>Single Phase Outlet #10<o:p></o:p></p><p =
class=3DMsoPlainText =
style=3D'margin-left:2.0in;text-indent:-.25in;mso-list:l1 level4 =
lfo1'><![if !supportLists]><span style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>...<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l1 level3 =
lfo1'><![if !supportLists]><span style=3D'font-family:Wingdings'><span =
style=3D'mso-list:Ignore'>=A7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]>...<o:p></o:p></p><p =
class=3DMsoPlainText =
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 =
lfo1'><![if !supportLists]><span style=3D'font-family:"Courier =
New"'><span style=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>...<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo1'><![if !supportLists]><span style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>Server01<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Note =
that &#8220;Server01&#8221; is a separate entity hierarchy from the =
ePower PDU itself.=A0 In this example, let&#8217;s say that Server01 =
points to Outlets #1 and #9, meaning the redundant power supplies on =
server01 are being powered by those physical outlets.=A0 Server01 is, in =
effect, a &#8220;logical&#8221; entity from the perspective of the MIB =
that is representing a &#8220;physical&#8221; entity in the real =
world.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>To simplify management, I&#8217;d report actual =
power metered on the ePower PDU hierarchy (the PDU itself, the inputs, =
the banks, and the outlets) AND aggregated power metered on the Server01 =
entity.=A0 So if Outlet 1 and Outlet 9 report 2.5 A each, I&#8217;d =
aggregate that to 5.0 A for the Server01 entity.=A0 (I&#8217;m using =
Amperage as an example only; a solution should not be limited to only =
that data type.)<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>There =
could even be a &#8220;logical-to-physical&#8221; mapping table like is =
in ENTITY-MIB.=A0 The main difference, however, is that there =
wouldn&#8217;t need to be a second table to separate logical and =
physical entities from each other.=A0 That breakdown is just inane, I =
think.=A0 Add a column that is the pmEntityType (or whatever name is =
appropriate) that distinguishes whether this entity is physical(1) or =
logical(2) or ....<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>But =
yes, your initial summary is my main point.=A0 With regards to linking =
to ENTITY-MIB, we should only link to it IF IT MAKES SENSE FOR OUR =
PRODUCT.=A0 (Emphasis added, not meaning to &#8220;yell.&#8221;)=A0 By =
splitting this linkage out to tables, we can enhance the flexibility of =
the framework.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Thanks,<o:p></o:p></p><p =
class=3DMsoPlainText>Chris<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>-----Original Message-----<br>From: john parello =
[mailto:jparello@cisco.com] <br>Sent: Tuesday, November 09, 2010 12:41 =
AM<br>To: Chris Verges<br>Cc: eman@ietf.org<br>Subject: Re: [eman] =
Entity identification method</p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Hi =
Chris,<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>That is a very good point wrt the entity mib. Our =
draft calls for linking to the entity mib if present. You seem to be =
sayig that even if it is present you may do not want to link to =
it.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>One question for the server power: would you want =
to report the aggragate or the remainder?<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Example if you have 8 outlets and the server =
itself.=A0 Wouldn't there be<o:p></o:p></p><p class=3DMsoPlainText>8 =
readings for the attached devices and then one reading for the server =
which is the draw of the PDU itself to function - albeit =
small.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>For PoE switches that's our intent. We report the =
draw on each interface then the draw for the switch itself to =
operate.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Jp<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>On =
11/8/10 7:10 AM, Chris Verges wrote:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; Hi Benoit,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; In Section 5.4, the &quot;keywords&quot; =
and/or &quot;role&quot; fields are perhaps the <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; two that can *best* achieve the business =
context being described.=A0 <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
However, neither of these take into account the data reporting =
aspect.=A0 <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
For<o:p></o:p></p><p class=3DMsoPlainText>&gt; example:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; A server's redundant power supplies are =
connected to two different <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
outlets on a smart power strip.=A0 Each outlet is enumerated in the EMAN =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; MIBs as separate entities, =
and the &quot;role&quot; is set to &quot;server01&quot;, =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; indicating that these =
outlets are linking in business context through <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; the server's hostname.=A0 (Use any other =
metric you want, the result is <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; still the same.)=A0 I know how much power each =
power supply is then <o:p></o:p></p><p class=3DMsoPlainText>&gt; drawing =
since the MIB splits the data out by outlet.=A0 However, I do =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; not know the aggregate power =
draw of the server itself, since there is <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; no &quot;server01&quot; data entry.=A0 There =
can't be, as there is no <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
corresponding pmIndex for the server entity.=A0 What's useful is to know =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; all three<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; datapoints: the power on supply A, the power =
on supply B, and the <o:p></o:p></p><p class=3DMsoPlainText>&gt; power =
on the server as a whole.=A0 Yes, it should be a fairly =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; straight-forward vector math =
calculation, but more complex scenarios <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; could be crafted using three phase, automatic =
transfer switches, solar panels, etc.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; The point is that while the &quot;role&quot; =
and &quot;keywords&quot; fields can be used <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; to establish business context for a particular =
entity in the MIB, I'm <o:p></o:p></p><p class=3DMsoPlainText>&gt; wary =
over whether they can be used to aggregate data or manage =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; aggregated control over =
multiple entities being logically grouped <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; together.=A0 At least, given the current =
sparse table extension <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
methodology behind the proposed set of MIBs.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; Perhaps mapping to ENTITY-MIB isn't required =
at this point.=A0 What if <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
power entities (POWER-ENTITY-MIB?) are separate from ENTITY-MIB =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; entirely?=A0 These two =
tables could later be mapped together through a <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; separate set of tables to ENTITY-MIB, which =
would establish the <o:p></o:p></p><p class=3DMsoPlainText>&gt; ability =
for an M:N mapping between POWER-ENTITY-MIB and the physical =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; and logical tables of =
ENTITY-MIB separately.=A0 That would allow us to <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; link the entities IF IT MAKES SENSE and in a =
way that makes sense.=A0 <o:p></o:p></p><p class=3DMsoPlainText>&gt; But =
it's not part of the core definition of a power entity, in a more =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; limited 1:1 =
fashion.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; Thanks,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; Chris<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; -----Original Message-----<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; From: Benoit Claise =
[mailto:bclaise@cisco.com]<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
Sent: Sunday, November 07, 2010 11:20 PM<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; To: Chris Verges<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; Cc: Christian Groves; =
eman@ietf.org<o:p></o:p></p><p class=3DMsoPlainText>&gt; Subject: Re: =
[eman] Entity identification method<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; Hi Chris,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; Question: could the business context be used =
to achieve what you want <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
to?<o:p></o:p></p><p class=3DMsoPlainText>&gt; See<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; <a =
href=3D"http://tools.ietf.org/html/draft-claise-power-management-arch-02#=
secti"><span =
style=3D'color:windowtext;text-decoration:none'>http://tools.ietf.org/htm=
l/draft-claise-power-management-arch-02#secti</span></a><o:p></o:p></p><p=
 class=3DMsoPlainText>&gt; on<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
-5.4<o:p></o:p></p><p class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; Regards, Benoit<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; Hi Christian et al.,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; How about the following two use cases to =
augment the existing <o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
power-allocation-per-virtual-machine scenario?<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; =A0=A0=A0 1. &quot;Grouped&quot; outlets =
on a smart PDU<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; =A0=A0=A0 2. Tenant submetering on a smart =
meter<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; In the first scenario, several smart PDUs =
allow the user to create a <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; user-defined grouping that consists of =
several outlets.=A0 Physical <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; outlets 1 and 7, for example, could be =
grouped together as logical <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; entity &quot;server01&quot;.=A0 This =
mapping could be created using the existing <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; ENTITY-MIB architecture.=A0 The power data =
for both the physical and <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; logical entities are useful to facilities =
and IT managers to <o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
understand power flow and usage.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; In the second scenario, a smart meter =
provides submetering for a <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; commercial rental building.=A0 Such =
buildings often occur turnover in <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; tenants.=A0 A submeter that meters each =
circuit in the building, for <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; example, could maintain that data in both =
granular and aggregate form.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; When a tenant moves in, the facilities =
manager can create a new <o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
logical entity for that tenant and map the physical circuit entries =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; to<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; the tenant's logical entity.=A0 This =
enables both real-time power usage <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; and management on an individual circuit =
basis (useful for <o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
troubleshooting facilities problems) as well as on a customized =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; aggregate basis (useful =
for the bean counters who have to allocate<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; costs).<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; Here's an interesting question as far as =
implementation is concerned<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
...<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; why not implement =
pmPhysicalMap and pmLogicalMap tables (like<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; entLPMappingTable) to map the pmIndex =
entity to the appropriate <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; physical or logical entity (1:1 =
only?)<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; Chris<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; -----Original =
Message-----<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; From: =
Christian Groves [mailto:Christian.Groves@nteczone.com]<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; Sent: Tuesday, November 02, 2010 7:14 =
PM<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; To: Chris =
Verges<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; Cc: =
eman@ietf.org<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; Subject: =
Re: [eman] Entity identification method<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; Hello Chris,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; I don't have any concrete suggestions for =
implementing virtual entity <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; energy usage support. I'm still at the =
stage of trying to see what <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; the<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; requirements and framework is for the =
work. There seems to be a focus <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; on the MIBs themselves, when without good =
requirements its hard to <o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
see<o:p></o:p></p><p class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; what needs they are meeting. The work of =
the eman WG could address IP <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; type servers only or the MIBs could also =
be used in other <o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
telecommunication equipment i.e. those used in outside plant. I'm =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; encouraged to see =
Bruce's email on topics for discussion as think its <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; in important to get =
consensus/understanding on these before the MIBs<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; are developed.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; Please see my comment below marked =
[CNG].<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; Regards, Christian<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; On 1/11/2010 11:39 PM, Chris Verges =
wrote:<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt; Hi =
Christian,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; Are you looking to allocate actual =
energy usage by a virtual entity, <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; like the amount of energy used by a =
virtual machine running on a <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; shared server? Certainly an =
interesting problem ... gives a lot of <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; room for innovation for different =
vendors to find solutions.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; [CNG] I agree its an interesting problem. =
In some instances it may be <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; possible to allocate the actual energy =
however in many cases it would <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; be very difficult/impossible. In these =
more difficult cases it may be <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; possible to simply report the identities =
of the virtual/logical <o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
entities that are included in the physical measurement.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;=A0=A0=A0 From a MIB standpoint, it =
seems like the requirement is to have a <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; flexible power-related MIB that can =
either map to physical or <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; logical<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; entities. One question is, &quot;where =
do you want those entities<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; enumerated?&quot;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; Are virtual entities that need to be =
mapped to power usage normally <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; enumerated in ENTITY-MIB in the =
&quot;logical&quot; table?<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; If so, perhaps something like this =
would fit the bill:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; POWER-ENTITY-MIB:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; pwrEntityTable<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; pwrEntityEntry<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; pwrEntityIndex<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; pwrEntityName<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; pwrEntityType<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; pwrEntityParent<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; pwrEntityPhysical<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; pwrEntityLogical<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; The pwrEntity[Physical|Logical] =
objects would point to the <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; appropriate index in =
ENTITY-MIB.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; However, if the virtual entities are =
not enumerated in ENTITY-MIB, <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; the pwrEntityLogical column is =
probably overkill. The virtual <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; entities can be enumerated in =
pwrEntityTable and linked to the <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; Physical meter using the =
pwrEntityParent column, much like how <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; ENTITY-MIB currently manages =
references between parent and component <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; entities. It would just involve a new =
pwrEntityType being added for <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; &quot;virtual&quot; or something =
similar.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; So what's the typical use case as =
these virtual entities relate to <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; ENTITY-MIB?<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; [CNG] I'm not sure the typical case. =
Either of the approaches above <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; could be sufficient but I think it depends =
on what people agree on <o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
with respect to virtual entities and how the data collected on them =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; would be =
used.<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt; =
Chris<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; -----Original =
Message-----<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt; From: =
eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt; Of Christian =
Groves<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt; Sent: Sunday, =
October 31, 2010 8:14 PM<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; To: eman@ietf.org<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; Subject: Re: [eman] Entity =
identification method<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; Hello Juergen,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; I think distinguishing the two cases =
is the correct way to go.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; I agree that reporting energy =
consumption for logical entities is a <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; challenge and not straight forward. I =
guess there are a number of <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; ways to look at this problem and how =
address the problem depends on <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; the ambition level.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; As you rightly mention where there is =
partial use of a physical <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; resource by a logical entity it is =
very difficult to have an exact <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; figure.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; However I think the &quot;grain =
size&quot; of the measurement comes into play.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; For example if we have a large gateway =
implementing several virtual <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; gateways if we take an overall =
measurement then we have the problem <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; determining a figure. If the however =
the virtual gateways were each <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; assigned a physical rack and the =
measurements were taken at a rack <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; level then we have a more precise =
estimate of contribution of each <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; virtual gateway to the overall =
picture.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; For me logical entities ultimately =
will be realised by physical <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; hardware. The key is understanding the =
relationship between these <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; entities. Thus I think virtualization =
can in some way be supported <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; by<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; allowing energy consumption reports =
for physical entities to <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; indicate<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; if/what logical entities they relate =
to. As they say information is <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; power (pardon the pun :-) =
).<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; Regards, Christian<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; On 29/10/2010 12:48 PM, Juergen =
Quittek wrote:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; Hi Christian,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; Thank you for this interesting =
comment.<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt; It looks =
like we have to distinguish two cases: power state <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; monitoring and energy consumption =
monitoring.<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt; For a =
logical entity and a virtual machine it may be well possible =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt; to report on =
their power state. However, reporting their energy <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; consumption seems to be a tough =
challenge at least if be base it on<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; real measurements.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; It is well feasible to measure =
energy consumption of physical <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; entities, but if you have a =
logical entity that consumes only <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; partial resources of a physical =
entity, then precise measurement of <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; the energy consumption will be =
hardly possible. Estimations may be <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; possible based on a model of the =
logical entity, but I don't know <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; how good such<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; models can be.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; Thanks,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; Juergen<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; On 29.10.10 03:25 &quot;Christian =
Groves&quot;&lt;Christian.Groves@nteczone.com<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; &lt;<a =
href=3D"mailto:Christian.Groves@nteczone.com"><span =
style=3D'color:windowtext;text-decoration:none'>mailto:Christian.Groves@n=
teczone.com</span></a>&gt;&gt;=A0=A0 wrote:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; Hello<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; I've just started to digest =
the various drafts of the eman wg and <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; I see the comment below on =
logical entities. It's not clear to me <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; how/if network virtualization =
is intended on being handled in the<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; eman work.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; In networks there's now a =
trend towards network virtualization and <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; cloud computing with the =
different &quot;X&quot; as a service models (i.e.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; Amazon EC2 &quot;platform as a =
service&quot; running different server <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; instances). Even in today's =
networks we have physical gateways <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; that are virtualized into =
different logical gateways. For example:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; H.248/Megaco virtual MG (VMG) =
concept.<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; I =
think it would be advantageous to be able to assess the energy =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; consumption =
of the VMGs or instances (which are logical entities) <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; independent of the physical =
gateway so that a customers energy use <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; may be recording. Will this =
sort of functionality be allowed?<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; Regards, =
Christian<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; On =
29/10/2010 1:22 AM, Juergen Quittek wrote:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; Hi Chris,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; I think it may become very =
difficult if we want to assess energy <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; consumption of logical =
entities. It seems to be reasonable and <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; practical to limit energy =
consumption measurements to physical <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; entities. The ENERGY AWARE =
MIB module<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; =
(draft-parello-eman-energy-aware-mib) and the POWER MIB<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; =
(draft-quittek-power-mib-02) went this way.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; Just using =
entPhysicalIndex solves some of the problem you<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; mentioned.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; Particularly, you don't =
need a mapping table to entities if you <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; restrict Yourself to =
entPhysicalIndex.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; Thanks,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; Juergen<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; On 28.10.10 13:34 =
&quot;Chris Verges&quot;&lt;chrisv@cyberswitching.com<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; &lt;<a =
href=3D"mailto:chrisv@cyberswitching.com"><span =
style=3D'color:windowtext;text-decoration:none'>mailto:chrisv@cyberswitch=
ing.com</span></a>&gt;&gt;=A0=A0 wrote:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; Hi Jurgen and =
all,<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
The more I've been thinking about these scenarios, the more =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
something doesn't seem quite right. I'll try to explain my =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
thought process behind this and see if my concerns/confusions =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
get<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; =
captured.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; ENTITY-MIB provides =
enumerated lists of physical and logical <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; entities on the =
system. The indices in both lists are maintained <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; separately, so there =
is not a single, unique identifier provided.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; Because of this, the =
MIBs being discussed by the EMAN WG must <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; only reference to one =
type (physical or logical) and are limited <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; to<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; that without additional =
work.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; At some point in my =
mind, I'm asking myself the question, <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; &quot;What's the point =
of linking to ENTITY-MIB?&quot;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; More on that question =
in later scenarios below ...<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; One possibility would =
be to create a separate mapping table that <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; gives a guaranteed =
unique index based on all entities, <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; regardless of type. =
The physical vs. logical extensions would <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; then become sparse =
tables that augment this. For example:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; ENTITY-MIB : =
entityGeneral.entGeneralTable.entGeneralEntry<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
+-----------------+-----------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; | entGeneralIndex | =
entGeneralDescr | ... |<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
+-----------------+-----------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; | 1 | PDU Chassis | =
|<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
+-----------------+-----------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; | 2 | Meter #1 | =
|<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
+-----------------+-----------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; | 3 | Meter #2 | =
|<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
+-----------------+-----------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; | 4 | Remote Meter #1 =
| |<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
+-----------------+-----------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; ENTITY-MIB : =
entityPhysical.entPhysicalTable.entPhysicalEntry<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
+-----------------+-----------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; | entGeneralIndex | =
entVendorType | ... |<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
+-----------------+-----------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; | 1 | enterprises.foo =
| |<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
+-----------------+-----------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; | 2 | enterprises.foo =
| |<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
+-----------------+-----------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; | 3 | enterprises.foo =
| |<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
+-----------------+-----------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; ENTITY-MIB : =
entityLogical.entLogicalTable.entLogicalEntry<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
+-----------------+----------------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; | entGeneralIndex | =
entLogicalCommunity | ... |<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
+-----------------+----------------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; | 4 | =
remote-power-group-1 | |<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
+-----------------+----------------------+-----+<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; It seems like this =
'entGeneralIndex' concept is what's missing <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; from the current =
ENTITY-MIB, and is causing problems when <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; thinking about local =
and remote power data being reported by the <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; same =
agent.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; Another possibility =
would be to choose one -- entLogicalIndex, <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; most likely -- and =
require that anyone who wants to implement <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; the EMAN WG MIBs to =
always create an entLogicalEntry for the <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; power =
data.<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
In<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
this context, the entLogicalTable fills the role of <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; entGeneralTable as =
described above. For all entPhysicalTable <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; entries, there would =
need to be a corresponding entry in <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; entLogicalTable with a =
1:1 mapping between them. For all remote <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; entries, there would =
be a unique entry in entLogicalTable. Of <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; course, this would add =
some additional overhead on the part of <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; the implementer, but =
isn't too<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt; =
overburdening.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; A third possibility is =
that ENTITY-MIB just doesn't do what we <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; need in its present =
form and we need to think about enumerating <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; power sensors =
separately from other components/sensors on the <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
system.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; It<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; seems like =
entPhysicalTable gives a good starting template for a <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; new =
'POWER-ENTITY-MIB', but can be extended to include support =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; for =
remote agents. The difference would be a clean break from =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; the =
legacy ENTITY-MIB structure.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; And with that, I look =
forward to others' feedback and ideas on <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; solving this =
problem!<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
Thanks,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; Chris<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; -----Original =
Message-----<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; From: =
eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
Behalf Of Chris Verges<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; Sent: Tuesday, October =
26, 2010 9:26 PM<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; To: Juergen Quittek; =
Benoit Claise; eman mailing list<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; Subject: Re: [eman] =
Entity identification method (was: EMAN <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; chartered itemsversus =
drafts) Hi Juergen and all, Agreed that a <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; common ID method makes =
sense, and ENTITY-MIB seems to be a good <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; choice. In case (c) =
from your list, wouldn't the remote agent <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; condition be handled =
by ENTITY-MIB supporting a logical entity <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; that is the remote =
agent iself? Since the logical entity is in <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; the ENTITY-MIB table, =
it would be given a unique ID mixed <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; amongst the other =
logical and physical entities.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; At that point, should =
all of the MIBs being discussed in the <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; EMAN WG be sparse =
table augmentations of ENTITY-MIB?<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
Thanks,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; Chris<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; -----Original =
Message-----<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; From: =
eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
Behalf Of Juergen Quittek<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; Sent: Tuesday, October =
26, 2010 6:01 AM<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; To: Benoit Claise; =
eman mailing list<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; Subject: [eman] Entity =
identification method (was: EMAN <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; chartered items versus =
drafts) Hi Benoit and all, I agree that <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; we should find a =
common identification method for entities used <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; by all MIB modules. =
This does not apply to the POWER MIB only, <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; but to all MIB modules =
in the eman WG.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; The modules will use =
an entity ID as index for their tables.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; Which entity is =
identified by the index can be resolved by other <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; MIB modules, such as =
the POWER AWARE MIB module<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
(draft-parello-eman-energy-aware-mib) or the ENTITY MIB module =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; (RFC =
4133).<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; I see three basic =
scenarios for the entity identification:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; a) a device just =
reports on its own power state and energy <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; consumption and it =
reports on its own as a single unit.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; Then we have a single =
index only stating &quot;it's me&quot;.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; Such a device usually =
does not need further identification of <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; itself, because =
typically there are sufficient other MIB modules <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; for this purpose =
running in the same SNMP engine, that provide <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; information about the =
device's IP address, manufacturer, <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; operating system, etc. =
In such a case a 'trivial' index, such as <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; '0' should be used in =
order to keep it simple in this most <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; simple =
case.<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
b) a device reports on its own but not just as a single unit but =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; it =
reports power states and energy consumption for its <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; individual components, =
for example it may report separately on <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; contained hard drives, =
line cards, back planes, processor <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; boards, =
etc.<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
In such a case, identification of these components as individual =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
entities would be required. The ENTITY MIB module was designed =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; for =
this purpose and would be a good choice here. Also the POWER =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
AWARE MIB module would be useful in this case.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; c) a device reports on =
energy consumption of other, remote <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; devices. Then remote =
devices (and potentially also their <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; contained components =
need to be identified. For identifying <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; remote components =
there is the POWER AWARE MIB module that has <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; been designed for this =
purpose. As far as I understand, the <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; ENTITY MIB module is =
not applicable to remote devices.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; In =
summary,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; - if you need to =
report on remote entities (case c)), you need <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; the POWER AWARE MIB =
module,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; - if you report only =
on entities locally contained in the <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; reporting device (case =
b)), you can use the POWER AWARE MIB or <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; the ENTITY =
MIB<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; - =
if you report just on your own as a single device (case a)), =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
identification is trivial Hence, my recommendation (stated for =
<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
POWER-STATE MIB and ENERGY MIB in<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
draft-quittek-power-mib-02) would be:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; If there is an =
implementation of the POWER AWARE MIB module <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; instantiated in the =
local SNMP engine, then you SHOULD (or <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; MUST?) use it for =
indexing (pmIndex).<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; If this is not the =
case but there is an ENTITY MIB instance <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; available, then you =
SHOULD use this one (entPhysicalIndex).<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; If neither of this MIB =
modules is available you should use index<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; 0<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; only and be limited to =
report on the local device as a single<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; entity only.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; That's just my view. =
Certainly, there are more ways of entity <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; identification. I look =
forward to discussing them.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
Thanks,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
Juergen<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; On 26.10.10 11:44 =
&quot;Benoit Claise&quot;&lt;bclaise@cisco.com<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; &lt;<a =
href=3D"mailto:bclaise@cisco.com"><span =
style=3D'color:windowtext;text-decoration:none'>mailto:bclaise@cisco.com<=
/span></a>&gt;&gt;=A0=A0 wrote:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Hi =
Juergen,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Thanks for the =
clarification.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Something key is =
to agree on the Power Monitor index for all <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; MIB modules, which =
IMHO should be part of the Energy-aware <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Networks and =
Devices MIB module, but reuse in the other MIB modules.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Regards, =
Benoit.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Hi =
Benoit,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Thanks for =
checking all drafts.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I don't think =
that draft-quittek-power-mib-02 makes <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; significant =
contributions to the Energy-aware Networks and Devices =
MIB.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; It just covers =
the Power and Energy Monitoring MIB and the <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
Battery<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; MIB.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
Thanks,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
Juergen<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; On 26.10.10 =
08:22 &quot;Benoit Claise&quot;&lt;bclaise@cisco.com<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; &lt;<a =
href=3D"mailto:bclaise@cisco.com"><span =
style=3D'color:windowtext;text-decoration:none'>mailto:bclaise@cisco.com<=
/span></a>&gt;&gt;=A0=A0 wrote:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Dear =
all,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; I went =
through the exercise of mapping the existing six <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; chartered =
items with the existing draft content.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; _Energy =
Management Requirements_ <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"http://tools.ietf.org/html/draft-quittek-power-monitoring-req"><s=
pan =
style=3D'color:windowtext;text-decoration:none'>http://tools.ietf.org/htm=
l/draft-quittek-power-monitoring-req</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
u<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
ir<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
emen<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
ts-02<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"https://datatracker.ietf.org/doc/draft-norwin-energy-consider"><s=
pan =
style=3D'color:windowtext;text-decoration:none'>https://datatracker.ietf.=
org/doc/draft-norwin-energy-consider</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
/<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
_<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Energy =
Management Framework_<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"http://tools.ietf.org/html/draft-claise-power-management-arch"><s=
pan =
style=3D'color:windowtext;text-decoration:none'>http://tools.ietf.org/htm=
l/draft-claise-power-management-arch</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
-<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
02<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
_Energy-aware Networks and Devices MIB_ <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"http://tools.ietf.org/html/draft-parello-eman-energy-aware-mi"><s=
pan =
style=3D'color:windowtext;text-decoration:none'>http://tools.ietf.org/htm=
l/draft-parello-eman-energy-aware-mi</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
b<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
-0<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
0<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"http://tools.ietf.org/html/draft-quittek-power-mib-02"><span =
style=3D'color:windowtext;text-decoration:none'>http://tools.ietf.org/htm=
l/draft-quittek-power-mib-02</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; _Power and =
Energy Monitoring MIB_<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"http://tools.ietf.org/html/draft-claise-energy-monitoring-mib"><s=
pan =
style=3D'color:windowtext;text-decoration:none'>http://tools.ietf.org/htm=
l/draft-claise-energy-monitoring-mib</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
-<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
06<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"http://tools.ietf.org/html/draft-quittek-power-mib-02"><span =
style=3D'color:windowtext;text-decoration:none'>http://tools.ietf.org/htm=
l/draft-quittek-power-mib-02</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; _Battery =
MIB_<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"http://tools.ietf.org/html/draft-quittek-power-mib-02"><span =
style=3D'color:windowtext;text-decoration:none'>http://tools.ietf.org/htm=
l/draft-quittek-power-mib-02</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; _Energy =
Management Applicability_ <o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"http://datatracker.ietf.org/doc/draft-tychon-eman-applicabili"><s=
pan =
style=3D'color:windowtext;text-decoration:none'>http://datatracker.ietf.o=
rg/doc/draft-tychon-eman-applicabili</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
t<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
y-<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
stat<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
ement/<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Please let =
me know if I made any mistakes or if I missed any<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; draft?<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; Regards, =
Benoit.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
_______________________________________________<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; eman =
mailing list<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"mailto:eman@ietf.org%3cmailto:eman@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>eman@ietf.org&lt;mailto:e=
man@ietf.org</span></a>&gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/eman"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/eman</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
_______________________________________________<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; eman mailing =
list<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; =
<a href=3D"mailto:eman@ietf.org%3cmailto:eman@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>eman@ietf.org&lt;mailto:e=
man@ietf.org</span></a>&gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/eman"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/eman</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; =
_______________________________________________<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; eman mailing =
list<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"mailto:eman@ietf.org%3cmailto:eman@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>eman@ietf.org&lt;mailto:e=
man@ietf.org</span></a>&gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt;&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/eman"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/eman</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; =
_______________________________________________<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; eman mailing =
list<o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; <a =
href=3D"mailto:eman@ietf.org%3cmailto:eman@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>eman@ietf.org&lt;mailto:e=
man@ietf.org</span></a>&gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt;&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/eman"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/eman</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; =
_______________________________________________<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; eman mailing list<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; <a =
href=3D"mailto:eman@ietf.org%3cmailto:eman@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>eman@ietf.org&lt;mailto:e=
man@ietf.org</span></a>&gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/eman"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/eman</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; =
_______________________________________________<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; eman mailing list<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; <a =
href=3D"mailto:eman@ietf.org%3cmailto:eman@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>eman@ietf.org&lt;mailto:e=
man@ietf.org</span></a>&gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/eman"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/eman</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt;&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;&gt; =
_______________________________________________<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; eman mailing list<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;&gt; <a href=3D"mailto:eman@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>eman@ietf.org</span></a><=
o:p></o:p></p><p class=3DMsoPlainText>&gt;&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/eman"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/eman</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; =
_______________________________________________<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; eman mailing list<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; <a href=3D"mailto:eman@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>eman@ietf.org</span></a><=
o:p></o:p></p><p class=3DMsoPlainText>&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/eman"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/eman</span></a><o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p></div></body></html>
------_=_NextPart_001_01CB801B.FCBA3AF3--

From chrisv@cyberswitching.com  Tue Nov  9 07:09:12 2010
Return-Path: <chrisv@cyberswitching.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C16363A6A0B for <eman@core3.amsl.com>; Tue,  9 Nov 2010 07:09:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vNy3aTVVmTSj for <eman@core3.amsl.com>; Tue,  9 Nov 2010 07:09:02 -0800 (PST)
Received: from p01c12o149.mxlogic.net (p01c12o149.mxlogic.net [208.65.145.72]) by core3.amsl.com (Postfix) with ESMTP id 41F493A6A0A for <eman@ietf.org>; Tue,  9 Nov 2010 07:09:01 -0800 (PST)
Received: from unknown [64.81.28.110] (EHLO mail03.cyberswitching.local) by p01c12o149.mxlogic.net(mxl_mta-6.7.0-2) with ESMTP id 52469dc4.0.18966.00-388.38980.p01c12o149.mxlogic.net (envelope-from <chrisv@cyberswitching.com>);  Tue, 09 Nov 2010 08:09:26 -0700 (MST)
X-MXL-Hash: 4cd964261a9a99fd-0c262e37acc67df88e57c826b416237a9074f7b8
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB801F.F93B46E3"
Date: Tue, 9 Nov 2010 07:08:32 -0800
Message-ID: <68FBE0F3CE97264395875AC1C468F22C514B1C@mail03.cyberswitching.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [eman] Proposed alternation of framework
Thread-Index: Act/0BiA6OD7fTSDQX2u7TA3HsXS6wAS+gJg
References: <AANLkTikFy7hzFSFtQonWZRXe_WAMbpZLLAGWrNjOVcFw@mail.gmail.com> <68FBE0F3CE97264395875AC1C468F22C514A74@mail03.cyberswitching.local> <4CD8DD96.6050507@cisco.com>
From: "Chris Verges" <chrisv@cyberswitching.com>
To: "john parello" <jparello@cisco.com>
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010110201)]
X-MAIL-FROM: <chrisv@cyberswitching.com>
X-SOURCE-IP: [64.81.28.110]
X-AnalysisOut: [v=1.0 c=1 a=rpQdwwq_DzYA:10 a=BLceEmwcHowA:10 a=4zsJQXJisS]
X-AnalysisOut: [Y22NXBO5KRuA==:17 a=8pif782wAAAA:8 a=AUd_NHdVAAAA:8 a=48vg]
X-AnalysisOut: [C7mUAAAA:8 a=g1WrHgk2NeTtDaoiHqIA:9 a=b6bQWggbTTNIA1yOb5YA]
X-AnalysisOut: [:7 a=aHxbnd7LrGBh7NNMbk3Qpdah6VwA:4 a=wPNLvfGTeEIA:10 a=Jf]
X-AnalysisOut: [D0Fch1gWkA:10 a=lZB815dzVvQA:10 a=A9xC4LL2Ej1vbE-W:21 a=6e]
X-AnalysisOut: [nlQhDJskaRG8S8:21 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=9DCU]
X-AnalysisOut: [-ziMdyQs3OVJO4YA:9 a=07Fh-lgwowpOvqUtcuoA:7 a=MhC1JDpJnrwC]
X-AnalysisOut: [iJO4U0E0U0gamQsA:4 a=0KY72OcAf6zflyTT:21 a=X838lcDQzQ6sL-6]
X-AnalysisOut: [P:21]
Cc: eman@ietf.org
Subject: Re: [eman] Proposed alternation of framework
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Nov 2010 15:09:12 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB801F.F93B46E3
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi John,

=20

We may be a little off on our interpretations of the ideal data model.  =
I hope you'll bear with me as we try to come to an understanding on it.

=20

I agree that both of the proposed MIB sets have all of the information =
needed -- "in some way".  What I'm arguing is, with respect, they may =
not have the ideal structure to represent this information quite yet.

=20

The current structure proposed in ENERGY-AWARE-MIB couples the =
definition of the power management entity with its network management =
data (domain, keywords, role) fairly tightly.  This kind of "high =
cohesion" is notoriously bad for complex systems that need to evolve =
over time.  Perhaps I'm making an assumption here, but wouldn't it be =
fair to state that our understanding of managing energy via networks =
will continue to change over the next decade?

=20

All I'm proposing is breaking the existing MIB set apart into more of a =
"low cohesion" pattern.  Like with objects modeled using CRC cards [1] =
from object oriented programming, each MIB/table should have a clearly =
defined set of roles and responsibilities:

=20

=B7         ENTITY-AWARE-MIB

o    pmEntityTable

=A7  Superclass: None

=A7  Responsibilities: List all "energy-aware" devices/components/etc. =
of the SNMP agent that are available

=A7  Collaborations: pmNetworkMgmtTable

o    pmNetworkMgmtTable

=A7  Superclass: pmEntityTable

=A7  Responsibilities: Provide network management attributes for =
modeling an energy-aware entity's relationship to the physical =
infrastructure, other logical devices, business-case groupings, etc.

=A7  Collaborations: pmEntityTable

o    pmEntityPhysicalMapTable

=A7  Superclass: None

=A7  Responsibilities: Map the entries in pmEntityTable with =
entPhysicalTable (ENTITY-MIB)

=A7  Collaborations: pmEntityTable, entPhysicalTable

o    pmEntityLogicalMapTable

=A7  Superclass: None

=A7  Responsibilities: Map the entries in pmEntityTable with =
entLogicalTable (ENTITY-MIB)

=A7  Collaborations: pmEntityTable, entLogicalTable

o    ...

=B7         ...

=20

(I'm using this pattern because it comes across visually in an e-mail, =
but effectively the IETF RFC's do the same thing in their textual =
descriptions of each of the components.)

=20

Currently, pmEntityTable and pmNetworkMgmtTable and =
pmEntityPhysicalMapTable from above are all glued together into a single =
pmTable in ENTITY-MIB.  Yet as you can see from above, they all =
accomplish various different things.  If we split them into three =
separate tables, not only is it clearer in terms of understanding, but =
it also helps when the EMAN WG decides (for example) 2 years from now to =
introduce some new "Smart Grid" integration schema that NIST is pushing. =
 Changes become more isolated to a handful of tables rather than =
impacting the core pmEntityTable, upon which a lot else will be built.

=20

Thanks,

Chris

=20

[1] http://en.wikipedia.org/wiki/CRC_cards

=20

=20

-----Original Message-----
From: john parello [mailto:jparello@cisco.com]=20
Sent: Monday, November 08, 2010 9:35 PM
To: Chris Verges
Cc: eman@ietf.org
Subject: Re: [eman] Proposed alternation of framework

=20

Hi Chris,

=20

Thanks for the replies I agree with your assessments as well. Also with =
respect to initial products I think we are past that.

=20

Both you and I have products which deliver the features that Bruce is =
talking about. So I think we are past initial product and down to =
setting common data modeling between them.

=20

What we need is the common standard that we have expressed in the =
drafts.

=20

w.r.t to the power domain the metering domain described in both

=20

draft-claise-power-management-arch-02

=20

and

=20

draft-parello-eman-energy-aware-mib-00

=20

have the flexibility to be specified based upon the physical metered =
topology but with the context information and tagging the different =
aggregation and reporting you asked for can be obtained.

=20

This is very much analogous to what we do in IP networking with physical =
topology versus vlan etc.

=20

Thanks

Jp

=20

On 11/7/10 5:15 PM, Chris Verges wrote:

> Hi Bruce,

>=20

>=20

>=20

> Questions and comments inline:

>=20

>=20

>=20

> [BN] As an observation, power state is a property of an individual=20

> device and cannot be aggregated.  Power level (W) and energy use can=20

> be readily aggregated.

>=20

>=20

>=20

> [CV] With respect, I think power state can be aggregated.  For=20

> example, please consider a standard datacenter.  When all servers are=20

> turned on in the datacenter, it is at 100% "on" state.  If 30% of the=20

> servers are turned off, the datacenter's state has reduced to 70%. =20

> This is fairly congruous with the ACPI model, where a server can be in =


> different states, and each state represents a power usage level.

>=20

>=20

>=20

> [CV] How such aggregated state is determined is beyond the scope of=20

> any MIB, but the ability to report such information can offer a hook=20

> for innovation in the industry.

>=20

>=20

>=20

> [CV] I agree that power state, like reporting meter data, could be=20

> pushed off to a later release, as enumerating the entities themselves=20

> is far more critical (core?) to establishing anything more complex.

>=20

>=20

>=20

> [BN] There are a number of complications that I would propose=20

> deferring from our initial product.  These include transition states,=20

> support for

>=20

> reporting intervals, and reporting on components within a host.  As=20

> noted above, we could be making progress on these in parallel to the=20

> more basic work, particularly if the content was in separate I-Ds.

>=20

>=20

>=20

> [CV] What would now be in the initial product?  After reading your two =


> recent threads, I'm a little confused over what the "initial product"

> is, as a definition and in its scope.

>=20

>=20

>=20

> [BN] Power Domain

>=20

>=20

>=20

> [BN] A system of power distribution with a common technology and fate.

> Technologies are usually distinguished by voltages and whether AC or =
DC.

> AC examples include 100V, 115V, 200V, and 230V.  DC examples include=20

> 380V, 48V, 24V, 12V, and 5V (variously including eMerge, PoE, USB, and =


> vehicle standards).  Increasingly communications go along with power,=20

> but this is incidental to power reporting.

>=20

>=20

>=20

> [BN] Power domains are often in trees, but this is not strictly=20

> required.  A domain with a single source may have a controller at its=20

> root (e.g. a PoE switch), or not (e.g. a circuit breaker in a =
building).

> At this time, we should consider domains as having a single source of=20

> power; later we could relax that requirement.

>=20

>=20

>=20

> [BN] Common fate includes quality, reliability, availability, total=20

> capacity, and price.  How devices learn what domain they are in is out =


> of our scope.

>=20

>=20

>=20

> [CV] With respect, this concept of a "Power Domain" is very limited to =


> the standard utility/facilities definition.  Given the advent of newer =


> reporting models and systems, should we extend this concept to simply=20

> mean any logical grouping of power entities.  The mapping between=20

> power domains and power entities can be many-to-many, not just =
one-to-many.

>=20

>=20

>=20

> [CV] For example, consider a deployment where the "power domain" is=20

> segmented in two ways: (1) the physical infrastructure, taking into=20

> account branch circuit and transformer capacities; and (2) the billing =


> structure, where entities are "grouped" according to who pays the =
costs.

> If the MIB model only handles a 1:N mapping, the administrator needs=20

> to choose only one.  If the MIB model handles a M:N mapping, more=20

> complex and useful systems can be built on top of this schema.

>=20

>=20

>=20

> Enjoy Beijing,

>=20

> Chris

>=20

>=20

>=20

>=20

>=20

> _______________________________________________

> eman mailing list

> eman@ietf.org <mailto:eman@ietf.org>=20

> https://www.ietf.org/mailman/listinfo/eman =
<https://www.ietf.org/mailman/listinfo/eman>=20


------_=_NextPart_001_01CB801F.F93B46E3
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DGenerator =
content=3D"Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:Consolas;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:639961804;
	mso-list-type:hybrid;
	mso-list-template-ids:-725046292 67698689 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1
	{mso-list-id:1954290522;
	mso-list-type:hybrid;
	mso-list-template-ids:707704022 67698689 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoPlainText>Hi =
John,<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>We may be a little off on our interpretations of =
the ideal data model.&nbsp; I hope you'll bear with me as we try to come =
to an understanding on it.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>I =
agree that both of the proposed MIB sets have all of the information =
needed -- &quot;in some way&quot;.&nbsp; What I'm arguing is, with =
respect, they may not have the ideal structure to represent this =
information quite yet.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>The =
current structure proposed in ENERGY-AWARE-MIB couples the definition of =
the power management entity with its network management data (domain, =
keywords, role) fairly tightly.&nbsp; This kind of &#8220;high =
cohesion&#8221; is notoriously bad for complex systems that need to =
evolve over time.&nbsp; Perhaps I&#8217;m making an assumption here, but =
wouldn&#8217;t it be fair to state that our understanding of managing =
energy via networks will continue to change over the next =
decade?<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>All I&#8217;m proposing is breaking the existing =
MIB set apart into more of a &#8220;low cohesion&#8221; pattern.&nbsp; =
Like with objects modeled using CRC cards [1] from object oriented =
programming, each MIB/table should have a clearly defined set of roles =
and responsibilities:<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><span style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>ENTITY-AWARE-MIB<o:p></o:p></p><p =
class=3DMsoPlainText =
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 =
lfo2'><![if !supportLists]><span style=3D'font-family:"Courier =
New"'><span style=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>pmEntityTable<o:p></o:p></p><p =
class=3DMsoPlainText =
style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l1 level3 =
lfo2'><![if !supportLists]><span style=3D'font-family:Wingdings'><span =
style=3D'mso-list:Ignore'>&sect;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]>Superclass: =
None<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l1 level3 =
lfo2'><![if !supportLists]><span style=3D'font-family:Wingdings'><span =
style=3D'mso-list:Ignore'>&sect;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]>Responsibilities: List all =
&#8220;energy-aware&#8221; devices/components/etc. of the SNMP agent =
that are available<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l1 level3 =
lfo2'><![if !supportLists]><span style=3D'font-family:Wingdings'><span =
style=3D'mso-list:Ignore'>&sect;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]>Collaborations: =
pmNetworkMgmtTable<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 =
lfo2'><![if !supportLists]><span style=3D'font-family:"Courier =
New"'><span style=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>pmNetworkMgmtTable<o:p></o:p></p><p =
class=3DMsoPlainText =
style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l1 level3 =
lfo2'><![if !supportLists]><span style=3D'font-family:Wingdings'><span =
style=3D'mso-list:Ignore'>&sect;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]>Superclass: =
pmEntityTable<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l1 level3 =
lfo2'><![if !supportLists]><span style=3D'font-family:Wingdings'><span =
style=3D'mso-list:Ignore'>&sect;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]>Responsibilities: Provide =
network management attributes for modeling an energy-aware =
entity&#8217;s relationship to the physical infrastructure, other =
logical devices, business-case groupings, etc.<o:p></o:p></p><p =
class=3DMsoPlainText =
style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l1 level3 =
lfo2'><![if !supportLists]><span style=3D'font-family:Wingdings'><span =
style=3D'mso-list:Ignore'>&sect;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]>Collaborations: =
pmEntityTable<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 =
lfo2'><![if !supportLists]><span style=3D'font-family:"Courier =
New"'><span style=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>pmEntityPhysicalMapTable<o:p></o:p></p><p =
class=3DMsoPlainText =
style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l1 level3 =
lfo2'><![if !supportLists]><span style=3D'font-family:Wingdings'><span =
style=3D'mso-list:Ignore'>&sect;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]>Superclass: =
None<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l1 level3 =
lfo2'><![if !supportLists]><span style=3D'font-family:Wingdings'><span =
style=3D'mso-list:Ignore'>&sect;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]>Responsibilities: Map the =
entries in pmEntityTable with entPhysicalTable =
(ENTITY-MIB)<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l1 level3 =
lfo2'><![if !supportLists]><span style=3D'font-family:Wingdings'><span =
style=3D'mso-list:Ignore'>&sect;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]>Collaborations: =
pmEntityTable, entPhysicalTable<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 =
lfo2'><![if !supportLists]><span style=3D'font-family:"Courier =
New"'><span style=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>pmEntityLogicalMapTable<o:p></o:p></p><p =
class=3DMsoPlainText =
style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l1 level3 =
lfo2'><![if !supportLists]><span style=3D'font-family:Wingdings'><span =
style=3D'mso-list:Ignore'>&sect;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]>Superclass: =
None<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l1 level3 =
lfo2'><![if !supportLists]><span style=3D'font-family:Wingdings'><span =
style=3D'mso-list:Ignore'>&sect;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]>Responsibilities: Map the =
entries in pmEntityTable with entLogicalTable =
(ENTITY-MIB)<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l1 level3 =
lfo2'><![if !supportLists]><span style=3D'font-family:Wingdings'><span =
style=3D'mso-list:Ignore'>&sect;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]>Collaborations: =
pmEntityTable, entLogicalTable<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l1 level2 =
lfo2'><![if !supportLists]><span style=3D'font-family:"Courier =
New"'><span style=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "Times =
New Roman"'>&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>...<o:p></o:p></p><p class=3DMsoPlainText =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo2'><![if !supportLists]><span style=3D'font-family:Symbol'><span =
style=3D'mso-list:Ignore'>&middot;<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]>...<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>(I&#8217;m using this pattern because it comes =
across visually in an e-mail, but effectively the IETF RFC&#8217;s do =
the same thing in their textual descriptions of each of the =
components.)<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Currently, pmEntityTable and pmNetworkMgmtTable and =
pmEntityPhysicalMapTable from above are all glued together into a single =
pmTable in ENTITY-MIB.&nbsp; Yet as you can see from above, they all =
accomplish various different things.&nbsp; If we split them into three =
separate tables, not only is it clearer in terms of understanding, but =
it also helps when the EMAN WG decides (for example) 2 years from now to =
introduce some new &#8220;Smart Grid&#8221; integration schema that NIST =
is pushing.&nbsp; Changes become more isolated to a handful of tables =
rather than impacting the core pmEntityTable, upon which a lot else will =
be built.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Thanks,<o:p></o:p></p><p =
class=3DMsoPlainText>Chris<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>[1] <a =
href=3D"http://en.wikipedia.org/wiki/CRC_cards">http://en.wikipedia.org/w=
iki/CRC_cards</a><o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>-----Original Message-----<br>From: john parello =
[mailto:jparello@cisco.com] <br>Sent: Monday, November 08, 2010 9:35 =
PM<br>To: Chris Verges<br>Cc: eman@ietf.org<br>Subject: Re: [eman] =
Proposed alternation of framework</p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Hi =
Chris,<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Thanks for the replies I agree with your =
assessments as well. Also with respect to initial products I think we =
are past that.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>Both =
you and I have products which deliver the features that Bruce is talking =
about. So I think we are past initial product and down to setting common =
data modeling between them.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>What =
we need is the common standard that we have expressed in the =
drafts.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>w.r.t to the power domain the metering domain =
described in both<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>draft-claise-power-management-arch-02<o:p></o:p></p>=
<p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>and<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>draft-parello-eman-energy-aware-mib-00<o:p></o:p></p=
><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>have the flexibility to be specified based upon the =
physical metered topology but with the context information and tagging =
the different aggregation and reporting you asked for can be =
obtained.<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>This is very much analogous to what we do in IP =
networking with physical topology versus vlan etc.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Thanks<o:p></o:p></p><p =
class=3DMsoPlainText>Jp<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>On =
11/7/10 5:15 PM, Chris Verges wrote:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; Hi Bruce,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; Questions and comments =
inline:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; [BN] As an observation, power state is a =
property of an individual <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
device and cannot be aggregated.&nbsp; Power level (W) and energy use =
can <o:p></o:p></p><p class=3DMsoPlainText>&gt; be readily =
aggregated.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; [CV] With respect, I think power state can be =
aggregated.&nbsp; For <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
example, please consider a standard datacenter.&nbsp; When all servers =
are <o:p></o:p></p><p class=3DMsoPlainText>&gt; turned on in the =
datacenter, it is at 100% &quot;on&quot; state.&nbsp; If 30% of the =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; servers are turned off, the =
datacenter's state has reduced to 70%.&nbsp; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; This is fairly congruous with the ACPI model, =
where a server can be in <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
different states, and each state represents a power usage =
level.<o:p></o:p></p><p class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; [CV] How such aggregated state is determined =
is beyond the scope of <o:p></o:p></p><p class=3DMsoPlainText>&gt; any =
MIB, but the ability to report such information can offer a hook =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; for innovation in the =
industry.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; [CV] I agree that power state, like reporting =
meter data, could be <o:p></o:p></p><p class=3DMsoPlainText>&gt; pushed =
off to a later release, as enumerating the entities themselves =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; is far more critical (core?) =
to establishing anything more complex.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; [BN] There are a number of complications that =
I would propose <o:p></o:p></p><p class=3DMsoPlainText>&gt; deferring =
from our initial product.&nbsp; These include transition states, =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; support for<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; reporting intervals, and reporting on =
components within a host.&nbsp; As <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; noted above, we could be making progress on =
these in parallel to the <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
more basic work, particularly if the content was in separate =
I-Ds.<o:p></o:p></p><p class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; [CV] What would now be in the initial =
product?&nbsp; After reading your two <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; recent threads, I'm a little confused over =
what the &quot;initial product&quot;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; is, as a definition and in its =
scope.<o:p></o:p></p><p class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; [BN] Power Domain<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; [BN] A system of power distribution with a =
common technology and fate.<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
Technologies are usually distinguished by voltages and whether AC or =
DC.<o:p></o:p></p><p class=3DMsoPlainText>&gt; AC examples include 100V, =
115V, 200V, and 230V.&nbsp; DC examples include <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; 380V, 48V, 24V, 12V, and 5V (variously =
including eMerge, PoE, USB, and <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; vehicle standards).&nbsp; Increasingly =
communications go along with power, <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; but this is incidental to power =
reporting.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; [BN] Power domains are often in trees, but =
this is not strictly <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
required.&nbsp; A domain with a single source may have a controller at =
its <o:p></o:p></p><p class=3DMsoPlainText>&gt; root (e.g. a PoE =
switch), or not (e.g. a circuit breaker in a building).<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; At this time, we should consider domains as =
having a single source of <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
power; later we could relax that requirement.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; [BN] Common fate includes quality, =
reliability, availability, total <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; capacity, and price.&nbsp; How devices learn =
what domain they are in is out <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; of our scope.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; [CV] With respect, this concept of a =
&quot;Power Domain&quot; is very limited to <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; the standard utility/facilities =
definition.&nbsp; Given the advent of newer <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; reporting models and systems, should we extend =
this concept to simply <o:p></o:p></p><p class=3DMsoPlainText>&gt; mean =
any logical grouping of power entities.&nbsp; The mapping between =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; power domains and power =
entities can be many-to-many, not just one-to-many.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; [CV] For example, consider a deployment where =
the &quot;power domain&quot; is <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; segmented in two ways: (1) the physical =
infrastructure, taking into <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
account branch circuit and transformer capacities; and (2) the billing =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; structure, where entities =
are &quot;grouped&quot; according to who pays the =
costs.<o:p></o:p></p><p class=3DMsoPlainText>&gt; If the MIB model only =
handles a 1:N mapping, the administrator needs <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; to choose only one.&nbsp; If the MIB model =
handles a M:N mapping, more <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
complex and useful systems can be built on top of this =
schema.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; Enjoy Beijing,<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; Chris<o:p></o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt;<o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>&gt; =
_______________________________________________<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; eman mailing list<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; <a href=3D"mailto:eman@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>eman@ietf.org</span></a><=
o:p></o:p></p><p class=3DMsoPlainText>&gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/eman"><span =
style=3D'color:windowtext;text-decoration:none'>https://www.ietf.org/mail=
man/listinfo/eman</span></a><o:p></o:p></p></div></body></html>
------_=_NextPart_001_01CB801F.F93B46E3--

From bill.mielke@alcatel-lucent.com  Tue Nov  9 13:19:05 2010
Return-Path: <bill.mielke@alcatel-lucent.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EE2563A6943 for <eman@core3.amsl.com>; Tue,  9 Nov 2010 13:19:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b1-Wq6Z4ckHG for <eman@core3.amsl.com>; Tue,  9 Nov 2010 13:19:05 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id E2C843A686D for <eman@ietf.org>; Tue,  9 Nov 2010 13:19:04 -0800 (PST)
Received: from usnavsmail2.ndc.alcatel-lucent.com (usnavsmail2.ndc.alcatel-lucent.com [135.3.39.10]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id oA9LJTGx028554 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <eman@ietf.org>; Tue, 9 Nov 2010 15:19:29 -0600 (CST)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by usnavsmail2.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id oA9LJQw6012392 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <eman@ietf.org>; Tue, 9 Nov 2010 15:19:29 -0600
Received: from USNAVSXCHMBSA3.ndc.alcatel-lucent.com ([135.3.39.119]) by USNAVSXCHHUB01.ndc.alcatel-lucent.com ([135.3.39.110]) with mapi; Tue, 9 Nov 2010 15:19:27 -0600
From: "Mielke, William F (Bill)" <bill.mielke@alcatel-lucent.com>
To: "eman@ietf.org" <eman@ietf.org>
Date: Tue, 9 Nov 2010 15:19:19 -0600
Thread-Topic: Comments on "Requirements for Power Monitoring"
Thread-Index: AcuAU8VICnzP+uFHSPK4xKWAZxLwUQ==
Message-ID: <0DEE3BCEE44BFD4EBC3B7DC009C8E79225066CEC63@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0025_01CB8029.DC837BD0"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.10
Subject: [eman] Comments on "Requirements for Power Monitoring"
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Nov 2010 21:19:06 -0000

------=_NextPart_000_0025_01CB8029.DC837BD0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

These comments are relative to
"draft-quittek-power-monitoring-requirements-02".

Substantive Comments:
---------------------

Section 4. Monitoring Models

"Applying these considerations to the required information leads to the
conclusion that most of the information can appropriately be reported using
the pull model.  The only exceptions are notification on power state changes
and high volume time series of energy consumption values."

I disagree with this conclusion.  The requirement is that users of this
standard be able to efficiently transfer the bulk data associated with the
time series data.  The ability to efficiently transfer bulk data is
independent of whether that transfer is initiated using either a push or a
pull model.  In other words, I disagree with the implied notion that large
data transfers can only be accomplished using a push model of management.
SNMP Get-Bulk is the currently defined solution to this problem as I
understand it within the existing IETF management standards and we should
support an approach which is consistent with the directions set in those
standard.

This does not mean that I don't see the need to extend those same standards
to include a more robust push model for use in cases such as this, if
desired, but the applicability of any such extension would be much wider
than simply energy management.  Therefore the proper place to address the
need for such a robust push model extension to SNMP would seem to be within
the SNMP area itself and not as part of the eman specifications.  Energy
management does not appear to have any particularly unique characteristics
in terms of how it's push model might operate whether for Time Series Data
or anything else.

I must admit that I am not currently familiar with the specifics of whether
the SNMP area is considering such an push model extension, or not, but in
the OPSAREA meeting held yesterday I believe that there was some discussion
to this effect.  If so I believe that anything we are proposing here must be
harmonized with anything that happens there.  Does this make sense?



Minor Wordsmithing:
-------------------

Section 1 - 3rd paragraph just before the bullet list:

"can be applied to several areas including" -> "can be applied to several
areas including but not limited to" 

Section 1.1 - 2nd paragraph after the first bullet list:

"without the consequence of a potential performance degredation" -> "without
the consequence of a potential performance or capacity degredation"

Section 3.4.2 - Last paragraph

"the precision of the measured data, i.e. the potential error in the
measured data, needs to be known as well"

I agree with the point being made here but I think the proper term is
"accuracy" rather than "precision".  This is a common point of confusion.
Precision refers to whether you are measuring in, for example, volts or
kilo-volts or milli-volts.  Accuracy refers to the degree to which a
measured value actually represents reality, so a given measurement may be
accurate to +- some percentage.

William F. Mielke
Alcatel-Lucent
Distinguished Member of Technical Staff
6200 East Broad Street
Room: 4B01-1V
Columbus, OH  43213-1530
Email: Bill.Mielke@alcatel-lucent.com
Phone: 614 367 5628

"Live like you're going to die tomorrow.
 Learn like you're going to live forever."

    - Albert Einstein



------=_NextPart_000_0025_01CB8029.DC837BD0
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIV8jCCA7Ew
ggKZoAMCAQICEBErBTlXKN63QvT+VRPTt1EwDQYJKoZIhvcNAQEFBQAwQzEXMBUGA1UEChMOQWxj
YXRlbCBMdWNlbnQxKDAmBgNVBAMTH0FsY2F0ZWwgTHVjZW50IEludGVybmFsIFJvb3QgQ0EwHhcN
MDgxMTAzMTU0MTE2WhcNMjgxMTAzMTU0MTE2WjBDMRcwFQYDVQQKEw5BbGNhdGVsIEx1Y2VudDEo
MCYGA1UEAxMfQWxjYXRlbCBMdWNlbnQgSW50ZXJuYWwgUm9vdCBDQTCCASIwDQYJKoZIhvcNAQEB
BQADggEPADCCAQoCggEBAL5IGBVth8afQdnpuLDI0Z37GgIcPWznOOzFJUV1gVbztqQ5CIxkVL4K
soAfLzc8LQHqNl2Nk3YbVBputIyCe2nzGsRjQeVt+HO2PV7h2YpMQlVd+XGsmpJ4fAP3A38wkTl6
tFPAYspyUFvjNON1J3BJE/2cuY7apvn9ZfSz99x7y4QBZh3hvm4g5Fn7mK04/q7K6O4Z8Y6zkSxG
ZFNyZ6NIuAPNCODZASqYnHiAgtEcCR4WPs6rj+Y8MU0q56ddwuIZ0qeP2ScHY0wVtnmqXzHyCzEQ
Eb2eJCsGpXFwUalVaxPUZEVoVDfjO+2ZN5gNJrGMTu7Mv9k1WG0LR3zZ1QsCAwEAAaOBoDCBnTAL
BgNVHQ8EBAMCAYYwDwYDVR0TAQH/BAUwAwEB/zAdBgNVHQ4EFgQUB6yyWvZhiXxcfOvilycpaQyK
H/AwEAYJKwYBBAGCNxUBBAMCAQAwTAYDVR0gBEUwQzBBBgRVHSAAMDkwNwYIKwYBBQUHAgEWK2h0
dHA6Ly93d3cuYWxjYXRlbC1sdWNlbnQuY29tL1BLSS9jcC9jcC5odG0wDQYJKoZIhvcNAQEFBQAD
ggEBADBMWG3WQyC6+mBzuuFuCGqJAiC4v+TQ3ZErd5KKSRGh8dwjzK5L2C51wJPVe6EAjb59CEb2
p2aPKSkoMrCC8seBRM/bs23DMyna1Jr9Q5EZDrmRqBLJy3Cs8NFpa/cKb6SkegFHcB/vi+SYgSdR
BwoNE5+y6MRPXcEBadI/9W8Zlkk5sJ3w55e+i8OCNg/fDYAQuJPa+hD3/byWGxUgGSMNGQ/GS2st
NETAa5Z/88Sh9FHk2BtrxSz7jPtekKhjsidD2ANJZTCyj9iRB+Nt9FEetNpcN6ke1FlepRbCsV10
I0y6weLwZ34h2GWbN9qEOSQV88NBA149a5ugJ/oCbHEwggTdMIIDxaADAgECAgoanQrOAAAAAAAG
MA0GCSqGSIb3DQEBBQUAMEMxFzAVBgNVBAoTDkFsY2F0ZWwgTHVjZW50MSgwJgYDVQQDEx9BbGNh
dGVsIEx1Y2VudCBJbnRlcm5hbCBSb290IENBMB4XDTA4MTEyMTIxNTcyOFoXDTE4MTEyMTIyMDcy
OFowgYUxEzARBgoJkiaJk/IsZAEZFgNjb20xFjAUBgoJkiaJk/IsZAEZFgZsdWNlbnQxFDASBgoJ
kiaJk/IsZAEZFgRuYTAyMRcwFQYDVQQKEw5BbGNhdGVsIEx1Y2VudDEnMCUGA1UEAxMeQWxjYXRl
bCBMdWNlbnQgSW50ZXJuYWwgU3ViIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA
2Ocmcli3LbVU6TRh+JLMtquBr5/grS+gzfN5YL/lauFCHmDlF7kNQvxtDWqwNpOkzb97CwWcVsdf
kyWAiGzVWeRIrYGhK/xNPFRYXOKYXLGqxFWkltZkYpSRudHzjTneUC4EVdMXnREMu8FTC0CM38Vb
xMvQ+ygjEyicg2QT9lZHWkKP9kCI1818P+AmS7905t6kXR9Q2m1GjcCa0KqARPGX/xe2toQS+Vdi
UwDary1Enk8j19KFmvFg1bhY2mNSHgzN2AWnhsOi/EID1SalzBwHylByB/UbbEv2dZUsAdMuOtYt
Z/8dM1axS0d3fW7q7mAYV5uM42mYX9o1B/RzjwIDAQABo4IBjjCCAYowDwYDVR0TAQH/BAUwAwEB
/zAdBgNVHQ4EFgQU2exrvZZYIvfYpnfN/k2B77qXvRIwCwYDVR0PBAQDAgHGMBAGCSsGAQQBgjcV
AQQDAgEAMBkGCSsGAQQBgjcUAgQMHgoAUwB1AGIAQwBBMB8GA1UdIwQYMBaAFAesslr2YYl8XHzr
4pcnKWkMih/wMHgGA1UdHwRxMG8wbaBroGmGOWh0dHA6Ly9zZXJ2aWNlcy5zdXBwb3J0LmFsY2F0
ZWwtbHVjZW50LmNvbS9QS0kvcm9vdENBLmNybIYsaHR0cDovL3d3dy5hbGNhdGVsLWx1Y2VudC5j
b20vUEtJL3Jvb3RDQS5jcmwwgYIGCCsGAQUFBwEBBHYwdDA4BggrBgEFBQcwAoYsaHR0cDovL3d3
dy5hbGNhdGVsLWx1Y2VudC5jb20vUEtJL3Jvb3RDQS5jcnQwOAYIKwYBBQUHMAKGLGh0dHA6Ly93
d3cuYWxjYXRlbC1sdWNlbnQuY29tL1BLSS9yb290Q0EuY3J0MA0GCSqGSIb3DQEBBQUAA4IBAQCl
GxDp5Z1IDjIEz8VaTEWa8Q1OWUbXwsszdoNg5Gg3F1a2VFFVegmsrpt4axbESlgE6AT/rkUUiyjb
EhcUgY2OHdeKN5Gc7VOGh9D7SER9peARwSwx4NYRrsIaRXDrUswWAM6T6ilDUogjKYk3uK2zZ6Vy
7z3JewxVlhpeSsNPQSMoyNibKkYLRoh6rvz94vB0mvcT0uVx7xowPNoTOjjGRAk4J/MBaNOupvwf
RfPmwRetdnD6NC5x8aRkhr4ZNBjvYxFT8IJaeLk8piQYMPRDlzi7dlb9d6C5WuC0LRpomk2r3bd6
/XpNOx2FyG18axeeASWtENgPvqEirM5MjwkCMIIGejCCBWKgAwIBAgIKGdtaDAAAAAA9bjANBgkq
hkiG9w0BAQUFADCBhTETMBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT8ixkARkWBmx1Y2Vu
dDEUMBIGCgmSJomT8ixkARkWBG5hMDIxFzAVBgNVBAoTDkFsY2F0ZWwgTHVjZW50MScwJQYDVQQD
Ex5BbGNhdGVsIEx1Y2VudCBJbnRlcm5hbCBTdWIgQ0EwHhcNMTAwNTMwMDIwNDQzWhcNMTIwNTI5
MDIwNDQzWjBAMQ8wDQYDVQQDEwZtaWVsa2UxLTArBgkqhkiG9w0BCQEWHmJpbGwubWllbGtlQGFs
Y2F0ZWwtbHVjZW50LmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAo1P58gTZrHri5vsA
ksaizRgNXUTQXDg7A2bIh725bEC7Y8V57vMTMx7kzzXR6iwpLbhn71jbdKFFHV4unSPWMssxwi8g
WanrFLaCSPnaAv/kqeLZ/XjRIsSunLvYpYvYLUuEtjzBUBEnp8uJ7WwhknUVFCf9f6yEXAUBtlbR
eokCAwEAAaOCA7IwggOuMAsGA1UdDwQEAwIHgDAdBgNVHQ4EFgQUs3huZkhOkBtaorqjkncKXxvY
iVowPgYJKwYBBAGCNxUHBDEwLwYnKwYBBAGCNxUIhb3FWYPjsTmHpYEqhr/DQoWUmBmBC4TQtFqF
w+FEAgFkAgEMMB8GA1UdIwQYMBaAFNnsa72WWCL32KZ3zf5Nge+6l70SMIIBXAYDVR0fBIIBUzCC
AU8wggFLoIIBR6CCAUOGgdlsZGFwOi8vL0NOPUFsY2F0ZWwlMjBMdWNlbnQlMjBJbnRlcm5hbCUy
MFN1YiUyMENBLENOPXVzbmF2c3BraTAzcCxDTj1DRFAsQ049UHVibGljJTIwS2V5JTIwU2Vydmlj
ZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixEQz1sdWFkLERDPWx1Y2VudCxEQz1jb20/
Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdD9iYXNlP29iamVjdENsYXNzPWNSTERpc3RyaWJ1dGlv
blBvaW50hitodHRwOi8vd3d3LmFsY2F0ZWwtbHVjZW50LmNvbS9QS0kvc3ViQ0EuY3JshjhodHRw
Oi8vc2VydmljZXMuc3VwcG9ydC5hbGNhdGVsLWx1Y2VudC5jb20vUEtJL3N1YkNBLmNybDCCAWAG
CCsGAQUFBwEBBIIBUjCCAU4wgcwGCCsGAQUFBzAChoG/bGRhcDovLy9DTj1BbGNhdGVsJTIwTHVj
ZW50JTIwSW50ZXJuYWwlMjBTdWIlMjBDQSxDTj1BSUEsQ049UHVibGljJTIwS2V5JTIwU2Vydmlj
ZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixEQz1sdWFkLERDPWx1Y2VudCxEQz1jb20/
Y0FDZXJ0aWZpY2F0ZT9iYXNlP29iamVjdENsYXNzPWNlcnRpZmljYXRpb25BdXRob3JpdHkwNwYI
KwYBBQUHMAKGK2h0dHA6Ly93d3cuYWxjYXRlbC1sdWNlbnQuY29tL1BLSS9zdWJDQS5jcnQwRAYI
KwYBBQUHMAKGOGh0dHA6Ly9zZXJ2aWNlcy5zdXBwb3J0LmFsY2F0ZWwtbHVjZW50LmNvbS9QS0kv
c3ViQ0EuY3J0MBMGA1UdJQQMMAoGCCsGAQUFBwMEMBsGCSsGAQQBgjcVCgQOMAwwCgYIKwYBBQUH
AwQwKQYDVR0RBCIwIIEeYmlsbC5taWVsa2VAYWxjYXRlbC1sdWNlbnQuY29tMA0GCSqGSIb3DQEB
BQUAA4IBAQAZRA+LIZRrEeIu8rlW3yprtze3O5EjtjyNS37sq2o0DatvvucKfFJoes1tLUmgeqKz
eObrOx2ZMpqjhvdzKPw0BmG+vIS2oVU/gSu+Kp9IvlYa/LBJgGqL6uwucG7NKb/KoYwY9XBQerPh
9NcfbsBcFoZlcV9e9J4NIXok2HOwyr+p8hKhK5SpeIoHf3Si8qSuyJuk4FtrjmTlUkgHmoFmj6U9
gKJR6WKpcBZhmOE8eQ9OZAaD1AycT7zdCAsxcBykgM58d59OeZajj1m7ZHTtOppCRMYl1A1lNxOo
w4IuokZ4L85KKzL6WqnuGflYCcNtO9it9JGZharIN+HarP3JMIIG2jCCBcKgAwIBAgIKGdxk1QAA
AAA9bzANBgkqhkiG9w0BAQUFADCBhTETMBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT8ixk
ARkWBmx1Y2VudDEUMBIGCgmSJomT8ixkARkWBG5hMDIxFzAVBgNVBAoTDkFsY2F0ZWwgTHVjZW50
MScwJQYDVQQDEx5BbGNhdGVsIEx1Y2VudCBJbnRlcm5hbCBTdWIgQ0EwHhcNMTAwNTMwMDIwNTUx
WhcNMTIwNTI5MDIwNTUxWjBAMQ8wDQYDVQQDEwZtaWVsa2UxLTArBgkqhkiG9w0BCQEWHmJpbGwu
bWllbGtlQGFsY2F0ZWwtbHVjZW50LmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAqpHW
Jco1co4MTnJ1WFCsJGeMVemFG7SQrcH0LARvpO/o9diiV3/Qvt08MYIv71lXTVBr/Kn8J9Rxq+Ew
eEGygQmO8v+kN3SIUOnWInanbEZkYFdf9jWNEArSvFZiazgrp9vgE3bKK3Id7kUFXXdWj2hK1xjQ
5BidCf9IpfyzKsECAwEAAaOCBBIwggQOMAsGA1UdDwQEAwIFIDBEBgkqhkiG9w0BCQ8ENzA1MA4G
CCqGSIb3DQMCAgIAgDAOBggqhkiG9w0DBAICAIAwBwYFKw4DAgcwCgYIKoZIhvcNAwcwHQYDVR0O
BBYEFFFsCLe38LJX1iIg54BxslUYaXvYMD4GCSsGAQQBgjcVBwQxMC8GJysGAQQBgjcVCIW9xVmD
47E5h6WBKoa/w0KFlJgZgQuCupMPhOrffgIBZAIBDTAfBgNVHSMEGDAWgBTZ7Gu9llgi99imd83+
TYHvupe9EjCCAVwGA1UdHwSCAVMwggFPMIIBS6CCAUegggFDhoHZbGRhcDovLy9DTj1BbGNhdGVs
JTIwTHVjZW50JTIwSW50ZXJuYWwlMjBTdWIlMjBDQSxDTj11c25hdnNwa2kwM3AsQ049Q0RQLENO
PVB1YmxpYyUyMEtleSUyMFNlcnZpY2VzLENOPVNlcnZpY2VzLENOPUNvbmZpZ3VyYXRpb24sREM9
bHVhZCxEQz1sdWNlbnQsREM9Y29tP2NlcnRpZmljYXRlUmV2b2NhdGlvbkxpc3Q/YmFzZT9vYmpl
Y3RDbGFzcz1jUkxEaXN0cmlidXRpb25Qb2ludIYraHR0cDovL3d3dy5hbGNhdGVsLWx1Y2VudC5j
b20vUEtJL3N1YkNBLmNybIY4aHR0cDovL3NlcnZpY2VzLnN1cHBvcnQuYWxjYXRlbC1sdWNlbnQu
Y29tL1BLSS9zdWJDQS5jcmwwggFgBggrBgEFBQcBAQSCAVIwggFOMIHMBggrBgEFBQcwAoaBv2xk
YXA6Ly8vQ049QWxjYXRlbCUyMEx1Y2VudCUyMEludGVybmFsJTIwU3ViJTIwQ0EsQ049QUlBLENO
PVB1YmxpYyUyMEtleSUyMFNlcnZpY2VzLENOPVNlcnZpY2VzLENOPUNvbmZpZ3VyYXRpb24sREM9
bHVhZCxEQz1sdWNlbnQsREM9Y29tP2NBQ2VydGlmaWNhdGU/YmFzZT9vYmplY3RDbGFzcz1jZXJ0
aWZpY2F0aW9uQXV0aG9yaXR5MDcGCCsGAQUFBzAChitodHRwOi8vd3d3LmFsY2F0ZWwtbHVjZW50
LmNvbS9QS0kvc3ViQ0EuY3J0MEQGCCsGAQUFBzAChjhodHRwOi8vc2VydmljZXMuc3VwcG9ydC5h
bGNhdGVsLWx1Y2VudC5jb20vUEtJL3N1YkNBLmNydDAfBgNVHSUEGDAWBggrBgEFBQcDBAYKKwYB
BAGCNwoDBDApBgkrBgEEAYI3FQoEHDAaMAoGCCsGAQUFBwMEMAwGCisGAQQBgjcKAwQwKQYDVR0R
BCIwIIEeYmlsbC5taWVsa2VAYWxjYXRlbC1sdWNlbnQuY29tMA0GCSqGSIb3DQEBBQUAA4IBAQCR
rwYqycRkzGvAxMozWQCh7wJ0axCuF5vqoBkjnhKz4gFtn89WViNTxeLdq+DhfAp3nnzqkE8ggrFn
X5b/DJZgUAGoLlvZ3IL1L0i2Ne3dK5QGq58VFK7KYrluedog6FXZ93jfXtZFq9Z4acpaR0H6DXvg
DAsdbnaLYkWI0+X/enGC7dzkJNQ8D5YUHxAA5qSGATRm6x71kb0R/ShzzFJvpxidYi2bht/mPOIa
ASZD7CSskrRKeaWEke7dKPaUpEPOFVG/do6yuG8iH1PEZ7IYy97x4SuemQmFEMwnjLz1ubf2wzhv
8Hw5Ku2kW2Vw+wI6O+IkjYAir40DgHHLNh4WMYIDVzCCA1MCAQEwgZQwgYUxEzARBgoJkiaJk/Is
ZAEZFgNjb20xFjAUBgoJkiaJk/IsZAEZFgZsdWNlbnQxFDASBgoJkiaJk/IsZAEZFgRuYTAyMRcw
FQYDVQQKEw5BbGNhdGVsIEx1Y2VudDEnMCUGA1UEAxMeQWxjYXRlbCBMdWNlbnQgSW50ZXJuYWwg
U3ViIENBAgoZ21oMAAAAAD1uMAkGBSsOAwIaBQCgggIYMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0B
BwEwHAYJKoZIhvcNAQkFMQ8XDTEwMTEwOTIxMTkxOVowIwYJKoZIhvcNAQkEMRYEFHUpRWf02E1W
eFaph6UjEhbkWzwlMGcGCSqGSIb3DQEJDzFaMFgwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCA
MA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMAcGBSsOAwIaMAoGCCqGSIb3
DQIFMIGlBgkrBgEEAYI3EAQxgZcwgZQwgYUxEzARBgoJkiaJk/IsZAEZFgNjb20xFjAUBgoJkiaJ
k/IsZAEZFgZsdWNlbnQxFDASBgoJkiaJk/IsZAEZFgRuYTAyMRcwFQYDVQQKEw5BbGNhdGVsIEx1
Y2VudDEnMCUGA1UEAxMeQWxjYXRlbCBMdWNlbnQgSW50ZXJuYWwgU3ViIENBAgoZ3GTVAAAAAD1v
MIGnBgsqhkiG9w0BCRACCzGBl6CBlDCBhTETMBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT
8ixkARkWBmx1Y2VudDEUMBIGCgmSJomT8ixkARkWBG5hMDIxFzAVBgNVBAoTDkFsY2F0ZWwgTHVj
ZW50MScwJQYDVQQDEx5BbGNhdGVsIEx1Y2VudCBJbnRlcm5hbCBTdWIgQ0ECChncZNUAAAAAPW8w
DQYJKoZIhvcNAQEBBQAEgYCI4J7q9OrzyeyUdj+nbl36r7+G3TuqajzoaHrGGuDfVQSTPGDAeZ3j
Nwzo306ljS2Wpv6Xb5x/klRnsWptnBYmfaKIYhRNUyiMW3kqo33mfvhZDsSbw7B4sd6jViKcnF8H
hNJBeQQBfN7KEpzRW32OtHil9emrhOUYiVfYZNYhqQAAAAAAAA==

------=_NextPart_000_0025_01CB8029.DC837BD0--

From chrisv@cyberswitching.com  Tue Nov  9 14:03:34 2010
Return-Path: <chrisv@cyberswitching.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8B0E63A6940 for <eman@core3.amsl.com>; Tue,  9 Nov 2010 14:03:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7fl3ioZ5n73D for <eman@core3.amsl.com>; Tue,  9 Nov 2010 14:03:33 -0800 (PST)
Received: from p01c12o141.mxlogic.net (p01c12o141.mxlogic.net [208.65.145.64]) by core3.amsl.com (Postfix) with ESMTP id C39043A696C for <eman@ietf.org>; Tue,  9 Nov 2010 14:03:32 -0800 (PST)
Received: from unknown [64.81.28.110] (EHLO mail03.cyberswitching.local) by p01c12o141.mxlogic.net(mxl_mta-6.7.0-2) with ESMTP id d45c9dc4.0.7553.00-384.17824.p01c12o141.mxlogic.net (envelope-from <chrisv@cyberswitching.com>);  Tue, 09 Nov 2010 15:03:58 -0700 (MST)
X-MXL-Hash: 4cd9c54e15a11419-490989e13247b037233c77f983cbb1b730c603e2
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 9 Nov 2010 14:03:06 -0800
Message-ID: <68FBE0F3CE97264395875AC1C468F22C514B72@mail03.cyberswitching.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [eman] New draft draft-quittek-eman-reference-model-00
Thread-Index: Act/39XT4axbhH+YSgmGgrAk4C/+3wAdkb4w
References: <20101108224927.6B96728C0DB@core3.amsl.com><C8FEA7BA.16D4A%quittek@neclab.eu> <AANLkTik-fGiNo+qTnj0LMMvygp_rSZkKgEvgSukaTn0X@mail.gmail.com>
From: "Chris Verges" <chrisv@cyberswitching.com>
To: "Juergen Quittek" <Quittek@neclab.eu>
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010110201)]
X-MAIL-FROM: <chrisv@cyberswitching.com>
X-SOURCE-IP: [64.81.28.110]
X-AnalysisOut: [v=1.0 c=1 a=NhDX0KWKZ8AA:10 a=BLceEmwcHowA:10 a=8nJEP1OIZ-]
X-AnalysisOut: [IA:10 a=4zsJQXJisSY22NXBO5KRuA==:17 a=wzgqfsuUAAAA:8 a=48v]
X-AnalysisOut: [gC7mUAAAA:8 a=m-lYr6aYvV0VJpJzYrsA:9 a=uels0MiBpVweuUtvtfM]
X-AnalysisOut: [A:7 a=ue9aF7jlxMKeR-isppDhyzqkfZUA:4 a=wPNLvfGTeEIA:10 a=l]
X-AnalysisOut: [ZB815dzVvQA:10 a=JY5OXjoDnfes75AV:21 a=5MjpVQJ-5Yn5Y4PC:21]
Cc: eman mailing list <eman@ietf.org>
Subject: Re: [eman] New draft draft-quittek-eman-reference-model-00
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Nov 2010 22:03:34 -0000

Hi Juergen,

In addition to JinHyeock's comments below, I notice that none of the use =
cases described in section 5 describe a case whereby a single device =
contains multiple energy meters with multiple energy consumers.  =
Building off the simpler subset shown in Section 5.3, I created a more =
complex model that is required for our product set:

http://demo.cyberswitching.com/chrisv/20101109-01_Intelligent_PDU_Use_Cas=
e.pdf

(Admittedly, I'm not as skilled in the ancient art of ASCII [art] as =
you, so took refudge to Visio for time considerations.)

If I misused any of the terms, I apologize.  The draft was definitely =
full of definitions, and I'm working to come up to speed on your usage =
of them.

In this scenario, I need to report the data for EACH Energy Consumption =
Meter listed __AND__ multiple aggregations of that meter data, based on =
business case needs.  (That is, "domains" can be defined in several =
different ways, simultaneously.)

Please comment on how such a use case might be modeled to ensure =
flexibility and future feature expansion by both the IETF and enterprise =
vendors.

Chris


-----Original Message-----
From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of =
JinHyeock Choi
Sent: Monday, November 08, 2010 11:30 PM
To: Juergen Quittek
Cc: eman mailing list
Subject: Re: [eman] New draft draft-quittek-eman-reference-model-00

Dear Juergen

Thanks for the draft
which also improved my understanding of energy management, especially =
about involving entities & their interactions.

Here are some quick comments.

First, the figure in Sec 3 gives an impression that single 'Energy =
Management System' manages 1.Power Provisioning Controller & 2.Energy =
Consumption Reporter 3.Power Controller but usually the first is managed =
by an electric power company whereas 2nd & 3rd may by network operator =
(or else).

For example, even if a mobile operator builds a management system to =
monitor & control its equipments, I wonder whether the system can also =
control the power supply.

It may be better to divide Energy Management System into two entities =
(as done for Power Provisioning Controller & Power Controller.)

Second, I wish the draft mentions more about the relationship among =
entities such as a single Energy Consumption Reporter can associate with =
several Energy Consumers/ Energy Consumption meters to aggregate the =
monitoring information or which constitute power domain or meter domain, =
(which still elude my understanding.)

In summary, the draft clarifies the overall energy management picture =
much (surprised how quickly you turned out a draft from discussion) and =
I wish the content would be integrated into eman work items such as =
architecture draft.

Thanks for your kind consideration.

Best regards

JinHyeock Choi




On Tue, Nov 9, 2010 at 8:25 AM, Juergen Quittek <Quittek@neclab.eu> =
wrote:
> Dear all,
>
> The discussions on this list during the last days and in restaurants=20
> at the last nights have been quite inspiring. Particularly my=20
> understanding of the fundamental steps of energy management has =
improved.
>
> I tried to record some of the new insights in an Internet draft that I =

> just posted. It suggests a more detailed reference model for energy=20
> management than we have it so far. Please find it at=20
> http://datatracker.ietf.org/doc/draft-quittek-eman-reference-model/
>
> This is just a contribution to the ongoing discussion. I have no=20
> intention of adding another document to our charter. The content of=20
> this draft will hopefully help understanding better what energy =
management is or could be.
>
> I know this draft arrives too late for discussing it during the=20
> session tomorrow. But we can do this on the list. Comments are highly =
appreciated.
>
> Thanks,
>
> =A0 =A0Juergen
>
>
> ------ Forwarded message
> From: IETF I-D Submission Tool <idsubmission@ietf.org>
> Date: Mon, 8 Nov 2010 14:49:27 -0800
> To: <quittek@neclab.eu>
> Subject: New Version Notification for =A0
> draft-quittek-eman-reference-model-00
>
>
> A new version of I-D, draft-quittek-eman-reference-model-00.txt has=20
> been successfully submitted by Juergen Quittek and posted to the IETF =
repository.
>
> Filename: =A0draft-quittek-eman-reference-model
> Revision: =A000
> Title: =A0 Reference Model for Energy Management
> Creation_date: =A02010-11-08
> WG ID: =A0 Independent Submission
> Number_of_pages: 15
>
> Abstract:
> This memo discusses suggest a reference model for energy consumption=20
> monitoring and control. =A0It defines entities involved in energy=20
> management, their roles, and relationships between them. =A0Considered =

> entities include energy consumers, energy consumption meters, energy=20
> consumption reporters, energy consumption controllers, and energy=20
> consumption management systems.
>
> The IETF Secretariat.
>
> ------ end of forwarded message
>
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman
>
>
_______________________________________________
eman mailing list
eman@ietf.org
https://www.ietf.org/mailman/listinfo/eman

From bnordman@lbl.gov  Tue Nov  9 19:08:53 2010
Return-Path: <bnordman@lbl.gov>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4325728C0E6 for <eman@core3.amsl.com>; Tue,  9 Nov 2010 19:08:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.56
X-Spam-Level: 
X-Spam-Status: No, score=-5.56 tagged_above=-999 required=5 tests=[AWL=0.416,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R12nSvItW3oK for <eman@core3.amsl.com>; Tue,  9 Nov 2010 19:08:52 -0800 (PST)
Received: from ironport2.lbl.gov (ironport2.lbl.gov [128.3.41.14]) by core3.amsl.com (Postfix) with ESMTP id 03F693A680C for <eman@ietf.org>; Tue,  9 Nov 2010 19:08:51 -0800 (PST)
X-Ironport-SBRS: 4.4
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlECAOab2UzRVditkGdsb2JhbACBb5g7AYgICBUBAQEBCQkMBxEDH6FQmhmDC4I/BIFbgnyFfw
X-IronPort-AV: E=Sophos;i="4.59,176,1288594800"; d="scan'208";a="115735295"
Received: from mail-qy0-f173.google.com ([209.85.216.173]) by ironport2.lbl.gov with ESMTP; 09 Nov 2010 19:09:17 -0800
Received: by mail-qy0-f173.google.com with SMTP id 33so2467956qyl.18 for <eman@ietf.org>; Tue, 09 Nov 2010 19:09:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.224.178.201 with SMTP id bn9mr5906012qab.254.1289358557423; Tue, 09 Nov 2010 19:09:17 -0800 (PST)
Received: by 10.229.105.8 with HTTP; Tue, 9 Nov 2010 19:09:17 -0800 (PST)
In-Reply-To: <68FBE0F3CE97264395875AC1C468F22C514B72@mail03.cyberswitching.local>
References: <20101108224927.6B96728C0DB@core3.amsl.com> <C8FEA7BA.16D4A%quittek@neclab.eu> <AANLkTik-fGiNo+qTnj0LMMvygp_rSZkKgEvgSukaTn0X@mail.gmail.com> <68FBE0F3CE97264395875AC1C468F22C514B72@mail03.cyberswitching.local>
Date: Wed, 10 Nov 2010 11:09:17 +0800
Message-ID: <AANLkTinJDPX5Z2Agp015vLrDfcyfvsLW1+ux8uUy6g+8@mail.gmail.com>
From: Bruce Nordman <bnordman@lbl.gov>
To: Chris Verges <chrisv@cyberswitching.com>
Content-Type: multipart/alternative; boundary=20cf303b3afdcda7d40494aa2eb4
Cc: eman mailing list <eman@ietf.org>
Subject: Re: [eman] New draft draft-quittek-eman-reference-model-00
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Nov 2010 03:08:53 -0000

--20cf303b3afdcda7d40494aa2eb4
Content-Type: text/plain; charset=ISO-8859-1

Chris--
  In your diagram, does the Reporter communicate only the total power
consumed from each supply, or is the supply part broken out by consumer?
Certainly the former is simpler, but your diagram seems to indicate
the latter.
  In your diagram, the power seems not to be pooled, but rather the
two electricity domains don't interact.  How about logically dividing
the PDU into two units, each with only one power supply.  Would that
meet your needs?
--Bruce

On Wed, Nov 10, 2010 at 6:03 AM, Chris Verges <chrisv@cyberswitching.com>wrote:

> Hi Juergen,
>
> In addition to JinHyeock's comments below, I notice that none of the use
> cases described in section 5 describe a case whereby a single device
> contains multiple energy meters with multiple energy consumers.  Building
> off the simpler subset shown in Section 5.3, I created a more complex model
> that is required for our product set:
>
>
> http://demo.cyberswitching.com/chrisv/20101109-01_Intelligent_PDU_Use_Case.pdf
>
> (Admittedly, I'm not as skilled in the ancient art of ASCII [art] as you,
> so took refudge to Visio for time considerations.)
>
> If I misused any of the terms, I apologize.  The draft was definitely full
> of definitions, and I'm working to come up to speed on your usage of them.
>
> In this scenario, I need to report the data for EACH Energy Consumption
> Meter listed __AND__ multiple aggregations of that meter data, based on
> business case needs.  (That is, "domains" can be defined in several
> different ways, simultaneously.)
>
> Please comment on how such a use case might be modeled to ensure
> flexibility and future feature expansion by both the IETF and enterprise
> vendors.
>
> Chris
>
> --
*Bruce Nordman*
Lawrence Berkeley National Laboratory
eetd.lbl.gov/ea/nordman
BNordman@LBL.gov
510-486-7089
m: 510-501-7943

--20cf303b3afdcda7d40494aa2eb4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Chris--<br>=A0 In your diagram, does the Reporter communicate only the tota=
l power<br>consumed from each supply, or is the supply part broken out by c=
onsumer?<br>Certainly the former is simpler, but your diagram seems to indi=
cate<br>
the latter.<br>=A0 In your diagram, the power seems not to be pooled, but r=
ather the<br>two electricity domains don&#39;t interact.=A0 How about logic=
ally dividing<br>the PDU into two units, each with only one power supply.=
=A0 Would that<br>
meet your needs?<br>--Bruce<br><br><div class=3D"gmail_quote">On Wed, Nov 1=
0, 2010 at 6:03 AM, Chris Verges <span dir=3D"ltr">&lt;<a href=3D"mailto:ch=
risv@cyberswitching.com">chrisv@cyberswitching.com</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; bord=
er-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi Juergen,<br>
<br>
In addition to JinHyeock&#39;s comments below, I notice that none of the us=
e cases described in section 5 describe a case whereby a single device cont=
ains multiple energy meters with multiple energy consumers. =A0Building off=
 the simpler subset shown in Section 5.3, I created a more complex model th=
at is required for our product set:<br>

<br>
<a href=3D"http://demo.cyberswitching.com/chrisv/20101109-01_Intelligent_PD=
U_Use_Case.pdf" target=3D"_blank">http://demo.cyberswitching.com/chrisv/201=
01109-01_Intelligent_PDU_Use_Case.pdf</a><br>
<br>
(Admittedly, I&#39;m not as skilled in the ancient art of ASCII [art] as yo=
u, so took refudge to Visio for time considerations.)<br>
<br>
If I misused any of the terms, I apologize. =A0The draft was definitely ful=
l of definitions, and I&#39;m working to come up to speed on your usage of =
them.<br>
<br>
In this scenario, I need to report the data for EACH Energy Consumption Met=
er listed __AND__ multiple aggregations of that meter data, based on busine=
ss case needs. =A0(That is, &quot;domains&quot; can be defined in several d=
ifferent ways, simultaneously.)<br>

<br>
Please comment on how such a use case might be modeled to ensure flexibilit=
y and future feature expansion by both the IETF and enterprise vendors.<br>
<font color=3D"#888888"><br>
Chris<br>
</font><div><div></div><br></div></blockquote></div>-- <br><font size=3D"4"=
><b>Bruce Nordman</b></font><br><span style=3D"color: rgb(0, 0, 153);">Lawr=
ence Berkeley National Laboratory</span><br><a href=3D"http://eetd.lbl.gov/=
ea/nordman" target=3D"_blank">eetd.lbl.gov/ea/nordman</a><br>
BNordman@LBL.gov<br>510-486-7089<br>m: 510-501-7943<br><br>

--20cf303b3afdcda7d40494aa2eb4--

From bill.mielke@alcatel-lucent.com  Tue Nov  9 19:09:06 2010
Return-Path: <bill.mielke@alcatel-lucent.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7FA903A680A for <eman@core3.amsl.com>; Tue,  9 Nov 2010 19:09:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gaOhoMPepZ5q for <eman@core3.amsl.com>; Tue,  9 Nov 2010 19:09:05 -0800 (PST)
Received: from ihemail4.lucent.com (ihemail4.lucent.com [135.245.0.39]) by core3.amsl.com (Postfix) with ESMTP id E558928C105 for <eman@ietf.org>; Tue,  9 Nov 2010 19:09:04 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail4.lucent.com (8.13.8/IER-o) with ESMTP id oAA39TeZ004648 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <eman@ietf.org>; Tue, 9 Nov 2010 21:09:29 -0600 (CST)
Received: from USNAVSXCHHUB02.ndc.alcatel-lucent.com (usnavsxchhub02.ndc.alcatel-lucent.com [135.3.39.111]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id oAA39SaL000549 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <eman@ietf.org>; Tue, 9 Nov 2010 21:09:29 -0600
Received: from USNAVSXCHMBSA3.ndc.alcatel-lucent.com ([135.3.39.119]) by USNAVSXCHHUB02.ndc.alcatel-lucent.com ([135.3.39.111]) with mapi; Tue, 9 Nov 2010 21:09:29 -0600
From: "Mielke, William F (Bill)" <bill.mielke@alcatel-lucent.com>
To: "eman@ietf.org" <eman@ietf.org>
Date: Tue, 9 Nov 2010 21:09:19 -0600
Thread-Topic: Comments on "Requirements for Power Monitoring"
Thread-Index: AcuAU8VICnzP+uFHSPK4xKWAZxLwUQAL5WAw
Message-ID: <0DEE3BCEE44BFD4EBC3B7DC009C8E79225066CED3F@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
References: <0DEE3BCEE44BFD4EBC3B7DC009C8E79225066CEC63@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
In-Reply-To: <0DEE3BCEE44BFD4EBC3B7DC009C8E79225066CEC63@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_004D_01CB805A.C1D5FE30"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.39
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Subject: Re: [eman] Comments on "Requirements for Power Monitoring"
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Nov 2010 03:09:06 -0000

------=_NextPart_000_004D_01CB805A.C1D5FE30
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Sigh.  I apologize.  Somehow my email system has managed to send an
intermediate draft of my comments and thus deleted some of them.  I shall
reproduce them here:

These comments are relative to
"draft-quittek-power-monitoring-requirements-02".

--------------------
Substantive Comments
--------------------

Section 4. Monitoring Models
----------------------------

My first sentence should have instead read: "I disagree with part of this
conclusion, specifically the last sentence."

Section 5. Control Requirements
-------------------------------

I believe that there is some need of work on this section.  My initial
reading of it is that it suggests a more direct style of management and
control than is expected or desired.

A crude example of what I mean is that we do not expect a Network Management
System to be proactively monitoring the power states of an individual CPU on
some line card or to be actively setting and resetting the states on those
individual CPUs.  It is true that from a management perspective such an NMS
may have need to be able to drill down and to report on the current power
status of such a CPU, to perhaps examine historical data about the state
transitions thereof, and in some very rare circumstances even be able to
effect a direct control on on such a component (although in this example
such action would be absurd).  The concept itself will have greater or
lessor applicability depending on the levels of abstraction within the NMS
heiarchy which are being discussed.

A more likely scenario is that the NMS will want to set specific power
related policies within the line card itself (or the containing device) and
then rely on the line card to manage the transitions of the individual CPUs
itself.  From the NMS perspective, such policies would be established so as
to effect an operator specific set of desired service levels with respect to
capacity, availability, etc.  Upon setting such policy based parameters the
device should be as self-managing as possible with respect to it's own
resources.

The goal, of course, is to enable individual pieces of equipment to operate
semi-autonomously or in conjunction with their peers so as to better match
the actual power consumption of the network equipment to the required
network loads as they vary over time.

I think some discussion of this policy based scenario would be desirable in
this section.

Section 7. Suggested Actions
----------------------------

I believe that most of this section may be misplaced in this document.  The
main points being made are more implementation decisions than actual
requirements.

Returning to the example of the efficient transfer of Time Series Data, the
actual requirement is that users of this standard to be able to efficiently
transfer such data.  Any discussions of push mode management and/or binding
to specific implementations thereof such as the currently proposed IPFIX
approach would probably be better placed in the architecture/framework
document than here in the requirements.

I recommend that we simply delete this section in the requirements document
and work to incorporate any of the specifics of the implementations
appropriately within the architecture/framework document.

I believe that my concerns about defining more robust push mode extensions
to the existing SNMP management approach apply here as well.  Our proposals
must be in line with the management directions set by the SNMP area.  Any
possible approaches to achieving those (such as the current IPFIX proposal)
are best handled within the SNMP area itself and anything we have to say on
the subject would have to be harmonized with those management standards.

Section 9. Security Considerations
----------------------------------

Without trying to enumerate what they might be at this time, by the time we
are finished with this document I anticipate that we should have something
to say in this area.  Enabling control of power without imposing or
addressing security concerns would be a mistake I think.  I will try to
offer some suggestions in follow-up email and I believe that the
Architecture/Framework document has made a bit of a start in this area
already.

Thanks,

William F. Mielke
Alcatel-Lucent
Distinguished Member of Technical Staff
6200 East Broad Street
Room: 4B01-1V
Columbus, OH  43213-1530
Email: Bill.Mielke@alcatel-lucent.com
Phone: 614 367 5628
Fax: 614 367 5965

"Live like you're going to die tomorrow.
 Learn like you're going to live forever."

    - Albert Einstein

-----Original Message-----
From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of
Mielke, William F (Bill)
Sent: Tuesday, November 09, 2010 4:19 PM
To: eman@ietf.org
Subject: [eman] Comments on "Requirements for Power Monitoring"

These comments are relative to
"draft-quittek-power-monitoring-requirements-02".

Substantive Comments:
---------------------

Section 4. Monitoring Models

"Applying these considerations to the required information leads to the
conclusion that most of the information can appropriately be reported using
the pull model.  The only exceptions are notification on power state changes
and high volume time series of energy consumption values."

I disagree with this conclusion.  The requirement is that users of this
standard be able to efficiently transfer the bulk data associated with the
time series data.  The ability to efficiently transfer bulk data is
independent of whether that transfer is initiated using either a push or a
pull model.  In other words, I disagree with the implied notion that large
data transfers can only be accomplished using a push model of management.
SNMP Get-Bulk is the currently defined solution to this problem as I
understand it within the existing IETF management standards and we should
support an approach which is consistent with the directions set in those
standard.

This does not mean that I don't see the need to extend those same standards
to include a more robust push model for use in cases such as this, if
desired, but the applicability of any such extension would be much wider
than simply energy management.  Therefore the proper place to address the
need for such a robust push model extension to SNMP would seem to be within
the SNMP area itself and not as part of the eman specifications.  Energy
management does not appear to have any particularly unique characteristics
in terms of how it's push model might operate whether for Time Series Data
or anything else.

I must admit that I am not currently familiar with the specifics of whether
the SNMP area is considering such an push model extension, or not, but in
the OPSAREA meeting held yesterday I believe that there was some discussion
to this effect.  If so I believe that anything we are proposing here must be
harmonized with anything that happens there.  Does this make sense?



Minor Wordsmithing:
-------------------

Section 1 - 3rd paragraph just before the bullet list:

"can be applied to several areas including" -> "can be applied to several
areas including but not limited to" 

Section 1.1 - 2nd paragraph after the first bullet list:

"without the consequence of a potential performance degredation" -> "without
the consequence of a potential performance or capacity degredation"

Section 3.4.2 - Last paragraph

"the precision of the measured data, i.e. the potential error in the
measured data, needs to be known as well"

I agree with the point being made here but I think the proper term is
"accuracy" rather than "precision".  This is a common point of confusion.
Precision refers to whether you are measuring in, for example, volts or
kilo-volts or milli-volts.  Accuracy refers to the degree to which a
measured value actually represents reality, so a given measurement may be
accurate to +- some percentage.

William F. Mielke
Alcatel-Lucent
Distinguished Member of Technical Staff
6200 East Broad Street
Room: 4B01-1V
Columbus, OH  43213-1530
Email: Bill.Mielke@alcatel-lucent.com
Phone: 614 367 5628

"Live like you're going to die tomorrow.
 Learn like you're going to live forever."

    - Albert Einstein



------=_NextPart_000_004D_01CB805A.C1D5FE30
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIV8jCCA7Ew
ggKZoAMCAQICEBErBTlXKN63QvT+VRPTt1EwDQYJKoZIhvcNAQEFBQAwQzEXMBUGA1UEChMOQWxj
YXRlbCBMdWNlbnQxKDAmBgNVBAMTH0FsY2F0ZWwgTHVjZW50IEludGVybmFsIFJvb3QgQ0EwHhcN
MDgxMTAzMTU0MTE2WhcNMjgxMTAzMTU0MTE2WjBDMRcwFQYDVQQKEw5BbGNhdGVsIEx1Y2VudDEo
MCYGA1UEAxMfQWxjYXRlbCBMdWNlbnQgSW50ZXJuYWwgUm9vdCBDQTCCASIwDQYJKoZIhvcNAQEB
BQADggEPADCCAQoCggEBAL5IGBVth8afQdnpuLDI0Z37GgIcPWznOOzFJUV1gVbztqQ5CIxkVL4K
soAfLzc8LQHqNl2Nk3YbVBputIyCe2nzGsRjQeVt+HO2PV7h2YpMQlVd+XGsmpJ4fAP3A38wkTl6
tFPAYspyUFvjNON1J3BJE/2cuY7apvn9ZfSz99x7y4QBZh3hvm4g5Fn7mK04/q7K6O4Z8Y6zkSxG
ZFNyZ6NIuAPNCODZASqYnHiAgtEcCR4WPs6rj+Y8MU0q56ddwuIZ0qeP2ScHY0wVtnmqXzHyCzEQ
Eb2eJCsGpXFwUalVaxPUZEVoVDfjO+2ZN5gNJrGMTu7Mv9k1WG0LR3zZ1QsCAwEAAaOBoDCBnTAL
BgNVHQ8EBAMCAYYwDwYDVR0TAQH/BAUwAwEB/zAdBgNVHQ4EFgQUB6yyWvZhiXxcfOvilycpaQyK
H/AwEAYJKwYBBAGCNxUBBAMCAQAwTAYDVR0gBEUwQzBBBgRVHSAAMDkwNwYIKwYBBQUHAgEWK2h0
dHA6Ly93d3cuYWxjYXRlbC1sdWNlbnQuY29tL1BLSS9jcC9jcC5odG0wDQYJKoZIhvcNAQEFBQAD
ggEBADBMWG3WQyC6+mBzuuFuCGqJAiC4v+TQ3ZErd5KKSRGh8dwjzK5L2C51wJPVe6EAjb59CEb2
p2aPKSkoMrCC8seBRM/bs23DMyna1Jr9Q5EZDrmRqBLJy3Cs8NFpa/cKb6SkegFHcB/vi+SYgSdR
BwoNE5+y6MRPXcEBadI/9W8Zlkk5sJ3w55e+i8OCNg/fDYAQuJPa+hD3/byWGxUgGSMNGQ/GS2st
NETAa5Z/88Sh9FHk2BtrxSz7jPtekKhjsidD2ANJZTCyj9iRB+Nt9FEetNpcN6ke1FlepRbCsV10
I0y6weLwZ34h2GWbN9qEOSQV88NBA149a5ugJ/oCbHEwggTdMIIDxaADAgECAgoanQrOAAAAAAAG
MA0GCSqGSIb3DQEBBQUAMEMxFzAVBgNVBAoTDkFsY2F0ZWwgTHVjZW50MSgwJgYDVQQDEx9BbGNh
dGVsIEx1Y2VudCBJbnRlcm5hbCBSb290IENBMB4XDTA4MTEyMTIxNTcyOFoXDTE4MTEyMTIyMDcy
OFowgYUxEzARBgoJkiaJk/IsZAEZFgNjb20xFjAUBgoJkiaJk/IsZAEZFgZsdWNlbnQxFDASBgoJ
kiaJk/IsZAEZFgRuYTAyMRcwFQYDVQQKEw5BbGNhdGVsIEx1Y2VudDEnMCUGA1UEAxMeQWxjYXRl
bCBMdWNlbnQgSW50ZXJuYWwgU3ViIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA
2Ocmcli3LbVU6TRh+JLMtquBr5/grS+gzfN5YL/lauFCHmDlF7kNQvxtDWqwNpOkzb97CwWcVsdf
kyWAiGzVWeRIrYGhK/xNPFRYXOKYXLGqxFWkltZkYpSRudHzjTneUC4EVdMXnREMu8FTC0CM38Vb
xMvQ+ygjEyicg2QT9lZHWkKP9kCI1818P+AmS7905t6kXR9Q2m1GjcCa0KqARPGX/xe2toQS+Vdi
UwDary1Enk8j19KFmvFg1bhY2mNSHgzN2AWnhsOi/EID1SalzBwHylByB/UbbEv2dZUsAdMuOtYt
Z/8dM1axS0d3fW7q7mAYV5uM42mYX9o1B/RzjwIDAQABo4IBjjCCAYowDwYDVR0TAQH/BAUwAwEB
/zAdBgNVHQ4EFgQU2exrvZZYIvfYpnfN/k2B77qXvRIwCwYDVR0PBAQDAgHGMBAGCSsGAQQBgjcV
AQQDAgEAMBkGCSsGAQQBgjcUAgQMHgoAUwB1AGIAQwBBMB8GA1UdIwQYMBaAFAesslr2YYl8XHzr
4pcnKWkMih/wMHgGA1UdHwRxMG8wbaBroGmGOWh0dHA6Ly9zZXJ2aWNlcy5zdXBwb3J0LmFsY2F0
ZWwtbHVjZW50LmNvbS9QS0kvcm9vdENBLmNybIYsaHR0cDovL3d3dy5hbGNhdGVsLWx1Y2VudC5j
b20vUEtJL3Jvb3RDQS5jcmwwgYIGCCsGAQUFBwEBBHYwdDA4BggrBgEFBQcwAoYsaHR0cDovL3d3
dy5hbGNhdGVsLWx1Y2VudC5jb20vUEtJL3Jvb3RDQS5jcnQwOAYIKwYBBQUHMAKGLGh0dHA6Ly93
d3cuYWxjYXRlbC1sdWNlbnQuY29tL1BLSS9yb290Q0EuY3J0MA0GCSqGSIb3DQEBBQUAA4IBAQCl
GxDp5Z1IDjIEz8VaTEWa8Q1OWUbXwsszdoNg5Gg3F1a2VFFVegmsrpt4axbESlgE6AT/rkUUiyjb
EhcUgY2OHdeKN5Gc7VOGh9D7SER9peARwSwx4NYRrsIaRXDrUswWAM6T6ilDUogjKYk3uK2zZ6Vy
7z3JewxVlhpeSsNPQSMoyNibKkYLRoh6rvz94vB0mvcT0uVx7xowPNoTOjjGRAk4J/MBaNOupvwf
RfPmwRetdnD6NC5x8aRkhr4ZNBjvYxFT8IJaeLk8piQYMPRDlzi7dlb9d6C5WuC0LRpomk2r3bd6
/XpNOx2FyG18axeeASWtENgPvqEirM5MjwkCMIIGejCCBWKgAwIBAgIKGdtaDAAAAAA9bjANBgkq
hkiG9w0BAQUFADCBhTETMBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT8ixkARkWBmx1Y2Vu
dDEUMBIGCgmSJomT8ixkARkWBG5hMDIxFzAVBgNVBAoTDkFsY2F0ZWwgTHVjZW50MScwJQYDVQQD
Ex5BbGNhdGVsIEx1Y2VudCBJbnRlcm5hbCBTdWIgQ0EwHhcNMTAwNTMwMDIwNDQzWhcNMTIwNTI5
MDIwNDQzWjBAMQ8wDQYDVQQDEwZtaWVsa2UxLTArBgkqhkiG9w0BCQEWHmJpbGwubWllbGtlQGFs
Y2F0ZWwtbHVjZW50LmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAo1P58gTZrHri5vsA
ksaizRgNXUTQXDg7A2bIh725bEC7Y8V57vMTMx7kzzXR6iwpLbhn71jbdKFFHV4unSPWMssxwi8g
WanrFLaCSPnaAv/kqeLZ/XjRIsSunLvYpYvYLUuEtjzBUBEnp8uJ7WwhknUVFCf9f6yEXAUBtlbR
eokCAwEAAaOCA7IwggOuMAsGA1UdDwQEAwIHgDAdBgNVHQ4EFgQUs3huZkhOkBtaorqjkncKXxvY
iVowPgYJKwYBBAGCNxUHBDEwLwYnKwYBBAGCNxUIhb3FWYPjsTmHpYEqhr/DQoWUmBmBC4TQtFqF
w+FEAgFkAgEMMB8GA1UdIwQYMBaAFNnsa72WWCL32KZ3zf5Nge+6l70SMIIBXAYDVR0fBIIBUzCC
AU8wggFLoIIBR6CCAUOGgdlsZGFwOi8vL0NOPUFsY2F0ZWwlMjBMdWNlbnQlMjBJbnRlcm5hbCUy
MFN1YiUyMENBLENOPXVzbmF2c3BraTAzcCxDTj1DRFAsQ049UHVibGljJTIwS2V5JTIwU2Vydmlj
ZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixEQz1sdWFkLERDPWx1Y2VudCxEQz1jb20/
Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdD9iYXNlP29iamVjdENsYXNzPWNSTERpc3RyaWJ1dGlv
blBvaW50hitodHRwOi8vd3d3LmFsY2F0ZWwtbHVjZW50LmNvbS9QS0kvc3ViQ0EuY3JshjhodHRw
Oi8vc2VydmljZXMuc3VwcG9ydC5hbGNhdGVsLWx1Y2VudC5jb20vUEtJL3N1YkNBLmNybDCCAWAG
CCsGAQUFBwEBBIIBUjCCAU4wgcwGCCsGAQUFBzAChoG/bGRhcDovLy9DTj1BbGNhdGVsJTIwTHVj
ZW50JTIwSW50ZXJuYWwlMjBTdWIlMjBDQSxDTj1BSUEsQ049UHVibGljJTIwS2V5JTIwU2Vydmlj
ZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixEQz1sdWFkLERDPWx1Y2VudCxEQz1jb20/
Y0FDZXJ0aWZpY2F0ZT9iYXNlP29iamVjdENsYXNzPWNlcnRpZmljYXRpb25BdXRob3JpdHkwNwYI
KwYBBQUHMAKGK2h0dHA6Ly93d3cuYWxjYXRlbC1sdWNlbnQuY29tL1BLSS9zdWJDQS5jcnQwRAYI
KwYBBQUHMAKGOGh0dHA6Ly9zZXJ2aWNlcy5zdXBwb3J0LmFsY2F0ZWwtbHVjZW50LmNvbS9QS0kv
c3ViQ0EuY3J0MBMGA1UdJQQMMAoGCCsGAQUFBwMEMBsGCSsGAQQBgjcVCgQOMAwwCgYIKwYBBQUH
AwQwKQYDVR0RBCIwIIEeYmlsbC5taWVsa2VAYWxjYXRlbC1sdWNlbnQuY29tMA0GCSqGSIb3DQEB
BQUAA4IBAQAZRA+LIZRrEeIu8rlW3yprtze3O5EjtjyNS37sq2o0DatvvucKfFJoes1tLUmgeqKz
eObrOx2ZMpqjhvdzKPw0BmG+vIS2oVU/gSu+Kp9IvlYa/LBJgGqL6uwucG7NKb/KoYwY9XBQerPh
9NcfbsBcFoZlcV9e9J4NIXok2HOwyr+p8hKhK5SpeIoHf3Si8qSuyJuk4FtrjmTlUkgHmoFmj6U9
gKJR6WKpcBZhmOE8eQ9OZAaD1AycT7zdCAsxcBykgM58d59OeZajj1m7ZHTtOppCRMYl1A1lNxOo
w4IuokZ4L85KKzL6WqnuGflYCcNtO9it9JGZharIN+HarP3JMIIG2jCCBcKgAwIBAgIKGdxk1QAA
AAA9bzANBgkqhkiG9w0BAQUFADCBhTETMBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT8ixk
ARkWBmx1Y2VudDEUMBIGCgmSJomT8ixkARkWBG5hMDIxFzAVBgNVBAoTDkFsY2F0ZWwgTHVjZW50
MScwJQYDVQQDEx5BbGNhdGVsIEx1Y2VudCBJbnRlcm5hbCBTdWIgQ0EwHhcNMTAwNTMwMDIwNTUx
WhcNMTIwNTI5MDIwNTUxWjBAMQ8wDQYDVQQDEwZtaWVsa2UxLTArBgkqhkiG9w0BCQEWHmJpbGwu
bWllbGtlQGFsY2F0ZWwtbHVjZW50LmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAqpHW
Jco1co4MTnJ1WFCsJGeMVemFG7SQrcH0LARvpO/o9diiV3/Qvt08MYIv71lXTVBr/Kn8J9Rxq+Ew
eEGygQmO8v+kN3SIUOnWInanbEZkYFdf9jWNEArSvFZiazgrp9vgE3bKK3Id7kUFXXdWj2hK1xjQ
5BidCf9IpfyzKsECAwEAAaOCBBIwggQOMAsGA1UdDwQEAwIFIDBEBgkqhkiG9w0BCQ8ENzA1MA4G
CCqGSIb3DQMCAgIAgDAOBggqhkiG9w0DBAICAIAwBwYFKw4DAgcwCgYIKoZIhvcNAwcwHQYDVR0O
BBYEFFFsCLe38LJX1iIg54BxslUYaXvYMD4GCSsGAQQBgjcVBwQxMC8GJysGAQQBgjcVCIW9xVmD
47E5h6WBKoa/w0KFlJgZgQuCupMPhOrffgIBZAIBDTAfBgNVHSMEGDAWgBTZ7Gu9llgi99imd83+
TYHvupe9EjCCAVwGA1UdHwSCAVMwggFPMIIBS6CCAUegggFDhoHZbGRhcDovLy9DTj1BbGNhdGVs
JTIwTHVjZW50JTIwSW50ZXJuYWwlMjBTdWIlMjBDQSxDTj11c25hdnNwa2kwM3AsQ049Q0RQLENO
PVB1YmxpYyUyMEtleSUyMFNlcnZpY2VzLENOPVNlcnZpY2VzLENOPUNvbmZpZ3VyYXRpb24sREM9
bHVhZCxEQz1sdWNlbnQsREM9Y29tP2NlcnRpZmljYXRlUmV2b2NhdGlvbkxpc3Q/YmFzZT9vYmpl
Y3RDbGFzcz1jUkxEaXN0cmlidXRpb25Qb2ludIYraHR0cDovL3d3dy5hbGNhdGVsLWx1Y2VudC5j
b20vUEtJL3N1YkNBLmNybIY4aHR0cDovL3NlcnZpY2VzLnN1cHBvcnQuYWxjYXRlbC1sdWNlbnQu
Y29tL1BLSS9zdWJDQS5jcmwwggFgBggrBgEFBQcBAQSCAVIwggFOMIHMBggrBgEFBQcwAoaBv2xk
YXA6Ly8vQ049QWxjYXRlbCUyMEx1Y2VudCUyMEludGVybmFsJTIwU3ViJTIwQ0EsQ049QUlBLENO
PVB1YmxpYyUyMEtleSUyMFNlcnZpY2VzLENOPVNlcnZpY2VzLENOPUNvbmZpZ3VyYXRpb24sREM9
bHVhZCxEQz1sdWNlbnQsREM9Y29tP2NBQ2VydGlmaWNhdGU/YmFzZT9vYmplY3RDbGFzcz1jZXJ0
aWZpY2F0aW9uQXV0aG9yaXR5MDcGCCsGAQUFBzAChitodHRwOi8vd3d3LmFsY2F0ZWwtbHVjZW50
LmNvbS9QS0kvc3ViQ0EuY3J0MEQGCCsGAQUFBzAChjhodHRwOi8vc2VydmljZXMuc3VwcG9ydC5h
bGNhdGVsLWx1Y2VudC5jb20vUEtJL3N1YkNBLmNydDAfBgNVHSUEGDAWBggrBgEFBQcDBAYKKwYB
BAGCNwoDBDApBgkrBgEEAYI3FQoEHDAaMAoGCCsGAQUFBwMEMAwGCisGAQQBgjcKAwQwKQYDVR0R
BCIwIIEeYmlsbC5taWVsa2VAYWxjYXRlbC1sdWNlbnQuY29tMA0GCSqGSIb3DQEBBQUAA4IBAQCR
rwYqycRkzGvAxMozWQCh7wJ0axCuF5vqoBkjnhKz4gFtn89WViNTxeLdq+DhfAp3nnzqkE8ggrFn
X5b/DJZgUAGoLlvZ3IL1L0i2Ne3dK5QGq58VFK7KYrluedog6FXZ93jfXtZFq9Z4acpaR0H6DXvg
DAsdbnaLYkWI0+X/enGC7dzkJNQ8D5YUHxAA5qSGATRm6x71kb0R/ShzzFJvpxidYi2bht/mPOIa
ASZD7CSskrRKeaWEke7dKPaUpEPOFVG/do6yuG8iH1PEZ7IYy97x4SuemQmFEMwnjLz1ubf2wzhv
8Hw5Ku2kW2Vw+wI6O+IkjYAir40DgHHLNh4WMYIDVzCCA1MCAQEwgZQwgYUxEzARBgoJkiaJk/Is
ZAEZFgNjb20xFjAUBgoJkiaJk/IsZAEZFgZsdWNlbnQxFDASBgoJkiaJk/IsZAEZFgRuYTAyMRcw
FQYDVQQKEw5BbGNhdGVsIEx1Y2VudDEnMCUGA1UEAxMeQWxjYXRlbCBMdWNlbnQgSW50ZXJuYWwg
U3ViIENBAgoZ21oMAAAAAD1uMAkGBSsOAwIaBQCgggIYMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0B
BwEwHAYJKoZIhvcNAQkFMQ8XDTEwMTExMDAzMDkxOVowIwYJKoZIhvcNAQkEMRYEFLQ8t30aEt8p
GOOh2c0XOsVO/6W0MGcGCSqGSIb3DQEJDzFaMFgwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCA
MA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMAcGBSsOAwIaMAoGCCqGSIb3
DQIFMIGlBgkrBgEEAYI3EAQxgZcwgZQwgYUxEzARBgoJkiaJk/IsZAEZFgNjb20xFjAUBgoJkiaJ
k/IsZAEZFgZsdWNlbnQxFDASBgoJkiaJk/IsZAEZFgRuYTAyMRcwFQYDVQQKEw5BbGNhdGVsIEx1
Y2VudDEnMCUGA1UEAxMeQWxjYXRlbCBMdWNlbnQgSW50ZXJuYWwgU3ViIENBAgoZ3GTVAAAAAD1v
MIGnBgsqhkiG9w0BCRACCzGBl6CBlDCBhTETMBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT
8ixkARkWBmx1Y2VudDEUMBIGCgmSJomT8ixkARkWBG5hMDIxFzAVBgNVBAoTDkFsY2F0ZWwgTHVj
ZW50MScwJQYDVQQDEx5BbGNhdGVsIEx1Y2VudCBJbnRlcm5hbCBTdWIgQ0ECChncZNUAAAAAPW8w
DQYJKoZIhvcNAQEBBQAEgYCbmEKm+Vlgw9RymU8A/GPkq7m1dMtF5J/RgRv4bR9wPiQSaeCVWUqP
A8bpuPvvqzLPF8xtZL4aIt6k0Pb1DO9oEMQJyaI8/6H5436KRQhRdjvgIif1owKkt/XZ5hbjmTR1
bDogHr2JfjtiCSJjsyapIIR2kIrsl/+EI7hXTdp1hgAAAAAAAA==

------=_NextPart_000_004D_01CB805A.C1D5FE30--

From chrisv@cyberswitching.com  Tue Nov  9 20:05:23 2010
Return-Path: <chrisv@cyberswitching.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1C54928C0E7 for <eman@core3.amsl.com>; Tue,  9 Nov 2010 20:05:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IbA51EuJUlaS for <eman@core3.amsl.com>; Tue,  9 Nov 2010 20:05:14 -0800 (PST)
Received: from p01c12o144.mxlogic.net (p01c12o144.mxlogic.net [208.65.145.67]) by core3.amsl.com (Postfix) with ESMTP id 510F73A682B for <eman@ietf.org>; Tue,  9 Nov 2010 20:05:13 -0800 (PST)
Received: from unknown [64.81.28.110] (EHLO mail03.cyberswitching.local) by p01c12o144.mxlogic.net(mxl_mta-6.7.0-2) with ESMTP id 21a1adc4.0.42926.00-360.74424.p01c12o144.mxlogic.net (envelope-from <chrisv@cyberswitching.com>);  Tue, 09 Nov 2010 21:05:39 -0700 (MST)
X-MXL-Hash: 4cda1a131af15bd0-3bcc11917ab58ecfe0131123bd7415f379d56a25
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CB808C.695EA2DB"
Date: Tue, 9 Nov 2010 20:04:47 -0800
Message-ID: <68FBE0F3CE97264395875AC1C468F22C514BB6@mail03.cyberswitching.local>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [eman] New draft draft-quittek-eman-reference-model-00
Thread-Index: AcuAhIt9AMe9nMWURY60o0WKGhwrTAABflgw
References: <20101108224927.6B96728C0DB@core3.amsl.com><C8FEA7BA.16D4A%quittek@neclab.eu><AANLkTik-fGiNo+qTnj0LMMvygp_rSZkKgEvgSukaTn0X@mail.gmail.com><68FBE0F3CE97264395875AC1C468F22C514B72@mail03.cyberswitching.local> <AANLkTinJDPX5Z2Agp015vLrDfcyfvsLW1+ux8uUy6g+8@mail.gmail.com>
From: "Chris Verges" <chrisv@cyberswitching.com>
To: "Bruce Nordman" <bnordman@lbl.gov>
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2010110201)]
X-MAIL-FROM: <chrisv@cyberswitching.com>
X-SOURCE-IP: [64.81.28.110]
X-AnalysisOut: [v=1.0 c=1 a=NhDX0KWKZ8AA:10 a=BLceEmwcHowA:10 a=4zsJQXJisS]
X-AnalysisOut: [Y22NXBO5KRuA==:17 a=wzgqfsuUAAAA:8 a=WKEUUsg48xWSzkFSbFcA:]
X-AnalysisOut: [9 a=jWvmSBR646wRU7bAhKwA:7 a=YerAPx2OnRhmR0_4ZEx55k-rpbkA:]
X-AnalysisOut: [4 a=wPNLvfGTeEIA:10 a=FnBvD0j_UmcA:10 a=lr71C7C2fScA:10 a=]
X-AnalysisOut: [yvfu_RGVus0A:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=J35dNK]
X-AnalysisOut: [fbAAAA:8 a=XOkKfy4zLWPwNH9QzUMA:9 a=TmpGzs_94EIzQXhK9SAA:7]
X-AnalysisOut: [ a=VwBSAPJ3T7oCYNumSCHHiAVpvy0A:4]
Cc: eman mailing list <eman@ietf.org>
Subject: Re: [eman] New draft draft-quittek-eman-reference-model-00
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Nov 2010 04:05:23 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CB808C.695EA2DB
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Bruce,

=20

Given that my head is still spinning to understand all of the nuances in =
the different terms/definitions in the new reference-model-00 draft, I'm =
not sure.  :-)

=20

Here's the traditional breakdown of a Smart PDU with 2 input cords, 6 =
banks, and 24 outlets:

=20

=B7         PDU

o    Internal overhead to manage PDU

o    Input Cord #1

=A7  Bank #1

=B7         Outlet #1

=B7         ...

=A7  Bank #2

=B7         Outlet #5

=B7         ...

=A7  Bank #3

=B7         Outlet #9

=B7         ...

o    Input Cord #2

=A7  Bank #4

=B7         Outlet #13

=B7         ...

=A7  Bank #5

=B7         Outlet #17

=B7         ...

=A7  Bank #6

=B7         Outlet #21

=B7         ...

=20

Each Outlet has an electrical meter.  These values are then aggregated =
to form the data for the Bank to which the Outlets are connected.  These =
Bank values are then aggregated for their parent Input Cord.  Finally, =
the total is aggregated for the PDU as a whole entity.

=20

This is the fundamental architecture of Cyber Switching's ePower series, =
but could very well apply to any of the other PDU vendors: APC, Server =
Technology, Raritan, Geist, Eaton/HP, etc.

=20

Customers have explicitly stated to us that even though each Input Cord =
may be part of a separate physical infrastructure path to two different =
power transformers, they don't care and want the power aggregated =
together at the PDU level.  Also, customers have stated that they want =
all of this data made available to them.  It may be redundant, it may be =
overlapping, but they don't really care because they find ways to use it =
for their particular business needs.

=20

What you're calling "electricity domains" is, I believe, synonymous with =
"power grid being supplied by a single transformer segment", correct?  =
What I'm trying to get across is that such a breakdown is merely one of =
a thousand ways that our customers use our products in daily use.  I =
agree that it's a good use case to model, but it is not the only use =
case that needs to be modeled.  We need to provide a model that can =
scale upwards with these sorts of complex business needs that are as of =
yet unseen and undefined, and I am questioning whether the existing two =
drafts handle this sufficiently in their current forms.

=20

If it helps the discussion, I can certainly put together a proposed MIB =
architecture to try and solidify what I'm meaning.  I see the Smart PDU =
/ Submeter style of product as being sufficiently more complex than a =
standard computer / server from a model standpoint.  Or to put it =
another way, the needs related to a server is a subset of the needs =
related to the Smart PDU and PoE networking gear; if we solve those, the =
server will naturally be handled.

=20

Thanks,

Chris

=20

From: Bruce Nordman [mailto:bnordman@lbl.gov]=20
Sent: Tuesday, November 09, 2010 7:09 PM
To: Chris Verges
Cc: eman mailing list
Subject: Re: [eman] New draft draft-quittek-eman-reference-model-00

=20

Chris--
  In your diagram, does the Reporter communicate only the total power
consumed from each supply, or is the supply part broken out by consumer?
Certainly the former is simpler, but your diagram seems to indicate
the latter.
  In your diagram, the power seems not to be pooled, but rather the
two electricity domains don't interact.  How about logically dividing
the PDU into two units, each with only one power supply.  Would that
meet your needs?
--Bruce

On Wed, Nov 10, 2010 at 6:03 AM, Chris Verges =
<chrisv@cyberswitching.com> wrote:

Hi Juergen,

In addition to JinHyeock's comments below, I notice that none of the use =
cases described in section 5 describe a case whereby a single device =
contains multiple energy meters with multiple energy consumers.  =
Building off the simpler subset shown in Section 5.3, I created a more =
complex model that is required for our product set:

http://demo.cyberswitching.com/chrisv/20101109-01_Intelligent_PDU_Use_Cas=
e.pdf

(Admittedly, I'm not as skilled in the ancient art of ASCII [art] as =
you, so took refudge to Visio for time considerations.)

If I misused any of the terms, I apologize.  The draft was definitely =
full of definitions, and I'm working to come up to speed on your usage =
of them.

In this scenario, I need to report the data for EACH Energy Consumption =
Meter listed __AND__ multiple aggregations of that meter data, based on =
business case needs.  (That is, "domains" can be defined in several =
different ways, simultaneously.)

Please comment on how such a use case might be modeled to ensure =
flexibility and future feature expansion by both the IETF and enterprise =
vendors.

Chris

=20

--=20
Bruce Nordman
Lawrence Berkeley National Laboratory
eetd.lbl.gov/ea/nordman
BNordman@LBL.gov
510-486-7089
m: 510-501-7943


------_=_NextPart_001_01CB808C.695EA2DB
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DGenerator =
content=3D"Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:619721134;
	mso-list-type:hybrid;
	mso-list-template-ids:1532247502 67698689 67698691 67698693 67698689 =
67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Hi Bruce,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Given that my head is still spinning to understand all of the nuances =
in the different terms/definitions in the new reference-model-00 draft, =
I&#8217;m not sure.=A0 :-)<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Here&#8217;s the traditional breakdown of a Smart PDU with 2 input =
cords, 6 banks, and 24 outlets:<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoListParagraph =
style=3D'text-indent:-.25in;mso-list:l0 level1 lfo1'><![if =
!supportLists]><span =
style=3D'font-size:10.0pt;font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>PDU<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;font-family:"Courier New";color:#1F497D'><span =
style=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Internal overhead to manage PDU<o:p></o:p></span></p><p =
class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;font-family:"Courier New";color:#1F497D'><span =
style=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Input Cord #1<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l0 level3 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;font-family:Wingdings;color:#1F497D'><span =
style=3D'mso-list:Ignore'>=A7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Bank #1<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:2.0in;text-indent:-.25in;mso-list:l0 level4 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Outlet #1<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:2.0in;text-indent:-.25in;mso-list:l0 level4 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&#8230;<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l0 level3 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;font-family:Wingdings;color:#1F497D'><span =
style=3D'mso-list:Ignore'>=A7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Bank #2<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:2.0in;text-indent:-.25in;mso-list:l0 level4 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Outlet #5<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:2.0in;text-indent:-.25in;mso-list:l0 level4 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&#8230;<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l0 level3 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;font-family:Wingdings;color:#1F497D'><span =
style=3D'mso-list:Ignore'>=A7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Bank #3<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:2.0in;text-indent:-.25in;mso-list:l0 level4 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Outlet #9<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:2.0in;text-indent:-.25in;mso-list:l0 level4 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&#8230;<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.0in;text-indent:-.25in;mso-list:l0 level2 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;font-family:"Courier New";color:#1F497D'><span =
style=3D'mso-list:Ignore'>o<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp; </span></span></span><![endif]><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Input Cord #2<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l0 level3 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;font-family:Wingdings;color:#1F497D'><span =
style=3D'mso-list:Ignore'>=A7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Bank #4<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:2.0in;text-indent:-.25in;mso-list:l0 level4 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Outlet #13<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:2.0in;text-indent:-.25in;mso-list:l0 level4 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&#8230;<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l0 level3 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;font-family:Wingdings;color:#1F497D'><span =
style=3D'mso-list:Ignore'>=A7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Bank #5<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:2.0in;text-indent:-.25in;mso-list:l0 level4 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Outlet #17<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:2.0in;text-indent:-.25in;mso-list:l0 level4 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&#8230;<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:1.5in;text-indent:-.25in;mso-list:l0 level3 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;font-family:Wingdings;color:#1F497D'><span =
style=3D'mso-list:Ignore'>=A7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp; </span></span></span><![endif]><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Bank #6<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:2.0in;text-indent:-.25in;mso-list:l0 level4 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Outlet #21<o:p></o:p></span></p><p class=3DMsoListParagraph =
style=3D'margin-left:2.0in;text-indent:-.25in;mso-list:l0 level4 =
lfo1'><![if !supportLists]><span =
style=3D'font-size:10.0pt;font-family:Symbol;color:#1F497D'><span =
style=3D'mso-list:Ignore'>=B7<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&#8230;<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Each Outlet has an electrical meter.=A0 These values are then =
aggregated to form the data for the Bank to which the Outlets are =
connected.=A0 These Bank values are then aggregated for their parent =
Input Cord.=A0 Finally, the total is aggregated for the PDU as a whole =
entity.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>This is the fundamental architecture of Cyber Switching&#8217;s =
ePower series, but could very well apply to any of the other PDU =
vendors: APC, Server Technology, Raritan, Geist, Eaton/HP, =
etc.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Customers have explicitly stated to us that even though each Input =
Cord may be part of a separate physical infrastructure path to two =
different power transformers, they don&#8217;t care and want the power =
aggregated together at the PDU level.=A0 Also, customers have stated =
that they want all of this data made available to them.=A0 It may be =
redundant, it may be overlapping, but they don&#8217;t really care =
because they find ways to use it for their particular business =
needs.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>What you&#8217;re calling &#8220;electricity domains&#8221; is, I =
believe, synonymous with &#8220;power grid being supplied by a single =
transformer segment&#8221;, correct?=A0 What I&#8217;m trying to get =
across is that such a breakdown is merely one of a thousand ways that =
our customers use our products in daily use.=A0 I agree that it&#8217;s =
a good use case to model, but it is not the only use case that needs to =
be modeled.=A0 We need to provide a model that can scale upwards with =
these sorts of complex business needs that are as of yet unseen and =
undefined, and I am questioning whether the existing two drafts handle =
this sufficiently in their current forms.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>If it helps the discussion, I can certainly put together a proposed =
MIB architecture to try and solidify what I&#8217;m meaning.=A0 I see =
the Smart PDU / Submeter style of product as being sufficiently more =
complex than a standard computer / server from a model standpoint.=A0 Or =
to put it another way, the needs related to a server is a subset of the =
needs related to the Smart PDU and PoE networking gear; if we solve =
those, the server will naturally be handled.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Thanks,<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Chris<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:10.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> =
Bruce Nordman [mailto:bnordman@lbl.gov] <br><b>Sent:</b> Tuesday, =
November 09, 2010 7:09 PM<br><b>To:</b> Chris Verges<br><b>Cc:</b> eman =
mailing list<br><b>Subject:</b> Re: [eman] New draft =
draft-quittek-eman-reference-model-00<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>Chris--<br>&nbsp; In your diagram, does =
the Reporter communicate only the total power<br>consumed from each =
supply, or is the supply part broken out by consumer?<br>Certainly the =
former is simpler, but your diagram seems to indicate<br>the =
latter.<br>&nbsp; In your diagram, the power seems not to be pooled, but =
rather the<br>two electricity domains don't interact.&nbsp; How about =
logically dividing<br>the PDU into two units, each with only one power =
supply.&nbsp; Would that<br>meet your =
needs?<br>--Bruce<o:p></o:p></p><div><p class=3DMsoNormal>On Wed, Nov =
10, 2010 at 6:03 AM, Chris Verges &lt;<a =
href=3D"mailto:chrisv@cyberswitching.com">chrisv@cyberswitching.com</a>&g=
t; wrote:<o:p></o:p></p><p class=3DMsoNormal>Hi Juergen,<br><br>In =
addition to JinHyeock's comments below, I notice that none of the use =
cases described in section 5 describe a case whereby a single device =
contains multiple energy meters with multiple energy consumers. =
&nbsp;Building off the simpler subset shown in Section 5.3, I created a =
more complex model that is required for our product set:<br><br><a =
href=3D"http://demo.cyberswitching.com/chrisv/20101109-01_Intelligent_PDU=
_Use_Case.pdf" =
target=3D"_blank">http://demo.cyberswitching.com/chrisv/20101109-01_Intel=
ligent_PDU_Use_Case.pdf</a><br><br>(Admittedly, I'm not as skilled in =
the ancient art of ASCII [art] as you, so took refudge to Visio for time =
considerations.)<br><br>If I misused any of the terms, I apologize. =
&nbsp;The draft was definitely full of definitions, and I'm working to =
come up to speed on your usage of them.<br><br>In this scenario, I need =
to report the data for EACH Energy Consumption Meter listed __AND__ =
multiple aggregations of that meter data, based on business case needs. =
&nbsp;(That is, &quot;domains&quot; can be defined in several different =
ways, simultaneously.)<br><br>Please comment on how such a use case =
might be modeled to ensure flexibility and future feature expansion by =
both the IETF and enterprise vendors.<br><span =
style=3D'color:#888888'><br>Chris</span><o:p></o:p></p><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>-- <br><b><span =
style=3D'font-size:13.5pt'>Bruce Nordman</span></b><br><span =
style=3D'color:#000099'>Lawrence Berkeley National =
Laboratory</span><br><a href=3D"http://eetd.lbl.gov/ea/nordman" =
target=3D"_blank">eetd.lbl.gov/ea/nordman</a><br><a =
href=3D"mailto:BNordman@LBL.gov">BNordman@LBL.gov</a><br>510-486-7089<br>=
m: 510-501-7943<o:p></o:p></p></div></body></html>
------_=_NextPart_001_01CB808C.695EA2DB--

From bnordman@lbl.gov  Thu Nov 11 14:00:04 2010
Return-Path: <bnordman@lbl.gov>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B83B33A6936 for <eman@core3.amsl.com>; Thu, 11 Nov 2010 14:00:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.602
X-Spam-Level: 
X-Spam-Status: No, score=-5.602 tagged_above=-999 required=5 tests=[AWL=0.374,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aP5ljz1suCSe for <eman@core3.amsl.com>; Thu, 11 Nov 2010 14:00:03 -0800 (PST)
Received: from ironport1.lbl.gov (ironport1.lbl.gov [128.3.41.47]) by core3.amsl.com (Postfix) with ESMTP id A10E13A6907 for <eman@ietf.org>; Thu, 11 Nov 2010 14:00:00 -0800 (PST)
X-Ironport-SBRS: 4.4
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqQBAGv220zRVdg0kGdsb2JhbACBcZJcAYV0AYgACBUBAQEBCQkMBxEDH6gKmh2DC4I/BIRYhgA
X-IronPort-AV: E=Sophos;i="4.59,185,1288594800"; d="scan'208";a="136525766"
Received: from mail-qw0-f52.google.com ([209.85.216.52]) by ironport1.lbl.gov with ESMTP; 11 Nov 2010 14:00:30 -0800
Received: by qwa26 with SMTP id 26so2374447qwa.39 for <eman@ietf.org>; Thu, 11 Nov 2010 14:00:30 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.246.129 with SMTP id ly1mr1197061qcb.126.1289512828410; Thu, 11 Nov 2010 14:00:28 -0800 (PST)
Received: by 10.229.105.8 with HTTP; Thu, 11 Nov 2010 14:00:28 -0800 (PST)
Date: Fri, 12 Nov 2010 06:00:28 +0800
Message-ID: <AANLkTin0xnM6VrCiQgOKUMoJ8DweOMQLhyt+c896n02N@mail.gmail.com>
From: Bruce Nordman <bnordman@lbl.gov>
To: eman mailing list <eman@ietf.org>
Content-Type: multipart/alternative; boundary=0016e64711a2124d0d0494ce1af1
Subject: [eman] Draft minutes uploaded
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Nov 2010 22:00:04 -0000

--0016e64711a2124d0d0494ce1af1
Content-Type: text/plain; charset=ISO-8859-1

Please review for errors or omissions.
Thank you,
--Bruce

-- 
*Bruce Nordman*
Lawrence Berkeley National Laboratory
eetd.lbl.gov/ea/nordman
BNordman@LBL.gov
510-486-7089
m: 510-501-7943

--0016e64711a2124d0d0494ce1af1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Please review for errors or omissions.<br>Thank you,<br>--Bruce<br clear=3D=
"all"><br>-- <br><font size=3D"4"><b>Bruce Nordman</b></font><br><span styl=
e=3D"color: rgb(0, 0, 153);">Lawrence Berkeley National Laboratory</span><b=
r><a href=3D"http://eetd.lbl.gov/ea/nordman" target=3D"_blank">eetd.lbl.gov=
/ea/nordman</a><br>
BNordman@LBL.gov<br>510-486-7089<br>m: 510-501-7943<br><br>

--0016e64711a2124d0d0494ce1af1--

From bnordman@lbl.gov  Thu Nov 11 16:37:23 2010
Return-Path: <bnordman@lbl.gov>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B792228C0EF for <eman@core3.amsl.com>; Thu, 11 Nov 2010 16:37:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.136
X-Spam-Level: 
X-Spam-Status: No, score=-4.136 tagged_above=-999 required=5 tests=[AWL=-1.160, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1b1V7676P5Gs for <eman@core3.amsl.com>; Thu, 11 Nov 2010 16:37:22 -0800 (PST)
Received: from ironport4.lbl.gov (ironport4.lbl.gov [128.3.41.45]) by core3.amsl.com (Postfix) with ESMTP id 6E7353A692D for <eman@ietf.org>; Thu, 11 Nov 2010 16:37:06 -0800 (PST)
X-Ironport-SBRS: 4.4
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuABAAQb3EzRVditkGdsb2JhbACBcZhSAYd/CBUBAQEBCQkMBxEDH6ZOmhGDC4I/BIRYhgA
X-IronPort-AV: E=Sophos;i="4.59,185,1288594800"; d="scan'208";a="28532616"
Received: from mail-qy0-f173.google.com ([209.85.216.173]) by ironport4.lbl.gov with ESMTP; 11 Nov 2010 16:37:31 -0800
Received: by mail-qy0-f173.google.com with SMTP id 33so469199qyl.18 for <eman@ietf.org>; Thu, 11 Nov 2010 16:37:30 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.81.12 with SMTP id v12mr1375356qck.12.1289522228594; Thu, 11 Nov 2010 16:37:08 -0800 (PST)
Received: by 10.229.105.8 with HTTP; Thu, 11 Nov 2010 16:37:08 -0800 (PST)
In-Reply-To: <AANLkTin0xnM6VrCiQgOKUMoJ8DweOMQLhyt+c896n02N@mail.gmail.com>
References: <AANLkTin0xnM6VrCiQgOKUMoJ8DweOMQLhyt+c896n02N@mail.gmail.com>
Date: Fri, 12 Nov 2010 08:37:08 +0800
Message-ID: <AANLkTimQZtkQvPmWR7-s1PWUwrfe7=zsrUyE5h4wa8c3@mail.gmail.com>
From: Bruce Nordman <bnordman@lbl.gov>
To: eman mailing list <eman@ietf.org>
Content-Type: multipart/alternative; boundary=00163646bf505d87550494d04a4d
Subject: Re: [eman] Draft minutes uploaded
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Nov 2010 00:37:23 -0000

--00163646bf505d87550494d04a4d
Content-Type: text/plain; charset=ISO-8859-1

Minutes at:
    http://www.ietf.org/proceedings/79/minutes/eman.txt

On Fri, Nov 12, 2010 at 6:00 AM, Bruce Nordman <bnordman@lbl.gov> wrote:

> Please review for errors or omissions.
> Thank you,
> --Bruce
>
> --
> *Bruce Nordman*
> Lawrence Berkeley National Laboratory
> eetd.lbl.gov/ea/nordman
> BNordman@LBL.gov
> 510-486-7089
> m: 510-501-7943
>
>


-- 
*Bruce Nordman*
Lawrence Berkeley National Laboratory
eetd.lbl.gov/ea/nordman
BNordman@LBL.gov
510-486-7089
m: 510-501-7943

--00163646bf505d87550494d04a4d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Minutes at:<br>=A0=A0=A0 <a href=3D"http://www.ietf.org/proceedings/79/minu=
tes/eman.txt">http://www.ietf.org/proceedings/79/minutes/eman.txt</a><br><b=
r><div class=3D"gmail_quote">On Fri, Nov 12, 2010 at 6:00 AM, Bruce Nordman=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:bnordman@lbl.gov">bnordman@lbl.gov=
</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0.8ex; borde=
r-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Please review for=
 errors or omissions.<br>Thank you,<br>--Bruce<br clear=3D"all"><font color=
=3D"#888888"><br>
-- <br><font size=3D"4"><b>Bruce Nordman</b></font><br><span style=3D"color=
: rgb(0, 0, 153);">Lawrence Berkeley National Laboratory</span><br><a href=
=3D"http://eetd.lbl.gov/ea/nordman" target=3D"_blank">eetd.lbl.gov/ea/nordm=
an</a><br>

BNordman@LBL.gov<br>510-486-7089<br>m: 510-501-7943<br><br>
</font></blockquote></div><br><br clear=3D"all"><br>-- <br><font size=3D"4"=
><b>Bruce Nordman</b></font><br><span style=3D"color: rgb(0, 0, 153);">Lawr=
ence Berkeley National Laboratory</span><br><a href=3D"http://eetd.lbl.gov/=
ea/nordman" target=3D"_blank">eetd.lbl.gov/ea/nordman</a><br>
BNordman@LBL.gov<br>510-486-7089<br>m: 510-501-7943<br><br>

--00163646bf505d87550494d04a4d--

From bclaise@cisco.com  Fri Nov 12 07:41:55 2010
Return-Path: <bclaise@cisco.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E136A3A697C for <eman@core3.amsl.com>; Fri, 12 Nov 2010 07:41:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level: 
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.036,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e8G5N1d5X259 for <eman@core3.amsl.com>; Fri, 12 Nov 2010 07:41:52 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id B0BF03A6953 for <eman@ietf.org>; Fri, 12 Nov 2010 07:41:51 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oACFgOJj009509 for <eman@ietf.org>; Fri, 12 Nov 2010 16:42:24 +0100 (CET)
Received: from [10.68.21.59] (sin-vpn-client-21-59.cisco.com [10.68.21.59]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oACFgLkS003236 for <eman@ietf.org>; Fri, 12 Nov 2010 16:42:22 +0100 (CET)
Message-ID: <4CDD605C.4020809@cisco.com>
Date: Fri, 12 Nov 2010 23:42:20 +0800
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: eman mailing list <eman@ietf.org>
Content-Type: multipart/alternative; boundary="------------070509010304070201010205"
Subject: [eman] WG documents adoption
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Nov 2010 15:41:56 -0000

This is a multi-part message in MIME format.
--------------070509010304070201010205
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dear all,

 From the meeting minutes at: 
http://www.ietf.org/proceedings/79/minutes/eman.txt, we would like to 
stress the following

draft-quittek-power-monitoring-requirements-02

    Chair asked if the sense of the room was that this should be made a
    working group draft. No objections. Take to the list.


draft-claise-power-management-arch-02

    Chair asked if the sense of the room was that this should be made a
    working group draft. No objections. Take to the list.


draft-parello-eman-energy-aware-mib-00

    Chair asked if the sense of the room was that this should be made a
    working group draft. No objections. Take to the list.

If you object any of the documents becoming a WG item, let us know.
Note that, if a document becomes a WG item, the open issues discussed 
will have to be solved based on the group consensus.

Regards, Bruce and Benoit


--------------070509010304070201010205
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body text="#000000" bgcolor="#ffffff">
    Dear all,<br>
    <br>
    From the meeting minutes at: <a
      href="http://www.ietf.org/proceedings/79/minutes/eman.txt">http://www.ietf.org/proceedings/79/minutes/eman.txt</a>,
    we would like to stress the following<br>
    <br>
    draft-quittek-power-monitoring-requirements-02<br>
    <blockquote>Chair asked if the sense of the room was that this
      should be made a <br>
      working group draft. No objections. Take to the list.<br>
    </blockquote>
    <br>
    draft-claise-power-management-arch-02<br>
    <blockquote>Chair asked if the sense of the room was that this
      should be made a <br>
      working group draft. No objections. Take to the list.<br>
    </blockquote>
    <br>
    draft-parello-eman-energy-aware-mib-00 <br>
    <blockquote>Chair asked if the sense of the room was that this
      should be made a <br>
      working group draft. No objections. Take to the list.<br>
    </blockquote>
    If you object any of the documents becoming a WG item, let us know.<br>
    Note that, if a document becomes a WG item, the open issues
    discussed will have to be solved based on the group consensus.<br>
    <br>
    Regards, Bruce and Benoit<br>
    <br>
  </body>
</html>

--------------070509010304070201010205--

From bclaise@cisco.com  Mon Nov 22 03:19:18 2010
Return-Path: <bclaise@cisco.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AC8BF3A68EE for <eman@core3.amsl.com>; Mon, 22 Nov 2010 03:19:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.593
X-Spam-Level: 
X-Spam-Status: No, score=-2.593 tagged_above=-999 required=5 tests=[AWL=0.005,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NS5C9edwVlMS for <eman@core3.amsl.com>; Mon, 22 Nov 2010 03:19:18 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id A2AA43A6ACC for <eman@ietf.org>; Mon, 22 Nov 2010 03:19:17 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oAMBKCZl000728 for <eman@ietf.org>; Mon, 22 Nov 2010 12:20:12 +0100 (CET)
Received: from [10.55.43.54] (ams-bclaise-8715.cisco.com [10.55.43.54]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oAMBKCST004491 for <eman@ietf.org>; Mon, 22 Nov 2010 12:20:12 +0100 (CET)
Message-ID: <4CEA51EB.8000206@cisco.com>
Date: Mon, 22 Nov 2010 12:20:11 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: eman mailing list <eman@ietf.org>
References: <4CDD605C.4020809@cisco.com>
In-Reply-To: <4CDD605C.4020809@cisco.com>
Content-Type: multipart/alternative; boundary="------------000502040008080401020607"
Subject: Re: [eman] WG documents adoption
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Nov 2010 11:19:18 -0000

This is a multi-part message in MIME format.
--------------000502040008080401020607
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Dear all,

Since they were no objections, we asked the authors to publish the 3 
drafts below as EMAN WG documents.

Regards, Bruce and Benoit.
> Dear all,
>
> From the meeting minutes at: 
> http://www.ietf.org/proceedings/79/minutes/eman.txt, we would like to 
> stress the following
>
> draft-quittek-power-monitoring-requirements-02
>
>     Chair asked if the sense of the room was that this should be made a
>     working group draft. No objections. Take to the list.
>
>
> draft-claise-power-management-arch-02
>
>     Chair asked if the sense of the room was that this should be made a
>     working group draft. No objections. Take to the list.
>
>
> draft-parello-eman-energy-aware-mib-00
>
>     Chair asked if the sense of the room was that this should be made a
>     working group draft. No objections. Take to the list.
>
> If you object any of the documents becoming a WG item, let us know.
> Note that, if a document becomes a WG item, the open issues discussed 
> will have to be solved based on the group consensus.
>
> Regards, Bruce and Benoit
>
>
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman


--------------000502040008080401020607
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#ffffff">
    Dear all,<br>
    <br>
    Since they were no objections, we asked the authors to publish the 3
    drafts below as EMAN WG documents.<br>
    <br>
    Regards, Bruce and Benoit.<br>
    <blockquote cite="mid:4CDD605C.4020809@cisco.com" type="cite">
      <meta http-equiv="content-type" content="text/html;
        charset=ISO-8859-1">
      Dear all,<br>
      <br>
      From the meeting minutes at: <a moz-do-not-send="true"
        href="http://www.ietf.org/proceedings/79/minutes/eman.txt">http://www.ietf.org/proceedings/79/minutes/eman.txt</a>,
      we would like to stress the following<br>
      <br>
      draft-quittek-power-monitoring-requirements-02<br>
      <blockquote>Chair asked if the sense of the room was that this
        should be made a <br>
        working group draft. No objections. Take to the list.<br>
      </blockquote>
      <br>
      draft-claise-power-management-arch-02<br>
      <blockquote>Chair asked if the sense of the room was that this
        should be made a <br>
        working group draft. No objections. Take to the list.<br>
      </blockquote>
      <br>
      draft-parello-eman-energy-aware-mib-00 <br>
      <blockquote>Chair asked if the sense of the room was that this
        should be made a <br>
        working group draft. No objections. Take to the list.<br>
      </blockquote>
      If you object any of the documents becoming a WG item, let us
      know.<br>
      Note that, if a document becomes a WG item, the open issues
      discussed will have to be solved based on the group consensus.<br>
      <br>
      Regards, Bruce and Benoit<br>
      <br>
      <pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
eman mailing list
<a class="moz-txt-link-abbreviated" href="mailto:eman@ietf.org">eman@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/eman">https://www.ietf.org/mailman/listinfo/eman</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------000502040008080401020607--

From bill.mielke@alcatel-lucent.com  Mon Nov 22 05:58:16 2010
Return-Path: <bill.mielke@alcatel-lucent.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D24513A68D4 for <eman@core3.amsl.com>; Mon, 22 Nov 2010 05:58:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[AWL=2.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VoLANBOtspRi for <eman@core3.amsl.com>; Mon, 22 Nov 2010 05:58:15 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by core3.amsl.com (Postfix) with ESMTP id 5CE683A69B3 for <eman@ietf.org>; Mon, 22 Nov 2010 05:58:14 -0800 (PST)
Received: from usnavsmail1.ndc.alcatel-lucent.com (usnavsmail1.ndc.alcatel-lucent.com [135.3.39.9]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id oAMDx9Yt002093 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 22 Nov 2010 07:59:09 -0600 (CST)
Received: from USNAVSXCHHUB01.ndc.alcatel-lucent.com (usnavsxchhub01.ndc.alcatel-lucent.com [135.3.39.110]) by usnavsmail1.ndc.alcatel-lucent.com (8.14.3/8.14.3/GMO) with ESMTP id oAMDx8Dh009860 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 22 Nov 2010 07:59:08 -0600
Received: from USNAVSXCHMBSA3.ndc.alcatel-lucent.com ([135.3.39.119]) by USNAVSXCHHUB01.ndc.alcatel-lucent.com ([135.3.39.110]) with mapi; Mon, 22 Nov 2010 07:59:08 -0600
From: "Mielke, William F (Bill)" <bill.mielke@alcatel-lucent.com>
To: Benoit Claise <bclaise@cisco.com>, eman mailing list <eman@ietf.org>
Date: Mon, 22 Nov 2010 07:59:05 -0600
Thread-Topic: [eman] WG documents adoption
Thread-Index: AcuKNz3DKCw+CIHcRVOi66J6yaEG9gAD1BzQ
Message-ID: <0DEE3BCEE44BFD4EBC3B7DC009C8E79225067FC590@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
References: <4CDD605C.4020809@cisco.com> <4CEA51EB.8000206@cisco.com>
In-Reply-To: <4CEA51EB.8000206@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0000_01CB8A23.842EA910"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Scanned-By: MIMEDefang 2.64 on 135.3.39.9
Subject: Re: [eman] WG documents adoption
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Nov 2010 13:58:16 -0000

------=_NextPart_000_0000_01CB8A23.842EA910
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Benoit,

You have stressed the following a couple of times now:

    Note that, if a document becomes a WG item, the open issues discussed
will have to be 
    solved based on the group consensus. 

Since I am new to the IETF I am unfamiliar with the actual implications of
this statement.  Could you perhaps explain a bit more about what this means
in practice for those who are less familiar with the nuances of IETF customs
and procedures?

I assume that adoption is done by group consensus and that future changes
will be done by group consensus so I am confused about what is different
between now and after adoption.  Does proposing changes or alternatives
become somehow more difficult after these have been adopted?  I am just
asking for clarification for the benefit of myself and possibly others on
the list.

I have provided some comments on the Requirements document but have not
heard back from Juergen as to whether the points I raised could be
addressed, or not, and some of these possibly had implications for the
framework / architecture document as well.

One example would be my request or suggestion that the references to IPFIX
be removed from the proposed requirements and that this issue be resolved
within the Architecture document.  I have concerns about the IETF EMAN
standard referencing IPFIX as being a required technology for a standards
conforming solution.  I understand the desire to have this approach
recognized as a standards conforming approach and I believe that this can be
easily accomodated in some way within the reference Architecture, but most
likely this will need to be considered an optional part of the standard and
not a required one.  I say this because acceptable management alternatives
for the efficient transfer of time series data are certainly possible and I
would like to see the standard accomodate those alternatives and not mandate
a specific solution as is currently being proposed.

So with respect to your statement above, is this something that could
customarily be easily addressed after adoption of Juergen's proposed
requirements or is this something that would be best handled as an alternate
proposal/draft to Juergen's which is put forward prior to the adoption of
either of the two alternatives?  

I just wish to understand the customary processes in this case to establish
some shared expectations on moving things forward.  I don't expect that even
in my current example that the group cannot come to some appropriate
agreement to address the concerns of all.

Thanks,

William F. Mielke
Alcatel-Lucent
Distinguished Member of Technical Staff
6200 East Broad Street
Room: 4B01-1V
Columbus, OH  43213-1530
Email: Bill.Mielke@alcatel-lucent.com <mailto:mielke@alcatel-lucent.com> 
Phone: 614 367 5628
Fax: 614 367 5965

"Live like you're going to die tomorrow.
 Learn like you're going to live forever."

    - Albert Einstein 

 

________________________________

From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of
Benoit Claise
Sent: Monday, November 22, 2010 6:20 AM
To: eman mailing list
Subject: Re: [eman] WG documents adoption


Dear all,

Since they were no objections, we asked the authors to publish the 3 drafts
below as EMAN WG documents.

Regards, Bruce and Benoit.


	Dear all,
	
	From the meeting minutes at:
http://www.ietf.org/proceedings/79/minutes/eman.txt, we would like to stress
the following
	
	draft-quittek-power-monitoring-requirements-02
	

		Chair asked if the sense of the room was that this should be
made a 
		working group draft. No objections. Take to the list.
		


	draft-claise-power-management-arch-02
	

		Chair asked if the sense of the room was that this should be
made a 
		working group draft. No objections. Take to the list.
		


	draft-parello-eman-energy-aware-mib-00 
	

		Chair asked if the sense of the room was that this should be
made a 
		working group draft. No objections. Take to the list.
		

	If you object any of the documents becoming a WG item, let us know.
	Note that, if a document becomes a WG item, the open issues
discussed will have to be solved based on the group consensus.
	
	Regards, Bruce and Benoit
	
	
	
	_______________________________________________
	eman mailing list
	eman@ietf.org
	https://www.ietf.org/mailman/listinfo/eman
	



------=_NextPart_000_0000_01CB8A23.842EA910
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIV8jCCA7Ew
ggKZoAMCAQICEBErBTlXKN63QvT+VRPTt1EwDQYJKoZIhvcNAQEFBQAwQzEXMBUGA1UEChMOQWxj
YXRlbCBMdWNlbnQxKDAmBgNVBAMTH0FsY2F0ZWwgTHVjZW50IEludGVybmFsIFJvb3QgQ0EwHhcN
MDgxMTAzMTU0MTE2WhcNMjgxMTAzMTU0MTE2WjBDMRcwFQYDVQQKEw5BbGNhdGVsIEx1Y2VudDEo
MCYGA1UEAxMfQWxjYXRlbCBMdWNlbnQgSW50ZXJuYWwgUm9vdCBDQTCCASIwDQYJKoZIhvcNAQEB
BQADggEPADCCAQoCggEBAL5IGBVth8afQdnpuLDI0Z37GgIcPWznOOzFJUV1gVbztqQ5CIxkVL4K
soAfLzc8LQHqNl2Nk3YbVBputIyCe2nzGsRjQeVt+HO2PV7h2YpMQlVd+XGsmpJ4fAP3A38wkTl6
tFPAYspyUFvjNON1J3BJE/2cuY7apvn9ZfSz99x7y4QBZh3hvm4g5Fn7mK04/q7K6O4Z8Y6zkSxG
ZFNyZ6NIuAPNCODZASqYnHiAgtEcCR4WPs6rj+Y8MU0q56ddwuIZ0qeP2ScHY0wVtnmqXzHyCzEQ
Eb2eJCsGpXFwUalVaxPUZEVoVDfjO+2ZN5gNJrGMTu7Mv9k1WG0LR3zZ1QsCAwEAAaOBoDCBnTAL
BgNVHQ8EBAMCAYYwDwYDVR0TAQH/BAUwAwEB/zAdBgNVHQ4EFgQUB6yyWvZhiXxcfOvilycpaQyK
H/AwEAYJKwYBBAGCNxUBBAMCAQAwTAYDVR0gBEUwQzBBBgRVHSAAMDkwNwYIKwYBBQUHAgEWK2h0
dHA6Ly93d3cuYWxjYXRlbC1sdWNlbnQuY29tL1BLSS9jcC9jcC5odG0wDQYJKoZIhvcNAQEFBQAD
ggEBADBMWG3WQyC6+mBzuuFuCGqJAiC4v+TQ3ZErd5KKSRGh8dwjzK5L2C51wJPVe6EAjb59CEb2
p2aPKSkoMrCC8seBRM/bs23DMyna1Jr9Q5EZDrmRqBLJy3Cs8NFpa/cKb6SkegFHcB/vi+SYgSdR
BwoNE5+y6MRPXcEBadI/9W8Zlkk5sJ3w55e+i8OCNg/fDYAQuJPa+hD3/byWGxUgGSMNGQ/GS2st
NETAa5Z/88Sh9FHk2BtrxSz7jPtekKhjsidD2ANJZTCyj9iRB+Nt9FEetNpcN6ke1FlepRbCsV10
I0y6weLwZ34h2GWbN9qEOSQV88NBA149a5ugJ/oCbHEwggTdMIIDxaADAgECAgoanQrOAAAAAAAG
MA0GCSqGSIb3DQEBBQUAMEMxFzAVBgNVBAoTDkFsY2F0ZWwgTHVjZW50MSgwJgYDVQQDEx9BbGNh
dGVsIEx1Y2VudCBJbnRlcm5hbCBSb290IENBMB4XDTA4MTEyMTIxNTcyOFoXDTE4MTEyMTIyMDcy
OFowgYUxEzARBgoJkiaJk/IsZAEZFgNjb20xFjAUBgoJkiaJk/IsZAEZFgZsdWNlbnQxFDASBgoJ
kiaJk/IsZAEZFgRuYTAyMRcwFQYDVQQKEw5BbGNhdGVsIEx1Y2VudDEnMCUGA1UEAxMeQWxjYXRl
bCBMdWNlbnQgSW50ZXJuYWwgU3ViIENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA
2Ocmcli3LbVU6TRh+JLMtquBr5/grS+gzfN5YL/lauFCHmDlF7kNQvxtDWqwNpOkzb97CwWcVsdf
kyWAiGzVWeRIrYGhK/xNPFRYXOKYXLGqxFWkltZkYpSRudHzjTneUC4EVdMXnREMu8FTC0CM38Vb
xMvQ+ygjEyicg2QT9lZHWkKP9kCI1818P+AmS7905t6kXR9Q2m1GjcCa0KqARPGX/xe2toQS+Vdi
UwDary1Enk8j19KFmvFg1bhY2mNSHgzN2AWnhsOi/EID1SalzBwHylByB/UbbEv2dZUsAdMuOtYt
Z/8dM1axS0d3fW7q7mAYV5uM42mYX9o1B/RzjwIDAQABo4IBjjCCAYowDwYDVR0TAQH/BAUwAwEB
/zAdBgNVHQ4EFgQU2exrvZZYIvfYpnfN/k2B77qXvRIwCwYDVR0PBAQDAgHGMBAGCSsGAQQBgjcV
AQQDAgEAMBkGCSsGAQQBgjcUAgQMHgoAUwB1AGIAQwBBMB8GA1UdIwQYMBaAFAesslr2YYl8XHzr
4pcnKWkMih/wMHgGA1UdHwRxMG8wbaBroGmGOWh0dHA6Ly9zZXJ2aWNlcy5zdXBwb3J0LmFsY2F0
ZWwtbHVjZW50LmNvbS9QS0kvcm9vdENBLmNybIYsaHR0cDovL3d3dy5hbGNhdGVsLWx1Y2VudC5j
b20vUEtJL3Jvb3RDQS5jcmwwgYIGCCsGAQUFBwEBBHYwdDA4BggrBgEFBQcwAoYsaHR0cDovL3d3
dy5hbGNhdGVsLWx1Y2VudC5jb20vUEtJL3Jvb3RDQS5jcnQwOAYIKwYBBQUHMAKGLGh0dHA6Ly93
d3cuYWxjYXRlbC1sdWNlbnQuY29tL1BLSS9yb290Q0EuY3J0MA0GCSqGSIb3DQEBBQUAA4IBAQCl
GxDp5Z1IDjIEz8VaTEWa8Q1OWUbXwsszdoNg5Gg3F1a2VFFVegmsrpt4axbESlgE6AT/rkUUiyjb
EhcUgY2OHdeKN5Gc7VOGh9D7SER9peARwSwx4NYRrsIaRXDrUswWAM6T6ilDUogjKYk3uK2zZ6Vy
7z3JewxVlhpeSsNPQSMoyNibKkYLRoh6rvz94vB0mvcT0uVx7xowPNoTOjjGRAk4J/MBaNOupvwf
RfPmwRetdnD6NC5x8aRkhr4ZNBjvYxFT8IJaeLk8piQYMPRDlzi7dlb9d6C5WuC0LRpomk2r3bd6
/XpNOx2FyG18axeeASWtENgPvqEirM5MjwkCMIIGejCCBWKgAwIBAgIKGdtaDAAAAAA9bjANBgkq
hkiG9w0BAQUFADCBhTETMBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT8ixkARkWBmx1Y2Vu
dDEUMBIGCgmSJomT8ixkARkWBG5hMDIxFzAVBgNVBAoTDkFsY2F0ZWwgTHVjZW50MScwJQYDVQQD
Ex5BbGNhdGVsIEx1Y2VudCBJbnRlcm5hbCBTdWIgQ0EwHhcNMTAwNTMwMDIwNDQzWhcNMTIwNTI5
MDIwNDQzWjBAMQ8wDQYDVQQDEwZtaWVsa2UxLTArBgkqhkiG9w0BCQEWHmJpbGwubWllbGtlQGFs
Y2F0ZWwtbHVjZW50LmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAo1P58gTZrHri5vsA
ksaizRgNXUTQXDg7A2bIh725bEC7Y8V57vMTMx7kzzXR6iwpLbhn71jbdKFFHV4unSPWMssxwi8g
WanrFLaCSPnaAv/kqeLZ/XjRIsSunLvYpYvYLUuEtjzBUBEnp8uJ7WwhknUVFCf9f6yEXAUBtlbR
eokCAwEAAaOCA7IwggOuMAsGA1UdDwQEAwIHgDAdBgNVHQ4EFgQUs3huZkhOkBtaorqjkncKXxvY
iVowPgYJKwYBBAGCNxUHBDEwLwYnKwYBBAGCNxUIhb3FWYPjsTmHpYEqhr/DQoWUmBmBC4TQtFqF
w+FEAgFkAgEMMB8GA1UdIwQYMBaAFNnsa72WWCL32KZ3zf5Nge+6l70SMIIBXAYDVR0fBIIBUzCC
AU8wggFLoIIBR6CCAUOGgdlsZGFwOi8vL0NOPUFsY2F0ZWwlMjBMdWNlbnQlMjBJbnRlcm5hbCUy
MFN1YiUyMENBLENOPXVzbmF2c3BraTAzcCxDTj1DRFAsQ049UHVibGljJTIwS2V5JTIwU2Vydmlj
ZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixEQz1sdWFkLERDPWx1Y2VudCxEQz1jb20/
Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdD9iYXNlP29iamVjdENsYXNzPWNSTERpc3RyaWJ1dGlv
blBvaW50hitodHRwOi8vd3d3LmFsY2F0ZWwtbHVjZW50LmNvbS9QS0kvc3ViQ0EuY3JshjhodHRw
Oi8vc2VydmljZXMuc3VwcG9ydC5hbGNhdGVsLWx1Y2VudC5jb20vUEtJL3N1YkNBLmNybDCCAWAG
CCsGAQUFBwEBBIIBUjCCAU4wgcwGCCsGAQUFBzAChoG/bGRhcDovLy9DTj1BbGNhdGVsJTIwTHVj
ZW50JTIwSW50ZXJuYWwlMjBTdWIlMjBDQSxDTj1BSUEsQ049UHVibGljJTIwS2V5JTIwU2Vydmlj
ZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixEQz1sdWFkLERDPWx1Y2VudCxEQz1jb20/
Y0FDZXJ0aWZpY2F0ZT9iYXNlP29iamVjdENsYXNzPWNlcnRpZmljYXRpb25BdXRob3JpdHkwNwYI
KwYBBQUHMAKGK2h0dHA6Ly93d3cuYWxjYXRlbC1sdWNlbnQuY29tL1BLSS9zdWJDQS5jcnQwRAYI
KwYBBQUHMAKGOGh0dHA6Ly9zZXJ2aWNlcy5zdXBwb3J0LmFsY2F0ZWwtbHVjZW50LmNvbS9QS0kv
c3ViQ0EuY3J0MBMGA1UdJQQMMAoGCCsGAQUFBwMEMBsGCSsGAQQBgjcVCgQOMAwwCgYIKwYBBQUH
AwQwKQYDVR0RBCIwIIEeYmlsbC5taWVsa2VAYWxjYXRlbC1sdWNlbnQuY29tMA0GCSqGSIb3DQEB
BQUAA4IBAQAZRA+LIZRrEeIu8rlW3yprtze3O5EjtjyNS37sq2o0DatvvucKfFJoes1tLUmgeqKz
eObrOx2ZMpqjhvdzKPw0BmG+vIS2oVU/gSu+Kp9IvlYa/LBJgGqL6uwucG7NKb/KoYwY9XBQerPh
9NcfbsBcFoZlcV9e9J4NIXok2HOwyr+p8hKhK5SpeIoHf3Si8qSuyJuk4FtrjmTlUkgHmoFmj6U9
gKJR6WKpcBZhmOE8eQ9OZAaD1AycT7zdCAsxcBykgM58d59OeZajj1m7ZHTtOppCRMYl1A1lNxOo
w4IuokZ4L85KKzL6WqnuGflYCcNtO9it9JGZharIN+HarP3JMIIG2jCCBcKgAwIBAgIKGdxk1QAA
AAA9bzANBgkqhkiG9w0BAQUFADCBhTETMBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT8ixk
ARkWBmx1Y2VudDEUMBIGCgmSJomT8ixkARkWBG5hMDIxFzAVBgNVBAoTDkFsY2F0ZWwgTHVjZW50
MScwJQYDVQQDEx5BbGNhdGVsIEx1Y2VudCBJbnRlcm5hbCBTdWIgQ0EwHhcNMTAwNTMwMDIwNTUx
WhcNMTIwNTI5MDIwNTUxWjBAMQ8wDQYDVQQDEwZtaWVsa2UxLTArBgkqhkiG9w0BCQEWHmJpbGwu
bWllbGtlQGFsY2F0ZWwtbHVjZW50LmNvbTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAqpHW
Jco1co4MTnJ1WFCsJGeMVemFG7SQrcH0LARvpO/o9diiV3/Qvt08MYIv71lXTVBr/Kn8J9Rxq+Ew
eEGygQmO8v+kN3SIUOnWInanbEZkYFdf9jWNEArSvFZiazgrp9vgE3bKK3Id7kUFXXdWj2hK1xjQ
5BidCf9IpfyzKsECAwEAAaOCBBIwggQOMAsGA1UdDwQEAwIFIDBEBgkqhkiG9w0BCQ8ENzA1MA4G
CCqGSIb3DQMCAgIAgDAOBggqhkiG9w0DBAICAIAwBwYFKw4DAgcwCgYIKoZIhvcNAwcwHQYDVR0O
BBYEFFFsCLe38LJX1iIg54BxslUYaXvYMD4GCSsGAQQBgjcVBwQxMC8GJysGAQQBgjcVCIW9xVmD
47E5h6WBKoa/w0KFlJgZgQuCupMPhOrffgIBZAIBDTAfBgNVHSMEGDAWgBTZ7Gu9llgi99imd83+
TYHvupe9EjCCAVwGA1UdHwSCAVMwggFPMIIBS6CCAUegggFDhoHZbGRhcDovLy9DTj1BbGNhdGVs
JTIwTHVjZW50JTIwSW50ZXJuYWwlMjBTdWIlMjBDQSxDTj11c25hdnNwa2kwM3AsQ049Q0RQLENO
PVB1YmxpYyUyMEtleSUyMFNlcnZpY2VzLENOPVNlcnZpY2VzLENOPUNvbmZpZ3VyYXRpb24sREM9
bHVhZCxEQz1sdWNlbnQsREM9Y29tP2NlcnRpZmljYXRlUmV2b2NhdGlvbkxpc3Q/YmFzZT9vYmpl
Y3RDbGFzcz1jUkxEaXN0cmlidXRpb25Qb2ludIYraHR0cDovL3d3dy5hbGNhdGVsLWx1Y2VudC5j
b20vUEtJL3N1YkNBLmNybIY4aHR0cDovL3NlcnZpY2VzLnN1cHBvcnQuYWxjYXRlbC1sdWNlbnQu
Y29tL1BLSS9zdWJDQS5jcmwwggFgBggrBgEFBQcBAQSCAVIwggFOMIHMBggrBgEFBQcwAoaBv2xk
YXA6Ly8vQ049QWxjYXRlbCUyMEx1Y2VudCUyMEludGVybmFsJTIwU3ViJTIwQ0EsQ049QUlBLENO
PVB1YmxpYyUyMEtleSUyMFNlcnZpY2VzLENOPVNlcnZpY2VzLENOPUNvbmZpZ3VyYXRpb24sREM9
bHVhZCxEQz1sdWNlbnQsREM9Y29tP2NBQ2VydGlmaWNhdGU/YmFzZT9vYmplY3RDbGFzcz1jZXJ0
aWZpY2F0aW9uQXV0aG9yaXR5MDcGCCsGAQUFBzAChitodHRwOi8vd3d3LmFsY2F0ZWwtbHVjZW50
LmNvbS9QS0kvc3ViQ0EuY3J0MEQGCCsGAQUFBzAChjhodHRwOi8vc2VydmljZXMuc3VwcG9ydC5h
bGNhdGVsLWx1Y2VudC5jb20vUEtJL3N1YkNBLmNydDAfBgNVHSUEGDAWBggrBgEFBQcDBAYKKwYB
BAGCNwoDBDApBgkrBgEEAYI3FQoEHDAaMAoGCCsGAQUFBwMEMAwGCisGAQQBgjcKAwQwKQYDVR0R
BCIwIIEeYmlsbC5taWVsa2VAYWxjYXRlbC1sdWNlbnQuY29tMA0GCSqGSIb3DQEBBQUAA4IBAQCR
rwYqycRkzGvAxMozWQCh7wJ0axCuF5vqoBkjnhKz4gFtn89WViNTxeLdq+DhfAp3nnzqkE8ggrFn
X5b/DJZgUAGoLlvZ3IL1L0i2Ne3dK5QGq58VFK7KYrluedog6FXZ93jfXtZFq9Z4acpaR0H6DXvg
DAsdbnaLYkWI0+X/enGC7dzkJNQ8D5YUHxAA5qSGATRm6x71kb0R/ShzzFJvpxidYi2bht/mPOIa
ASZD7CSskrRKeaWEke7dKPaUpEPOFVG/do6yuG8iH1PEZ7IYy97x4SuemQmFEMwnjLz1ubf2wzhv
8Hw5Ku2kW2Vw+wI6O+IkjYAir40DgHHLNh4WMYIDVzCCA1MCAQEwgZQwgYUxEzARBgoJkiaJk/Is
ZAEZFgNjb20xFjAUBgoJkiaJk/IsZAEZFgZsdWNlbnQxFDASBgoJkiaJk/IsZAEZFgRuYTAyMRcw
FQYDVQQKEw5BbGNhdGVsIEx1Y2VudDEnMCUGA1UEAxMeQWxjYXRlbCBMdWNlbnQgSW50ZXJuYWwg
U3ViIENBAgoZ21oMAAAAAD1uMAkGBSsOAwIaBQCgggIYMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0B
BwEwHAYJKoZIhvcNAQkFMQ8XDTEwMTEyMjEzNTkwNVowIwYJKoZIhvcNAQkEMRYEFPw/bs54nPtx
ph17fEjwuJWKbjONMGcGCSqGSIb3DQEJDzFaMFgwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCA
MA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMAcGBSsOAwIaMAoGCCqGSIb3
DQIFMIGlBgkrBgEEAYI3EAQxgZcwgZQwgYUxEzARBgoJkiaJk/IsZAEZFgNjb20xFjAUBgoJkiaJ
k/IsZAEZFgZsdWNlbnQxFDASBgoJkiaJk/IsZAEZFgRuYTAyMRcwFQYDVQQKEw5BbGNhdGVsIEx1
Y2VudDEnMCUGA1UEAxMeQWxjYXRlbCBMdWNlbnQgSW50ZXJuYWwgU3ViIENBAgoZ3GTVAAAAAD1v
MIGnBgsqhkiG9w0BCRACCzGBl6CBlDCBhTETMBEGCgmSJomT8ixkARkWA2NvbTEWMBQGCgmSJomT
8ixkARkWBmx1Y2VudDEUMBIGCgmSJomT8ixkARkWBG5hMDIxFzAVBgNVBAoTDkFsY2F0ZWwgTHVj
ZW50MScwJQYDVQQDEx5BbGNhdGVsIEx1Y2VudCBJbnRlcm5hbCBTdWIgQ0ECChncZNUAAAAAPW8w
DQYJKoZIhvcNAQEBBQAEgYCTqDiTEO0oEeHOPr3Md7cz94xQH9WXfUIQEgk5Bi03aWBGrCKotFmO
MDBqI/+f6hl/AiwYzxAMmMsK4jZWIgOg2YpxRxQWgWk7v+KebLB5Q2qYM+JELXYUn0u7ZmlB2PK8
Is8CBTc30Lqv5R9HgD5vPwUL81bhvihy2RFuIDSwPQAAAAAAAA==

------=_NextPart_000_0000_01CB8A23.842EA910--

From bclaise@cisco.com  Mon Nov 22 06:53:44 2010
Return-Path: <bclaise@cisco.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C3D8228C10B for <eman@core3.amsl.com>; Mon, 22 Nov 2010 06:53:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.593
X-Spam-Level: 
X-Spam-Status: No, score=-2.593 tagged_above=-999 required=5 tests=[AWL=0.006,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jNbuVNKvVbEc for <eman@core3.amsl.com>; Mon, 22 Nov 2010 06:53:43 -0800 (PST)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id B7AAE3A6A97 for <eman@ietf.org>; Mon, 22 Nov 2010 06:53:39 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oAMEWHCk029418; Mon, 22 Nov 2010 15:32:17 +0100 (CET)
Received: from [10.55.43.54] (ams-bclaise-8715.cisco.com [10.55.43.54]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oAMEWEga007320; Mon, 22 Nov 2010 15:32:14 +0100 (CET)
Message-ID: <4CEA7EED.3030100@cisco.com>
Date: Mon, 22 Nov 2010 15:32:13 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: "Mielke, William F (Bill)" <bill.mielke@alcatel-lucent.com>
References: <4CDD605C.4020809@cisco.com> <4CEA51EB.8000206@cisco.com> <0DEE3BCEE44BFD4EBC3B7DC009C8E79225067FC590@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
In-Reply-To: <0DEE3BCEE44BFD4EBC3B7DC009C8E79225067FC590@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: eman mailing list <eman@ietf.org>
Subject: Re: [eman] WG documents adoption
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Nov 2010 14:53:44 -0000

Hi Bill,
> Benoit,
>
> You have stressed the following a couple of times now:
>
>      Note that, if a document becomes a WG item, the open issues discussed
> will have to be
>      solved based on the group consensus.
>
> Since I am new to the IETF I am unfamiliar with the actual implications of
> this statement.  Could you perhaps explain a bit more about what this means
> in practice for those who are less familiar with the nuances of IETF customs
> and procedures?
>
> I assume that adoption is done by group consensus and that future changes
> will be done by group consensus so I am confused about what is different
> between now and after adoption.
When a document is an individual draft, you can give comments to the 
authors, but it's up to the authors to address them.
When a document is a WG item, the document belongs to the WG. As such, 
all comments should be addressed, based on the WG consensus.

> Does proposing changes or alternatives
> become somehow more difficult after these have been adopted?
That's the reverse: it should be easier, as the authors should at least 
respond to your comments.
> I am just
> asking for clarification for the benefit of myself and possibly others on
> the list.
Sure.
> I have provided some comments on the Requirements document but have not
> heard back from Juergen as to whether the points I raised could be
> addressed, or not, and some of these possibly had implications for the
> framework / architecture document as well.
>
> One example would be my request or suggestion that the references to IPFIX
> be removed from the proposed requirements and that this issue be resolved
> within the Architecture document.  I have concerns about the IETF EMAN
> standard referencing IPFIX as being a required technology for a standards
> conforming solution.  I understand the desire to have this approach
> recognized as a standards conforming approach and I believe that this can be
> easily accomodated in some way within the reference Architecture, but most
> likely this will need to be considered an optional part of the standard and
> not a required one.  I say this because acceptable management alternatives
> for the efficient transfer of time series data are certainly possible and I
> would like to see the standard accomodate those alternatives and not mandate
> a specific solution as is currently being proposed.
>
> So with respect to your statement above, is this something that could
> customarily be easily addressed after adoption of Juergen's proposed
> requirements
yes exactly.
> or is this something that would be best handled as an alternate
> proposal/draft to Juergen's which is put forward prior to the adoption of
> either of the two alternatives?
>
> I just wish to understand the customary processes in this case to establish
> some shared expectations on moving things forward.  I don't expect that even
> in my current example that the group cannot come to some appropriate
> agreement to address the concerns of all.
Btw, this specific issue of IPFIX was discussed in the context of the 
EMAN architecture, and I remembered that the feedback received was in 
favor of not mentioning IPFIX in the architecture, but at the same time, 
not preclude this potential adoption in the future.

A common good practice for document authors is to include a TO DO 
section at the beginning of each document, listing the points that need 
further discussion.

Regards, Benoit.
> Thanks,
>
> William F. Mielke
> Alcatel-Lucent
> Distinguished Member of Technical Staff
> 6200 East Broad Street
> Room: 4B01-1V
> Columbus, OH  43213-1530
> Email: Bill.Mielke@alcatel-lucent.com<mailto:mielke@alcatel-lucent.com>
> Phone: 614 367 5628
> Fax: 614 367 5965
>
> "Live like you're going to die tomorrow.
>   Learn like you're going to live forever."
>
>      - Albert Einstein
>
>
>
> ________________________________
>
> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of
> Benoit Claise
> Sent: Monday, November 22, 2010 6:20 AM
> To: eman mailing list
> Subject: Re: [eman] WG documents adoption
>
>
> Dear all,
>
> Since they were no objections, we asked the authors to publish the 3 drafts
> below as EMAN WG documents.
>
> Regards, Bruce and Benoit.
>
>
> 	Dear all,
> 	
> 	From the meeting minutes at:
> http://www.ietf.org/proceedings/79/minutes/eman.txt, we would like to stress
> the following
> 	
> 	draft-quittek-power-monitoring-requirements-02
> 	
>
> 		Chair asked if the sense of the room was that this should be
> made a
> 		working group draft. No objections. Take to the list.
> 		
>
>
> 	draft-claise-power-management-arch-02
> 	
>
> 		Chair asked if the sense of the room was that this should be
> made a
> 		working group draft. No objections. Take to the list.
> 		
>
>
> 	draft-parello-eman-energy-aware-mib-00
> 	
>
> 		Chair asked if the sense of the room was that this should be
> made a
> 		working group draft. No objections. Take to the list.
> 		
>
> 	If you object any of the documents becoming a WG item, let us know.
> 	Note that, if a document becomes a WG item, the open issues
> discussed will have to be solved based on the group consensus.
> 	
> 	Regards, Bruce and Benoit
> 	
> 	
> 	
> 	_______________________________________________
> 	eman mailing list
> 	eman@ietf.org
> 	https://www.ietf.org/mailman/listinfo/eman
> 	
>
>


From fletchj@us.ibm.com  Mon Nov 22 16:30:22 2010
Return-Path: <fletchj@us.ibm.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 16E9328C155 for <eman@core3.amsl.com>; Mon, 22 Nov 2010 16:30:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level: 
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X5HCClKNvCop for <eman@core3.amsl.com>; Mon, 22 Nov 2010 16:30:21 -0800 (PST)
Received: from e38.co.us.ibm.com (e38.co.us.ibm.com [32.97.110.159]) by core3.amsl.com (Postfix) with ESMTP id 25B563A68F9 for <eman@ietf.org>; Mon, 22 Nov 2010 16:30:21 -0800 (PST)
Received: from d03relay01.boulder.ibm.com (d03relay01.boulder.ibm.com [9.17.195.226]) by e38.co.us.ibm.com (8.14.4/8.13.1) with ESMTP id oAN1MncH002006 for <eman@ietf.org>; Mon, 22 Nov 2010 18:22:49 -0700
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d03relay01.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id oAN0V78J167772 for <eman@ietf.org>; Mon, 22 Nov 2010 17:31:07 -0700
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id oAN0V6B3017290 for <eman@ietf.org>; Mon, 22 Nov 2010 17:31:06 -0700
Received: from d03nm120.boulder.ibm.com (d03nm120.boulder.ibm.com [9.17.195.146]) by d03av03.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id oAN0V6FL017254 for <eman@ietf.org>; Mon, 22 Nov 2010 17:31:06 -0700
Auto-Submitted: auto-generated
From: Jim Fletcher <fletchj@us.ibm.com>
To: eman@ietf.org
Message-ID: <OF45E1D9FE.E7CBD23E-ON872577E4.0002D8BF-872577E4.0002D8BF@us.ibm.com>
Date: Mon, 22 Nov 2010 17:31:05 -0700
X-MIMETrack: Serialize by Router on D03NM120/03/M/IBM(Release 8.5.1FP2|March 17, 2010) at 11/22/2010 17:31:06
MIME-Version: 1.0
Content-type: multipart/alternative;  Boundary="0__=08BBFD77DF915E2F8f9e8a93df938690918c08BBFD77DF915E2F"
Content-Disposition: inline
Subject: [eman] AUTO: Jim fletcher is out of the office with no email or cell phone -- returning Sunday November 27 (returning 11/27/2010)
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Nov 2010 00:30:22 -0000

--0__=08BBFD77DF915E2F8f9e8a93df938690918c08BBFD77DF915E2F
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: quoted-printable



I am out of the office until 11/27/2010.

for technical issues see my team and for management issues see Jim Cros=
skey


Note: This is an automated response to your message  "eman Digest, Vol =
4,
Issue 23" sent on 11/22/10 13:00:02.

This is the only notification you will receive while this person is awa=
y.=

--0__=08BBFD77DF915E2F8f9e8a93df938690918c08BBFD77DF915E2F
Content-type: text/html; charset=US-ASCII
Content-Disposition: inline
Content-transfer-encoding: quoted-printable

<html><body>
<p><font size=3D"2">I am out of the office until 11/27/2010.<br>
</font><font size=3D"2"><br>
</font><font size=3D"2">for technical issues see my team and for manage=
ment issues see Jim Crosskey<br>
</font><font size=3D"2"><br>
</font><font size=3D"2"><br>
</font><font size=3D"2" color=3D"#808080">Note: This is an automated re=
sponse to your message  </font><b><font size=3D"2">&quot;eman Digest, V=
ol 4, Issue 23&quot;</font></b><font size=3D"2" color=3D"#808080"> sent=
 on </font><b><font size=3D"2">11/22/10 13:00:02</font></b><font size=3D=
"2" color=3D"#808080">. <br>
</font><font size=3D"2" color=3D"#808080"><br>
</font><font size=3D"2" color=3D"#808080">This is the only notification=
 you will receive while this person is away.</font></body></html>=

--0__=08BBFD77DF915E2F8f9e8a93df938690918c08BBFD77DF915E2F--


From Quittek@neclab.eu  Tue Nov 23 10:04:08 2010
Return-Path: <Quittek@neclab.eu>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 86CBB3A698C for <eman@core3.amsl.com>; Tue, 23 Nov 2010 10:04:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.314
X-Spam-Level: 
X-Spam-Status: No, score=-102.314 tagged_above=-999 required=5 tests=[AWL=0.286, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EYKC2vRnNhJV for <eman@core3.amsl.com>; Tue, 23 Nov 2010 10:04:07 -0800 (PST)
Received: from smtp0.neclab.eu (smtp0.neclab.eu [195.37.70.41]) by core3.amsl.com (Postfix) with ESMTP id DF9DC28C0F6 for <eman@ietf.org>; Tue, 23 Nov 2010 10:04:06 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.neclab.eu (Postfix) with ESMTP id 8B62C2C0001AF; Tue, 23 Nov 2010 19:05:04 +0100 (CET)
X-Virus-Scanned: Amavisd on Debian GNU/Linux (atlas2.office.hd)
Received: from smtp0.neclab.eu ([127.0.0.1]) by localhost (atlas2.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yKPOP5GmWJm6; Tue, 23 Nov 2010 19:05:04 +0100 (CET)
Received: from ENCELADUS.office.hd (ENCELADUS.office.hd [192.168.24.52]) by smtp0.neclab.eu (Postfix) with ESMTP id 5E8A22C0001AD; Tue, 23 Nov 2010 19:04:54 +0100 (CET)
Received: from DAPHNIS.office.hd ([169.254.2.241]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0255.000; Tue, 23 Nov 2010 19:04:54 +0100
From: Juergen Quittek <Quittek@neclab.eu>
To: "Mielke, William F (Bill)" <bill.mielke@alcatel-lucent.com>, eman mailing list <eman@ietf.org>
Thread-Topic: [eman] Comments on "Requirements for Power Monitoring"
Thread-Index: AcuAU8VICnzP+uFHSPK4xKWAZxLwUQK5SQV/
Date: Tue, 23 Nov 2010 18:04:53 +0000
Message-ID: <C911C0CE.17EF8%quittek@neclab.eu>
In-Reply-To: <0DEE3BCEE44BFD4EBC3B7DC009C8E79225066CEC63@USNAVSXCHMBSA3.ndc.alcatel-lucent.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-Entourage/13.7.0.100913
x-originating-ip: [10.7.0.92]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3373383886_71084743"
MIME-Version: 1.0
Subject: Re: [eman] Comments on "Requirements for Power Monitoring"
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Nov 2010 18:04:08 -0000

--B_3373383886_71084743
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

Dear Bill,

Sorry for the late reply.
I have been busy with other things after the IETF.

In general, I have two replies on your comments:

First. there is no work item in the eman charter on developing means for
using IPFIX for energy management, for example, for defining IPFIX
information elements for this purpose. We may decide to add such items to
our charter in the future, but now is not the time to discuss this.

Second, the current draft on eman requirements has a section called
"suggested Actions". This one suggests the IETF to establish new work items
in the area of energy management. This has been done already and I would
suggest removing this section.

Please find more specific replies inline below.


On 10.11.10 05:19  "Mielke, William F (Bill)"
<bill.mielke@alcatel-lucent.com> wrote:

> These comments are relative to
> "draft-quittek-power-monitoring-requirements-02".
> 
> Substantive Comments:
> ---------------------
> 
> Section 4. Monitoring Models
> 
> "Applying these considerations to the required information leads to the
> conclusion that most of the information can appropriately be reported using
> the pull model.  The only exceptions are notification on power state changes
> and high volume time series of energy consumption values."
> 
> I disagree with this conclusion.  The requirement is that users of this
> standard be able to efficiently transfer the bulk data associated with the
> time series data.  The ability to efficiently transfer bulk data is
> independent of whether that transfer is initiated using either a push or a
> pull model.  In other words, I disagree with the implied notion that large
> data transfers can only be accomplished using a push model of management.
> SNMP Get-Bulk is the currently defined solution to this problem as I
> understand it within the existing IETF management standards and we should
> support an approach which is consistent with the directions set in those
> standard.

Again, two comments:
First, there were two exceptions. One was power state change notifications.
I assume you do not disagree, that these should be transmitted preferably in
push mode.

Second, yes, there is a bulk transfer option in SNMP. And yes, it may be
used for reporting energy and power values. However, for this kind of
reporting, other protocols have proven to be much more appropriate.

In the draft we state that
>>                                   However, the overhead of pull
>>   model monitoring is typically higher than for push model monitoring,
>>   particularly when large numbers of values are to be collected, such
>>   as time series of power values.
Do you have a problem with this statement? It is the main argument provided
for conclusion that you disagree with.

Particularly if you collect large amounts of data from large amounts of
reporting nodes, SNMP scalability is more limited than scalability of other
protocols. Particularly, IPFIX is much more efficient in transferring larg
numbers of data and it has a mediation and aggregation framework for large
numbers of data to be collected.

> This does not mean that I don't see the need to extend those same standards
> to include a more robust push model for use in cases such as this, if
> desired, but the applicability of any such extension would be much wider
> than simply energy management.  Therefore the proper place to address the
> need for such a robust push model extension to SNMP would seem to be within
> the SNMP area itself and not as part of the eman specifications.  Energy
> management does not appear to have any particularly unique characteristics
> in terms of how it's push model might operate whether for Time Series Data
> or anything else.

You are right, it is not necessarily important whether it is the push or the
pull model. But the IETF has a developed a set of management protocols which
all have advantages and disadvantages in different application areas.
SNMP is the preferred protocol for general (pull-based) monitoring, NETCONF
is the preferred protocol for configuration management, and SYSLOG and IPFIX
are the preferred protocols for push-based monitoring where the strength of
IPFIX is on sending huge amounts of measured values.

Thus, for a continuous reporting of time series of power/energy values of
monitored devices, IPFIX seems to be a good choice, well suited for this
particular task.

> I must admit that I am not currently familiar with the specifics of whether
> the SNMP area is considering such an push model extension, or not, but in
> the OPSAREA meeting held yesterday I believe that there was some discussion
> to this effect.  If so I believe that anything we are proposing here must be
> harmonized with anything that happens there.  Does this make sense?

I don't think that the SNMP community is working on developing a standard
for push-based bulk reporting. And one good reason for this is that there is
already IPFIX covering this task well.

> Minor Wordsmithing:
> -------------------
> 
> Section 1 - 3rd paragraph just before the bullet list:
> 
> "can be applied to several areas including" -> "can be applied to several
> areas including but not limited to"
> 
> Section 1.1 - 2nd paragraph after the first bullet list:
> 
> "without the consequence of a potential performance degredation" -> "without
> the consequence of a potential performance or capacity degredation"
> 
> Section 3.4.2 - Last paragraph
> 
> "the precision of the measured data, i.e. the potential error in the
> measured data, needs to be known as well"
> 
> I agree with the point being made here but I think the proper term is
> "accuracy" rather than "precision".  This is a common point of confusion.
> Precision refers to whether you are measuring in, for example, volts or
> kilo-volts or milli-volts.  Accuracy refers to the degree to which a
> measured value actually represents reality, so a given measurement may be
> accurate to +- some percentage.

Thanks for all the comments.

We will consider them in the next revision.

    Juergen

> William F. Mielke
> Alcatel-Lucent
> Distinguished Member of Technical Staff
> 6200 East Broad Street
> Room: 4B01-1V
> Columbus, OH  43213-1530
> Email: Bill.Mielke@alcatel-lucent.com
> Phone: 614 367 5628
> 
> "Live like you're going to die tomorrow.
>  Learn like you're going to live forever."
> 
>     - Albert Einstein
> 
> 
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman

--B_3373383886_71084743
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIQ5wYJKoZIhvcNAQcCoIIQ2DCCENQCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
Do8wggUzMIIEG6ADAgECAgQP7R53MA0GCSqGSIb3DQEBBQUAMIGQMQswCQYDVQQGEwJERTEY
MBYGA1UEChMPTkVDIEV1cm9wZSBMdGQuMSAwHgYDVQQLExdORUMgTGFib3JhdG9yaWVzIEV1
cm9wZTESMBAGA1UEAxMJTkVDTEFCLUNBMTEwLwYJKoZIhvcNAQkBFiJ6ZXJ0aWZpemllcnVu
Z3NzdGVsbGVAbncubmVjbGFiLmV1MB4XDTEwMDQyMDEyNDExMloXDTEzMDQxOTEyNDExMlow
YzELMAkGA1UEBhMCREUxGDAWBgNVBAoTD05FQyBFdXJvcGUgTHRkLjEgMB4GA1UECxMXTkVD
IExhYm9yYXRvcmllcyBFdXJvcGUxGDAWBgNVBAMTD0p1ZXJnZW4gUXVpdHRlazCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBANga4Hf5iSjDiva8/BTlatnXFlOWPfqZvY7AU6bt
CUKFiaGwytFar7XCwRggHcCeodYaMZoDRSEGY+bRUDvayjNvFTkhL19Fmzxg4MPmQA92tcIb
/+IylZD5YkVkw88/6zb6k+T+o875LlLAR79f8gvloaPMbxiB8KwQtdlGB9OiN1k3+7NiESpW
myT8WWrWw4F7qc0WLXaWuqv6/3vRo+jJSxyOwefEnzrRojCePJ2ZD4mgPMQvMHPqodDhTvIB
BupYoAtW53024WnL/PHH34pQ0Zmclz8u/YocnfMEYoyLDVuJKnQowDF75LVbnKmpXfCscKeb
SndFpSANP2TiI2cCAwEAAaOCAb8wggG7MAkGA1UdEwQCMAAwCwYDVR0PBAQDAgXgMCkGA1Ud
JQQiMCAGCCsGAQUFBwMCBggrBgEFBQcDBAYKKwYBBAGCNxQCAjAdBgNVHQ4EFgQU9WUPxjFB
AtJOXxJ7agqXozHDy9gwHwYDVR0jBBgwFoAUTxyHeh3gL5n2vhWq0TWdDkrmujYwHAYDVR0R
BBUwE4ERUXVpdHRla0BuZWNsYWIuZXUwfQYDVR0fBHYwdDA4oDagNIYyaHR0cDovL2NkcDEu
cGNhLmRmbi5kZS9uZWNsYWItY2EvcHViL2NybC9jYWNybC5jcmwwOKA2oDSGMmh0dHA6Ly9j
ZHAyLnBjYS5kZm4uZGUvbmVjbGFiLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIGYBggrBgEFBQcB
AQSBizCBiDBCBggrBgEFBQcwAoY2aHR0cDovL2NkcDEucGNhLmRmbi5kZS9uZWNsYWItY2Ev
cHViL2NhY2VydC9jYWNlcnQuY3J0MEIGCCsGAQUFBzAChjZodHRwOi8vY2RwMi5wY2EuZGZu
LmRlL25lY2xhYi1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQEFBQADggEB
AH9VRaZ978LNoc+eM/2k/OQafNJl4UjKLjiEnH8FCuqnuNXZMAOdcfnMrRKK1bl+FhCy3sjg
gsuP4Nam2oSy7RDYWYjLY/MKMPO/MD/PpNSe6gox4948wfjWGmj4Uz3gqgDovQEC2H03jcPX
etJqBTipqmfnvMFqozoN5zjiEzJuuLpLMYNPM+E+4pQnLtRAhN94C1e9C7oP66b7as6OgVVC
CplE5llnoKM5ngtAFL5G3ygm/rZtptdmaNgRO6jDX1w9AOrsmSPGp+S+YRNonKGEqTolJpul
EJB7rMdAUimsUp/qdzvWrhIZ6A3fgzHwFhrIHqVBlDLmu7cQHu/QMUEwggUvMIIEF6ADAgEC
AgQNIQpHMA0GCSqGSIb3DQEBBQUAMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVy
ZWluMRAwDgYDVQQLEwdERk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwg
LSBHMDEwHhcNMDgxMDI0MDg1MjA4WhcNMTkwNjMwMDAwMDAwWjCBkDELMAkGA1UEBhMCREUx
GDAWBgNVBAoTD05FQyBFdXJvcGUgTHRkLjEgMB4GA1UECxMXTkVDIExhYm9yYXRvcmllcyBF
dXJvcGUxEjAQBgNVBAMTCU5FQ0xBQi1DQTExMC8GCSqGSIb3DQEJARYiemVydGlmaXppZXJ1
bmdzc3RlbGxlQG53Lm5lY2xhYi5ldTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB
AJ7yFbG1EaoyDnG5367mJEXHljmacrzNnm52KW3dXD/s3Vpuskex0jvaaTntWWRSGrAK6kKX
nTxBb3J3EhveBUbltzQ+K0XKtPJm6VE5qVpl33WJSaUHs27Dhwlke+DV6BBGyukz2SDBaSa+
nc0AwMZ0XO1DoDuiUNVeNmd/QT4SGzyFs+uLfLL2n8WzkZsbpSZ+xecwyw3EdQBBsp/i/W+u
OQBsGqaCjYe3EkBU6nW+pBsj0Iy1n7b9PXb5gQynrK3Mi2V7g1idSzHos0o1BMoHUrMzVw94
Hj4CWlWmQ0t6Pdt1uYAMjwk0saQBY/Fyfv+wKeYycGIYyYCfJIRUeyUCAwEAAaOCAcQwggHA
MBIGA1UdEwEB/wQIMAYBAf8CAQEwCwYDVR0PBAQDAgEGMB0GA1UdDgQWBBRPHId6HeAvmfa+
FarRNZ0OSua6NjAfBgNVHSMEGDAWgBRJt8bP6D0ff+pEexMp9/EKcD7eZDAtBgNVHREEJjAk
gSJ6ZXJ0aWZpemllcnVuZ3NzdGVsbGVAbncubmVjbGFiLmV1MIGIBgNVHR8EgYAwfjA9oDug
OYY3aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY3JsL2NhY3Js
LmNybDA9oDugOYY3aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIv
Y3JsL2NhY3JsLmNybDCBogYIKwYBBQUHAQEEgZUwgZIwRwYIKwYBBQUHMAKGO2h0dHA6Ly9j
ZHAxLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MEcG
CCsGAQUFBzAChjtodHRwOi8vY2RwMi5wY2EuZGZuLmRlL2dsb2JhbC1yb290LWNhL3B1Yi9j
YWNlcnQvY2FjZXJ0LmNydDANBgkqhkiG9w0BAQUFAAOCAQEAbDEPnQ9JpouPHYA1OEekP3l3
GNM0HBzadVbtbN5MDtFmoVgdLYqlQaHb30wFhuOMbsNCOzV0k8EOvBVOT9BiEJ70RWclSZQ4
60jZS2MY6n5oG/ilZuu6N/N3GSLg2pBBNH9vZFCyBJ9n4Px7A4gQF07G+CNfV2jdE1yyPjzI
VPhg6bBgia8nXroBFe6oteavMspo0gLGIJ63NsCbl6ckPa96grT+mnnQD0h6jk/IGtXS09mE
WRbN7zZu0x0q+SScpljG36Q+jnG0U5zQI0jAx8CcYEQQH5QOlsw1Zu35OI4lsi7ycFkzJNfb
fEC4ihuw9J2L43BFGMojkhPkhVExHTCCBCEwggMJoAMCAQICAgDHMA0GCSqGSIb3DQEBBQUA
MHExCzAJBgNVBAYTAkRFMRwwGgYDVQQKExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQL
ExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMwIQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJv
b3QgQ0EgMjAeFw0wNjEyMTkxMDI5MDBaFw0xOTA2MzAyMzU5MDBaMFoxCzAJBgNVBAYTAkRF
MRMwEQYDVQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdERk4tUEtJMSQwIgYDVQQDExtERk4t
VmVyZWluIFBDQSBHbG9iYWwgLSBHMDEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIB
AQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U1wBblSJ01CDrNI/W7MAxBAuZgeKmFNJSoCgjhIt0
iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6fL9KDhsAw4bpXCsxEXsM84IkQ4wcOItqaACa7txP
eKvSxhObdq3u3ibo7wGvdA/BCaL2a869080UME/15eOkyGKbghoDJzANAmVgTe3RCSMqljVY
J9N2xnG2kB3E7f81hn1vM7PbD8URwoqDoZRdQWvY0hD1TP3KUazZve+Sg7va64sWVlZDz+HV
Ez2mHycwzUlU28kTNJpxdcVs6qcLmPkhnSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjgdkwgdYw
cAYDVR0fBGkwZzBloGOgYYZfaHR0cDovL3BraS50ZWxlc2VjLmRlL2NnaS1iaW4vc2Vydmlj
ZS9hZl9Eb3dubG9hZEFSTC5jcmw/LWNybF9mb3JtYXQ9WF81MDkmLWlzc3Vlcj1EVF9ST09U
X0NBXzIwHQYDVR0OBBYEFEm3xs/oPR9/6kR7Eyn38QpwPt5kMB8GA1UdIwQYMBaAFDHDeRu6
9VPXF+CJei0XbAqzK50zMA4GA1UdDwEB/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgECMA0G
CSqGSIb3DQEBBQUAA4IBAQA74Vp3wEgX3KkY7IGvWonwvSiSpspZGBJw7Cjy565/lizn8l0Z
MfYTK3S9vYCyufdnyTmieTvhERHua3iRM347XyYndVNljjNj7s9zw7CSI0khUHUjoR8Y4pSF
PT8z6XcgjaK95qGFKUD2P3MyWA0Ja6bahWzAP7uNZmRWJE6uDT8yNQFb6YyC2XJZT7GGhfF0
hVblw/hc843uR7NTBXDn5U2KaYMo4RMJhp5eyOpYHgwf+aTUWgRo/Sg+iwK2WLX2oSw3VwBn
qyNojWOl75lrXP1LVvarQIc01BGSbOyHxQoLBzNytG8MHVQs2FHHzL8w00Ny8TK/jM5JY6gA
9/IcMYICIDCCAhwCAQEwgZkwgZAxCzAJBgNVBAYTAkRFMRgwFgYDVQQKEw9ORUMgRXVyb3Bl
IEx0ZC4xIDAeBgNVBAsTF05FQyBMYWJvcmF0b3JpZXMgRXVyb3BlMRIwEAYDVQQDEwlORUNM
QUItQ0ExMTAvBgkqhkiG9w0BCQEWInplcnRpZml6aWVydW5nc3N0ZWxsZUBudy5uZWNsYWIu
ZXUCBA/tHncwCQYFKw4DAhoFAKBdMCMGCSqGSIb3DQEJBDEWBBSIpeij2w1AgtNRs5fO6MYj
EV5LaTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xMDExMjMx
ODA0NDZaMA0GCSqGSIb3DQEBAQUABIIBAG+7iUjMlRyD96LZdMKmWAGus+x4Mbhz6YPBJY+K
onpoBjY4cCr/533jVRc5rjfc/P7mmBKWmQnIexX9e3G7+OOoy8OLLo2CDXfsyIyq2j4Yo1Gd
cxun5rk6CZPkqhKfFhJcP5Xsi1fprIqBMZRu7lPOilc1KFYveVlRcVNSRDEpdiHjsVgGrGvy
BJTH1m+K6pU1dWaHgTUKNk+QcuQbuVu/InBn8Fj5rob2W+02J3f6e7Zi5rmZRvz4Raq/nNDo
ZqDP2ie6boUUpi9egRBD0r5jFqvivwnu7uoI8UylHyS9+ks1AxwBRcKYUp5+6XO/lCqBhMnD
35Um+xQmxFLy+RA=

--B_3373383886_71084743--
