From trac+eman@trac.tools.ietf.org Wed Apr 3 10:38:45 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E472521F8D02 for ; Wed, 3 Apr 2013 10:38:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01A8zcjx3aND for ; Wed, 3 Apr 2013 10:38:44 -0700 (PDT) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 2D05021F8CEC for ; Wed, 3 Apr 2013 10:38:43 -0700 (PDT) Received: from localhost ([127.0.0.1]:40173 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1UNRdt-0006J5-D9; Wed, 03 Apr 2013 19:38:37 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "eman issue tracker" X-Trac-Version: 0.12.3 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.3, by Edgewall Software To: ietf@quittek.at, jparello@cisco.com, n.brownlee@auckland.ac.nz X-Trac-Project: eman Date: Wed, 03 Apr 2013 17:38:37 -0000 X-URL: http://tools.ietf.org/eman/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/eman/trac/ticket/27#comment:2 Message-ID: <072.00079cedd25afb717e7a7104771d8239@trac.tools.ietf.org> References: <057.e10adf845382d57bfcdea737b48b358b@trac.tools.ietf.org> X-Trac-Ticket-ID: 27 In-Reply-To: <057.e10adf845382d57bfcdea737b48b358b@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: ietf@quittek.at, jparello@cisco.com, n.brownlee@auckland.ac.nz, eman@ietf.org X-SA-Exim-Mail-From: trac+eman@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: eman@ietf.org Subject: Re: [eman] #27: Add text on compenents from consensus at IETF 85 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Apr 2013 17:38:45 -0000 #27: Add text on compenents from consensus at IETF 85 Changes (by n.brownlee@auckland.ac.nz): * status: new => closed * resolution: => fixed Comment: This text now in sdection 3.4 -- -------------------------------------+------------------------------ Reporter: jparello@cisco.com | Owner: ietf@quittek.at Type: defect | Status: closed Priority: major | Milestone: Component: applicability-statement | Version: Severity: - | Resolution: fixed Keywords: | -------------------------------------+------------------------------ Ticket URL: eman From B.Hedstrom@CableLabs.com Thu Apr 4 12:38:20 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B191A21F85A1 for ; Thu, 4 Apr 2013 12:38:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.462 X-Spam-Level: X-Spam-Status: No, score=-0.462 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sq3vRCoccaUs for ; Thu, 4 Apr 2013 12:38:20 -0700 (PDT) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id 2217D21F85C2 for ; Thu, 4 Apr 2013 12:38:20 -0700 (PDT) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.5/8.14.5) with ESMTP id r34JcI0v031074 for ; Thu, 4 Apr 2013 13:38:18 -0600 Received: from exchange.cablelabs.com (10.5.0.19) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com); Thu, 04 Apr 2013 13:38:18 -0600 (MDT) X-Virus-Status: clean(F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com) Received: from EXCHANGE.cablelabs.com ([fe80::797a:96d1:3c53:18ee]) by EXCHANGE.cablelabs.com ([fe80::797a:96d1:3c53:18ee%11]) with mapi id 14.02.0328.009; Thu, 4 Apr 2013 13:38:19 -0600 From: Brian Hedstrom To: "eman@ietf.org" Thread-Topic: Applicability Statement draft constrained to SNMP protocol and MIB data model Thread-Index: AQHOMWv1r8K96WewIk+2bgzmctPPcg== Date: Thu, 4 Apr 2013 19:38:18 +0000 Message-ID: <686B406F73B0F245AB30195F4E80E2D517F39C7E@EXCHANGE.cablelabs.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.2.130206 x-originating-ip: [10.4.10.81] Content-Type: multipart/alternative; boundary="_000_686B406F73B0F245AB30195F4E80E2D517F39C7EEXCHANGEcablela_" MIME-Version: 1.0 X-Approved: ondar Subject: [eman] Applicability Statement draft constrained to SNMP protocol and MIB data model X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Apr 2013 19:38:20 -0000 --_000_686B406F73B0F245AB30195F4E80E2D517F39C7EEXCHANGEcablela_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable I finished reading the Applicability statement draft =9602 and had a commen= t regarding the references to the SNMP protocol and MIB data models. There is an assumption that SNMP will be used and that other network manage= ment protocols and data models will not be used. I think this draft could be Network Management Protocol agnostic, but give = some examples or use cases for reference, e.g., SNMP (and reference the EMA= N MIB Modules), NETCONF, TR-069, TR-232, etc. Thanks, Brian Hedstrom Senior Architect, Business & Operational Support Systems CableLabs, Inc. 858 Coal Creek Circle Louisville, CO 80027 Direct: 303.661.3829 eFax: 303.664.8120 Google+: brian.hedstrom Skype IM: brian.hedstrom b.hedstrom@cablelabs.com --_000_686B406F73B0F245AB30195F4E80E2D517F39C7EEXCHANGEcablela_ Content-Type: text/html; charset="Windows-1252" Content-ID: <69F331F4A3037C4E8AF4723722ACE0D4@cablelabs.com> Content-Transfer-Encoding: quoted-printable
I finished reading the Applicability statement draft =9602 and had a c= omment regarding the references to the SNMP protocol and MIB data models.
There is an assumption that SNMP will be used and that other network m= anagement protocols and data models will not be used.
I think this draft could be Network Management Protocol agnostic, but = give some examples or use cases for reference, e.g., SNMP (and reference th= e EMAN MIB Modules), NETCONF, TR-069, TR-232, etc.

Thanks,

Brian Hedstrom
Senior Architect, Business & Operational Support Systems
CableLabs, Inc.
858 Coal Creek Circle
Louisville, CO 80027
Direct: 303.661.3829
eFax: 303.664.8120
Google+: brian.hedstrom
Skype IM: brian.hedstrom 
b.hedstrom@cablelabs.com=

X-Trac-Version: 0.12.3 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.3, by Edgewall Software To: draft-ietf-eman-framework@tools.ietf.org, jparello@cisco.com X-Trac-Project: eman Date: Wed, 10 Apr 2013 18:32:35 -0000 X-URL: http://tools.ietf.org/eman/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/eman/trac/ticket/29#comment:1 Message-ID: <079.84fb90bbd1a420d9d3560997f313da3d@trac.tools.ietf.org> References: <064.716466cc60ff414a38d13249506e9ab3@trac.tools.ietf.org> X-Trac-Ticket-ID: 29 In-Reply-To: <064.716466cc60ff414a38d13249506e9ab3@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-eman-framework@tools.ietf.org, jparello@cisco.com, eman@ietf.org X-SA-Exim-Mail-From: trac+eman@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: bclaise@cisco.com, bnordman@lbl.gov, brad.schoening@verizon.net, jparello@cisco.com, quittek@netlab.nec.de Resent-Message-Id: <20130410183246.9521E21F8EBD@ietfa.amsl.com> Resent-Date: Wed, 10 Apr 2013 11:32:46 -0700 (PDT) Resent-From: trac+eman@trac.tools.ietf.org Cc: eman@ietf.org Subject: Re: [eman] #29: IANA Considerations section needs more detail X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Apr 2013 18:32:47 -0000 #29: IANA Considerations section needs more detail Comment (by jparello@cisco.com): UML Drawing is in asci and xml in this document. IANA would have a model registered (as xml scmea). We would link to that model in the IANA section. Procedurally Perhaps we need a tmp draft or work with the GUI. Nevil to check how that would work as process. In general sets within a models have sub/registries and can be used by other implementations such as snmp. Lets look at IANA registries and ipfix sub table. In general the power sets registry may be used independent of the eman information model and goal is to make this obvious at IANA. -- -------------------------------------+------------------------------------- Reporter: | Owner: draft-ietf-eman- n.brownlee@auckland.ac.nz | framework@tools.ietf.org Type: defect | Status: new Priority: blocker | Milestone: milestone1 Component: framework | Version: Severity: Active WG Document | Resolution: Keywords: | -------------------------------------+------------------------------------- Ticket URL: eman From B.Hedstrom@CableLabs.com Thu Apr 11 15:11:57 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F15C221F86F7 for ; Thu, 11 Apr 2013 15:11:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.462 X-Spam-Level: X-Spam-Status: No, score=-0.462 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nJRxUfvCsQtG for ; Thu, 11 Apr 2013 15:11:56 -0700 (PDT) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id 5EE8821F898A for ; Thu, 11 Apr 2013 15:11:56 -0700 (PDT) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.5/8.14.5) with ESMTP id r3BMBkte000380; Thu, 11 Apr 2013 16:11:46 -0600 Received: from exchange.cablelabs.com (10.5.0.19) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com); Thu, 11 Apr 2013 16:11:46 -0600 (MDT) X-Virus-Status: clean(F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com) Received: from EXCHANGE.cablelabs.com ([fe80::797a:96d1:3c53:18ee]) by EXCHANGE.cablelabs.com ([fe80::797a:96d1:3c53:18ee%11]) with mapi id 14.02.0328.009; Thu, 11 Apr 2013 16:11:46 -0600 From: Brian Hedstrom To: Bruce Nordman , Nevil Brownlee Thread-Topic: [eman] DRAFT minutes for our Orlando meeting Thread-Index: AQHOH21OILZcx2eL5Uiw7FzXMCxfipixpLIAgCAfkIA= Date: Thu, 11 Apr 2013 22:11:45 +0000 Message-ID: <686B406F73B0F245AB30195F4E80E2D517F3FDF9@EXCHANGE.cablelabs.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.2.130206 x-originating-ip: [10.253.129.203] Content-Type: multipart/alternative; boundary="_000_686B406F73B0F245AB30195F4E80E2D517F3FDF9EXCHANGEcablela_" MIME-Version: 1.0 X-Approved: ondar Cc: "eman@ietf.org" Subject: Re: [eman] DRAFT minutes for our Orlando meeting X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Apr 2013 22:11:58 -0000 --_000_686B406F73B0F245AB30195F4E80E2D517F3FDF9EXCHANGEcablela_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable This definition appears in both the Framework Draft and the Terminology Dra= ft. We should avoid defining terms in multiple locations and keep the formal de= finition in one draft and reference that definition/term in all other draft= s. Energy Management Energy Management is a set of functions for measuring, modeling, planning, and optimizing networks to ensure that the network elements and attached devices use energy efficiently and is appropriate for the nature of the application and the cost constraints of the organization. Reference: Adapted from [ITU-T-M-3400] NOTES: 1. Energy management refers to the activities, methods, procedures and tools that pertain to measuring, modeling, planning, controlling and optimizing the use of energy in networked systems [NMF]. 2. Energy Management is a management domain which is congruent to any of FCAPS areas of management in the ISO/OSI Network Management Model [TMN]. Energy Management for communication networks and attached devices is a subset or part of an organization's greater Energy Management Policies. From: Bruce Nordman > Date: Thursday, March 21, 2013 11:38 PM To: Nevil Brownlee > Cc: "eman@ietf.org" > Subject: Re: [eman] DRAFT minutes for our Orlando meeting Thanks much to Nevil for taking well care of the minutes. A few minor comments. For the framework it is state: . Since this is the I-D that describes "IETF Energy Management," it needs to state a clear definition of Energy Management. There is a definition of Energy Management in the framework draft already so I think this is covered. . This I-D also needs to indicate how it relates to Energy Management standards from other organisation. The Applicability Statement does this, and the Introduction to the framework document notes this. So, I think this also already covered. On the Applicability Statement: - Many changes (see slides), needs more text about ASHRAE 201P =3D Now fairly stable; ready for WGLC once Framework is done Actually we have not had changes, but the rest is correct. It has been nine days since Nevil posted the minutes. I think early next week would be a suitable time for he and myself to finalize the minutes, so if there are any other comments, please post them ASAP. Thanks, --Bruce On Tue, Mar 12, 2013 at 3:02 PM, Nevil Brownlee > wrote: Hi all: Here are my draft minutes, please read them and send me any comments or corrections. My one-para summary of the meeting is: The Entity MIBv4 and EMAN Requirements are (nearly) completed. The meeting focused on the EMAN Framework; in particular we explored the question "should we develop the EMAN Information Model using UML, so that it can be used by other organisations such as SCTE." That question will be discussed further on the EMAN list. Meanwhile the EMAN Framework authors will continue their work on that I-D; our Milestone for it is 'April 2013." Cheers, Nevil -- --------------------------------------------------------------------- Nevil Brownlee Computer Science Department | ITS Phone: +64 9 373 7599 x88941 = The University of Auckland FAX: +64 9 373 7453 Private Bag 92019, Auckl= and 1142, New Zealand _______________________________________________ eman mailing list eman@ietf.org https://www.ietf.org/mailman/listinfo/eman -- Bruce Nordman Lawrence Berkeley National Laboratory nordman.lbl.gov BNordman@LBL.gov 510-486-7089 m: 510-501-7943 --_000_686B406F73B0F245AB30195F4E80E2D517F3FDF9EXCHANGEcablela_ Content-Type: text/html; charset="us-ascii" Content-ID: <901EBF8A62A9BE4FB4FCC0FC26A6DA95@cablelabs.com> Content-Transfer-Encoding: quoted-printable

This definition appears in both the =
Framework Draft and the Terminology Draft.
We should avoid defining terms in mu=
ltiple locations and keep the formal definition in one draft and reference =
that definition/term in all other drafts.



       Energy Management
    =20
          Energy Management is a set of functions for
          measuring, modeling, planning, and optimizing
          networks to ensure that the network elements and
          attached devices use energy efficiently and is   =20
 =
          appropriate for the nature=
 of the application and
          the cost constraints of the organization.
          Reference: Adapted from [ITU-T-M-3400]
          NOTES:
          1. Energy management refers to the activities,
            methods, procedures and tools that pertain to
            measuring, modeling, planning, controlling and
            optimizing the use of energy in networked
            systems [NMF].
          2. Energy Management is a management domain which
            is congruent to any of FCAPS areas of
            management in the ISO/OSI Network Management
            Model [TMN]. Energy Management for
            communication networks and attached devices is
            a subset or part of an organization's greater 
          &n= bsp; Energy Management Policies.&n= bsp;



From: Bruce Nordman <bnordman@lbl.gov>
Date: Thursday, March 21, 2013 11:3= 8 PM
To: Nevil Brownlee <n.brownlee@auckland.ac.nz>
Cc: "eman@ietf.org" <eman@i= etf.org>
Subject: Re: [eman] DRAFT minutes f= or our Orlando meeting

Thanks much to Nevil for taking well care of the minutes.

A few minor comments.  For the framework it is state:
  . Since this is the I-D that describes "IETF Energy Management,=
"
    it needs to state a clear definition of Energy Management.

There is a def= inition of Energy Management in the framework
draft already = so I think this is covered.

 . This= I-D also needs to indicate how it relates to Energy Management standards from other organisation.
The Applicability Statement does this, and the Introduction to the
framework document notes this.  So, I think this also already covered.=

On the Applicability Statement:

- Many changes (see slides), needs more text about ASHRAE 201P
=3D Now fairly stable; ready for WGLC once Framework is done
Actually we have not had changes, but the rest is correct.

It has been nine days since Nevil posted the minutes.
I think early next week would be a suitable time for he
and myself to finalize the minutes, so if there are any
other comments, please post them ASAP.
Thanks,

--Bruce

On Tue, Mar 12, 2013 at 3:02 PM, Nevil Brownlee = <n.brownl= ee@auckland.ac.nz> wrote:

Hi all:

Here are my draft minutes, please read them and send me any comments or
corrections.

My one-para summary of the meeting is:

The Entity MIBv4 and EMAN Requirements are (nearly) completed.  The meeting focused on the EMAN Framework; in particular we explored the
question "should we develop the EMAN Information Model using UML, so that it can be used by other organisations such as SCTE."  That question will be discussed further on the EMAN list.  Meanwhile the EMAN Framework authors will continue their work on that I-D; our
Milestone for it is 'April 2013."

Cheers, Nevil

--
-------------------------------------------------------------= --------
 Nevil Brownlee                = ;    Computer Science Department | ITS
 Phone: +64 9 373 7599 x88941             The= University of Auckland
 FAX: +64 9 373 7453   Private Bag 92019, Aucklan= d 1142, New Zealand


_______________________________________________
eman mailing list
eman@ietf.org
ht= tps://www.ietf.org/mailman/listinfo/eman




--
Bruce Nordman
Lawrence Berkeley National Laboratory
nordman.lbl.gov
BNordman@LBL.gov
510-486-7089
m: 510-501-7943
--_000_686B406F73B0F245AB30195F4E80E2D517F3FDF9EXCHANGEcablela_-- From bnordman@lbl.gov Wed Apr 17 14:49:24 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2184321F8CEE for ; Wed, 17 Apr 2013 14:49:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.976 X-Spam-Level: X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u3QrvhSyPcCO for ; Wed, 17 Apr 2013 14:49:23 -0700 (PDT) Received: from fe1.lbl.gov (fe1.lbl.gov [128.3.41.133]) by ietfa.amsl.com (Postfix) with ESMTP id 87A5521F8C08 for ; Wed, 17 Apr 2013 14:49:23 -0700 (PDT) X-Ironport-SBRS: 2.2 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvQCAC4Yb1HRVaHFemdsb2JhbABNA4JCeq5fAYkyiTYIFg4BAQkLDAgUBCSDPgddEgEFASITCIgMnCiCcp45jzKDNQOJBo4AgSOIXQSFLhYphE4c X-IronPort-AV: E=Sophos;i="4.87,496,1363158000"; d="scan'208";a="15133071" Received: from mail-gg0-f197.google.com ([209.85.161.197]) by fe1.lbl.gov with ESMTP; 17 Apr 2013 14:49:22 -0700 Received: by mail-gg0-f197.google.com with SMTP id k5so2839109ggn.8 for ; Wed, 17 Apr 2013 14:49:22 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=rGnLGfwQhLZRC4+mHviAWDuUDDwuOC8LS+SQE57Ta0c=; b=Sq0vkaCD7hRG8dHFn1qD2zdX3bqGjkR3MWRWUGwn5kjkaTpXAgC8yqr5rWZa4TIkXg GSux1niT8Qpiq5k+d44hXvdeJMKvriXBwfunZ5TEu7uyrBnWU8IsEbkRr++Bgb/ES0Lj QMOHs9rHS+AovjcNiqQ80PhBGoSdoNQ3ZX2UvRbv0No+aRbnrZbcjJ2QYpZoWPpc9+yC rx+UYALO/ty7jB5PV/R4vP3Cg3gMR16CxRsQzzLNOnlHqkIlrfM4aDz/JPXmzeLCPPnD p/tzEfxcsOh8i1p2dV4IFKYVDvQ8gJeVA0cNdPOQf7spqqEueqgT0XYlekYEFxmqVtK5 Ljcg== X-Received: by 10.52.34.140 with SMTP id z12mr5295258vdi.106.1366235362310; Wed, 17 Apr 2013 14:49:22 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.52.34.140 with SMTP id z12mr5295251vdi.106.1366235362080; Wed, 17 Apr 2013 14:49:22 -0700 (PDT) Received: by 10.220.124.10 with HTTP; Wed, 17 Apr 2013 14:49:22 -0700 (PDT) Date: Wed, 17 Apr 2013 14:49:22 -0700 Message-ID: From: Bruce Nordman To: eman mailing list Content-Type: multipart/alternative; boundary=20cf3079bf966fca5204da9575e9 X-Gm-Message-State: ALoCoQnoL6S+/mxBXDpo7uTEGNB+O6i+NgOyAJt51BF5nV0PdiaahThGLrL17yYjmg4u2t05ZG58zdeXF0XAGbJQG7fyJfbV9VHPNMLcM2kX5hl8/aGoZcu+94zBGxmUPpN+dlpvoFZQ Subject: [eman] CEA energy reporting project X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Apr 2013 21:49:24 -0000 --20cf3079bf966fca5204da9575e9 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Today the Consumer Electronics Association announced a new standards development effort: CEA=92s R7.8 Modular Communications Interface for Energy Management Subcommittee is developing a standard to enable consumer electronic devices to communicate their energy usage information for example over a home network as well as optionally respond to basic demand/response commands. The standard will enable mapping to and from the NAESB/PAP10 EUI model (North American Energy Standards Board) as well as utilize ANSI/CEA-2045 Modular Communications Interface for Energy Management messaging where possible. I will monitor developments in this process and fill them in on EMAN details. For some purposes CEA is a U.S. trade association, but many of the standards activities are global. --Bruce --=20 *Bruce Nordman* Lawrence Berkeley National Laboratory *nordman.lbl.gov* BNordman@LBL.gov 510-486-7089 m: 510-501-7943 --20cf3079bf966fca5204da9575e9 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
Today the Consumer Electronics Association = announced a new
standards development effort:

CEA=92s R7.8 Modular Communications Interface for Energy Management=20 Subcommittee is developing a standard to enable consumer electronic=20 devices to communicate their energy usage information for example over a home network as well as optionally respond to basic demand/response=20 commands. The standard will enable mapping to and from the NAESB/PAP10=20 EUI model (North American Energy Standards Board) as well as utilize=20 ANSI/CEA-2045 Modular Communications Interface for Energy Management=20 messaging where possible.
<= span style=3D"font-family:"Arial","sans-serif"">=
=
I will monitor developments in this process and fill them in on
<= /span>
EMAN details.=A0 For some purposes CEA is a U.S. trade association, but many of the standards activities are global.

--Bruce
<= /span>


--
= Bruce Nordman
Lawrence Berkeley National Laboratory
nordman.lbl.gov
BNordman@LBL.gov<= br>510-486-7089
m: 510-501-7943
--20cf3079bf966fca5204da9575e9-- From internet-drafts@ietf.org Thu Apr 18 23:32:37 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEFD021F926E; Thu, 18 Apr 2013 23:32:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.6 X-Spam-Level: X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d1phfrGHgPpc; Thu, 18 Apr 2013 23:32:37 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8971E21F8859; Thu, 18 Apr 2013 23:32:37 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.44.p3 Message-ID: <20130419063237.5210.26607.idtracker@ietfa.amsl.com> Date: Thu, 18 Apr 2013 23:32:37 -0700 Cc: eman@ietf.org Subject: [eman] I-D Action: draft-ietf-eman-applicability-statement-03.txt X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Apr 2013 06:32:38 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Energy Management Working Group of the IE= TF. Title : Energy Management (EMAN) Applicability Statement Author(s) : Brad Schoening Mouli Chandramouli Bruce Nordman Filename : draft-ietf-eman-applicability-statement-03.txt Pages : 30 Date : 2013-04-18 Abstract: The objective of Energy Management (EMAN) is to provide an energy management framework for networked devices. This document presents the applicability of the EMAN framework to a variety of scenarios. This document lists use cases and target devices that can potentially implement the EMAN framework and associated SNMP MIB modules. These use cases are useful for identifying requirements for the framework and MIBs. Further, we describe the relationship of the EMAN framework to relevant other energy monitoring standards and architectures. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-eman-applicability-statement There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-eman-applicability-statement-03 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eman-applicability-statement-= 03 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From moulchan@cisco.com Thu Apr 18 23:38:11 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0695E21F919D for ; Thu, 18 Apr 2013 23:38:11 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7AgsMjy4JzQW for ; Thu, 18 Apr 2013 23:38:10 -0700 (PDT) Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 57FCF21F9079 for ; Thu, 18 Apr 2013 23:38:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2373; q=dns/txt; s=iport; t=1366353490; x=1367563090; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=HCIsfrz/fOolnKCX7uu/b02stjxWuc+l8ty1XXvt2bQ=; b=QmjcG5HY+n7nAn7y0O88ffY9991rKTbk1yFRFv+9m+1hcSVpR5iT66Bp KEoqOtqIc8u0pueDrPW38PFaVZWdaByRMQeJk42kLBEMowKKTRL6zi/mC h1AortkRCsjpzjYLkhQSCZELNZ+DTNUSFl/u5NtRtldz5ifdWV4MM8zba 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhwFAKPlcFGtJV2Z/2dsb2JhbABQgwY2RMAegQgWdIIhAQQBAQE3NAQZAQgiFDcLJQIEEwgBiAsHBZw3oTqOZQI4gmZhA5gqj3GDC4Io X-IronPort-AV: E=Sophos;i="4.87,507,1363132800"; d="scan'208";a="200664023" Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-4.cisco.com with ESMTP; 19 Apr 2013 06:38:09 +0000 Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r3J6c9hd017866 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Fri, 19 Apr 2013 06:38:09 GMT Received: from xmb-rcd-x08.cisco.com ([169.254.8.173]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.02.0318.004; Fri, 19 Apr 2013 01:38:08 -0500 From: "Mouli Chandramouli (moulchan)" To: "eman@ietf.org" Thread-Topic: [eman] I-D Action: draft-ietf-eman-applicability-statement-03.txt Thread-Index: AQHOPMfFL+TN2iV/J0GYEdPL699mXpjdx1sA Date: Fri, 19 Apr 2013 06:38:08 +0000 Message-ID: <852AF0ED49D9F24BBBFA1B4DEEBE3BA4286FE257@xmb-rcd-x08.cisco.com> In-Reply-To: <20130419063237.5210.26607.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.2.130206 x-originating-ip: [10.142.100.91] Content-Type: text/plain; charset="us-ascii" Content-ID: <960FEC70158DF04E9F92433180EAD2E8@emea.cisco.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [eman] I-D Action: draft-ietf-eman-applicability-statement-03.txt X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Apr 2013 06:38:11 -0000 An updated version of the draft has been submitted. Thanks for the comments from Brian Hedstorm. The open issue on ASHRAE has been closed; the draft contains a section with a synopsis on ASHRAE standards and its relationship to EMAN. If there is any other aspects that should be considered, we welcome feedback from the WG. As discussed in the WG, the Applicability Statement draft would be finalised after the Framework and MIB drafts are baselined. Thanks Brad, Bruce and Mouli On 19/04/13 12:02 PM, "internet-drafts@ietf.org" wrote: > >A New Internet-Draft is available from the on-line Internet-Drafts >directories. > This draft is a work item of the Energy Management Working Group of the >IETF. > > Title : Energy Management (EMAN) Applicability Statement > Author(s) : Brad Schoening > Mouli Chandramouli > Bruce Nordman > Filename : draft-ietf-eman-applicability-statement-03.txt > Pages : 30 > Date : 2013-04-18 > >Abstract: > The objective of Energy Management (EMAN) is to provide an > energy management framework for networked devices. This > document presents the applicability of the EMAN framework to a > variety of scenarios. This document lists use cases and target > devices that can potentially implement the EMAN framework and > associated SNMP MIB modules. These use cases are useful for > identifying requirements for the framework and MIBs. Further, > we describe the relationship of the EMAN framework to relevant > other energy monitoring standards and architectures. > > > >The IETF datatracker status page for this draft is: >https://datatracker.ietf.org/doc/draft-ietf-eman-applicability-statement > >There's also a htmlized version available at: >http://tools.ietf.org/html/draft-ietf-eman-applicability-statement-03 > >A diff from the previous version is available at: >http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eman-applicability-statement= -0 >3 > > >Internet-Drafts are also available by anonymous FTP at: >ftp://ftp.ietf.org/internet-drafts/ > >_______________________________________________ >eman mailing list >eman@ietf.org >https://www.ietf.org/mailman/listinfo/eman From internet-drafts@ietf.org Fri Apr 19 04:13:39 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 311CE21F8F25; Fri, 19 Apr 2013 04:13:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.477 X-Spam-Level: X-Spam-Status: No, score=-102.477 tagged_above=-999 required=5 tests=[AWL=0.123, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E-sgrndQzAMS; Fri, 19 Apr 2013 04:13:38 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A639321F8BC5; Fri, 19 Apr 2013 04:13:38 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.44.p3 Message-ID: <20130419111338.3215.30773.idtracker@ietfa.amsl.com> Date: Fri, 19 Apr 2013 04:13:38 -0700 Cc: eman@ietf.org Subject: [eman] I-D Action: draft-ietf-eman-energy-aware-mib-08.txt X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Apr 2013 11:13:39 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Energy Management Working Group of the IE= TF. Title : Energy Object Context MIB Author(s) : John Parello Benoit Claise Mouli Chandramouli Filename : draft-ietf-eman-energy-aware-mib-08.txt Pages : 34 Date : 2013-04-19 Abstract: This document defines a subset of a Management Information Base (MIB) for energy management of devices. The module addresses device identification, context information, and the relationships between reporting devices, remote devices, and monitoring devices. = The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-eman-energy-aware-mib There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-eman-energy-aware-mib-08 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eman-energy-aware-mib-08 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From moulchan@cisco.com Fri Apr 19 04:23:16 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E57D721F955A for ; Fri, 19 Apr 2013 04:23:16 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zzV-cmtTUh1A for ; Fri, 19 Apr 2013 04:23:15 -0700 (PDT) Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 5286721F94AF for ; Fri, 19 Apr 2013 04:23:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2101; q=dns/txt; s=iport; t=1366370595; x=1367580195; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=NIO74YLyUFyOcNZzFaXbX9X4SOqkTgf7cs8oyH80ccA=; b=jTFsxncaxBYDDx6+SnMBgJ73f5wb2VeG+bi/Qu1U4wlU6SI40ytdZwNk l8/Oq1IRfEoQs0Makh0VXrxhT3FKK1goSnBpr6WFdZNWKq0pjOyG/qeou JCv+5V3sFzDMnPb/7cp6Y3jxGwW+rFoQDL6MWCZQRFndM2NDqi52ub205 w=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhwFALkocVGtJV2c/2dsb2JhbABQgwY2RMAegQYWdIIhAQQBAQE3NAQZAQgiFDcLJQIEEwgBiAsHBZt6oTSOZziCZmEDmCqPcYMLgig X-IronPort-AV: E=Sophos;i="4.87,508,1363132800"; d="scan'208";a="200651842" Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-7.cisco.com with ESMTP; 19 Apr 2013 11:23:02 +0000 Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r3JBN2Q4015894 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Fri, 19 Apr 2013 11:23:02 GMT Received: from xmb-rcd-x08.cisco.com ([169.254.8.173]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.02.0318.004; Fri, 19 Apr 2013 06:23:02 -0500 From: "Mouli Chandramouli (moulchan)" To: "eman@ietf.org" Thread-Topic: [eman] I-D Action: draft-ietf-eman-energy-aware-mib-08.txt Thread-Index: AQHOPO8KNMSTFDPH3kuPqwynWqwVnJjeFqeA Date: Fri, 19 Apr 2013 11:23:02 +0000 Message-ID: <852AF0ED49D9F24BBBFA1B4DEEBE3BA4286FE648@xmb-rcd-x08.cisco.com> In-Reply-To: <20130419111338.3215.30773.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.2.130206 x-originating-ip: [10.142.100.91] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [eman] I-D Action: draft-ietf-eman-energy-aware-mib-08.txt X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Apr 2013 11:23:17 -0000 Hello all,=20 An updated version of the draft has been submitted. The OID tree of the MIB has been revised and updated. Thanks to the comments of Brian Hedstorm and Alan Luchuk. Regarding the question of eoRelationID and eoProxID as read-only objects; since they are UUID and the relationship are defined by the bitmap eoRelationship, which is a read-write object to indicate relationship between energy objects. An open issue has been added to possibly to have two smaller groups of objects as optional for implementation. Please provide your feedback. Thanks John, Benoit and Mouli On 19/04/13 4:43 PM, "internet-drafts@ietf.org" wrote: > >A New Internet-Draft is available from the on-line Internet-Drafts >directories. > This draft is a work item of the Energy Management Working Group of the >IETF. > > Title : Energy Object Context MIB > Author(s) : John Parello > Benoit Claise > Mouli Chandramouli > Filename : draft-ietf-eman-energy-aware-mib-08.txt > Pages : 34 > Date : 2013-04-19 > >Abstract: > This document defines a subset of a Management Information Base > (MIB) for energy management of devices. The module addresses > device identification, context information, and the > relationships between reporting devices, remote devices, and > monitoring devices. > > =20 > >The IETF datatracker status page for this draft is: >https://datatracker.ietf.org/doc/draft-ietf-eman-energy-aware-mib > >There's also a htmlized version available at: >http://tools.ietf.org/html/draft-ietf-eman-energy-aware-mib-08 > >A diff from the previous version is available at: >http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eman-energy-aware-mib-08 > > >Internet-Drafts are also available by anonymous FTP at: >ftp://ftp.ietf.org/internet-drafts/ > >_______________________________________________ >eman mailing list >eman@ietf.org >https://www.ietf.org/mailman/listinfo/eman From internet-drafts@ietf.org Mon Apr 22 06:46:22 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B941A21F902B; Mon, 22 Apr 2013 06:46:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.507 X-Spam-Level: X-Spam-Status: No, score=-102.507 tagged_above=-999 required=5 tests=[AWL=0.093, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ap5lQfDZzztb; Mon, 22 Apr 2013 06:46:22 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4572721F8FE5; Mon, 22 Apr 2013 06:46:22 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.44.p3 Message-ID: <20130422134622.7863.4899.idtracker@ietfa.amsl.com> Date: Mon, 22 Apr 2013 06:46:22 -0700 Cc: eman@ietf.org Subject: [eman] I-D Action: draft-ietf-eman-energy-monitoring-mib-05.txt X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Apr 2013 13:46:22 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Energy Management Working Group of the IE= TF. Title : Power and Energy Monitoring MIB Author(s) : Mouli Chandramouli Brad Schoening Juergen Quittek Thomas Dietz Benoit Claise Filename : draft-ietf-eman-energy-monitoring-mib-05.txt Pages : 82 Date : 2013-04-22 Abstract: This document defines a subset of the Management Information Base (MIB) for power and energy monitoring of devices. = The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mib There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-eman-energy-monitoring-mib-05 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eman-energy-monitoring-mib-05 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From moulchan@cisco.com Mon Apr 22 10:39:59 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B368721F930B for ; Mon, 22 Apr 2013 10:39:59 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IfGYtfnI+ahg for ; Mon, 22 Apr 2013 10:39:59 -0700 (PDT) Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id E1FCB21F92FC for ; Mon, 22 Apr 2013 10:39:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2150; q=dns/txt; s=iport; t=1366652399; x=1367861999; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=cPQWCfmpeujeDF1mlpXTMs+l+Md/zSXPw5Rxm9IERcg=; b=IB5wB9/wGyfmuqV4pEl3vHZ/2gEF1oBBEKdG5zfzr2U/8953JlHBf4pN mhcEIX4+6o+00FixPkfbyzlxDgyzmXa4jQZzl+EvRtXzoyL2dSOC+MWPn MLxze9DKB8bgeHjOtfPO1ZwU187mZIODb1Z2UecsGe5SyLhY2WHVyzyJd g=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ai0FAJd1dVGtJXG8/2dsb2JhbABPgwY2RMA9gQYWdIIhAQQBAQE3NB0BCCIUNwslAgQTCAGICwcFm2WfZ44OfgI4gmZhA5g4j3eDDIIo X-IronPort-AV: E=Sophos;i="4.87,528,1363132800"; d="scan'208";a="201409842" Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-1.cisco.com with ESMTP; 22 Apr 2013 17:39:53 +0000 Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r3MHdrjG022593 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Mon, 22 Apr 2013 17:39:53 GMT Received: from xmb-rcd-x08.cisco.com ([169.254.8.173]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.02.0318.004; Mon, 22 Apr 2013 12:39:52 -0500 From: "Mouli Chandramouli (moulchan)" To: "eman@ietf.org" Thread-Topic: [eman] I-D Action: draft-ietf-eman-energy-monitoring-mib-05.txt Thread-Index: AQHOP1/iYrkqWij5t0KPFSvyrNXdy5jjMgwA Date: Mon, 22 Apr 2013 17:39:52 +0000 Message-ID: <852AF0ED49D9F24BBBFA1B4DEEBE3BA4286FF840@xmb-rcd-x08.cisco.com> In-Reply-To: <20130422134622.7863.4899.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.2.130206 x-originating-ip: [10.65.35.141] Content-Type: text/plain; charset="us-ascii" Content-ID: <01CA9232B3C6694AB7BCD9E2C37026B9@emea.cisco.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [eman] I-D Action: draft-ietf-eman-energy-monitoring-mib-05.txt X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Apr 2013 17:39:59 -0000 Hello all, An updated version of the Energy Monitoring MIB draft has been submitted. Many thanks to the diligent reviews of Alan Luchuk and Brian Hedstorm. - All the editorial comments are incorporated. - The UML and OID tree are updated - Power Attributes is used instead of Power Characteristics - eoEnergyParametersTable has been revised with indices eoEnergyObjectIndex and eoEnergyParametersIndex - Open issues which need discussion from the WG are listed We hope to address some of the open issues before the next IETF. Once the requirements and Framework are baselined, the Monitoring MIB draft can be finalised. Thanks very much Brad, Juergen, Thomas, Benoit and Mouli On 22/04/13 7:16 PM, "internet-drafts@ietf.org" wrote: > >A New Internet-Draft is available from the on-line Internet-Drafts >directories. > This draft is a work item of the Energy Management Working Group of the >IETF. > > Title : Power and Energy Monitoring MIB > Author(s) : Mouli Chandramouli > Brad Schoening > Juergen Quittek > Thomas Dietz > Benoit Claise > Filename : draft-ietf-eman-energy-monitoring-mib-05.txt > Pages : 82 > Date : 2013-04-22 > >Abstract: > This document defines a subset of the Management Information > Base (MIB) for power and energy monitoring of devices. > > =20 > >The IETF datatracker status page for this draft is: >https://datatracker.ietf.org/doc/draft-ietf-eman-energy-monitoring-mib > >There's also a htmlized version available at: >http://tools.ietf.org/html/draft-ietf-eman-energy-monitoring-mib-05 > >A diff from the previous version is available at: >http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eman-energy-monitoring-mib-0= 5 > > >Internet-Drafts are also available by anonymous FTP at: >ftp://ftp.ietf.org/internet-drafts/ > >_______________________________________________ >eman mailing list >eman@ietf.org >https://www.ietf.org/mailman/listinfo/eman From bnordman@lbl.gov Wed Apr 24 11:36:01 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 195AA21F89B2 for ; Wed, 24 Apr 2013 11:36:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.976 X-Spam-Level: X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hF42P7fHKSGH for ; Wed, 24 Apr 2013 11:36:00 -0700 (PDT) Received: from fe1.lbl.gov (fe1.lbl.gov [128.3.41.133]) by ietfa.amsl.com (Postfix) with ESMTP id 28BEF21F8624 for ; Wed, 24 Apr 2013 11:36:00 -0700 (PDT) X-Ironport-SBRS: 2.2 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AlwEADwleFHRVdRGemdsb2JhbABNA4JCeqx9AYkyAYg0eAgWDgEBCQsMCBQEJIM+B10SAQUBIhMIiAyeI4JynR6Nfw+BEiiDOgOJEI4MgSWOFhYphFQc X-IronPort-AV: E=Sophos;i="4.87,545,1363158000"; d="scan'208";a="15770735" Received: from mail-vb0-f70.google.com ([209.85.212.70]) by fe1.lbl.gov with ESMTP; 24 Apr 2013 11:35:55 -0700 Received: by mail-vb0-f70.google.com with SMTP id 11so3747612vbf.1 for ; Wed, 24 Apr 2013 11:35:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=Ds+8GDpen1PPy2GG/r4ouWqSFSuUJCFbDIxUJaVmyrQ=; b=pHtUyTwYJszpGEEswStHVxeuOrojSpWviOCP298KlnigD8cciFi2HGs04DTZb512Db ye6gK38gD89mlN7HeRPqBQKrQM4KWyh1Rm1OBHE4DkRgxZQQekib7dYqA+A67mwhaz2O wCaK5dzmQfB+rZvumwROUwezD5aRKYB2895AOdMLfsVJ9YCOdgmn3odo0a2bVYlovc3g M9eZSO4PJo9VK8IGUdntAF27CmPuX7HGVwugCXa3r0xZL+1cE1LEoFjdd0wnXNJJUW5E 03YA1+CS7/AzyY9ow+3dh4PRrSItfhA2z7YXwlsGutJXmPi7QwF+gngSX0HrwK3FkxzB t6VQ== X-Received: by 10.52.157.194 with SMTP id wo2mr21851510vdb.30.1366828553882; Wed, 24 Apr 2013 11:35:53 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.52.157.194 with SMTP id wo2mr21851501vdb.30.1366828553705; Wed, 24 Apr 2013 11:35:53 -0700 (PDT) Received: by 10.220.124.10 with HTTP; Wed, 24 Apr 2013 11:35:53 -0700 (PDT) Date: Wed, 24 Apr 2013 11:35:53 -0700 Message-ID: From: Bruce Nordman To: eman mailing list Content-Type: multipart/alternative; boundary=089e016338c069a6d804db1f9208 X-Gm-Message-State: ALoCoQlY+FNuS4G81nNfYzifNP1p/TgsbcKzX3RyfkX9Vgk72gnULGKEKpSW3n8zl8hx+4g2NeeU881i/abS405J/1FAzfTkL7eiPctYQtH1/leWZCD9TYZ8VaWvmvlIQCAAwmqxR5HL Subject: [eman] Nominal/Nameplate values X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 18:36:01 -0000 --089e016338c069a6d804db1f9208 Content-Type: text/plain; charset=ISO-8859-1 In discussions with Brad and Nevil, we noted that the requirements draft says: 5.2.8. Nominal Voltage Range The standard must provide means for reporting the nominal voltage range for each Power Interface. 5.2.9. Nominal AC Frequency The standard must provide means for reporting the nominal AC frequency for each Power Interface. In Orlando we discussed adding a URI where lots of useful static information about a brand/model of device could be posted, including this. It seems elegant to remove the above two requirements and replace it with one saying something like: The standard must provide means for reporting a URI that links to static data about a device. This information would be for the entire device, whereas the existing requirements are for each power interface. I realize that the standard is in IESG review so that this would require some extra effort but it would simplify the MIB and provide extra capability. --Bruce -- *Bruce Nordman* Lawrence Berkeley National Laboratory *nordman.lbl.gov* BNordman@LBL.gov 510-486-7089 m: 510-501-7943 --089e016338c069a6d804db1f9208 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
In discussions with Brad and Nevil, we noted tha= t the requirements draft says:

=09 =09 =09 =09 =09
5.2.=
8.  Nominal Voltage Range
   T=
he standard must provide means for reporting the nominal voltage
   range for each Power Interface.
5.2.=
9.  Nominal AC Frequency
   T=
he standard must provide means for reporting the nominal AC
   frequency for each Power Interface.
=09 In Orlando we discussed adding a URI where lots of useful static informatio= n
about a brand/model of device could be posted, including this.

=
It seems elegant to remove the above two requirements and replace it = with
one saying something like:
   The standard must provide means for reporting =
a URI that links to
static data about a device.
This information would be for the entire device, whereas the exis= ting requirements
are for each power interface.

I real= ize that the standard is in IESG review so that this would require some
extra effort but it would simplify the MIB and provide extra cap= ability.

--Bruce


--
Bruce Nordman
Lawrence Berkeley National Laboratory
nordman.lbl.gov
BNordman@LBL.gov
510-4= 86-7089
m: 510-501-7943
--089e016338c069a6d804db1f9208-- From bnordman@lbl.gov Wed Apr 24 14:00:42 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0E3121F8BE8 for ; Wed, 24 Apr 2013 14:00:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.976 X-Spam-Level: X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vYMisHdzT7u2 for ; Wed, 24 Apr 2013 14:00:42 -0700 (PDT) Received: from fe2.lbl.gov (fe2.lbl.gov [128.3.41.134]) by ietfa.amsl.com (Postfix) with ESMTP id 33D3521F8A6B for ; Wed, 24 Apr 2013 14:00:42 -0700 (PDT) X-Ironport-SBRS: 2.2 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AlsEAMlGeFHRVaDFemdsb2JhbABOA4JCeqxEAYkyAYg0eggWDgEBCQsMCBQEJIM+B10SAQUBIhOIFJ45gnKdDY1/gSEogzoDiRCODIEljhYWKYRUHA X-IronPort-AV: E=Sophos;i="4.87,545,1363158000"; d="scan'208";a="17451636" Received: from mail-gh0-f197.google.com ([209.85.160.197]) by fe2.lbl.gov with ESMTP; 24 Apr 2013 14:00:41 -0700 Received: by mail-gh0-f197.google.com with SMTP id r17so3637697ghr.8 for ; Wed, 24 Apr 2013 14:00:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=2HTu674p93i9+KyeiOUUkIeNgISSqcB3SM0rYFrKc9o=; b=aX1IDRTU89Fbw0eCdVK3GkRae0ucV5z66Bp2UdDkDqAMdkCBRjD2g8zpZZAcLNvUmg 3OszAohZql0yiDcQzta8AwEoKk0cPuVw8n1gUJv+VP7pfMKFyNBJhlwTUhhvFflPBPwb Z2/4abJZSyDmoBFfY0hr/zW1Pb7cREEmsqt4bircLUggPZoNSkR96LtblBCOg+l8ktAL P03rCrhq0OH66tjd/Tlc+mqoqSnoK+QZqbAbdnkmZUPjG/IcitdIUerLbDJSWexKw2am gJMnSnFF0qGIbfo3+vKO7TOxEbC1FSVlM1DzUhFpmLAkJoNOEpYLLFwH/tOTK466wzLX aTqg== X-Received: by 10.52.94.227 with SMTP id df3mr4582021vdb.48.1366837241278; Wed, 24 Apr 2013 14:00:41 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.52.94.227 with SMTP id df3mr4582019vdb.48.1366837241160; Wed, 24 Apr 2013 14:00:41 -0700 (PDT) Received: by 10.220.124.10 with HTTP; Wed, 24 Apr 2013 14:00:41 -0700 (PDT) Date: Wed, 24 Apr 2013 14:00:41 -0700 Message-ID: From: Bruce Nordman To: eman mailing list Content-Type: multipart/alternative; boundary=20cf307d048e39d6a904db219815 X-Gm-Message-State: ALoCoQknXlyu4WldJ90sAkGDB2COQGXb3sUhI0ZQTR6byQLW91X1sH9A5Pm6rRXnMNbJl5c7qLJyOxQamotcvAYzAUowmMbYZQksC0Qo8B7nULl0sLr9nQDQZqSXo1bHFZoP7N4j75z3 Subject: [eman] AC vs DC and # of phases X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Apr 2013 21:00:42 -0000 --20cf307d048e39d6a904db219815 Content-Type: text/plain; charset=ISO-8859-1 There are two requirements that are related: 5.2.7. Type Of current The standard must provide means for reporting the type of current (AC or DC) for each Power Interface as well as for a device. 5.2.10. Number Of AC Phases The standard must provide means for reporting the number of AC phases for each Power Interface. The first is presumably only AC or DC and the second 1-phase or 3-phase. It seems for implementation purposes these could be combined into a single value of DC, 1-phase AC, 3-phase AC delta, or 3-phase AC wye. I assume the framework could specify this and be consistent with the two requirements. --Bruce -- *Bruce Nordman* Lawrence Berkeley National Laboratory *nordman.lbl.gov* BNordman@LBL.gov 510-486-7089 m: 510-501-7943 --20cf307d048e39d6a904db219815 Content-Type: text/html; charset=ISO-8859-1
There are two requirements that are related:

5.2.7.  Type Of current
   The standard must provide means for reporting the type of current (AC
   or DC) for each Power Interface as well as for a device.
5.2.10.  Number Of AC Phases
   The standard must provide means for reporting the number of AC phases
   for each Power Interface.
The first is presumably only AC or DC and the second 1-phase or 3-phase.
It seems for implementation purposes these could be combined into a
single value of DC, 1-phase AC, 3-phase AC delta, or 3-phase AC wye.
I assume the framework could specify this and be consistent with the
two requirements.

--Bruce




--
Bruce Nordman
Lawrence Berkeley National Laboratory
nordman.lbl.gov
BNordman@LBL.gov
510-486-7089
m: 510-501-7943
--20cf307d048e39d6a904db219815-- From johnsonhammond2@hushmail.com Sat Apr 27 10:02:45 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FFBC21F9844 for ; Sat, 27 Apr 2013 10:02:45 -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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ADg-y8rn5QF7 for ; Sat, 27 Apr 2013 10:02:45 -0700 (PDT) Received: from smtp2.hushmail.com (smtp2a.hushmail.com [65.39.178.237]) by ietfa.amsl.com (Postfix) with ESMTP id D9AE221F983B for ; Sat, 27 Apr 2013 10:02:44 -0700 (PDT) Received: from smtp2.hushmail.com (smtp2a.hushmail.com [65.39.178.237]) by smtp2.hushmail.com (Postfix) with SMTP id 8FAC5E7C07 for ; Sat, 27 Apr 2013 17:02:44 +0000 (UTC) Received: from smtp.hushmail.com (w8.hushmail.com [65.39.178.52]) by smtp2.hushmail.com (Postfix) with ESMTP for ; Sat, 27 Apr 2013 17:02:44 +0000 (UTC) Received: by smtp.hushmail.com (Postfix, from userid 99) id 3918314DBDE; Sat, 27 Apr 2013 17:02:44 +0000 (UTC) MIME-Version: 1.0 Date: Sat, 27 Apr 2013 13:02:44 -0400 To: eman@ietf.org From: johnsonhammond2@hushmail.com Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="UTF-8" Message-Id: <20130427170244.3918314DBDE@smtp.hushmail.com> Subject: [eman] Biggest Fake Conference in Computer Science X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Apr 2013 18:45:54 -0000 Biggest Fake Conference in Computer Science We are researchers from different parts of the world and conducted a study on the world’s biggest bogus computer science conference WORLDCOMP ( http://sites.google.com/site/worlddump1 ) organized by Prof. Hamid Arabnia from University of Georgia, USA. We submitted a fake paper to WORLDCOMP 2011 and again (the same paper with a modified title) to WORLDCOMP 2012. This paper had numerous fundamental mistakes. Sample statements from that paper include: (1). Binary logic is fuzzy logic and vice versa (2). Pascal developed fuzzy logic (3). Object oriented languages do not exhibit any polymorphism or inheritance (4). TCP and IP are synonyms and are part of OSI model (5). Distributed systems deal with only one computer (6). Laptop is an example for a super computer (7). Operating system is an example for computer hardware Also, our paper did not express any conceptual meaning. However, it was accepted both the times without any modifications (and without any reviews) and we were invited to submit the final paper and a payment of $500+ fee to present the paper. We decided to use the fee for better purposes than making Prof. Hamid Arabnia (Chairman of WORLDCOMP) rich. After that, we received few reminders from WORLDCOMP to pay the fee but we never responded. We MUST say that you should look at the above website if you have any thoughts to submit a paper to WORLDCOMP. DBLP and other indexing agencies have stopped indexing WORLDCOMP’s proceedings since 2011 due to its fakeness. See http://www.informatik.uni-trier.de/~ley/db/conf/icai/index.html for of one of the conferences of WORLDCOMP and notice that there is no listing after 2010. See Section 2 of http://sites.google.com/site/dumpconf for comments from well-known researchers about WORLDCOMP. The status of your WORLDCOMP papers can be changed from scientific to other (i.e., junk or non-technical) at any time. Better not to have a paper than having it in WORLDCOMP and spoil the resume and peace of mind forever! Our study revealed that WORLDCOMP is a money making business, using University of Georgia mask, for Prof. Hamid Arabnia. He is throwing out a small chunk of that money (around 20 dollars per paper published in WORLDCOMP’s proceedings) to his puppet (Mr. Ashu Solo or A.M.G. Solo) who publicizes WORLDCOMP and also defends it at various forums, using fake/anonymous names. The puppet uses fake names and defames other conferences to divert traffic to WORLDCOMP. He also makes anonymous phone calls and tries to threaten the critiques of WORLDCOMP (See Item 7 of Section 5 of above website). That is, the puppet does all his best to get a maximum number of papers published at WORLDCOMP to get more money into his (and Prof. Hamid Arabnia’s) pockets. Monte Carlo Resort (the venue of WORLDCOMP for more than 10 years, until 2012) has refused to provide the venue for WORLDCOMP’13 because of the fears of their image being tarnished due to WORLDCOMP’s fraudulent activities. That is why WORLDCOMP’13 is taking place at a different resort. WORLDCOMP will not be held after 2013. The draft paper submission deadline is over but still there are no committee members, no reviewers, and there is no conference Chairman. The only contact details available on WORLDCOMP’s website is just an email address! Let us make a direct request to Prof. Hamid arabnia: publish all reviews for all the papers (after blocking identifiable details) since 2000 conference. Reveal the names and affiliations of all the reviewers (for each year) and how many papers each reviewer had reviewed on average. We also request him to look at the Open Challenge (Section 6) at https://sites.google.com/site/moneycomp1 Sorry for posting to multiple lists. Spreading the word is the only way to stop this bogus conference. Please forward this message to other mailing lists and people. We are shocked with Prof. Hamid Arabnia and his puppet’s activities http://worldcomp-fake-bogus.blogspot.com Search Google using the keyword worldcomp fake for additional links. From bclaise@cisco.com Mon Apr 29 08:31:23 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B701921F97D1 for ; Mon, 29 Apr 2013 08:31:21 -0700 (PDT) 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jALm0paRdo18 for ; Mon, 29 Apr 2013 08:31:20 -0700 (PDT) Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id D2AE721F97DD for ; Mon, 29 Apr 2013 08:31:19 -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 r3TFVAnj012298; Mon, 29 Apr 2013 17:31:10 +0200 (CEST) Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3TFUhk3011802; Mon, 29 Apr 2013 17:30:59 +0200 (CEST) Message-ID: <517E9223.2000405@cisco.com> Date: Mon, 29 Apr 2013 17:30:43 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: Bruce Nordman References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------000308000102000807020105" Cc: eman mailing list Subject: Re: [eman] Nominal/Nameplate values X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Apr 2013 15:31:23 -0000 This is a multi-part message in MIME format. --------------000308000102000807020105 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi Bruce, Actually, it's too late to change the EMAN requirements at this point in time. However, what's possible is a note in the EMAN-FMWK, along the lines of: EMAN-REQ] mentioned that the standard must provide means for reporting the nominal voltage range for each Power Interface. If the nominal voltage is identical for every Power Interfaces on a specific device, a single object might be reporting the nominal voltage. I guess the MIB module will have to updated. Regards, Benoit > In discussions with Brad and Nevil, we noted that the requirements > draft says: > > 5.2.8. Nominal Voltage Range > The standard must provide means for reporting the nominal voltage > range for each Power Interface. > 5.2.9. Nominal AC Frequency > The standard must provide means for reporting the nominal AC > frequency for each Power Interface. > In Orlando we discussed adding a URI where lots of useful static > information > about a brand/model of device could be posted, including this. > > It seems elegant to remove the above two requirements and replace it with > one saying something like: > The standard must provide means for reporting a URI that links to > static data about a device. > This information would be for the entire device, whereas the existing > requirements > are for each power interface. > > I realize that the standard is in IESG review so that this would > require some > extra effort but it would simplify the MIB and provide extra capability. > > --Bruce > > > -- > *Bruce Nordman* > Lawrence Berkeley National Laboratory > *nordman.lbl.gov * > BNordman@LBL.gov > 510-486-7089 > m: 510-501-7943 > > > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman --------------000308000102000807020105 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Hi Bruce,

Actually, it's too late to change the EMAN requirements at this point in time.
However, what's possible is a note in the EMAN-FMWK, along the lines of:

   EMAN-REQ] mentioned that the standard must provide means for reporting 
   the nominal voltage range for each Power Interface.
   If the nominal voltage is identical for every Power Interfaces on a specific device, 
   a single object might be reporting the nominal voltage.

I guess the MIB module will have to updated.

Regards, Benoit

In discussions with Brad and Nevil, we noted that the requirements draft says:

5.2.8.  Nominal Voltage Range
   The standard must provide means for reporting the nominal voltage
   range for each Power Interface.
5.2.9.  Nominal AC Frequency
   The standard must provide means for reporting the nominal AC
   frequency for each Power Interface.
In Orlando we discussed adding a URI where lots of useful static information
about a brand/model of device could be posted, including this.

It seems elegant to remove the above two requirements and replace it with
one saying something like:
   The standard must provide means for reporting a URI that links to
   static data about a device.
This information would be for the entire device, whereas the existing requirements
are for each power interface.

I realize that the standard is in IESG review so that this would require some
extra effort but it would simplify the MIB and provide extra capability.

--Bruce


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


_______________________________________________
eman mailing list
eman@ietf.org
https://www.ietf.org/mailman/listinfo/eman

--------------000308000102000807020105-- From bclaise@cisco.com Tue Apr 30 07:58:50 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9903D21F9B83 for ; Tue, 30 Apr 2013 07:58:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.47 X-Spam-Level: X-Spam-Status: No, score=-10.47 tagged_above=-999 required=5 tests=[AWL=0.128, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RSnZe+7SXemG for ; Tue, 30 Apr 2013 07:58:45 -0700 (PDT) Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 0704921F9AB9 for ; Tue, 30 Apr 2013 07:58:44 -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 r3UEwZtm000788; Tue, 30 Apr 2013 16:58:36 +0200 (CEST) Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r3UEw46L010552; Tue, 30 Apr 2013 16:58:14 +0200 (CEST) Message-ID: <517FDBFC.6000107@cisco.com> Date: Tue, 30 Apr 2013 16:58:04 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: eman mailing list Content-Type: multipart/alternative; boundary="------------090709050605050208020309" Cc: Sean Turner , Stephen Farrell Subject: [eman] Energy management use cases in the EMAN applicability statement X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Apr 2013 14:58:50 -0000 This is a multi-part message in MIME format. --------------090709050605050208020309 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Dear all, While reviewing the EMAN requirements draft, both Stephen and Sean came up with the same remark: section 3.2 - not all energy management is about simply using less, in the case of power harvesting devices, one may need to preserve energy so that it can be used when communications are needed (with radios being the most expensive power consumers) Here is the change that will be done in the next version of the requirements draft. OLD: 3.2. Saving Energy Versus Maintaining Service Level While the general objective of Energy Management is quite clear, the way to attain that goal is often difficult. In many cases there is no way of reducing power without the consequence of a potential service (performance or capacity) degradation. In this case, a trade-off needs to be made between service level objectives and energy minimization. In other cases a reduction of power can easily be achieved while still maintaining sufficient service level performance, for example, by switching entities to lower Power States when higher performance is not needed. NEW: 3.2. Saving Energy Versus Maintaining Service Level One of the objectives of Energy Management is to reduce the Energy consumption. While this objective is clear, the way to attain that goal is often difficult. In many cases there is no way of reducing power without the consequence of a potential service (performance or capacity) degradation. In this case, a trade-off needs to be made between service level objectives and energy minimization. In other cases a reduction of power can easily be achieved while still maintaining sufficient service level performance, for example, by switching entities to lower Power States when higher performance is not needed. However, there is an extra action item for the applicability statement authors: they should include the different Energy Management use cases. For example, Sean mentioned: Is energy management all about actually using less energy? I would have thought energy management was about informing the management entity about the power consumption to allow them to take some action, which just as well might be no action because it's operating in some normal range. I mean I can run a nuclear reactor right at the minimum Level of Energy needed or maybe I can be somewhere above that minimum in a safety zone. Then again, maybe minimal is the lower bar of the safety bar. Regardless, I'm sticking with my first sentence ;) Regards, Benoit --------------090709050605050208020309 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Dear all,

While reviewing the EMAN requirements draft, both Stephen and Sean came up with the same remark:
section 3.2 - not all energy management is about simply using less,
in the case of power harvesting devices, one may need to
preserve energy so that it can be used when communications are
needed (with radios being the most expensive power consumers)
Here is the change that will be done in the next version of the requirements draft.

OLD:

       3.2. Saving Energy Versus Maintaining Service Level

       While the general objective of Energy Management is quite clear, the
       way to attain that goal is often difficult.  In many cases there is
       no way of reducing power without the consequence of a potential
       service (performance or capacity) degradation.  In this case, a
       trade-off needs to be made between service level objectives and
       energy minimization.  In other cases a reduction of power can easily
       be achieved while still maintaining sufficient service level
       performance, for example, by switching entities to lower Power
       States when higher performance is not needed.

NEW:

       3.2. Saving Energy Versus Maintaining Service Level

       One of the objectives of Energy Management is to reduce the
       Energy consumption. While this objective is clear, the
       way to attain that goal is often difficult.  
       In many cases there is
       no way of reducing power without the consequence of a potential
       service (performance or capacity) degradation.  In this case, a
       trade-off needs to be made between service level objectives and
       energy minimization.  In other cases a reduction of power can easily
       be achieved while still maintaining sufficient service level
       performance, for example, by switching entities to lower Power
       States when higher performance is not needed.


However, there is an extra action item for the applicability statement authors: they should include the different Energy Management use cases.
For example, Sean mentioned:
Is energy management all about actually using less energy?  I
would have thought energy management was about informing the management
entity about the power consumption to allow them to take some action,
which just as well might be no action because it's operating in some
normal range.  I mean I can run a nuclear reactor right at the minimum
Level of Energy needed or maybe I can be somewhere above that minimum in
a safety zone.  Then again, maybe minimal is the lower bar of the safety
bar.  Regardless, I'm sticking with my first sentence ;)

Regards, Benoit

--------------090709050605050208020309-- From internet-drafts@ietf.org Tue Apr 30 14:28:09 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82A0F21F9487; Tue, 30 Apr 2013 14:28:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.6 X-Spam-Level: X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UKGybNPbzVTJ; Tue, 30 Apr 2013 14:28:08 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AF6D21F9903; Tue, 30 Apr 2013 14:28:04 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.44.p4 Message-ID: <20130430212645.914.77106.idtracker@ietfa.amsl.com> Date: Tue, 30 Apr 2013 14:26:45 -0700 Cc: eman@ietf.org Subject: [eman] I-D Action: draft-ietf-eman-requirements-13.txt X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Apr 2013 21:28:09 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Energy Management Working Group of the IE= TF. Title : Requirements for Energy Management Author(s) : Juergen Quittek Mouli Chandramouli Rolf Winter Thomas Dietz Benoit Claise Filename : draft-ietf-eman-requirements-13.txt Pages : 27 Date : 2013-04-30 Abstract: This document defines requirements for standards specifications for energy management. The requirements defined in this document concern monitoring functions as well as control functions. Monitoring functions include identification of energy-managed devices and their components, monitoring of their power states, power inlets, power outlets, actual power (the instantaneous power, as opposed to the demand, which is an averaged power), power attributes, received energy, provided energy, and contained batteries. Control functions serve for controlling power supply and power state of energy-managed devices and their components. This document does not specify the features that must be implemented by compliant implementations but rather features that must be supported by standards for energy management. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-eman-requirements There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-eman-requirements-13 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eman-requirements-13 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/