From bclaise@cisco.com Tue Jun 14 02:45:22 2011 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 355A021F8586 for ; Tue, 14 Jun 2011 02:45:22 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yIb3hcmCoa0N for ; Tue, 14 Jun 2011 02:45:21 -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 4D6F521F8582 for ; Tue, 14 Jun 2011 02:45:21 -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 p5E9fXIX022913 for ; Tue, 14 Jun 2011 11:41:33 +0200 (CEST) Received: from [10.55.43.51] (ams-bclaise-8712.cisco.com [10.55.43.51]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p5E9fXts001198 for ; Tue, 14 Jun 2011 11:41:33 +0200 (CEST) Message-ID: <4DF72CCD.4050802@cisco.com> Date: Tue, 14 Jun 2011 11:41:33 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: eman mailing list Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [eman] Nomcom 2011-12: Call for Volunteers 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, 14 Jun 2011 09:45:22 -0000 Dear all, FYI. Regards, Benoit. -------- Original Message -------- Subject: Nomcom 2011-12: Call for Volunteers Date: Fri, 10 Jun 2011 19:56:06 -0700 (PDT) From: NomCom Chair To: IETF Announcement list The IETF nominating committee process for 2011-12 has begun. The IETF nominating committee appoints folks to fill the open slots on the IAOC, the IAB, and the IESG. The 10 nominating committee members are selected randomly from a pool of volunteers. The more volunteers, the better the chance we have of choosing a random yet representative cross section of the IETF population. The details of the nomcom process can be found in RFC 3777. To be eligible, volunteers for the nomcom need to have attended 3 of the past 5 IETF meetings as of the time this announcement goes out (i.e. IETF76-IETF80). If you qualify, and are not seeking appointment to any of the open positions this nomcom will be filling, please consider volunteering. The list of people and posts whose terms end with the March 2012 IETF meeting, and thus the positions for which the nominating committee is responsible, are as follows: IAB === Bernard Aboba Hannes Tschofenig Andrei Robachevsky Olaf Kolkman Spencer Dawkins Ross Callon IAOC ==== Marshall Eubanks IESG ==== Peter Saint-Andre (Applications) Jari Arkko (Internet) Dan Romascanu (Operations& Management) Gonzalo Camarillo (RAI) Stewart Bryant (Routing) Sean Turner (Security) David Harrington (Transport) The primary activity for this nomcom will begin during IETF-81 in Quebec City and should be completed by January 2012. The nomcom will be collecting requirements from the community, as well as talking to candidates and to community members about candidates. There will be regularly scheduled conference calls to ensure progress. Thus, being a nomcom member does require some time commitment. Please volunteer by sending an email to me before 11:59 pm EDT July 10, 2011 as follows: To: suresh.krishnan@ericsson.com Subject: Nomcom 2011-12 Volunteer Please include the following information in the body of the mail: Full Name: // As you enter in the IETF Registration Form, // First/Given name followed by Last/Family Name Current Primary Affiliation: // typically what goes in the Company // field in the IETF Registration Form Email Address(es): // all email addresses used to Register for the // past 5 IETF meetings // Please designate a Preferred email address for // contact if there is more than one email address Telephone number: // With country code (for confirmation if selected) Please expect an email response from me within 3 business days stating whether or not you are qualified. If you do not receive a response in this timeframe, please re-send your email with the tag "RESEND:" added to the subject line. If you are not yet sure you would like to volunteer, please consider that nomcom members play a very important role in shaping the leadership of the IETF. Ensuring the leadership of the IETF is fair and balanced and comprised of those who can lead the IETF in the right direction is an important responsibility that rests on the IETF participants at large. Volunteering for the nomcom is a good way of contributing in that direction. I will be publishing a more detailed target timetable, as well as details of the randomness seeds to be used for the RFC 3797 selection process within the next few days. Thank you in advance for your participation. Suresh Krishnan Nomcom Chair 2011-2012 Email: nomcom-chair@ietf.org, suresh.krishnan@ericsson.com _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce From Quittek@neclab.eu Tue Jun 14 08:44:33 2011 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 DF89711E8175 for ; Tue, 14 Jun 2011 08:44:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.048 X-Spam-Level: X-Spam-Status: No, score=-101.048 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, RDNS_NONE=0.1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9DV4xuTSi+op for ; Tue, 14 Jun 2011 08:44:33 -0700 (PDT) Received: from smtp0.neclab.eu (unknown [195.37.70.41]) by ietfa.amsl.com (Postfix) with ESMTP id E62AD11E812A for ; Tue, 14 Jun 2011 08:44:32 -0700 (PDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.neclab.eu (Postfix) with ESMTP id 0916D2C00008A; Tue, 14 Jun 2011 17:44:32 +0200 (CEST) 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 FlJWCVcWe3AB; Tue, 14 Jun 2011 17:44:31 +0200 (CEST) Received: from METHONE.office.hd (Methone.office.hd [192.168.24.54]) by smtp0.neclab.eu (Postfix) with ESMTP id DB3AC2C000088; Tue, 14 Jun 2011 17:44:16 +0200 (CEST) Received: from DAPHNIS.office.hd ([169.254.2.223]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0270.001; Tue, 14 Jun 2011 17:44:16 +0200 From: Juergen Quittek To: Benoit Claise , Juergen Quittek Thread-Topic: [eman] power inlets Thread-Index: AQHL+49xiIo9Q8jGhEi7lUijcCBbH5RxNjsAgEwmcQA= Date: Tue, 14 Jun 2011 15:44:16 +0000 Message-ID: In-Reply-To: <4DB7BCC8.50405@cisco.com> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-Entourage/13.9.0.110114 x-originating-ip: [10.1.2.219] Content-Type: text/plain; charset="Windows-1252" Content-ID: <039B1158BD7B5044BF0F50346FB50517@office.hd> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: eman mailing list Subject: Re: [eman] power inlets 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, 14 Jun 2011 15:44:34 -0000 Hi Benoit, I am not really happy about the term 'inlet'. It just corresponds to 'outlet'. As I said in the previous version of the requirements draft, The UPS Mib calls them 'input'. I am not sure power source is the right term, because this is already taken by the sourcing device. In PoE terminology a PoE switch is a Power Sourcing Equipment (PSE). The inlet/input or whatever we want to call it is rather not a source of power but just the inlet. And unfortunately, a power qualit= y you measure at an inlet is not necessarily the same as the one you measure at the corresponding sourcing device. Best regards, Juergen Am 27.04.11 08:50 schrieb "Benoit Claise" unter : > Juergen, >=20 > Thinking some more about this term "inlet", I believe that we should use > the term =B3power source=B2 in the requirement draft as it=B9s more gener= ic to > the pattern versus the implementation (inlet) on specific devices. The > inlet can be used some use cases >=20 > Use Case X: Device with Multiple power Sources > In this use case a device is powered by 1..N power sources=8A.etc > Examples: > PoE Device connected to two interfaces from two sources > A PC with two power inlets plugged into two wall outlets > A washing machine bank requiring 240V wired to two 120V sources >=20 > Regards, Benoit. >> Dear all, >>=20 >> We are currently revising the eman requirements and discussing how to co= ver >> devices with multiple power supplies. >>=20 >> A typical case is a server with dual main power supply. Often such serve= rs >> have their two power inlets connected to different power distribution tr= ees >> in order to be able to continue operation even when power fails in one p= ower >> distribution tree. Typically, servers do not just have two inlets, but t= wo >> full built-in power supply units. If one breaks, the other can take over= . >>=20 >> I have thought about how to cover such servers in the requrements. My cu= rrent >> solution starts with the point that a powered device may have more than = one >> power inlet. Then the eman standard to be developed must provide means >> (managed objects in MIB modules) for monitoring each power inlet >> individually. This concerns monitoring of instantaneous power, consumed >> energy, power quality, and maybe even just availability of power at an i= nlet. >>=20 >> Does anyone think this is a reasonable way to go? The inlet concept some= how >> blurs the role of built-in power supply units. >>=20 >> Do we have better alternatives? >>=20 >> Thanks, >>=20 >> Juergen >> _______________________________________________ >> eman mailing list >> eman@ietf.org >> https://www.ietf.org/mailman/listinfo/eman >=20 > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman From ramorgan@ra.rockwell.com Tue Jun 14 14:02:17 2011 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 843AB11E80EA for ; Tue, 14 Jun 2011 14:02:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.237 X-Spam-Level: X-Spam-Status: No, score=-0.237 tagged_above=-999 required=5 tests=[AWL=0.052, BAYES_00=-2.599, SARE_URGBIZ=0.725, URG_BIZ=1.585] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sq7ZYXRsDJzc for ; Tue, 14 Jun 2011 14:02:17 -0700 (PDT) Received: from ramilwsmtp01.ra.rockwell.com (ramkesd003-e.ra.rockwell.com [205.175.240.251]) by ietfa.amsl.com (Postfix) with ESMTP id 1880E11E80D8 for ; Tue, 14 Jun 2011 14:02:16 -0700 (PDT) Auto-Submitted: auto-generated From: Rich A Morgan To: eman@ietf.org Message-ID: Date: Tue, 14 Jun 2011 16:02:07 -0500 X-MIMETrack: Serialize by Router on RAMilwSMTP01/Milwaukee/RA/Rockwell(Release 8.5.2FP1|November 29, 2010) at 06/14/2011 04:02:17 PM MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Subject: [eman] Rich A Morgan is out of the office 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, 14 Jun 2011 21:02:17 -0000 I will be out of the office starting 06/13/2011 and will not return until 06/17/2011. I will be checking email in the evenings for urgent business. From bclaise@cisco.com Thu Jun 16 05:28:14 2011 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 BE49011E80DD for ; Thu, 16 Jun 2011 05:28:14 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LwnIli23rTGk for ; Thu, 16 Jun 2011 05:28:14 -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 C370B11E808E for ; Thu, 16 Jun 2011 05:28:13 -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 p5GCORuu014736; Thu, 16 Jun 2011 14:24:27 +0200 (CEST) Received: from [10.55.43.51] (ams-bclaise-8712.cisco.com [10.55.43.51]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p5GCOQYi023920; Thu, 16 Jun 2011 14:24:26 +0200 (CEST) Message-ID: <4DF9F5FA.2020903@cisco.com> Date: Thu, 16 Jun 2011 14:24:26 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: Juergen Quittek References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Cc: eman mailing list Subject: Re: [eman] power inlets 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, 16 Jun 2011 12:28:14 -0000 Hi Juergen, To me, power inlet and outlet correspond to physical connectors. So I could be fine if these terms are used in this context. However, does the term power inlet apply to PoE? I don't think so. So maybe we want to distinguish the two cases: PoE with Power Sourcing Device and non PoE with power inlet? Regards, Benoit. > Hi Benoit, > > I am not really happy about the term 'inlet'. It just corresponds to > 'outlet'. As I said in the previous version of the requirements draft, > The UPS Mib calls them 'input'. > > I am not sure power source is the right term, because this is already taken > by the sourcing device. In PoE terminology a PoE switch is a Power Sourcing > Equipment (PSE). The inlet/input or whatever we want to call it is rather > not a source of power but just the inlet. And unfortunately, a power quality > you measure at an inlet is not necessarily the same as the one you measure > at the corresponding sourcing device. > > Best regards, > > Juergen > > > Am 27.04.11 08:50 schrieb "Benoit Claise" unter: > >> Juergen, >> >> Thinking some more about this term "inlet", I believe that we should use >> the term ³power source² in the requirement draft as itıs more generic to >> the pattern versus the implementation (inlet) on specific devices. The >> inlet can be used some use cases >> >> Use Case X: Device with Multiple power Sources >> In this use case a device is powered by 1..N power sourcesŠ.etc >> Examples: >> PoE Device connected to two interfaces from two sources >> A PC with two power inlets plugged into two wall outlets >> A washing machine bank requiring 240V wired to two 120V sources >> >> Regards, Benoit. >>> Dear all, >>> >>> We are currently revising the eman requirements and discussing how to cover >>> devices with multiple power supplies. >>> >>> A typical case is a server with dual main power supply. Often such servers >>> have their two power inlets connected to different power distribution trees >>> in order to be able to continue operation even when power fails in one power >>> distribution tree. Typically, servers do not just have two inlets, but two >>> full built-in power supply units. If one breaks, the other can take over. >>> >>> I have thought about how to cover such servers in the requrements. My current >>> solution starts with the point that a powered device may have more than one >>> power inlet. Then the eman standard to be developed must provide means >>> (managed objects in MIB modules) for monitoring each power inlet >>> individually. This concerns monitoring of instantaneous power, consumed >>> energy, power quality, and maybe even just availability of power at an inlet. >>> >>> Does anyone think this is a reasonable way to go? The inlet concept somehow >>> blurs the role of built-in power supply units. >>> >>> Do we have better alternatives? >>> >>> Thanks, >>> >>> Juergen >>> _______________________________________________ >>> 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 Quittek@neclab.eu Fri Jun 17 01:59:24 2011 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 188099E800D for ; Fri, 17 Jun 2011 01:59:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.649 X-Spam-Level: X-Spam-Status: No, score=-101.649 tagged_above=-999 required=5 tests=[AWL=0.601, BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id byyJhWkwSOyB for ; Fri, 17 Jun 2011 01:59:23 -0700 (PDT) Received: from smtp0.netlab.nec.de (smtp0.netlab.nec.de [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 36E7F9E8008 for ; Fri, 17 Jun 2011 01:59:23 -0700 (PDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.netlab.nec.de (Postfix) with ESMTP id DC6C6280003A6; Fri, 17 Jun 2011 10:59:21 +0200 (CEST) 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 DQu2U927JZtM; Fri, 17 Jun 2011 10:59:21 +0200 (CEST) Received: from METHONE.office.hd (Methone.office.hd [192.168.24.54]) by smtp0.netlab.nec.de (Postfix) with ESMTP id B6AFF28000189; Fri, 17 Jun 2011 10:59:06 +0200 (CEST) Received: from Polydeuces.office.hd ([169.254.3.115]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0270.001; Fri, 17 Jun 2011 10:58:56 +0200 From: Juergen Quittek To: Benoit Claise Thread-Topic: [eman] power inlets Thread-Index: AQHL+49xiIo9Q8jGhEi7lUijcCBbH5RxNjsAgEwmcQCAAstXAIABensA Date: Fri, 17 Jun 2011 08:58:55 +0000 Message-ID: In-Reply-To: <4DF9F5FA.2020903@cisco.com> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-Entourage/13.9.0.110114 x-originating-ip: [10.1.2.219] Content-Type: text/plain; charset="utf-8" Content-ID: <4DD014BC7CD51940B09A1BE928B92AB0@office.hd> Content-Transfer-Encoding: base64 MIME-Version: 1.0 Cc: eman mailing list Subject: Re: [eman] power inlets 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, 17 Jun 2011 08:59:24 -0000 RGVhciBCZW5vaXQsDQoNCkkgYWdyZWUgdGhhdCBwb3dlciBpbmxldCBhbmQgb3V0bGV0IGNvcnJl c3BvbmQgdG8gcGh5c2ljYWwgY29ubmVjdG9ycy4NCkluIGNhc2Ugb2YgUG9FLCBpdCBpcyB0aGUg OFA4QyAoUko0NSkgc29ja2V0IGF0IHRoZSBkZXZpY2UuIE9idmlvdXNseSwgdGhpcw0KcGh5c2lj YWwgY29ubmVjdG9yIGlzIHRoZSBwb3dlciBpbmxldCBvZiBhIFBvRSBwb3dlcmVkIGRldmljZS4N Cg0KSSBjaGVja2VkIHRoZSBQb0UgdGVybWlub2xvZ3kgb2YgODAyLjNhZiBhbnQgODAyLjNhdC4N ClRoZXJlIGlzIG5vIGEgY29uZmxpY3RpbmcgdGVybSBmb3IgdGhpcy4gVGhleSBkb24ndCBoYXZl IHBhcnRpY3VsYXIgdGVybXMNCmZvciBwb3dlciBpbmxldHMgYW5kIG91dGxldHMuIFRoZXkgdGFs ayBhYm91dCB0aGUgcG93ZXIgaW50ZXJmYWNlIChQSSkgd2hpY2gNCmlzIHVzZWQgZm9yIHBvd2Vy IGlubGV0cyBhcyB3ZWxsIGFzIGZvciBwb3dlciBvdXRsZXRzLg0KDQpTbyB3aGF0IHdlIGNhbGwg YSBwb3dlciBpbmxldCBpcyBpbiBQb0UgdGVybSB0aGUNCiAgICAicG93ZXIgaW50ZXJmYWNlIChQ SSkgYXQgdGhlIHBvd2VyZWQgZGV2aWNlIChQRCkiDQphbmQgd2hhdCB3ZSBjYWxsIGEgcG93ZXIg b3V0bGV0IGlzIGluIFBvRSB0ZXJtIHRoZQ0KICAtICJwb3dlciBpbnRlcmZhY2UgKFBJKSBhdCB0 aGUgcG93ZXIgc291cmNpbmcgZXF1aXBtZW50IChQU0UpIg0KDQpJIHRoaW5rIHBvd2VyIGlubGV0 IGFuZCBwb3dlciBvdXRsZXQgYXJlIG11Y2ggc2hvcnRlciB0ZXJtcyBhbmQgZWFzaWVyIHRvDQpw YXJzZSB0aGFuIHRoZSBsb25nIHZlcnNpb25zIGZyb20gdGhlIFBvRSBzdGFuZGFyZC4gSWYgbmVl ZGVkLCB3ZSBjYW4gZ2l2ZSBhDQptYXBwaW5nIG9mIG91ciB0ZXJtcyB0byBQb0UgdGVybXMuDQoN CkJ1dCBhbnl3YXksIHRoZSBFTUFOIHN0YW5kYXJkcyBzaG91bGQgYmUgaW5kZXBlbmRlbnQgb2Yg dGhlIHBvd2VyIHN1cHBseQ0KdHlwZS4gV2Ugd2lsbCBzdXBwb3J0IGFyYml0cmFyeSBraW5kcyBv ZiBBQyBhbmQgREMgcG93ZXIgc3VwcGx5IGluY2x1ZGluZw0KUG9FLiBTbyB3ZSBkbyBub3QgZGVw ZW5kIG9uIGp1c3QgUG9FIHRlcm1pbm9sb2d5Lg0KDQpUaGFua3MsDQoNCiAgICBKdWVyZ2VuDQoN CkFtIDE2LjA2LjExIDE0OjI0IHNjaHJpZWIgIkJlbm9pdCBDbGFpc2UiIHVudGVyIDxiY2xhaXNl QGNpc2NvLmNvbT46DQoNCj4gSGkgSnVlcmdlbiwNCj4gDQo+IFRvIG1lLCBwb3dlciBpbmxldCBh bmQgb3V0bGV0IGNvcnJlc3BvbmQgdG8gcGh5c2ljYWwgY29ubmVjdG9ycy4gU28gSQ0KPiBjb3Vs ZCBiZSBmaW5lIGlmIHRoZXNlIHRlcm1zIGFyZSB1c2VkIGluIHRoaXMgY29udGV4dC4NCj4gSG93 ZXZlciwgZG9lcyB0aGUgdGVybSBwb3dlciBpbmxldCBhcHBseSB0byBQb0U/IEkgZG9uJ3QgdGhp bmsgc28uDQo+IFNvIG1heWJlIHdlIHdhbnQgdG8gZGlzdGluZ3Vpc2ggdGhlIHR3byBjYXNlczog UG9FIHdpdGggUG93ZXIgU291cmNpbmcNCj4gRGV2aWNlIGFuZCBub24gUG9FIHdpdGggcG93ZXIg aW5sZXQ/DQo+IA0KPiBSZWdhcmRzLCBCZW5vaXQuDQo+PiBIaSBCZW5vaXQsDQo+PiANCj4+IEkg YW0gbm90IHJlYWxseSBoYXBweSBhYm91dCB0aGUgdGVybSAnaW5sZXQnLiBJdCBqdXN0IGNvcnJl c3BvbmRzIHRvDQo+PiAnb3V0bGV0Jy4gQXMgSSBzYWlkIGluIHRoZSBwcmV2aW91cyB2ZXJzaW9u IG9mIHRoZSByZXF1aXJlbWVudHMgZHJhZnQsDQo+PiBUaGUgVVBTIE1pYiBjYWxscyB0aGVtICdp bnB1dCcuDQo+PiANCj4+IEkgYW0gbm90IHN1cmUgcG93ZXIgc291cmNlIGlzIHRoZSByaWdodCB0 ZXJtLCBiZWNhdXNlIHRoaXMgaXMgYWxyZWFkeSB0YWtlbg0KPj4gYnkgdGhlIHNvdXJjaW5nIGRl dmljZS4gSW4gUG9FIHRlcm1pbm9sb2d5IGEgUG9FIHN3aXRjaCBpcyBhIFBvd2VyIFNvdXJjaW5n DQo+PiBFcXVpcG1lbnQgKFBTRSkuIFRoZSBpbmxldC9pbnB1dCBvciB3aGF0ZXZlciB3ZSB3YW50 IHRvIGNhbGwgaXQgaXMgcmF0aGVyDQo+PiBub3QgYSBzb3VyY2Ugb2YgcG93ZXIgYnV0IGp1c3Qg dGhlIGlubGV0LiBBbmQgdW5mb3J0dW5hdGVseSwgYSBwb3dlciBxdWFsaXR5DQo+PiB5b3UgbWVh c3VyZSBhdCBhbiBpbmxldCBpcyBub3QgbmVjZXNzYXJpbHkgdGhlIHNhbWUgYXMgdGhlIG9uZSB5 b3UgbWVhc3VyZQ0KPj4gYXQgdGhlIGNvcnJlc3BvbmRpbmcgc291cmNpbmcgZGV2aWNlLg0KPj4g DQo+PiBCZXN0IHJlZ2FyZHMsDQo+PiANCj4+ICAgICAgSnVlcmdlbg0KPj4gDQo+PiANCj4+IEFt IDI3LjA0LjExIDA4OjUwIHNjaHJpZWIgIkJlbm9pdCBDbGFpc2UiIHVudGVyPGJjbGFpc2VAY2lz Y28uY29tPjoNCj4+IA0KPj4+IEp1ZXJnZW4sDQo+Pj4gDQo+Pj4gVGhpbmtpbmcgc29tZSBtb3Jl IGFib3V0IHRoaXMgdGVybSAiaW5sZXQiLCBJIGJlbGlldmUgdGhhdCB3ZSBzaG91bGQgdXNlDQo+ Pj4gdGhlIHRlcm0gwrNwb3dlciBzb3VyY2XCsiBpbiB0aGUgcmVxdWlyZW1lbnQgZHJhZnQgYXMg aXTCuXMgbW9yZSBnZW5lcmljIHRvDQo+Pj4gdGhlIHBhdHRlcm4gdmVyc3VzIHRoZSBpbXBsZW1l bnRhdGlvbiAoaW5sZXQpIG9uIHNwZWNpZmljIGRldmljZXMuIFRoZQ0KPj4+IGlubGV0IGNhbiBi ZSB1c2VkIHNvbWUgdXNlIGNhc2VzDQo+Pj4gDQo+Pj4gVXNlIENhc2UgWDogRGV2aWNlIHdpdGgg TXVsdGlwbGUgcG93ZXIgU291cmNlcw0KPj4+IEluIHRoaXMgdXNlIGNhc2UgYSBkZXZpY2UgaXMg cG93ZXJlZCBieSAxLi5OIHBvd2VyIHNvdXJjZXPFoC5ldGMNCj4+PiBFeGFtcGxlczoNCj4+PiBQ b0UgRGV2aWNlIGNvbm5lY3RlZCB0byB0d28gaW50ZXJmYWNlcyBmcm9tIHR3byBzb3VyY2VzDQo+ Pj4gQSBQQyB3aXRoIHR3byBwb3dlciBpbmxldHMgcGx1Z2dlZCBpbnRvIHR3byB3YWxsIG91dGxl dHMNCj4+PiBBIHdhc2hpbmcgbWFjaGluZSBiYW5rIHJlcXVpcmluZyAyNDBWIHdpcmVkIHRvIHR3 byAxMjBWIHNvdXJjZXMNCj4+PiANCj4+PiBSZWdhcmRzLCBCZW5vaXQuDQo+Pj4+IERlYXIgYWxs LA0KPj4+PiANCj4+Pj4gV2UgYXJlIGN1cnJlbnRseSByZXZpc2luZyB0aGUgZW1hbiByZXF1aXJl bWVudHMgYW5kIGRpc2N1c3NpbmcgaG93IHRvIGNvdmVyDQo+Pj4+IGRldmljZXMgd2l0aCBtdWx0 aXBsZSBwb3dlciBzdXBwbGllcy4NCj4+Pj4gDQo+Pj4+IEEgdHlwaWNhbCBjYXNlIGlzIGEgc2Vy dmVyIHdpdGggZHVhbCBtYWluIHBvd2VyIHN1cHBseS4gT2Z0ZW4gc3VjaCBzZXJ2ZXJzDQo+Pj4+ IGhhdmUgdGhlaXIgdHdvIHBvd2VyIGlubGV0cyBjb25uZWN0ZWQgdG8gZGlmZmVyZW50IHBvd2Vy IGRpc3RyaWJ1dGlvbiB0cmVlcw0KPj4+PiBpbiBvcmRlciB0byBiZSBhYmxlIHRvIGNvbnRpbnVl IG9wZXJhdGlvbiBldmVuIHdoZW4gcG93ZXIgZmFpbHMgaW4gb25lDQo+Pj4+IHBvd2VyDQo+Pj4+ IGRpc3RyaWJ1dGlvbiB0cmVlLiBUeXBpY2FsbHksIHNlcnZlcnMgZG8gbm90IGp1c3QgaGF2ZSB0 d28gaW5sZXRzLCBidXQgdHdvDQo+Pj4+IGZ1bGwgYnVpbHQtaW4gcG93ZXIgc3VwcGx5IHVuaXRz LiBJZiBvbmUgYnJlYWtzLCB0aGUgb3RoZXIgY2FuIHRha2Ugb3Zlci4NCj4+Pj4gDQo+Pj4+IEkg aGF2ZSB0aG91Z2h0IGFib3V0IGhvdyB0byBjb3ZlciBzdWNoIHNlcnZlcnMgaW4gdGhlIHJlcXVy ZW1lbnRzLiBNeQ0KPj4+PiBjdXJyZW50DQo+Pj4+IHNvbHV0aW9uIHN0YXJ0cyB3aXRoIHRoZSBw b2ludCB0aGF0IGEgcG93ZXJlZCBkZXZpY2UgbWF5IGhhdmUgbW9yZSB0aGFuIG9uZQ0KPj4+PiBw b3dlciBpbmxldC4gVGhlbiB0aGUgZW1hbiBzdGFuZGFyZCB0byBiZSBkZXZlbG9wZWQgbXVzdCBw cm92aWRlIG1lYW5zDQo+Pj4+IChtYW5hZ2VkIG9iamVjdHMgaW4gTUlCIG1vZHVsZXMpIGZvciBt b25pdG9yaW5nIGVhY2ggcG93ZXIgaW5sZXQNCj4+Pj4gaW5kaXZpZHVhbGx5LiBUaGlzIGNvbmNl cm5zIG1vbml0b3Jpbmcgb2YgaW5zdGFudGFuZW91cyBwb3dlciwgY29uc3VtZWQNCj4+Pj4gZW5l cmd5LCBwb3dlciBxdWFsaXR5LCBhbmQgbWF5YmUgZXZlbiBqdXN0IGF2YWlsYWJpbGl0eSBvZiBw b3dlciBhdCBhbg0KPj4+PiBpbmxldC4NCj4+Pj4gDQo+Pj4+IERvZXMgYW55b25lIHRoaW5rIHRo aXMgaXMgYSByZWFzb25hYmxlIHdheSB0byBnbz8gVGhlIGlubGV0IGNvbmNlcHQgc29tZWhvdw0K Pj4+PiBibHVycyB0aGUgcm9sZSBvZiBidWlsdC1pbiBwb3dlciBzdXBwbHkgdW5pdHMuDQo+Pj4+ IA0KPj4+PiBEbyB3ZSBoYXZlIGJldHRlciBhbHRlcm5hdGl2ZXM/DQo+Pj4+IA0KPj4+PiBUaGFu a3MsDQo+Pj4+IA0KPj4+PiAgICAgICBKdWVyZ2VuDQo+Pj4+IF9fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+Pj4+IGVtYW4gbWFpbGluZyBsaXN0DQo+Pj4+ IGVtYW5AaWV0Zi5vcmcNCj4+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m by9lbWFuDQo+Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X18NCj4+PiBlbWFuIG1haWxpbmcgbGlzdA0KPj4+IGVtYW5AaWV0Zi5vcmcNCj4+PiBodHRwczov L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2VtYW4NCj4gDQoNCg== From moulchan@cisco.com Tue Jun 21 05:46:38 2011 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 D85409E8021 for ; Tue, 21 Jun 2011 05:46:38 -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=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VjMmGmvvsvFt for ; Tue, 21 Jun 2011 05:46:38 -0700 (PDT) Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by ietfa.amsl.com (Postfix) with ESMTP id 2C7599E8014 for ; Tue, 21 Jun 2011 05:46:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=moulchan@cisco.com; l=3523; q=dns/txt; s=iport; t=1308660398; x=1309869998; h=mime-version:subject:date:message-id:from:to; bh=IzltB0zAZ5DYK2mruqt4RFIzH9/MpgnJX0jABN7/+OQ=; b=BsNHB/Hjs7XxJIRtU7b/5JR+1lsI7RvU3D6C7+MzVq0UJZWsloqjzvOF VsO0ZYN0d50wIYgYDmpQ+JyPh5G7UHqUEe0t3gg++xJEk5+irs5u+jhI4 udVRnHrGp8Vz6rvFQTwcUK+uATCWqkeblqi0q8ExpRojG9b7YqErzhsvS A=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ai4JAHSSAE6tJXG//2dsb2JhbABUglGVS4Zgh3J3qRiBHZ5FhioEhyKPL4s5 X-IronPort-AV: E=Sophos;i="4.65,401,1304294400"; d="scan'208,217";a="718508067" Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by sj-iport-6.cisco.com with ESMTP; 21 Jun 2011 12:46:37 +0000 Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core2-4.cisco.com (8.14.3/8.14.3) with ESMTP id p5LCkaoN019985 for ; Tue, 21 Jun 2011 12:46:36 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, 21 Jun 2011 07:46:36 -0500 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_01CC3011.42342A84" Date: Tue, 21 Jun 2011 07:46:33 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: AC power measurements for output Thread-Index: AcwwET/q58nyGmP4TxKTg1fY4395vg== From: "Mouli Chandramouli (moulchan)" To: X-OriginalArrivalTime: 21 Jun 2011 12:46:36.0544 (UTC) FILETIME=[41EBA000:01CC3011] Subject: [eman] AC power measurements for output 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, 21 Jun 2011 12:46:38 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01CC3011.42342A84 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, =20 There are metrics for AC power on quality of power (active power, reactive power, power factor ...) for AC power inlets.=20 Are there similar power metrics for AC power outlets ?=20 =20 Thanks Mouli =20 =20 ------_=_NextPart_001_01CC3011.42342A84 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello,

 

There are = metrics for AC power on quality of power (active power, reactive power, power factor …) = for AC power inlets.

Are there = similar power metrics for AC power outlets ?

 

Thanks

Mouli

 

 

------_=_NextPart_001_01CC3011.42342A84-- From bclaise@cisco.com Tue Jun 21 05:50:47 2011 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 5FF4E11E8078 for ; Tue, 21 Jun 2011 05:50:47 -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=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KGqK1WKng9W0 for ; Tue, 21 Jun 2011 05:50:46 -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 2D13821F844A for ; Tue, 21 Jun 2011 05:50:46 -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 p5LCohXw007393 for ; Tue, 21 Jun 2011 14:50:43 +0200 (CEST) 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 p5LCogEn016730; Tue, 21 Jun 2011 14:50:42 +0200 (CEST) Message-ID: <4E0093A2.4010907@cisco.com> Date: Tue, 21 Jun 2011 14:50:42 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: "Mouli Chandramouli (moulchan)" References: In-Reply-To: Content-Type: multipart/alternative; boundary="------------090301030005010008080806" Cc: eman@ietf.org Subject: Re: [eman] AC power measurements for output 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, 21 Jun 2011 12:50:47 -0000 This is a multi-part message in MIME format. --------------090301030005010008080806 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, Most importantly, are they any requirements to report the power quality for power outlets? Maybe in the Smart PDU? Regards, Benoit. > > Hello, > > There are metrics for AC power on quality of power (active power, > reactive power, power factor ...) for AC power inlets. > > Are there similar power metrics for AC power outlets ? > > Thanks > > Mouli > > > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman --------------090301030005010008080806 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi,

Most importantly, are they any requirements to report the power quality for power outlets?
Maybe in the Smart PDU?

Regards, Benoit.

Hello,

 

There are metrics for AC power on quality of power (active power, reactive power, power factor …) for AC power inlets.

Are there similar power metrics for AC power outlets ?

 

Thanks

Mouli

 

 


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

--------------090301030005010008080806-- From bnordman@lbl.gov Tue Jun 21 08:30:10 2011 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 A75F711E8148 for ; Tue, 21 Jun 2011 08:30:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.976 X-Spam-Level: X-Spam-Status: No, score=-5.976 tagged_above=-999 required=5 tests=[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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KAfDVIZP2N2h for ; Tue, 21 Jun 2011 08:30:09 -0700 (PDT) Received: from ironport4.lbl.gov (ironport4.lbl.gov [128.3.41.45]) by ietfa.amsl.com (Postfix) with ESMTP id 830CD11E8263 for ; Tue, 21 Jun 2011 08:30:09 -0700 (PDT) X-Ironport-SBRS: 5.2 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AngBAOq3AE7RVdy0mGdsb2JhbABOBoJRnBkBh34IFAEBAQEBCAkNBxQlq1KdG4M3gnMEhyKKRIt7PINv X-IronPort-AV: E=Sophos;i="4.65,401,1304319600"; d="scan'208";a="44102285" Received: from mail-vx0-f180.google.com ([209.85.220.180]) by ironport4.lbl.gov with ESMTP; 21 Jun 2011 08:30:00 -0700 Received: by mail-vx0-f180.google.com with SMTP id 7so4565380vxd.39 for ; Tue, 21 Jun 2011 08:30:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.97.163 with SMTP id eb3mr103489vdb.269.1308670200044; Tue, 21 Jun 2011 08:30:00 -0700 (PDT) Received: by 10.52.164.10 with HTTP; Tue, 21 Jun 2011 08:30:00 -0700 (PDT) In-Reply-To: <4E0093A2.4010907@cisco.com> References: <4E0093A2.4010907@cisco.com> Date: Tue, 21 Jun 2011 08:30:00 -0700 Message-ID: From: Bruce Nordman To: Benoit Claise Content-Type: multipart/alternative; boundary=20cf307f379466dca004a63a86f3 Cc: eman@ietf.org Subject: Re: [eman] AC power measurements for output 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, 21 Jun 2011 15:30:10 -0000 --20cf307f379466dca004a63a86f3 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable I'm not an engineer, but my understanding is that these metrics are for the flow of electricity through a wire. An inlet or outlet by itself would not have any flow. If this is correct, I don't think we need to make a distinction. --Bruce On Tue, Jun 21, 2011 at 5:50 AM, Benoit Claise wrote: > ** > Hi, > > Most importantly, are they any requirements to report the power quality f= or > power outlets? > Maybe in the Smart PDU? > > Regards, Benoit. > > Hello,**** > > ** ** > > There are metrics for AC power on quality of power (active power, reactiv= e > power, power factor =85) for AC power inlets. **** > > Are there similar power metrics for AC power outlets ? **** > > ** ** > > Thanks**** > > Mouli**** > > ** ** > > ** ** > > > _______________________________________________ > eman mailing listeman@ietf.orghttps://www.ietf.org/mailman/listinfo/eman > > > > _______________________________________________ > 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 --20cf307f379466dca004a63a86f3 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable I'm not an engineer, but my understanding is that these metrics are for=
the flow of electricity through a wire.=A0 An inlet or outlet by itself= would
not have any flow.
=A0 If this is correct, I don't think w= e need to make a distinction.

--Bruce

On Tue, Jun 21, 2011 at 5:50 = AM, Benoit Claise <bclaise@cisco.com> wrote:
Hi,

Most importantly, are they any requirements to report the power quality for power outlets?
Maybe in the Smart PDU?

Regards, Benoit.
=20 =20 =20

Hello,

=A0

There are metrics for AC power on quality of power (active power, reactive power, power factor =85) for AC power inlets.

Are there similar power metrics for AC power outlets ?

=A0

Thanks

Mouli

=A0

=A0


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


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




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

--20cf307f379466dca004a63a86f3-- From Michael.Suchoff@raritan.com Tue Jun 21 08:37:00 2011 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 8581011E826D for ; Tue, 21 Jun 2011 08:37:00 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7mCkbiAY6dfI for ; Tue, 21 Jun 2011 08:36:58 -0700 (PDT) Received: from fig.raritan.com (fig.raritan.com [12.144.63.197]) by ietfa.amsl.com (Postfix) with ESMTP id B0EA311E826C for ; Tue, 21 Jun 2011 08:36:58 -0700 (PDT) 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_01CC3029.0DFAEB4B" Date: Tue, 21 Jun 2011 11:36:56 -0400 Message-ID: <9C329342B62B87498B92834DEC9FF51E0CFA68FC@fig.raritan.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [eman] AC power measurements for output Thread-Index: AcwwKCIg2b7bcFmhQW+2xt/jzD/nSwAAFUCA References: <4E0093A2.4010907@cisco.com> From: "Michael Suchoff" To: "Bruce Nordman" , "Benoit Claise" Cc: eman@ietf.org Subject: Re: [eman] AC power measurements for output 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, 21 Jun 2011 15:37:00 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01CC3029.0DFAEB4B Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable In the AC power distribution units Raritan (and other vendors) manufactures, we report metrics for all outlets, the inlet(s) and circuit breakers. =20 By monitoring the outlet, we can report whether the device connected to it is operating correctly. =20 By monitoring the inlet we can report the power quality being received by the PDU and report how close current is to tripping upstream breaker. =20 By monitoring the circuit breakers, we can report whether any is tripped and how close current flow is to tripping the breaker. =20 =20 ________________________________ From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of Bruce Nordman Sent: Tuesday, June 21, 2011 11:30 AM To: Benoit Claise Cc: eman@ietf.org Subject: Re: [eman] AC power measurements for output =20 I'm not an engineer, but my understanding is that these metrics are for the flow of electricity through a wire. An inlet or outlet by itself would not have any flow. If this is correct, I don't think we need to make a distinction. --Bruce On Tue, Jun 21, 2011 at 5:50 AM, Benoit Claise wrote: Hi, Most importantly, are they any requirements to report the power quality for power outlets? Maybe in the Smart PDU? Regards, Benoit. Hello, =20 There are metrics for AC power on quality of power (active power, reactive power, power factor ...) for AC power inlets.=20 Are there similar power metrics for AC power outlets ?=20 =20 Thanks Mouli =20 =20 =20 _______________________________________________ eman mailing list eman@ietf.org https://www.ietf.org/mailman/listinfo/eman =20 _______________________________________________ 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 ------_=_NextPart_001_01CC3029.0DFAEB4B Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

In the AC power distribution units = Raritan (and other vendors) manufactures, we report metrics for all outlets, the inlet(s) and circuit breakers.

 

By monitoring the outlet, we can = report whether the device connected to it is operating = correctly.

 

By monitoring the inlet we can = report the power quality being received by the PDU and report how close current is = to tripping upstream breaker.

 

 By monitoring the circuit = breakers, we can report whether any is tripped and how close current flow is to = tripping the breaker.

 

 

From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of Bruce Nordman
Sent: Tuesday, June 21, = 2011 11:30 AM
To: Benoit Claise
Cc: eman@ietf.org
Subject: Re: [eman] AC = power measurements for output

 

I'm not an = engineer, but my understanding is that these metrics are for
the flow of electricity through a wire.  An inlet or outlet by = itself would
not have any flow.
  If this is correct, I don't think we need to make a = distinction.

--Bruce

On Tue, Jun 21, 2011 at 5:50 AM, Benoit Claise <bclaise@cisco.com> = wrote:

Hi,

Most importantly, are they any requirements to report the power quality = for power outlets?
Maybe in the Smart PDU?

Regards, Benoit.

Hello,

 

There are metrics for AC power on quality of power (active power, reactive power, = power factor …) for AC power inlets.

Are there similar power metrics for AC power outlets ? =

 

Thanks

Mouli

 

 

 
______________________________________________=
_
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




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

------_=_NextPart_001_01CC3029.0DFAEB4B-- From bclaise@cisco.com Tue Jun 21 08:45:11 2011 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 8360711E8284 for ; Tue, 21 Jun 2011 08:45:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.156 X-Spam-Level: X-Spam-Status: No, score=-2.156 tagged_above=-999 required=5 tests=[AWL=-0.442, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aRglLYOV2xw4 for ; Tue, 21 Jun 2011 08:45:10 -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 E754811E8288 for ; Tue, 21 Jun 2011 08:45:08 -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 p5LFfMFq028100; Tue, 21 Jun 2011 17:41:22 +0200 (CEST) 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 p5LFfIId003764; Tue, 21 Jun 2011 17:41:19 +0200 (CEST) Message-ID: <4E00BB9F.8040406@cisco.com> Date: Tue, 21 Jun 2011 17:41:19 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: Michael Suchoff References: <4E0093A2.4010907@cisco.com> <9C329342B62B87498B92834DEC9FF51E0CFA68FC@fig.raritan.com> In-Reply-To: <9C329342B62B87498B92834DEC9FF51E0CFA68FC@fig.raritan.com> Content-Type: multipart/alternative; boundary="------------090103070804050803050905" Cc: eman@ietf.org Subject: Re: [eman] AC power measurements for output 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, 21 Jun 2011 15:45:11 -0000 This is a multi-part message in MIME format. --------------090103070804050803050905 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Michael, Great. So AC power quality for power outlet should be part of the EMAN requirements. Regards, Benoit. > > In the AC power distribution units Raritan (and other vendors) > manufactures, we report metrics for all outlets, the inlet(s) and > circuit breakers. > > By monitoring the outlet, we can report whether the device connected > to it is operating correctly. > > By monitoring the inlet we can report the power quality being received > by the PDU and report how close current is to tripping upstream breaker. > > By monitoring the circuit breakers, we can report whether any is > tripped and how close current flow is to tripping the breaker. > > ------------------------------------------------------------------------ > > *From:*eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] *On Behalf > Of *Bruce Nordman > *Sent:* Tuesday, June 21, 2011 11:30 AM > *To:* Benoit Claise > *Cc:* eman@ietf.org > *Subject:* Re: [eman] AC power measurements for output > > I'm not an engineer, but my understanding is that these metrics are for > the flow of electricity through a wire. An inlet or outlet by itself > would > not have any flow. > If this is correct, I don't think we need to make a distinction. > > --Bruce > > On Tue, Jun 21, 2011 at 5:50 AM, Benoit Claise > wrote: > > Hi, > > Most importantly, are they any requirements to report the power > quality for power outlets? > Maybe in the Smart PDU? > > Regards, Benoit. > > Hello, > > There are metrics for AC power on quality of power (active power, > reactive power, power factor ...) for AC power inlets. > > Are there similar power metrics for AC power outlets ? > > Thanks > > Mouli > > > _______________________________________________ > 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 > > > > > -- > *Bruce Nordman* > Lawrence Berkeley National Laboratory > eetd.lbl.gov/ea/nordman > BNordman@LBL.gov > 510-486-7089 > m: 510-501-7943 > --------------090103070804050803050905 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Michael,

Great. So AC power quality for power outlet should be part of the EMAN requirements.

Regards, Benoit.

In the AC power distribution units Raritan (and other vendors) manufactures, we report metrics for all outlets, the inlet(s) and circuit breakers.

 

By monitoring the outlet, we can report whether the device connected to it is operating correctly.

 

By monitoring the inlet we can report the power quality being received by the PDU and report how close current is to tripping upstream breaker.

 

 By monitoring the circuit breakers, we can report whether any is tripped and how close current flow is to tripping the breaker.

 

 

From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of Bruce Nordman
Sent: Tuesday, June 21, 2011 11:30 AM
To: Benoit Claise
Cc: eman@ietf.org
Subject: Re: [eman] AC power measurements for output

 

I'm not an engineer, but my understanding is that these metrics are for
the flow of electricity through a wire.  An inlet or outlet by itself would
not have any flow.
  If this is correct, I don't think we need to make a distinction.

--Bruce

On Tue, Jun 21, 2011 at 5:50 AM, Benoit Claise <bclaise@cisco.com> wrote:

Hi,

Most importantly, are they any requirements to report the power quality for power outlets?
Maybe in the Smart PDU?

Regards, Benoit.

Hello,

 

There are metrics for AC power on quality of power (active power, reactive power, power factor …) for AC power inlets.

Are there similar power metrics for AC power outlets ?

 

Thanks

Mouli

 

 

 
_______________________________________________
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




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


--------------090103070804050803050905-- From jinchoe@gmail.com Tue Jun 21 23:02:02 2011 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 410F221F8579 for ; Tue, 21 Jun 2011 23:02:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3P+TmacB-7lC for ; Tue, 21 Jun 2011 23:02:01 -0700 (PDT) Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id C643421F856F for ; Tue, 21 Jun 2011 23:02:01 -0700 (PDT) Received: by pwj5 with SMTP id 5so419240pwj.31 for ; Tue, 21 Jun 2011 23:02:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=afVYna0Nf6B/Eame6nYdkwiaxVpbHxwF0fD3i0vfQFQ=; b=ur+QvJtY+p7rDoutMpYkvA0K9/UcgH8xyArHoAd1120pi6m+Y06/h3MtPBuics2l8L xD2jdDKnYH7eLUz4tBDKtiDzsB454flaXLtiAd5A7A2ncKNjB9YDBt9WcmwPuRv7aPWG MtrZ7t3y0WNldCFKYWt0doJcytU0aOZLBzGLo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=akUD0YSCf702hew1/qWso1OtH9EtftdBFslWzUlJWdGGaHV3WdoKpfxoABcbHhs4VN iSR7VA85DnQhjHVrPqrc9qjT9YbN2CQgYmTp2t8RUbTnJ0qMD5dIalApOMrx7Dukd5iM KPDD7VAGrzEPQrCUONBXe8gH43+Nq9IVFMq1Y= MIME-Version: 1.0 Received: by 10.68.66.101 with SMTP id e5mr105782pbt.239.1308722521300; Tue, 21 Jun 2011 23:02:01 -0700 (PDT) Received: by 10.68.59.138 with HTTP; Tue, 21 Jun 2011 23:02:01 -0700 (PDT) Date: Wed, 22 Jun 2011 15:02:01 +0900 Message-ID: From: JinHyeock Choi To: Benoit Claise Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: eman mailing list Subject: [eman] Framework I-D Update? 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, 22 Jun 2011 06:02:02 -0000 Hi I wonder how the framework document is going. At Prague meeting, I got the impression that Juerguen's draft =91Reference Model for Energy Management (draft-quittek-eman-reference-mode= l-01)=92 would be incorporated into the framework, right? I=92d like to have a look on the updated framework. Best regards JinHyeock From bclaise@cisco.com Wed Jun 22 07:53:09 2011 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 B237C11E807A for ; Wed, 22 Jun 2011 07:53:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.536 X-Spam-Level: X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[AWL=0.063, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q0TEd93+qM00 for ; Wed, 22 Jun 2011 07:53:09 -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 EC5CF228005 for ; Wed, 22 Jun 2011 07:53:08 -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 p5MEr6Vu003678; Wed, 22 Jun 2011 16:53:06 +0200 (CEST) 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 p5MEr5uc020993; Wed, 22 Jun 2011 16:53:05 +0200 (CEST) Message-ID: <4E0201D1.5030204@cisco.com> Date: Wed, 22 Jun 2011 16:53:05 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: JinHyeock Choi References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Cc: eman mailing list Subject: Re: [eman] Framework I-D Update? -> EMAN Document Status 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, 22 Jun 2011 14:53:09 -0000 Hi JinHyeock, Thanks for the follow up. Actually, we haven't seen much activity on the mailing list recently. Historically, this is very typical of the IETF where there is a peak of discussions before the deadlines ;-), but that's not really an excuse! We would like to request a quick update from the primary editor(s) on each of the document: requirements, framework, energy-aware mib, energy monitoring mib, battery mib, and applicability. This update should ideally contain a status update, current progress, expected date for a draft new version, etc... Regards, Bruce and Benoit. > Hi > > I wonder how the framework document is going. > > At Prague meeting, I got the impression that Juerguen's draft > ‘Reference Model for Energy Management (draft-quittek-eman-reference-model-01)’ > would be incorporated into the framework, right? > > I’d like to have a look on the updated framework. > > Best regards > > JinHyeock From jparello@cisco.com Wed Jun 22 09:39:03 2011 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 F3B8311E8127 for ; Wed, 22 Jun 2011 09:39:02 -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=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q8SeLdhdgABi for ; Wed, 22 Jun 2011 09:39:02 -0700 (PDT) Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by ietfa.amsl.com (Postfix) with ESMTP id 1346411E80E6 for ; Wed, 22 Jun 2011 09:39:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jparello@cisco.com; l=4115; q=dns/txt; s=iport; t=1308760741; x=1309970341; h=mime-version:subject:date:message-id:references:from:to: cc; bh=r506Ns55+wqkJY/wgsPtd+/Hi7c+uBFYd9Jslo7wyGk=; b=iTBRmU7vTT+2GrGcuFKX65OmU2Xu1KH/8ZGkDUr/1tnQG+dN+qFcxJCI 7PRtVHE2I7Lbj6Pjs17RDBexRHLzji29K41SUmZmSlRuWlnpNmt4y/c9i EKU4WB5/QuJRti/bYN1GhNdxLYTFk5mlbheJuOgcFUa6vo4s/FFDnPvfv A=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0EANcZAk6rRDoG/2dsb2JhbABUpxB3iHOhLp5Mhi0EhyWPM4s+ X-IronPort-AV: E=Sophos;i="4.65,407,1304294400"; d="scan'208,217";a="719663453" Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-6.cisco.com with ESMTP; 22 Jun 2011 16:39:01 +0000 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p5MGd1Hb012211; Wed, 22 Jun 2011 16:39:01 GMT Received: from xmb-sjc-21b.amer.cisco.com ([171.70.151.143]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 22 Jun 2011 09:39:01 -0700 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_01CC30FA.E3C5BE8F" Date: Wed, 22 Jun 2011 09:37:57 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [eman] Framework I-D Update? -> EMAN Document Status Thread-Index: Acww7CPXr6gqDkKDRne59E2OJW/VewADppIY References: <4E0201D1.5030204@cisco.com> From: "John Parello (jparello)" To: "Benoit Claise (bclaise)" , "JinHyeock Choi" X-OriginalArrivalTime: 22 Jun 2011 16:39:01.0333 (UTC) FILETIME=[E4135050:01CC30FA] Cc: eman mailing list Subject: Re: [eman] Framework I-D Update? -> EMAN Document Status 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, 22 Jun 2011 16:39:03 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01CC30FA.E3C5BE8F Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable For the EMAN-FRAMEWORK we have gone through 5 revisions amongst the = authors. We are converging and should be publishing within a week or so = to the list. Jp -----Original Message----- From: eman-bounces@ietf.org on behalf of Benoit Claise (bclaise) Sent: Wed 6/22/2011 7:53 AM To: JinHyeock Choi Cc: eman mailing list Subject: Re: [eman] Framework I-D Update? -> EMAN Document Status =20 Hi JinHyeock, Thanks for the follow up. Actually, we haven't seen much activity on the mailing list recently.=20 Historically, this is very typical of the IETF where there is a peak of=20 discussions before the deadlines ;-), but that's not really an excuse! We would like to request a quick update from the primary editor(s) on=20 each of the document: requirements, framework, energy-aware mib, energy=20 monitoring mib, battery mib, and applicability. This update should=20 ideally contain a status update, current progress, expected date for a=20 draft new version, etc... Regards, Bruce and Benoit. > Hi > > I wonder how the framework document is going. > > At Prague meeting, I got the impression that Juerguen's draft > 'Reference Model for Energy Management = (draft-quittek-eman-reference-model-01)' > would be incorporated into the framework, right? > > I'd like to have a look on the updated framework. > > Best regards > > JinHyeock _______________________________________________ eman mailing list eman@ietf.org https://www.ietf.org/mailman/listinfo/eman ------_=_NextPart_001_01CC30FA.E3C5BE8F Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [eman] Framework I-D Update? -> EMAN Document = Status

For the EMAN-FRAMEWORK we have gone through 5 = revisions amongst the authors. We are converging and should be = publishing within a week or so to the list.

Jp
-----Original Message-----
From: eman-bounces@ietf.org on behalf of Benoit Claise (bclaise)
Sent: Wed 6/22/2011 7:53 AM
To: JinHyeock Choi
Cc: eman mailing list
Subject: Re: [eman] Framework I-D Update? -> EMAN Document Status

Hi JinHyeock,

Thanks for the follow up.
Actually, we haven't seen much activity on the mailing list = recently.
Historically, this is very typical of the IETF where there is a peak = of
discussions before the deadlines ;-), but that's not really an = excuse!

We would like to request a quick update from the primary editor(s) = on
each of the document: requirements, framework, energy-aware mib, = energy
monitoring mib, battery mib, and applicability. This update should
ideally contain a status update, current progress, expected date for = a
draft new version, etc...

Regards, Bruce and Benoit.

> Hi
>
> I wonder how the framework document is going.
>
> At Prague meeting, I got the impression that Juerguen's draft
> 'Reference Model for Energy Management = (draft-quittek-eman-reference-model-01)'
> would be incorporated into the framework, right?
>
> I'd like to have a look on the updated framework.
>
> Best regards
>
> JinHyeock

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

------_=_NextPart_001_01CC30FA.E3C5BE8F-- From jinchoe@gmail.com Wed Jun 22 18:13:21 2011 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 14EBF21F85A3 for ; Wed, 22 Jun 2011 18:13:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kDE30LvtDvZV for ; Wed, 22 Jun 2011 18:13:20 -0700 (PDT) Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 82F0121F85A1 for ; Wed, 22 Jun 2011 18:13:20 -0700 (PDT) Received: by pwj5 with SMTP id 5so1009174pwj.31 for ; Wed, 22 Jun 2011 18:13:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=48p2f3k2Dq8+3EUGtIIzqvmbNCDEbVz9a6RW7HCzWBU=; b=jS7l+c7FYS9a/qbMfsDRu9x7nGklafR0yrKopRjLGNfLmgrsYd4DHLldvYrncSeNIQ yygNwz79BbjZ6Hzd8KMDEpZKjz06Z7yJu/hwJmK6uSSDMLu20a+dbP9HDb6Z+Vrmttal ApoPTFGXwRsihGU0UTpZDMM3YKXGfS9uFJhgc= 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; b=huzXTuudu/vw87Z+Osz/++PwQMme/TTa9YrtyyrC+wwtWVPCUaMbZ69zJqgVSgJwsI Enfkg0AFCJo8FJQoERgSgMvugmNIIubVSyay8nLR6XXlD0wWY6uNBu8bGFwV1EluxUSE rxlF6nz8HReCGqpAi3l6RK3P2AIl1JAX/PNIk= MIME-Version: 1.0 Received: by 10.68.36.135 with SMTP id q7mr860636pbj.38.1308791600058; Wed, 22 Jun 2011 18:13:20 -0700 (PDT) Received: by 10.68.59.138 with HTTP; Wed, 22 Jun 2011 18:13:20 -0700 (PDT) In-Reply-To: References: <4E0201D1.5030204@cisco.com> Date: Thu, 23 Jun 2011 10:13:20 +0900 Message-ID: From: JinHyeock Choi To: "John Parello (jparello)" Content-Type: text/plain; charset=ISO-8859-1 Cc: eman mailing list Subject: Re: [eman] Framework I-D Update? -> EMAN Document Status 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, 23 Jun 2011 01:13:21 -0000 John thanks for an update on the update. best regards with great expectation. JinHyeock On Thu, Jun 23, 2011 at 1:37 AM, John Parello (jparello) wrote: > > > For the EMAN-FRAMEWORK we have gone through 5 revisions amongst the authors. > We are converging and should be publishing within a week or so to the list. > > Jp > > -----Original Message----- > From: eman-bounces@ietf.org on behalf of Benoit Claise (bclaise) > Sent: Wed 6/22/2011 7:53 AM > To: JinHyeock Choi > Cc: eman mailing list > Subject: Re: [eman] Framework I-D Update? -> EMAN Document Status > > Hi JinHyeock, > > Thanks for the follow up. > Actually, we haven't seen much activity on the mailing list recently. > Historically, this is very typical of the IETF where there is a peak of > discussions before the deadlines ;-), but that's not really an excuse! > > We would like to request a quick update from the primary editor(s) on > each of the document: requirements, framework, energy-aware mib, energy > monitoring mib, battery mib, and applicability. This update should > ideally contain a status update, current progress, expected date for a > draft new version, etc... > > Regards, Bruce and Benoit. > >> Hi >> >> I wonder how the framework document is going. >> >> At Prague meeting, I got the impression that Juerguen's draft >> 'Reference Model for Energy Management >> (draft-quittek-eman-reference-model-01)' >> would be incorporated into the framework, right? >> >> I'd like to have a look on the updated framework. >> >> Best regards >> >> JinHyeock > > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman > > From moulchan@cisco.com Wed Jun 22 23:46:26 2011 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 AD24A21F8541 for ; Wed, 22 Jun 2011 23:46:26 -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=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Evzuq5YycyC5 for ; Wed, 22 Jun 2011 23:46:25 -0700 (PDT) Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id D502A21F8540 for ; Wed, 22 Jun 2011 23:46:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=moulchan@cisco.com; l=1758; q=dns/txt; s=iport; t=1308811585; x=1310021185; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=y7U6UCWHsGLGPFTYqPKgzJ/2jbqNux0XMbVQZJ7N4zE=; b=Lc+UettAljA/A008roJd7bOIBdSj1R1bHZOxIkI7G2L//gcsOk/AS3Ml jUNkvm8aVcTJY8yDRu6CSdNXe1IayB3BOFBAtNT/9A8P95yzc0HkqvrcN 0UyJ+x7cTUjdvpfKJ1jHgEEgg3y4QeDYTUTeeW0qne72rmeSVFID47Afn Y=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvEAAIjgAk6tJV2Z/2dsb2JhbABTmASPGXeIc6MQnjOGLQSHJo86iz0 X-IronPort-AV: E=Sophos;i="4.65,411,1304294400"; d="scan'208";a="344808940" Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by sj-iport-3.cisco.com with ESMTP; 23 Jun 2011 06:46:25 +0000 Received: from xbh-rcd-302.cisco.com (xbh-rcd-302.cisco.com [72.163.63.9]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p5N6kPnk003150; Thu, 23 Jun 2011 06:46:25 GMT Received: from xmb-rcd-106.cisco.com ([72.163.62.148]) by xbh-rcd-302.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 23 Jun 2011 01:46:24 -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: Thu, 23 Jun 2011 01:46:22 -0500 Message-ID: In-Reply-To: <4E0201D1.5030204@cisco.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [eman] EMAN Document Status Thread-Index: Acww7CMLNWitmWSsRgGoHoftwZ84bwAhER0w References: <4E0201D1.5030204@cisco.com> From: "Mouli Chandramouli (moulchan)" To: "Benoit Claise (bclaise)" , "JinHyeock Choi" X-OriginalArrivalTime: 23 Jun 2011 06:46:24.0957 (UTC) FILETIME=[453CA6D0:01CC3171] Cc: eman mailing list Subject: Re: [eman] EMAN Document Status 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, 23 Jun 2011 06:46:26 -0000 Hello, We had submitted an updated version of the EMAN Monitoring MIB draft on May 24th.=20 http://www.ietf.org/mail-archive/web/eman/current/msg00506.html Juergen Schoenwaelder had provided review comments. We are requesting feedback from others.=20 We may submit a revised version of this draft before IETF deadline based on feedback.=20 Thanks Mouli -----Original Message----- From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of Benoit Claise (bclaise) Sent: Wednesday, June 22, 2011 8:23 PM To: JinHyeock Choi Cc: eman mailing list Subject: Re: [eman] Framework I-D Update? -> EMAN Document Status Hi JinHyeock, Thanks for the follow up. Actually, we haven't seen much activity on the mailing list recently.=20 Historically, this is very typical of the IETF where there is a peak of=20 discussions before the deadlines ;-), but that's not really an excuse! We would like to request a quick update from the primary editor(s) on=20 each of the document: requirements, framework, energy-aware mib, energy=20 monitoring mib, battery mib, and applicability. This update should=20 ideally contain a status update, current progress, expected date for a=20 draft new version, etc... Regards, Bruce and Benoit. > Hi > > I wonder how the framework document is going. > > At Prague meeting, I got the impression that Juerguen's draft > 'Reference Model for Energy Management (draft-quittek-eman-reference-model-01)' > would be incorporated into the framework, right? > > I'd like to have a look on the updated framework. > > Best regards > > JinHyeock _______________________________________________ eman mailing list eman@ietf.org https://www.ietf.org/mailman/listinfo/eman From jparello@cisco.com Thu Jun 23 01:46:04 2011 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 5692511E809E for ; Thu, 23 Jun 2011 01:46:04 -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=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1yu7fLF6mjcs for ; Thu, 23 Jun 2011 01:46:03 -0700 (PDT) Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by ietfa.amsl.com (Postfix) with ESMTP id BBA2411E807D for ; Thu, 23 Jun 2011 01:46:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jparello@cisco.com; l=4458; q=dns/txt; s=iport; t=1308818763; x=1310028363; h=mime-version:subject:date:message-id:references:from:to: cc; bh=cTifJE60O0CovRxL7l+K9E4JilWeVydE1GKo3ugdd6M=; b=Iv+fu6uIJdEG6CFv2edGhSx2GpK2lsiDONGN4xmxxvoxVUXwCAwbbLJD QWBKqdGx9NnzunQLtYNPQBBasnV31/3W5oExgmEB7Cw09b5v11CdEDb2j gcswrs5wdJv6shx0Y/fPKic4RVWORm4B07UzceTFYESD03r+z5+hEybSF k=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0EALj8Ak6rRDoG/2dsb2JhbABTpx53iHOidp4shi0EhyaPOotA X-IronPort-AV: E=Sophos;i="4.65,412,1304294400"; d="scan'208,217";a="344911508" Received: from mtv-core-1.cisco.com ([171.68.58.6]) by sj-iport-3.cisco.com with ESMTP; 23 Jun 2011 08:46:03 +0000 Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p5N8k3XX002459; Thu, 23 Jun 2011 08:46:03 GMT Received: from xmb-sjc-21b.amer.cisco.com ([171.70.151.143]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 23 Jun 2011 01:46:02 -0700 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_01CC3181.FB1630F4" Date: Thu, 23 Jun 2011 01:44:10 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [eman] Framework I-D Update? -> EMAN Document Status Thread-Index: Acww7CPXr6gqDkKDRne59E2OJW/VewAlZSws References: <4E0201D1.5030204@cisco.com> From: "John Parello (jparello)" To: "Benoit Claise (bclaise)" , "JinHyeock Choi" X-OriginalArrivalTime: 23 Jun 2011 08:46:02.0472 (UTC) FILETIME=[FB5E8680:01CC3181] Cc: eman mailing list Subject: Re: [eman] Framework I-D Update? -> EMAN Document Status 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, 23 Jun 2011 08:46:04 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01CC3181.FB1630F4 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, Also for the authors (myself included) are reviewing = draft-ietf-eman-energy-aware. As soon there is a new version of = requirements out, it will be updated and posted. IF anyone has comments on this draft that would be helpful to get them = so we can incorporate them before the next deadline. Thanks Jp -----Original Message----- From: eman-bounces@ietf.org on behalf of Benoit Claise (bclaise) Sent: Wed 6/22/2011 7:53 AM To: JinHyeock Choi Cc: eman mailing list Subject: Re: [eman] Framework I-D Update? -> EMAN Document Status =20 Hi JinHyeock, Thanks for the follow up. Actually, we haven't seen much activity on the mailing list recently.=20 Historically, this is very typical of the IETF where there is a peak of=20 discussions before the deadlines ;-), but that's not really an excuse! We would like to request a quick update from the primary editor(s) on=20 each of the document: requirements, framework, energy-aware mib, energy=20 monitoring mib, battery mib, and applicability. This update should=20 ideally contain a status update, current progress, expected date for a=20 draft new version, etc... Regards, Bruce and Benoit. > Hi > > I wonder how the framework document is going. > > At Prague meeting, I got the impression that Juerguen's draft > 'Reference Model for Energy Management = (draft-quittek-eman-reference-model-01)' > would be incorporated into the framework, right? > > I'd like to have a look on the updated framework. > > Best regards > > JinHyeock _______________________________________________ eman mailing list eman@ietf.org https://www.ietf.org/mailman/listinfo/eman ------_=_NextPart_001_01CC3181.FB1630F4 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [eman] Framework I-D Update? -> EMAN Document = Status

Hi,

Also for the authors (myself included) are reviewing = draft-ietf-eman-energy-aware.  As soon there is a new version of = requirements out, it will be updated and posted.

IF anyone has comments on this draft that would be helpful to get them = so we can incorporate them before the next deadline.

Thanks
Jp


-----Original Message-----
From: eman-bounces@ietf.org on behalf of Benoit Claise (bclaise)
Sent: Wed 6/22/2011 7:53 AM
To: JinHyeock Choi
Cc: eman mailing list
Subject: Re: [eman] Framework I-D Update? -> EMAN Document Status

Hi JinHyeock,

Thanks for the follow up.
Actually, we haven't seen much activity on the mailing list = recently.
Historically, this is very typical of the IETF where there is a peak = of
discussions before the deadlines ;-), but that's not really an = excuse!

We would like to request a quick update from the primary editor(s) = on
each of the document: requirements, framework, energy-aware mib, = energy
monitoring mib, battery mib, and applicability. This update should
ideally contain a status update, current progress, expected date for = a
draft new version, etc...

Regards, Bruce and Benoit.

> Hi
>
> I wonder how the framework document is going.
>
> At Prague meeting, I got the impression that Juerguen's draft
> 'Reference Model for Energy Management = (draft-quittek-eman-reference-model-01)'
> would be incorporated into the framework, right?
>
> I'd like to have a look on the updated framework.
>
> Best regards
>
> JinHyeock

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

------_=_NextPart_001_01CC3181.FB1630F4-- From Michael.Suchoff@raritan.com Fri Jun 24 12:28:12 2011 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 1FFC211E80BE for ; Fri, 24 Jun 2011 12:28:12 -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=[AWL=0.001, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NHtwq1C4Qyvs for ; Fri, 24 Jun 2011 12:28:11 -0700 (PDT) Received: from fig.raritan.com (fig.raritan.com [12.144.63.197]) by ietfa.amsl.com (Postfix) with ESMTP id 6E4A611E8084 for ; Fri, 24 Jun 2011 12:28:09 -0700 (PDT) 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: Fri, 24 Jun 2011 15:24:18 -0400 Message-ID: <9C329342B62B87498B92834DEC9FF51E0D01072C@fig.raritan.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [eman] EMAN Document Status Thread-Index: Acww7CMLNWitmWSsRgGoHoftwZ84bwAhER0wAEzIsyA= References: <4E0201D1.5030204@cisco.com> From: "Michael Suchoff" To: "Mouli Chandramouli \(moulchan\)" , "Benoit Claise \(bclaise\)" , "JinHyeock Choi" Cc: eman mailing list Subject: Re: [eman] EMAN Document Status 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, 24 Jun 2011 19:28:12 -0000 In prior e-mail, I made suggestions to correct the errors pertaining to the AC measurement portions of the MIB. None of these suggestions were acted on. Therefore, the MIB is not very useful for reporting AC measurements and I would not recommend it as an IETF standard. -----Original Message----- From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of Mouli Chandramouli (moulchan) Sent: Thursday, June 23, 2011 2:46 AM To: Benoit Claise (bclaise); JinHyeock Choi Cc: eman mailing list Subject: Re: [eman] EMAN Document Status Hello, We had submitted an updated version of the EMAN Monitoring MIB draft on May 24th.=20 http://www.ietf.org/mail-archive/web/eman/current/msg00506.html Juergen Schoenwaelder had provided review comments. We are requesting feedback from others.=20 We may submit a revised version of this draft before IETF deadline based on feedback.=20 Thanks Mouli -----Original Message----- From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of Benoit Claise (bclaise) Sent: Wednesday, June 22, 2011 8:23 PM To: JinHyeock Choi Cc: eman mailing list Subject: Re: [eman] Framework I-D Update? -> EMAN Document Status Hi JinHyeock, Thanks for the follow up. Actually, we haven't seen much activity on the mailing list recently.=20 Historically, this is very typical of the IETF where there is a peak of=20 discussions before the deadlines ;-), but that's not really an excuse! We would like to request a quick update from the primary editor(s) on=20 each of the document: requirements, framework, energy-aware mib, energy=20 monitoring mib, battery mib, and applicability. This update should=20 ideally contain a status update, current progress, expected date for a=20 draft new version, etc... Regards, Bruce and Benoit. > Hi > > I wonder how the framework document is going. > > At Prague meeting, I got the impression that Juerguen's draft > 'Reference Model for Energy Management (draft-quittek-eman-reference-model-01)' > would be incorporated into the framework, right? > > I'd like to have a look on the updated framework. > > Best regards > > JinHyeock _______________________________________________ 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 etychon@cisco.com Fri Jun 24 14:13:03 2011 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 9FA2F11E8073 for ; Fri, 24 Jun 2011 14:13:03 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iMtLR-+2F52x for ; Fri, 24 Jun 2011 14:13:02 -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 E2C0C228011 for ; Fri, 24 Jun 2011 14:13:01 -0700 (PDT) X-TACSUNS: Virus Scanned Received: from stew-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 p5OL9F7v001151 for ; Fri, 24 Jun 2011 23:09:15 +0200 (CEST) Received: from ams3-vpn-dhcp5208.cisco.com (ams3-vpn-dhcp5208.cisco.com [10.61.84.87]) by stew-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p5OL9CE2015519 for ; Fri, 24 Jun 2011 23:09:13 +0200 (CEST) From: Emmanuel Tychon Content-Type: multipart/alternative; boundary=Apple-Mail-13--69928525 Date: Fri, 24 Jun 2011 23:09:13 +0200 Message-Id: To: eman@ietf.org Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) Subject: [eman] draft-tychon-eman-applicability-statement-02.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, 24 Jun 2011 21:13:03 -0000 --Apple-Mail-13--69928525 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii A major revision of the EMAN-AS applicability statement draft has been = posted.=20 Here's the link to the new version: http://tools.ietf.org/html/draft-tychon-eman-applicability-statement-02=20= The diff can be viewed here: = http://tools.ietf.org/rfcdiff?difftype=3D--hwdiff&url2=3Ddraft-tychon-eman= -applicability-statement-02.txt Changes: - A new section on Use cases with examples and target devices in the = scope of EMAN has been included.=20 - A section of use case contexts as an abstraction of the example = scenarios is included These two sections can be useful to continue the discussion from the = EMAN WG discussion @ Prague = http://www.ietf.org/proceedings/80/minutes/eman.txt - Can Entity MIB be used to model the EMAN scenarios ? =20 - The relevant standards for EMAN have been updated with information = on how these standards have been reused and also how these influence = EMAN is presented - The introduction section has been reorganized and would make it = easier for a relative newcomer to understand and participate in the = Energy work @ EMAN WG. - Many rewording to improve readability Your comments are welcome. Thanks, Emmanuel, Mouli, and Brad --Apple-Mail-13--69928525 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii

A major revision of the = EMAN-AS applicability statement draft has been = posted. 

Here's the link to the new version:

The = diff can be viewed here:

Changes:

-    A new section on Use cases = with examples and target devices in the scope of EMAN has been = included. 

-    A section of use case contexts = as an abstraction of the example scenarios is = included

   These = two sections can be useful to continue the discussion from the EMAN WG = discussion @ Prague  http://www.ietf.org/proceedings/80/minutes/eman.txt

-    Can Entity MIB be used to = model the EMAN scenarios ?  

-    The relevant standards for = EMAN have been updated with information on how these standards have been = reused and also how these influence EMAN is = presented

-    The introduction section has = been reorganized and would make it easier for a relative newcomer to = understand and participate in the Energy work @ EMAN = WG.

-    Many = rewording to improve readability

Your comments are welcome.

Thanks,

Emmanuel, Mouli, and = Brad


= --Apple-Mail-13--69928525-- From ramorgan@ra.rockwell.com Sat Jun 25 14:06:01 2011 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 1C74011E80C8 for ; Sat, 25 Jun 2011 14:06:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.263 X-Spam-Level: X-Spam-Status: No, score=-0.263 tagged_above=-999 required=5 tests=[AWL=0.026, BAYES_00=-2.599, SARE_URGBIZ=0.725, URG_BIZ=1.585] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j6-Uk3M73e33 for ; Sat, 25 Jun 2011 14:06:00 -0700 (PDT) Received: from ramilwsmtp01.ra.rockwell.com (ramkesd003-e.ra.rockwell.com [205.175.240.251]) by ietfa.amsl.com (Postfix) with ESMTP id A386B11E80AC for ; Sat, 25 Jun 2011 14:06:00 -0700 (PDT) Auto-Submitted: auto-generated From: Rich A Morgan To: eman@ietf.org Message-ID: Date: Sat, 25 Jun 2011 16:05:59 -0500 X-MIMETrack: Serialize by Router on RAMilwSMTP01/Milwaukee/RA/Rockwell(Release 8.5.2FP1|November 29, 2010) at 06/25/2011 04:06:00 PM MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Subject: [eman] Rich A Morgan is out of the office 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, 25 Jun 2011 21:06:01 -0000 I will be out of the office starting 06/24/2011 and will not return until 06/29/2011. I will be checking email in the evenings for urgent business. From internet-drafts@ietf.org Mon Jun 27 08:02:42 2011 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 E93E91F0C3E; Mon, 27 Jun 2011 08:02:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.406 X-Spam-Level: X-Spam-Status: No, score=-102.406 tagged_above=-999 required=5 tests=[AWL=0.193, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YKvS-acfuyxR; Mon, 27 Jun 2011 08:02:42 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9397B1F0C35; Mon, 27 Jun 2011 08:02:42 -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: 3.55 Message-ID: <20110627150242.10690.77805.idtracker@ietfa.amsl.com> Date: Mon, 27 Jun 2011 08:02:42 -0700 Cc: eman@ietf.org Subject: [eman] I-D Action: draft-ietf-eman-battery-mib-01.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, 27 Jun 2011 15:02:43 -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 th= e IETF. Title : Definition of Managed Objects for Battery Monitoring Author(s) : Juergen Quittek Rolf Winter Thomas Dietz Filename : draft-ietf-eman-battery-mib-01.txt Pages : 24 Date : 2011-06-27 This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines managed objects that provide information on the status of batteries in managed devices. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-eman-battery-mib-01.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-eman-battery-mib-01.txt From Rolf.Winter@neclab.eu Mon Jun 27 08:07:58 2011 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 693D01F0C47 for ; Mon, 27 Jun 2011 08:07:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.924 X-Spam-Level: X-Spam-Status: No, score=-101.924 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R21tiHqABg9q for ; Mon, 27 Jun 2011 08:07:58 -0700 (PDT) Received: from smtp0.netlab.nec.de (smtp0.netlab.nec.de [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 0F8721F0C4D for ; Mon, 27 Jun 2011 08:07:19 -0700 (PDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.netlab.nec.de (Postfix) with ESMTP id 78D4C2800022E for ; Mon, 27 Jun 2011 17:07:18 +0200 (CEST) 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 5w9Mj65eFRpM for ; Mon, 27 Jun 2011 17:07:18 +0200 (CEST) Received: from METHONE.office.hd (Methone.office.hd [192.168.24.54]) by smtp0.netlab.nec.de (Postfix) with ESMTP id 5D5272800022A for ; Mon, 27 Jun 2011 17:07:13 +0200 (CEST) Received: from Polydeuces.office.hd ([169.254.3.115]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0270.001; Mon, 27 Jun 2011 17:07:10 +0200 From: Rolf Winter To: eman mailing list Thread-Topic: new Battery MIB version Thread-Index: Acw02+KK8iZRIupCQgikVwXnrrC3Ug== Date: Mon, 27 Jun 2011 15:07:09 +0000 Message-ID: <791AD3077F94194BB2BDD13565B6295D13B69A0C@Polydeuces.office.hd> Accept-Language: en-US, de-DE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.6.28] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [eman] new Battery MIB version 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, 27 Jun 2011 15:07:58 -0000 Hi, We just posted a new version of the Battery MIB I-D. Please find it at http://www.ietf.org/internet-drafts/draft-ietf-eman-batte= ry-mib-01.txt We added objects providing a battery ID and a firmware version in this upda= te of the draft. Here are the remaining open issues: 1. Define Charging Cycle 2. Writable Notification thresholds 3. Re-arming batteryLowNotification 4. Add Charging Data of Batteries? 5. Add batteryHealth? So far we have not received much feedback on the issues. Please help us solving them. Regarding issue 1. we have not found a common definition for a charging cyc= le. The new version has some definition from Apple but maybe it is best to = leave this manufacturer definable and only specify one in case the manufact= urer does not define one. Other opinions? Regarding issue 4. we propose to not include properties such as boost volta= ge as these seem to be relevant to the local charger but less so for monito= ring purposes. Feedback on all open issues and the document as such are of course highly w= elcome. If you could provide feedback on the draft soon, then we might be a= ble to create another updated version just before the cut-off. Best, The authors NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London = W3 6BL | Registered in England 2832014=20 From SChew@bren-tronics.com Tue Jun 28 12:05:30 2011 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 D847A11E811C for ; Tue, 28 Jun 2011 12:05:30 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZBGhm-fL2Nxw for ; Tue, 28 Jun 2011 12:05:29 -0700 (PDT) Received: from EXHUB018-2.exch018.msoutlookonline.net (exhub018-2.exch018.msoutlookonline.net [64.78.17.17]) by ietfa.amsl.com (Postfix) with ESMTP id AA3FB21F856F for ; Tue, 28 Jun 2011 12:05:29 -0700 (PDT) Received: from EXVMBX018-1.exch018.msoutlookonline.net ([64.78.17.47]) by EXHUB018-2.exch018.msoutlookonline.net ([64.78.17.17]) with mapi; Tue, 28 Jun 2011 12:05:29 -0700 From: Steven Chew To: "eman@ietf.org" Date: Tue, 28 Jun 2011 12:05:27 -0700 Thread-Topic: Charge Cycle Definition Thread-Index: Acw1xJSZC+EOOVoHR3G1p9ABqQ3f2w== Message-ID: <0BB24042CB683840B986F84BC859CFB569F09099FA@EXVMBX018-1.exch018.msoutlookonline.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_0BB24042CB683840B986F84BC859CFB569F09099FAEXVMBX0181exc_" MIME-Version: 1.0 Subject: [eman] Charge Cycle Definition 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, 28 Jun 2011 19:06:11 -0000 --_000_0BB24042CB683840B986F84BC859CFB569F09099FAEXVMBX0181exc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I would like to comment about "8.1. Define Charging Cycle" in draft-ietf-e= man-battery-mib-01.txt. I think it is good to keep definition in line with that of Apple's, as give= n in the MIB document. Counting the number of times the discharged energy e= qual to the battery's capacity is commonly how battery manufacturers count = charge cycles. I refer to the Smart Battery Data Specification Revision 1.1= 0. 5.1.22. CycleCount() (0x17) Description: Returns the number of cycles the battery has experienced. A cycle is define= d as: An amount of discharge approximately equal to the value of DesignCapacity. Purpose: The CycleCount() function provides a means to determine their battery's wea= r. It may be used to give advanced warning that the battery is nearing its end of life. The CycleCoun= t returned value multiplied by the DesignCapacity value can give an approximate "odometer" reading for the= total capacity delivered by the Smart Battery. SMBus Protocol: Read Word Output: unsigned int -- count of charge/discharge cycles the battery has ex= perienced Units: cycle Range: 0 to 65,534 cycles 65,535 indicates battery has experienced 65,535 or more cycles. Granularity: 1 cycle Accuracy: absolute count This is a quantity already tracked and supplied by Smart Batteries. It woul= d make sense for this MIB to align with this definition. Regards, Steven. --_000_0BB24042CB683840B986F84BC859CFB569F09099FAEXVMBX0181exc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I would like to comment about “8.1.  Define Charging C= ycle” in draft-ietf-eman-battery-mib-01.txt.=

 =

I think it is go= od to keep definition in line with that of Apple’s, as given in the M= IB document. Counting the number of times the discharged energy equal to th= e battery’s capacity is commonly how battery manufacturers count char= ge cycles. I refer to the Smart Battery Data Specification Revision 1.10.

<= o:p> 

5.1.22. CycleCount() (0x17)

Description:

Returns the number of cycles the = battery has experienced. A cycle is defined as:

An amount of discharge approximate= ly equal to the value of DesignCapacity.

Purpose:

The CycleCount() function provid= es a means to determine their battery's wear. It may be used to give

advanced warn= ing that the battery is nearing its end of life. The CycleCount returned va= lue multiplied by

the DesignCapacity value can give an approximate “odometer= ” reading for the total capacity delivered by

the Smart Battery.<= /span>

SMBus Protocol:= Read Word

Output: unsigned int -- count of charge/discharge cycl= es the battery has experienced

Units: cycle

Range: 0 to 65,534 cycles

65,535 indicates battery h= as experienced 65,535 or more

cycles.

Granularity: 1 cycle

Accuracy: absolute count

 

This is a quantity already tracked = and supplied by Smart Batteries. It would make sense for this MIB to align = with this definition.

 

Regards,

S= teven.

= --_000_0BB24042CB683840B986F84BC859CFB569F09099FAEXVMBX0181exc_-- From Rolf.Winter@neclab.eu Tue Jun 28 13:18:10 2011 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 18F7E11E8106 for ; Tue, 28 Jun 2011 13:18:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.989 X-Spam-Level: X-Spam-Status: No, score=-101.989 tagged_above=-999 required=5 tests=[AWL=0.260, BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r+jOefREkpj3 for ; Tue, 28 Jun 2011 13:18:09 -0700 (PDT) Received: from smtp0.netlab.nec.de (smtp0.netlab.nec.de [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 8D76411E80E7 for ; Tue, 28 Jun 2011 13:18:09 -0700 (PDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.netlab.nec.de (Postfix) with ESMTP id E231328000226; Tue, 28 Jun 2011 22:18:08 +0200 (CEST) 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 9oH2iW6aYCqH; Tue, 28 Jun 2011 22:18:08 +0200 (CEST) Received: from ENCELADUS.office.hd (ENCELADUS.office.hd [192.168.24.52]) by smtp0.netlab.nec.de (Postfix) with ESMTP id B6E36280001DB; Tue, 28 Jun 2011 22:17:58 +0200 (CEST) Received: from PALLENE.office.hd ([169.254.1.100]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0270.001; Tue, 28 Jun 2011 22:17:58 +0200 From: Rolf Winter To: Steven Chew , "eman@ietf.org" Thread-Topic: Charge Cycle Definition Thread-Index: Acw1xJSZC+EOOVoHR3G1p9ABqQ3f2wAC6e7Q Date: Tue, 28 Jun 2011 20:17:57 +0000 Message-ID: <791AD3077F94194BB2BDD13565B6295D1C733D1E@PALLENE.office.hd> References: <0BB24042CB683840B986F84BC859CFB569F09099FA@EXVMBX018-1.exch018.msoutlookonline.net> In-Reply-To: <0BB24042CB683840B986F84BC859CFB569F09099FA@EXVMBX018-1.exch018.msoutlookonline.net> Accept-Language: en-US, de-DE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.7.0.201] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [eman] Charge Cycle Definition 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, 28 Jun 2011 20:18:10 -0000 Hi Steven, great input. Thanks a lot. Are you aware of any other definition in use? Best, Rolf 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 > Steven Chew > Sent: Dienstag, 28. Juni 2011 21:05 > To: eman@ietf.org > Subject: [eman] Charge Cycle Definition >=20 > I would like to comment about "8.1. Define Charging Cycle" in draft- > ietf-eman-battery-mib-01.txt. >=20 >=20 >=20 > I think it is good to keep definition in line with that of Apple's, as > given in the MIB document. Counting the number of times the discharged > energy equal to the battery's capacity is commonly how battery > manufacturers count charge cycles. I refer to the Smart Battery Data > Specification Revision 1.10. >=20 >=20 >=20 > 5.1.22. CycleCount() (0x17) >=20 > Description: >=20 > Returns the number of cycles the battery has experienced. A cycle is > defined as: >=20 > An amount of discharge approximately equal to the value of > DesignCapacity. >=20 > Purpose: >=20 > The CycleCount() function provides a means to determine their battery's > wear. It may be used to give >=20 > advanced warning that the battery is nearing its end of life. The > CycleCount returned value multiplied by >=20 > the DesignCapacity value can give an approximate "odometer" reading for > the total capacity delivered by >=20 > the Smart Battery. >=20 > SMBus Protocol: Read Word >=20 > Output: unsigned int -- count of charge/discharge cycles the battery > has experienced >=20 > Units: cycle >=20 > Range: 0 to 65,534 cycles >=20 > 65,535 indicates battery has experienced 65,535 or more >=20 > cycles. >=20 > Granularity: 1 cycle >=20 > Accuracy: absolute count >=20 >=20 >=20 > This is a quantity already tracked and supplied by Smart Batteries. It > would make sense for this MIB to align with this definition. >=20 >=20 >=20 > Regards, >=20 > Steven. From SChew@bren-tronics.com Tue Jun 28 14:56:38 2011 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 DB06211E80F2 for ; Tue, 28 Jun 2011 14:56:38 -0700 (PDT) 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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mnIGkENQclB7 for ; Tue, 28 Jun 2011 14:56:38 -0700 (PDT) Received: from EXHUB018-4.exch018.msoutlookonline.net (exhub018-4.exch018.msoutlookonline.net [64.78.17.19]) by ietfa.amsl.com (Postfix) with ESMTP id 2362C11E80C0 for ; Tue, 28 Jun 2011 14:56:38 -0700 (PDT) Received: from EXVMBX018-1.exch018.msoutlookonline.net ([64.78.17.47]) by EXHUB018-4.exch018.msoutlookonline.net ([64.78.17.19]) with mapi; Tue, 28 Jun 2011 14:56:38 -0700 From: Steven Chew To: Rolf Winter , "eman@ietf.org" Date: Tue, 28 Jun 2011 14:56:36 -0700 Thread-Topic: Charge Cycle Definition Thread-Index: Acw1xJSZC+EOOVoHR3G1p9ABqQ3f2wAC6e7QAAJ1PtA= Message-ID: <0BB24042CB683840B986F84BC859CFB569F0909AE5@EXVMBX018-1.exch018.msoutlookonline.net> References: <0BB24042CB683840B986F84BC859CFB569F09099FA@EXVMBX018-1.exch018.msoutlookonline.net> <791AD3077F94194BB2BDD13565B6295D1C733D1E@PALLENE.office.hd> In-Reply-To: <791AD3077F94194BB2BDD13565B6295D1C733D1E@PALLENE.office.hd> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [eman] Charge Cycle Definition 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, 28 Jun 2011 21:56:39 -0000 I work in the battery industry. This is the only definition of which I am a= ware. I know it is not possible for the end user to keep track of fractiona= l charges and discharges, but this is why smart batteries do this accountin= g automatously. -----Original Message----- From: Rolf Winter [mailto:Rolf.Winter@neclab.eu]=20 Sent: Tuesday, June 28, 2011 4:18 PM To: Steven Chew; eman@ietf.org Subject: RE: Charge Cycle Definition Hi Steven, great input. Thanks a lot. Are you aware of any other definition in use? Best, Rolf 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=20 > Of Steven Chew > Sent: Dienstag, 28. Juni 2011 21:05 > To: eman@ietf.org > Subject: [eman] Charge Cycle Definition >=20 > I would like to comment about "8.1. Define Charging Cycle" in draft-=20 > ietf-eman-battery-mib-01.txt. >=20 >=20 >=20 > I think it is good to keep definition in line with that of Apple's, as=20 > given in the MIB document. Counting the number of times the discharged=20 > energy equal to the battery's capacity is commonly how battery=20 > manufacturers count charge cycles. I refer to the Smart Battery Data=20 > Specification Revision 1.10. >=20 >=20 >=20 > 5.1.22. CycleCount() (0x17) >=20 > Description: >=20 > Returns the number of cycles the battery has experienced. A cycle is=20 > defined as: >=20 > An amount of discharge approximately equal to the value of=20 > DesignCapacity. >=20 > Purpose: >=20 > The CycleCount() function provides a means to determine their=20 > battery's wear. It may be used to give >=20 > advanced warning that the battery is nearing its end of life. The=20 > CycleCount returned value multiplied by >=20 > the DesignCapacity value can give an approximate "odometer" reading=20 > for the total capacity delivered by >=20 > the Smart Battery. >=20 > SMBus Protocol: Read Word >=20 > Output: unsigned int -- count of charge/discharge cycles the battery=20 > has experienced >=20 > Units: cycle >=20 > Range: 0 to 65,534 cycles >=20 > 65,535 indicates battery has experienced 65,535 or more >=20 > cycles. >=20 > Granularity: 1 cycle >=20 > Accuracy: absolute count >=20 >=20 >=20 > This is a quantity already tracked and supplied by Smart Batteries. It=20 > would make sense for this MIB to align with this definition. >=20 >=20 >=20 > Regards, >=20 > Steven. From Rolf.Winter@neclab.eu Tue Jun 28 23:54:31 2011 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 029AF9E8034 for ; Tue, 28 Jun 2011 23:54:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.032 X-Spam-Level: X-Spam-Status: No, score=-102.032 tagged_above=-999 required=5 tests=[AWL=0.217, BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tuvDUA5eo20O for ; Tue, 28 Jun 2011 23:54:30 -0700 (PDT) Received: from smtp0.netlab.nec.de (smtp0.netlab.nec.de [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 35E819E802D for ; Tue, 28 Jun 2011 23:54:30 -0700 (PDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.netlab.nec.de (Postfix) with ESMTP id EA35328000226; Wed, 29 Jun 2011 08:54:28 +0200 (CEST) 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 fCfZzHg9j6w1; Wed, 29 Jun 2011 08:54:28 +0200 (CEST) Received: from ENCELADUS.office.hd (ENCELADUS.office.hd [192.168.24.52]) by smtp0.netlab.nec.de (Postfix) with ESMTP id C3C2D280001DB; Wed, 29 Jun 2011 08:54:18 +0200 (CEST) Received: from PALLENE.office.hd ([169.254.1.100]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0270.001; Wed, 29 Jun 2011 08:54:18 +0200 From: Rolf Winter To: Steven Chew , "eman@ietf.org" Thread-Topic: Charge Cycle Definition Thread-Index: Acw1xJSZC+EOOVoHR3G1p9ABqQ3f2wAC6e7QAAJ1PtAAE8cNIA== Date: Wed, 29 Jun 2011 06:54:18 +0000 Message-ID: <791AD3077F94194BB2BDD13565B6295D1C737F73@PALLENE.office.hd> References: <0BB24042CB683840B986F84BC859CFB569F09099FA@EXVMBX018-1.exch018.msoutlookonline.net> <791AD3077F94194BB2BDD13565B6295D1C733D1E@PALLENE.office.hd> <0BB24042CB683840B986F84BC859CFB569F0909AE5@EXVMBX018-1.exch018.msoutlookonline.net> In-Reply-To: <0BB24042CB683840B986F84BC859CFB569F0909AE5@EXVMBX018-1.exch018.msoutlookonline.net> Accept-Language: en-US, de-DE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.1.6.28] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [eman] Charge Cycle Definition 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, 29 Jun 2011 06:54:31 -0000 Steven, again, thanks for the valuable input. Is there anything you think is missin= g in the current MIB module definition that you think should be added? Any = opinion about any of the open issues? Best, Rolf NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London = W3 6BL | Registered in England 2832014=20 > -----Original Message----- > From: Steven Chew [mailto:SChew@bren-tronics.com] > Sent: Dienstag, 28. Juni 2011 23:57 > To: Rolf Winter; eman@ietf.org > Subject: RE: Charge Cycle Definition >=20 > I work in the battery industry. This is the only definition of which I > am aware. I know it is not possible for the end user to keep track of > fractional charges and discharges, but this is why smart batteries do > this accounting automatously. >=20 > -----Original Message----- > From: Rolf Winter [mailto:Rolf.Winter@neclab.eu] > Sent: Tuesday, June 28, 2011 4:18 PM > To: Steven Chew; eman@ietf.org > Subject: RE: Charge Cycle Definition >=20 > Hi Steven, >=20 > great input. Thanks a lot. Are you aware of any other definition in > use? >=20 > Best, >=20 > Rolf >=20 >=20 >=20 > NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, > London W3 6BL | Registered in England 2832014 >=20 >=20 > > -----Original Message----- > > From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf > > Of Steven Chew > > Sent: Dienstag, 28. Juni 2011 21:05 > > To: eman@ietf.org > > Subject: [eman] Charge Cycle Definition > > > > I would like to comment about "8.1. Define Charging Cycle" in draft- > > ietf-eman-battery-mib-01.txt. > > > > > > > > I think it is good to keep definition in line with that of Apple's, > as > > given in the MIB document. Counting the number of times the > discharged > > energy equal to the battery's capacity is commonly how battery > > manufacturers count charge cycles. I refer to the Smart Battery Data > > Specification Revision 1.10. > > > > > > > > 5.1.22. CycleCount() (0x17) > > > > Description: > > > > Returns the number of cycles the battery has experienced. A cycle is > > defined as: > > > > An amount of discharge approximately equal to the value of > > DesignCapacity. > > > > Purpose: > > > > The CycleCount() function provides a means to determine their > > battery's wear. It may be used to give > > > > advanced warning that the battery is nearing its end of life. The > > CycleCount returned value multiplied by > > > > the DesignCapacity value can give an approximate "odometer" reading > > for the total capacity delivered by > > > > the Smart Battery. > > > > SMBus Protocol: Read Word > > > > Output: unsigned int -- count of charge/discharge cycles the battery > > has experienced > > > > Units: cycle > > > > Range: 0 to 65,534 cycles > > > > 65,535 indicates battery has experienced 65,535 or more > > > > cycles. > > > > Granularity: 1 cycle > > > > Accuracy: absolute count > > > > > > > > This is a quantity already tracked and supplied by Smart Batteries. > It > > would make sense for this MIB to align with this definition. > > > > > > > > Regards, > > > > Steven. From bclaise@cisco.com Wed Jun 29 00:21:19 2011 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 480B621F8686 for ; Wed, 29 Jun 2011 00:21:14 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WkPhmR6eigwk for ; Wed, 29 Jun 2011 00:21:12 -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 E0B6621F8683 for ; Wed, 29 Jun 2011 00:21:06 -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 p5T75Y9e009533 for ; Wed, 29 Jun 2011 09:05:34 +0200 (CEST) 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 p5T75Xg7027081 for ; Wed, 29 Jun 2011 09:05:34 +0200 (CEST) Message-ID: <4E0ACEBE.90301@cisco.com> Date: Wed, 29 Jun 2011 09:05:34 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11 MIME-Version: 1.0 To: eman mailing list Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [eman] Nomcom 2011-2012: Second Call for Volunteers 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, 29 Jun 2011 07:21:24 -0000 FYI. Regards, Benoit. -----Original Message----- From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Suresh Krishnan Sent: Friday, June 24, 2011 9:13 PM To: IETF Discussion Subject: Nomcom 2011-2012: Second Call for Volunteers This is the Second call for Volunteers for the 2011-12 Nomcom. We are just about halfway through the volunteer period so if you are considering volunteering, please do so very soon. We have had a very good response to the initial call for volunteers and I am pleased to report that we have 50 volunteers thus far whose qualifications have been confirmed by the secretariat. I have notified each of these volunteers by email. However, we would like to have many more volunteers. The more volunteers, the better chance we have of choosing a random yet representative cross section of the IETF population. You have until 11:59 pm EDT July 10, 2011 to volunteer for Nomcom but it would be much better if you can volunteer as early as possible. If you volunteered before 21:00 EDT on June 21 to serve as a voting member and have not received a confirmation email from me, please re-submit and bring to my attention right away! Details about the process for volunteering for the Nomcom and the list of open positions for which the nominating committee is responsible are summarized in the initial announcement: https://datatracker.ietf.org/ann/nomcom/2938/ The 50 volunteers who have thus far been qualified by the secretariat are: Alia Atlas , Juniper Networks Lixia Zhang , UCLA Wassim Haddad , Ericsson Glen Zorn , Network Zen Richard Barnes , BBN Technologies Stephen Kent , BBN Technologies Scott Mansfield , Ericsson Tina TSOU , FutureWei Technologies Fernando Gont , UTN/FRH Karen Seo , BBN Technologies Jie Dong , Huawei Technologies Mach Chen , Huawei Technologies Co. Sheng Jiang , Huawei Technologies Co. Ltd. Dimitri Papadimitriou , Alcatel-Lucent Thomas D. Nadeau , CA Technologies David Meyer , Cisco Systems/University of Oregon Wesley George , Time Warner Cable Cullen Jennings , Cisco Stephen Hanna , Juniper Networks Stephan Wenger , Bidyo Keyur Patel , Cisco Systems Michael Hamilton , BreakingPoint Systems Behcet Sarikaya , Huawei USA Mark Townsley , Cisco Systems Fred Baker , Cisco Systems Brian Trammell , ETH Zurich Sam Hartman , Painless Security Chris Griffiths , Comcast George Michaelson , APNIC Jiankang Yao , CNNIC Sohel Khan , Comcast Dacheng Zhang , Huawei Lianshu Zheng , Huawei Technologies Hui Deng , China Mobile Gang Chen , China Mobile Mirja Kuhlewind , University of Stuttgart John E Drake , Juniper Networks Matt Lepinski , BBN Technologies Subir Das , Telcordia Technologies Inc Yi Zhao , Huawei John Scudder , Juniper Networks Christer Holmberg , LM Ericsson Teemu Savolainen , Nokia Samita Chakrabarti , Ericsson Jaap Akkerhuis , NLnet labs Jason Weil , Time Warner Cable Randy Bush , Internet Initiative Japan Christian Schmidt , Nokia Siemens Networks Sean Shen , CNNIC Lou Berger , LabN Consulting The primary activity for this nomcom will begin during IETF-81 in Quebec City and should be completed by January 2012. The nomcom will be collecting requirements from the community, as well as talking to candidates and to community members about candidates. There will be regularly scheduled conference calls to ensure progress. Thus, being a nomcom member does require some time commitment. Please volunteer by sending an email to me before 11:59 pm EDT July 10, 2011 as follows: To: suresh.krishnan@ericsson.com Subject: Nomcom 2011-12 Volunteer Please include the following information in the body of the mail: Full Name: // As you enter in the IETF Registration Form, // First/Given name followed by Last/Family Name Current Primary Affiliation: // typically what goes in the Company // field in the IETF Registration Form Email Address(es): // all email addresses used to Register for the // past 5 IETF meetings // Please designate a Preferred email address for // contact if there is more than one email address Telephone number: // With country code (for confirmation if selected) Please expect an email response from me within 3 business days stating whether or not you are qualified. If you do not receive a response in this timeframe, please re-send your email with the tag "RESEND:" added to the subject line. If you are not yet sure you would like to volunteer, please consider that Nomcom members play a very important role in shaping the leadership of the IETF. Ensuring the leadership of the IETF is fair and balanced and comprised of those who can lead the IETF in the right direction is an important responsibility that rests on the IETF participants at large. Volunteering for the Nomcom is a good way of contributing in that direction. I will be publishing a more detailed target timetable, as well as details of the randomness seeds to be used for the RFC 3797 selection process within the next few days. Thank you in advance for your participation. Suresh Krishnan Nomcom Chair 2011-2012 Email: nomcom-chair@ietf.org, suresh.krishnan@ericsson.com _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf From bclaise@cisco.com Wed Jun 29 02:19:40 2011 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 12FC521F8628 for ; Wed, 29 Jun 2011 02:19:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.157 X-Spam-Level: X-Spam-Status: No, score=-2.157 tagged_above=-999 required=5 tests=[AWL=-0.443, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hZKX+9N0BoBW for ; Wed, 29 Jun 2011 02:19:36 -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 9A40A21F862A for ; Wed, 29 Jun 2011 02:19:35 -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 p5T9JXSh026036; Wed, 29 Jun 2011 11:19:33 +0200 (CEST) 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 p5T9JW4K024001; Wed, 29 Jun 2011 11:19:32 +0200 (CEST) Message-ID: <4E0AEE24.20303@cisco.com> Date: Wed, 29 Jun 2011 11:19:32 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11 MIME-Version: 1.0 To: Michael Suchoff References: <9C329342B62B87498B92834DEC9FF51E0BB8B031@fig.raritan.com> In-Reply-To: <9C329342B62B87498B92834DEC9FF51E0BB8B031@fig.raritan.com> Content-Type: multipart/alternative; boundary="------------020501040204040907030508" Cc: eman@ietf.org Subject: Re: [eman] feedback on drafts 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, 29 Jun 2011 09:19:40 -0000 This is a multi-part message in MIME format. --------------020501040204040907030508 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Michael, Sorry for overlooking your email > > All, > > I have been a silent observer of this group for about a month. > > By way of introduction, I am a principal engineer at Raritan. Raritan > manufactures rack power distribution units and is an industry leader > in outlet level metered rack PDUs. Our products contain a billing > grade AC energy metering chip for each outlet and our devices contain > a networked SNMP agent. Raritan also develops and sells SNMP data > center power management software -- and our management software is > designed to work with any vendor's PDU -- not just our own. I learned > of this group through our client Cisco that outfits their data centers > with our PDUs and power management software. > > As an "implementer" of AC energy management products and as someone > that has experience with many vendors' implementation of SNMP energy > management, here are two thoughts on the MIBs produced by the eman > ietf group. > > 1. Timestamps > > When taking power measurements, there is no indication of the time > when the measurement occurred. The major vendors of metered power > distribution units and panel energy meters all include time stamped > data logs. These data logs typically contain 100+ time stamped > measurements per sensor (voltage/current/power, etc.). > > The proposed MIBs do not take time of measurement into consideration > and this will be a problem. Assume we want to get readings on an > hourly basis from an SNMP manager that must communicate with many > thousands of devices. Without data logging, it isn't possible to get > accurately get timed measurements due to the variable delay times in > the manager, network and agents. Our experience supporting every > major vendor's PDU SNMP agent indicates variable SNMP GET delays of > 2-45 seconds. > There is a difference between energy, power, and power quality. - Energy slots needs to aggregated between different devices, so yes knowing the precise time is important. In the MIB module, we have pmEnergyIntervalStartTime and the parameters we have the pmEnergyParametersIntervalLength. So the energy is taken care of, right? - For power, The measurement will happen at the time of the SNMP request, and not regularly, right? I'm wondering: aren't we trying to solve a SNMP response problem by inserting a timestamps in the MIB module? It's a good practice to request the sysUpTime when polling counters, so the measurement time (in this case) is tagged. - For power quality, isn't it the same thing as for the power? I mean, will the power quality measurement start at the time of the SNMP request? Bottom line: if there is a new requirement, then it should be part of the EMAN requirements draft, as the EMAN MIB modules take their inputs from the requirements and the framework. > 2. AC Power Terminology > > There is a bit of a lack of understanding of AC power in the MIBs. > Here are some examples: > > ·AC power is not an RMS measurement, it is an average reading. AC > power is sinusoidal at 2x the AC line frequency, so use of the term > "instantaneous AC power" is misleading and power meters do not report it. > Agreed. This is the reason why instantaneous was written between quotes. pmPower OBJECT-TYPE SYNTAX Integer32 UNITS "Watts" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the 'instantaneous' RMS consumption for the Power Monitor. This value is specified in SI units of watts with the magnitude of watts (milliwatts, kilowatts, etc.) indicated separately in pmPowerUnitMultiplier. The accuracy of the measurement is specfied in pmPowerAccuracy. The direction of power flow is indicated by the sign on pmPower. If the Power Monitor is consuming power, the pmPower value will be positive. If the Power Monitor is producing power, the pmPower value will be negative. The pmPower MUST be less than or equal to the maximum power that can be consumed at the power state specified by pmPowerState. The pmPowerMeasurementCaliber object specifies how the usage value reported by pmPower was obtained. The pmPower value must report 0 if the pmPowerMeasurementCaliber is 'unavailable'. For devices that can not measure or report power, this option can be used." ::= { pmPowerEntry 3 } Certainly some more clarifications are required. What do you suggest? Some more explanation in the description clause, or a generic paragraph from all the 'instantaneous' > ·Voltage & current RMS measurements are by definition averaged values, > they are not "instantaneous RMS" measurements > Same as above. > > ·3-phase PDUs are not black and white either Wye or Delta. In North > American 208V systems, power distribution units contain a combination > of delta wired circuits (208V) and wye wired circuits (120V). > The question is whether EMAN should cover that third case. If the group thinks that we should, then it should be specified in the EMAN requirements. Question: what's specific to this combination of delta wired circuits (208V) and wye wired circuits (120V)? It implies that we need to have a third series of tables, specifically for this model? > ·The nameplate MIB objects use names such as "max voltage" and have > fixed single numeric values. Actual device nameplate values follow > the UL (or IEC) 60950-1 conventions and are rated (not max) ranges > (not single values). Example: "Rated Voltage: "190-240V 3-phase". > You're right. The goal behind the nameplate (and maybe the MIB variable name is wrong), was to get the max value in order to do power planning. So 240V in this case. The requirement needs to be clearly spelled out in the EMAN requirements. > > ·There are many IEC and ANSI standards for AC energy meters. The > attempts in the MIB to define energy metering accuracy are nonstandard. > Can you please elaborate, i.e. clarify which parts are not standard? The intend was not to reinvent anything, but to refer to existing standards (IEC). Example: accuracy and unit multipliers > > ·A major concern in AC data center management is detection of tripped > circuit breakers (or blown fuses). The MIB contains no modeling for > over current devices. > As far as I understood, circuit breakers were not in the EMAN scope. Note that circuit breakers are not described in the EMAN requirements. Note: discussing with Juergen, he plans on submitting a new version of the EMAN requirements very soon. Thanks for your feedback, Mouli and Benoit. > > I hope the above are taken as constructive help. I mean no disrespect > to the members that have put in long hours developing the MIBs. I am > available to help improve the group's efforts. > > Regards, > > **Michael Suchoff*** > *Principal Engineer > > Raritan . 801 Jones Franklin Rd . Raleigh, NC 27606 USA > Tel: 1.919.851.3663 ext.1371 > > michael.suchoff@raritan.com > > Visit our blog: blog.raritan.com > > > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman --------------020501040204040907030508 Content-Type: multipart/related; boundary="------------090203090108060202030404" --------------090203090108060202030404 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Michael,

Sorry for overlooking your email

All,

 

I have been a silent observer of this group for about a month.

 

By way of introduction, I am a principal engineer at Raritan.  Raritan manufactures rack power distribution units and is an industry leader in outlet level metered rack PDUs.  Our products contain a billing grade AC energy metering chip for each outlet and our devices contain a networked SNMP agent.  Raritan also develops and sells SNMP data center power management software – and our management software is designed to work with any vendor’s PDU – not just our own.  I learned of this group through our client Cisco that outfits their data centers with our PDUs and power management software.

 

As an “implementer” of AC energy management products and as someone that has experience with many vendors’ implementation of SNMP energy management, here are two thoughts on the MIBs produced by the eman ietf group.

 

  1. Timestamps

 

When taking power measurements, there is no indication of the time when the measurement occurred.  The major vendors of metered power distribution units and panel energy meters all include time stamped data logs.  These data logs typically contain 100+ time stamped measurements per sensor (voltage/current/power, etc.).

 

The proposed MIBs do not take time of measurement into consideration and this will be a problem.  Assume we want to get readings on an hourly basis from an SNMP manager that must communicate with many thousands of devices.  Without data logging, it isn’t possible to get accurately get timed measurements due to the variable delay times in the manager, network and agents.  Our experience supporting every major vendor’s PDU SNMP agent indicates variable SNMP GET delays of 2-45 seconds.

There is a difference between energy, power, and power quality.
- Energy slots needs to aggregated between different devices, so yes knowing the precise time is important.
In the MIB module, we have pmEnergyIntervalStartTime and the parameters we have the pmEnergyParametersIntervalLength. So the energy is taken care of, right?
- For power, The measurement will happen at the time of the SNMP request, and not regularly, right?
I'm wondering: aren't we trying to solve a SNMP response problem by inserting a timestamps in the MIB module? It's a good practice to request the sysUpTime when polling counters, so the measurement time (in this case) is tagged.
- For power quality, isn't it the same thing as for the power? I mean, will the power quality measurement start at the time of the SNMP request?

Bottom line: if there is a new requirement, then it should be part of the EMAN requirements draft, as the EMAN MIB modules take their inputs from the requirements and the framework.

  1. AC Power Terminology

 

There is a bit of a lack of understanding of AC power in the MIBs.  Here are some examples:

 

·         AC power is not an RMS measurement, it is an average reading.  AC power is sinusoidal at 2x the AC line frequency, so use of the term “instantaneous AC power” is misleading and power meters do not report it.

Agreed. This is the reason why instantaneous was written between quotes.

       pmPower OBJECT-TYPE     
            SYNTAX          Integer32
            UNITS           "Watts"
            MAX-ACCESS      read-only
            STATUS          current
            DESCRIPTION
               "This object indicates the 'instantaneous' RMS
               consumption for the Power Monitor.  This value is
               specified in SI units of watts with the magnitude of
               watts (milliwatts, kilowatts, etc.) indicated separately
               in pmPowerUnitMultiplier. The accuracy of the measurement
               is specfied in pmPowerAccuracy. The direction of power
               flow is indicated by the sign on pmPower. If the Power
               Monitor is consuming power, the pmPower value will be
               positive. If the Power Monitor is producing power, the
               pmPower value will be negative.
     
               The pmPower MUST be less than or equal to the maximum
               power that can be consumed at the power state specified
               by pmPowerState.
     
               The pmPowerMeasurementCaliber object specifies how the
               usage value reported by pmPower was obtained. The pmPower
               value must report 0 if the pmPowerMeasurementCaliber is
               'unavailable'.  For devices that can not measure or
               report power, this option can be used."
            ::= { pmPowerEntry 3 }

Certainly some more clarifications are required. What do you suggest? Some more explanation in the description clause, or a generic paragraph from all the 'instantaneous'


·         Voltage & current RMS measurements are by definition averaged values, they are not “instantaneous RMS” measurements

Same as above.

·         3-phase PDUs are not black and white either Wye or Delta.  In North American 208V systems, power distribution units contain a combination of delta wired circuits (208V) and wye wired circuits (120V).

The question is whether EMAN should cover that third case.
If the group thinks that we should, then it should be specified in the EMAN requirements.
Question: what's specific to this combination of delta wired circuits (208V) and wye wired circuits (120V)? It implies that we need to have a third series of tables, specifically for this model?

·         The nameplate MIB objects use names such as “max voltage” and have fixed single numeric values.  Actual device nameplate values follow the UL (or IEC) 60950-1 conventions and are rated (not max) ranges (not single values).  Example:  “Rated Voltage: “190-240V 3-phase”.

You're right.
The goal behind the nameplate (and maybe the MIB variable name is wrong), was to get the max value in order to do power planning. So 240V in this case.
The requirement needs to be clearly spelled out in the EMAN requirements.

·         There are many IEC and ANSI standards for AC energy meters.  The attempts in the MIB to define energy metering accuracy are nonstandard.

Can you please elaborate, i.e. clarify which parts are not standard?
The intend was not to reinvent anything, but to refer to existing standards (IEC). Example: accuracy and unit multipliers

·         A major concern in AC data center management is detection of tripped circuit breakers (or blown fuses).  The MIB contains no modeling for over current devices.

As far as I understood, circuit breakers were not in the EMAN scope.
Note that circuit breakers are not described in the EMAN requirements.

Note: discussing with Juergen, he plans on submitting a new version of the EMAN requirements very soon.

Thanks for your feedback, Mouli and Benoit.

 

I hope the above are taken as constructive help. I mean no disrespect to the members that have put in long hours developing the MIBs.  I am available to help improve the group’s efforts.

 

Regards,

Michael Suchoff
Principal Engineer 

 

Raritan • 801 Jones Franklin Rd • Raleigh, NC 27606 USA
Tel: 1.919.851.3663 ext.1371

michael.suchoff@raritan.com

Visit our blog: blog.raritan.com

 


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

--------------090203090108060202030404 Content-Type: image/jpeg Content-Transfer-Encoding: base64 Content-ID: /9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAoHBwgHBgoICAgLCgoLDhgQDg0NDh0VFhEYIx8l JCIfIiEmKzcvJik0KSEiMEExNDk7Pj4+JS5ESUM8SDc9Pjv/2wBDAQoLCw4NDhwQEBw7KCIo Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozv/wAAR CAAtAKADASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAA AgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWG h4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl 5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREA AgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYk NOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk 5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD0W88S6NJaSoblm3IVwsbAnI6AkYBrlvt2 hf8APDUP+/w/xrp7zWs2sofRbwjY27fGAuMdznpXJ/23Z/8AQDs/1rvox0dk/vPGxVRtq7X3 MdqttEtlb6jpskwt5CVcO5ZkYHofqP8APNTrDYabYW76p9pluLhTIEjkxsXtnJ71PJewwaD9 oj0l447l1DRNkxblIIYHqM4x6cfm7Vr63haK6uNJaaS5UMWuMhUHQKAPT8+atSk7LXd9dTBw jFuSavZdHZX62IrPU9BjvYnWG9jKsCGaTIHPUgHJFdba65pt7OILa43yMDgbGGccnkjFcZYa 3afbYduhwBt42+XktnP8IPU12NnqpubgRf2ZdwbgTvkjCqMepzWFePdPbudmEm3pdb9Eed65 DNeeNriyjmaMzXKopJOFLYGf1qTUbLXfB9xDMt8SkhO1o3YoxHVWU0zV7pLHx5NdurOsN0rs B1IUg4FTeINeuPF09vZ2FjLtjYsqj5mZjxk44AFcp6Z6Jouo/wBqaRbXuADKmWUdmHBH5g1o VwWsatP4R0Gx0e1dRemPe74BCAk5wD3JJA+lULZ/GttZ/wBrCSaSEruZJHDkr67DyB345pDP TKK848OeItXvItWa4vWcwWMksZKr8rAcNwKo6brnivWWksbS6eR3AYt8qlFGc/NgYzke/FAH S+NtD1bVzamwO+OLcHj3hcE4w3PB/pU2p61d+FNB09Z4hdzkCORmcjkLnOcc+lYGs6h4i8P6 Vp8U19LHcyvMXJZXJUFdvJz6n86g8YSajcafpNzcSM9tLaxsCSvzSlcscDnofpTEegaNqB1X Sbe+aMRmZSxQHIHJHX8K0K820XVdY0LQzfXeXsTFts0JTDOW44HzYADHn0qvYXHjHXne9tLm YqjYyHVEz/dCnAP+c0hnqNFeY6f4k1+bxLbWl3ctGGnSOWLYoHUAjGOM0XHiLxC/ii5sLK6d ybmSKKNlXaBuZR27Dnn0oA9Oory3UL7xT4Z1CJry+eXzBvCl96OAeVwen6da9LtLlbu0huFG FmRXA9MjNAGLdX+vrbyldJiUhTgicMRx1xjn6Vz/APa/if8A59X/APAb/wCtXczx+dA8YdkL qVDqcMMjqPesX/hGJ/8AoOah/wB/K6KdSKTukedXoVG1ytv7jDvtRvrPSlmvW/066I2IwAEc akH7vYkj/OKlur/VTFFe6SHkt7kbmjEYfy3HBAGOAev51euPBkVy4e41K7lcDALsGIHpk1JF 4R+yx7INWvYlJyVR8DPrgVpz07Lv6aGHsa7bVnaytqrmVaap4mN1GGsmZSwBDQhQfq2OPrXS 2Vzq8k4W6sIoosHLrNuI9OKhtvD81vcxytrF9IEYMUaTKtjsR6VtZwKxqTUtkjrw9GcFeTfz PLL+JLj4iNDKodJL1FZT0ZSQCKG+0+CPFRKhngJyB/z0jY9PqP5iuxk8G2sniAawbqYSiZZt gA25BBx644q5r3h618QwRxzs0bRMWSRANwB6jnsePyrI7ThfHTrNrNrqEbeZb3FujRsOjAE5 H6j867k+JNI/sg3v2qLyvLz5e4b84+7jrntVOPwZZjSDps9xNPEH3xMwAaJj12kdj6dKzrb4 a2iT77i/kljHRFQKT9Tk0gOe8KsGj11lG0HTJiB6Vr/DFQZtSbHIWMZ+pb/CtrTPBFppiXax 3c0gu7doG3AfKrdSPerXh7wzB4ea4MFxJL54UNvAGNuemPrQI5z4n/f03/dl/wDZah8W/wDI maD/ANcl/wDRYrqfEPhmDxC1uZ7iSLyAwXYAc7sdc/Smal4Vt9U0qy0+W5ljSzVVVkxlsKF5 /KmM5XWIJJPhzpUqAlYny+OwJYA/n/OtrwTrNgPDsdq9xFDNblg6uwUkFiQ3PUc/pW9aaNbW 2jLpUmZ7dUKNvHLAknt9a5mb4aWrzl4tQljhJzsMYZgPTdn+lAGLNf2+pfEWG5tiDE1yiqw6 NtwCfxxTtIGfic+f+fy4/k9dLa+AtPs9ThvILidfJdGVDgglcdT15xU9p4QtbXxC2srcytK0 ry7CBty27I9eN1IDD+J339P/AN2T/wBlrqNHu7eHRtPjkmRHa3j2oxAJyAB+tReIfDMHiFoD NcSReSGC7ADnOOufpSS+GbWUW8bTSFYYRCR3ZQMdexI/xGDzQBpalM1vptzPGQHiidlJGcEK SKyrbWZZLC41WUZhhXaIBgOWBAZmz90nsvp9a25oUuYJIJASkilWGeoIwapSaRZSFmMbDzYg jhXI3AYxn1I9etAEP9sukzWz2bi6LqqRBwQ25SwJbtgK2eO3emrr6BpUltnWSJWBTIO5lKja D3zvUg/7VXJtKtrqRppAwlfad6sQylc4IPbqfzqMaPZBocozNDIZg7OSxc9ye/QfkPSgB9lq cd6f3cbALCkrEn7pbPyn3GDmqCeIZXiVxpsmJLc3KZkXlBjdn0PIwO+e1aVpY29n53kqR57m R8sTyeuPQe1NXSrRESNUbbHbG2Ubj/qzjI+vyjmgCp/bgcGVbZzaJIsbzbgMM23+HqQCwBP1 4NR/8JEEhSR7YIs0rJCZJQobaSGYnHyjjjqTmrSaNZ+YCBIEDKxjDnazAAAkdzwPyFPOk2zQ xRrvj8py8bI5DKWJ3YPoc9KAJbK8W9sEu41YeYpIVuoI4I/MVg2uuX0miOHdW1ByohO0AMHG 4Nj/AGQGz/uV0EVssbcSStlAh3uW4Geee/vVePR7GOSCRYjut4jFGdx4Xp+eM8+5oAoweINk FgJ9sklwkPmFZFDKz4AO30yfb8alh13zRE8lq8MMyuY3Mi8lckg+gIBwc9u1SroFijJs81VU x/IJDtLR42sR3I2j8qkfRrGa1S2eMmKIMqruPRhg/wA6AKkPiBbhvKitxJOZFRUSUFW3KWzu x0AU54/OmP4mjjAV7crKGcNHJKq42NtOD3JPQfyqtr622i2IvfKmuJWnRS7Tsrg7WwQw6cEj GMEGptD06C60q2vN00Usu6UOkhDBZGyUJ/iHTk9xnigC9c6vHClnIkeVvMFHdtirkAgEkcE5 4Hc1ANankmRIrF2813jiYyAAshO4njgYBweenSr93p0N9AIZmk8sDBVXIDjjhvXpSR6fbRGF kQgwuzp8x4L5z/6EaAKDeI4AttJ5a7ZlUlTIu9NzbR8vcA98j2zTE16d2tZvsey2ljeRi7gt tUAlhj6njvx0qyPD1ggAUSquVyiyEKxU5UkdyMVMdJtTHbRhWVbdSqYY8qRgqfUGgDPj8TpI o2WzSSOUCKkinO5toDHopBxke9akf24zAymEQsuSi5LKcdM9CPwqGPSreGNU3zOkZWRFeQkL tOQB7Vbt4xHH5YZ2C55dixPPqaAP/9k= --------------090203090108060202030404-- --------------020501040204040907030508-- From moulchan@cisco.com Wed Jun 29 02:42:15 2011 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 D6CC121F85CF for ; Wed, 29 Jun 2011 02:42:15 -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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D6Izma+zwPUl for ; Wed, 29 Jun 2011 02:42:15 -0700 (PDT) Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by ietfa.amsl.com (Postfix) with ESMTP id C044A21F85CA for ; Wed, 29 Jun 2011 02:42:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=moulchan@cisco.com; l=4845; q=dns/txt; s=iport; t=1309340534; x=1310550134; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=0ZCVGi7Jsqi39qbVSUassj05VO6d5oNnvd9z9UzyzGM=; b=Pjv9mwHdQLNHBbTmwDM7sYKL3OJ18PpZMEI+mUHARg3aDqLu7JtH9lt0 J4dJM7p3b0P1XNM5U4gj5r9Q68lFLdu8Q2aNVs/X+Af80NuKlPBdvk3YA VZ4brem/W+9HTt0MYL0EQX6z8S8WWaBCoBi4BOk4COUlTuAwwzgv45G4h I=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av8AAA7zCk6tJV2c/2dsb2JhbABMBpgejzp3iHihU54NAoM3gncEhzaPX4tK X-IronPort-AV: E=Sophos;i="4.65,442,1304294400"; d="scan'208";a="238164857" Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rtp-iport-1.cisco.com with ESMTP; 29 Jun 2011 09:42:13 +0000 Received: from xbh-rcd-301.cisco.com (xbh-rcd-301.cisco.com [72.163.63.8]) by rcdn-core-5.cisco.com (8.14.3/8.14.3) with ESMTP id p5T9gDIG010643; Wed, 29 Jun 2011 09:42:13 GMT Received: from xmb-rcd-106.cisco.com ([72.163.62.148]) by xbh-rcd-301.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Wed, 29 Jun 2011 04:42:13 -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: Wed, 29 Jun 2011 04:42:09 -0500 Message-ID: In-Reply-To: <20110525093647.GA2777@elstar.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [eman] draft-claise-energy-monitoring-mib-08.txt Thread-Index: Acwav0l1aHPqjMckRXibxFEHSMaXKAbgQEcw References: <20110525093647.GA2777@elstar.local> From: "Mouli Chandramouli (moulchan)" To: "Juergen Schoenwaelder" X-OriginalArrivalTime: 29 Jun 2011 09:42:13.0724 (UTC) FILETIME=[D34541C0:01CC3640] Cc: eman mailing list Subject: Re: [eman] draft-claise-energy-monitoring-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: Wed, 29 Jun 2011 09:42:16 -0000 Hi Juergen, Thanks for your comments.=20 We intend to update the MIB draft and submit a revised version before the IETF based on the updated requirements draft (to be published soon) and the feedback from the mailing list. We shall revise based on your comments and if there are open issues to be discussed, we shall send it to the mailing list.=20 Thanks Mouli -----Original Message----- From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-university.de]=20 Sent: Wednesday, May 25, 2011 3:07 PM To: Mouli Chandramouli (moulchan) Cc: eman mailing list Subject: Re: [eman] draft-claise-energy-monitoring-mib-08.txt On Tue, May 24, 2011 at 02:44:55AM -0500, Mouli Chandramouli (moulchan) wrote: =20 > Among other changes, the draft provides support for multiple Power State > Series and an IANA considerations section describing the procedure for > adding new Power State Series and Power States within the series. Many > thanks to all who provided comments. PowerStateSeries ::=3D TEXTUAL-CONVENTION STATUS current DESCRIPTION "PowerStateSeries is a TC that describes the Power State Series a Power Monitor supports. IANA has created a registry of Power State Series supported by a Power Monitor entity and IANA shall administer the list of Power State Series. One byte is used to represent the Power State Series. field octets contents range ----- ------ -------- ----- 1 1 Power State Series 1..255 Note: the value of Power State Series in network byte order 1 in the first byte indicates IEEE1621 Power State Series 2 in the first byte indicates DMTF Power State Series 3 in the first byte indicates EMAN Power State Series REFERENCE "http://www.iana.org/assignments/eman" "RFC EDITOR NOTE: please change the previous URL if this is not the correct one after IANA assigned it." SYNTAX OCTETSTRING (SIZE(1)) Why is this an OCTET STRING (SIZE(1)) and not simply an enumerated INTEGER? And if this is to be maintained by IANA, why not create a IANA-POWER-SERIES-TC MIB module so that one can simply fetch the latest version from IANA? New assignments in Power State Series require a Standards Action [RFC5226], i.e., they are to be made via Standards Track RFCs approved by the IESG. This raises the bar pretty high. If some future organization defines popular power states, do you think someone is going to go through the trouble of producing a standards-track specification for this? I also do not see why all objects in the pmPowerEntry are necessarily indexed by power series - some appear to me to be rather a property of the monitor and not the power state series the monitor happens to support. I also like to see more text moved from the document into DESCRIPTION clauses. This in particular concerns the actual power state values. There is no way to find out what power state 2 in power state series 1 means if all you have are MIB modules. And lastly, I still prefer a design where the power states are simply enumerated. Since you require a standard-track action to allocate a new series and you reserved 8 bits for power state series, I fail to see why a simple TC can not do the job equally well. Since I started looking at the IANA considerations, I believe this text needs to be removed: Additions to the MIB modules are subject to Expert Review [RFC5226], i.e., review by one of a group of experts designated by an IETF Area Director. The group of experts MUST check the requested MIB objects for completeness and accuracy of the description. Requests for MIB objects that duplicate the functionality of existing objects SHOULD be declined. The smallest available OIDs SHOULD be assigned to the new MIB objects. The specification of new MIB objects SHOULD follow the structure specified in Section 10. and MUST be published using a well-established and persistent publication medium. IETF MIB modules are not modified by Expert Review. This text looks inconsistent with existing practice in maintaining IETF MIB modules. /js --=20 Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From internet-drafts@ietf.org Wed Jun 29 07:10:49 2011 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 CA37C21F8531; Wed, 29 Jun 2011 07:10:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.57 X-Spam-Level: X-Spam-Status: No, score=-102.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yRE2F7oS0xET; Wed, 29 Jun 2011 07:10:49 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98E3621F852B; Wed, 29 Jun 2011 07:10:48 -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: 3.55 Message-ID: <20110629141048.16582.23648.idtracker@ietfa.amsl.com> Date: Wed, 29 Jun 2011 07:10:48 -0700 Cc: eman@ietf.org Subject: [eman] I-D Action: draft-ietf-eman-requirements-02.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: Wed, 29 Jun 2011 14:10:50 -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 th= e IETF. Title : Requirements for Energy Management Author(s) : Juergen Quittek Rolf Winter Thomas Dietz Benoit Claise Mouli Chandramouli Filename : draft-ietf-eman-requirements-02.txt Pages : 33 Date : 2011-06-29 This document defines requirements for standards specifications for energy management. Defined requirements concern monitoring functions as well as control functions. Covered functions include identification of powered entities, monitoring of their power state, power inlets, power outlets, actual power, consumed energy, and contained batteries. Further included is control of powered entities' power supply and power state. 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-eman-requirements-02.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-eman-requirements-02.txt From Quittek@neclab.eu Wed Jun 29 07:53:34 2011 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 669A221F858D for ; Wed, 29 Jun 2011 07:53:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.249 X-Spam-Level: X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iC-DT12Rlkn9 for ; Wed, 29 Jun 2011 07:53:32 -0700 (PDT) Received: from smtp0.netlab.nec.de (smtp0.netlab.nec.de [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 9168A21F858A for ; Wed, 29 Jun 2011 07:53:32 -0700 (PDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.netlab.nec.de (Postfix) with ESMTP id F3830280001AA for ; Wed, 29 Jun 2011 16:53:31 +0200 (CEST) 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 bJJNI13kMo9z for ; Wed, 29 Jun 2011 16:53:31 +0200 (CEST) Received: from METHONE.office.hd (Methone.office.hd [192.168.24.54]) by smtp0.netlab.nec.de (Postfix) with ESMTP id D78F528000189 for ; Wed, 29 Jun 2011 16:53:26 +0200 (CEST) Received: from Polydeuces.office.hd ([169.254.3.5]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0270.001; Wed, 29 Jun 2011 16:53:27 +0200 From: Juergen Quittek To: eman mailing list Thread-Topic: New draft on eman requirements Thread-Index: Acw2bEgLUSQNJgXDjE6Pk4zAd/RgeA== Date: Wed, 29 Jun 2011 14:53:25 +0000 Message-ID: Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-Entourage/13.10.0.110428 x-originating-ip: [10.7.0.92] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [eman] New draft on eman requirements 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, 29 Jun 2011 14:53:34 -0000 Dear all, I just posted a new version on the requirements draft. Please find it at=20 http://www.ietf.org/internet-drafts/draft-ietf-eman-requirements-02.txt We had intensive discussions among the authors and received a lot of useful comments from John Parello. This resulted in many changes and a modified structure. We consider the version posted today as an intermediate one and intend to post another update before the cut-off date. Please have a look at the new structure and give us your feedback. Issues that we definitely want to solve for the next version are described in section 12. Among them are - High/Low power notifications - Power and energy time series? - Inlet/outlet combinations - Aggregation functions Your advice on these issues is highly appreciated. Thanks, Juergen=20 From internet-drafts@ietf.org Thu Jun 30 02:18:35 2011 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 61A7B21F87A8; Thu, 30 Jun 2011 02:18:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.581 X-Spam-Level: X-Spam-Status: No, score=-102.581 tagged_above=-999 required=5 tests=[AWL=0.018, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qD3vyopnY6-I; Thu, 30 Jun 2011 02:18:34 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB7BA21F87AF; Thu, 30 Jun 2011 02:18:34 -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: 3.55 Message-ID: <20110630091834.4353.30289.idtracker@ietfa.amsl.com> Date: Thu, 30 Jun 2011 02:18:34 -0700 Cc: eman@ietf.org Subject: [eman] I-D Action: draft-ietf-eman-requirements-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: Thu, 30 Jun 2011 09:18:35 -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 th= e IETF. Title : Requirements for Energy Management Author(s) : Juergen Quittek Rolf Winter Thomas Dietz Benoit Claise Mouli Chandramouli Filename : draft-ietf-eman-requirements-03.txt Pages : 33 Date : 2011-06-30 This document defines requirements for standards specifications for energy management. Defined requirements concern monitoring functions as well as control functions. Covered functions include identification of powered entities, monitoring of their power state, power inlets, power outlets, actual power, consumed energy, and contained batteries. Further included is control of powered entities' power supply and power state. 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-eman-requirements-03.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-eman-requirements-03.txt From Quittek@neclab.eu Thu Jun 30 02:26:15 2011 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 A543421F8736 for ; Thu, 30 Jun 2011 02:26:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.249 X-Spam-Level: X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i49zAZXUiChH for ; Thu, 30 Jun 2011 02:26:15 -0700 (PDT) Received: from smtp0.netlab.nec.de (smtp0.netlab.nec.de [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 240CB21F857A for ; Thu, 30 Jun 2011 02:26:15 -0700 (PDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp0.netlab.nec.de (Postfix) with ESMTP id 3B472280001DB for ; Thu, 30 Jun 2011 11:26:14 +0200 (CEST) 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 DUa2WmfSEQzG for ; Thu, 30 Jun 2011 11:26:14 +0200 (CEST) Received: from METHONE.office.hd (Methone.office.hd [192.168.24.54]) by smtp0.netlab.nec.de (Postfix) with ESMTP id 20B16280001AA for ; Thu, 30 Jun 2011 11:26:09 +0200 (CEST) Received: from Polydeuces.office.hd ([169.254.3.5]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0270.001; Thu, 30 Jun 2011 11:26:09 +0200 From: Juergen Quittek To: eman mailing list Thread-Topic: [eman] New draft on eman requirements Thread-Index: Acw2bEgLUSQNJgXDjE6Pk4zAd/RgeAAm3TUG Date: Thu, 30 Jun 2011 09:26:08 +0000 Message-ID: In-Reply-To: Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-Entourage/13.10.0.110428 x-originating-ip: [10.7.0.92] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [eman] New draft on eman requirements 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, 30 Jun 2011 09:26:15 -0000 Dear all, I am sorry for posting another version just one day after the previous one. Now out is version -03 to be found at http://www.ietf.org/internet-drafts/draft-ietf-eman-requirements-03.txt The reason was that a change in terminology ("powered device" -> "powered entity") was not done consistently in all sections, particularly not in the battery section. There are no further changes, particularly no technical changes compared to the previous version. Thanks, Juergen Am 29.06.11 16:53 schrieb "Juergen Quittek" unter : > Dear all, >=20 > I just posted a new version on the requirements draft. > Please find it at > http://www.ietf.org/internet-drafts/draft-ietf-eman-requirements-02.txt >=20 > We had intensive discussions among the authors and received a lot of usef= ul > comments from John Parello. This resulted in many changes and a modified > structure. We consider the version posted today as an intermediate one an= d > intend to post another update before the cut-off date. >=20 > Please have a look at the new structure and give us your feedback. >=20 > Issues that we definitely want to solve for the next version are describe= d > in section 12. Among them are > - High/Low power notifications > - Power and energy time series? > - Inlet/outlet combinations > - Aggregation functions > Your advice on these issues is highly appreciated. >=20 > Thanks, >=20 > Juergen=20 >=20 > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman From etychon@cisco.com Thu Jun 30 09:31:40 2011 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 84E5111E8242 for ; Thu, 30 Jun 2011 09:31:40 -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=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lEXSaYve7aPj for ; Thu, 30 Jun 2011 09:31:40 -0700 (PDT) Received: from av-tac-sj.cisco.com (firebird.cisco.com [171.68.227.73]) by ietfa.amsl.com (Postfix) with ESMTP id 03ACF11E8085 for ; Thu, 30 Jun 2011 09:31:40 -0700 (PDT) X-TACSUNS: Virus Scanned Received: from bonfire.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-sj.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p5UGVc5O000506 for ; Thu, 30 Jun 2011 09:31:39 -0700 (PDT) Received: from ams-etychon-89113.cisco.com (ams-etychon-89113.cisco.com [10.60.74.14]) by bonfire.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p5UGVXv3027402 for ; Thu, 30 Jun 2011 09:31:33 -0700 (PDT) From: Emmanuel Tychon Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: multipart/alternative; boundary=Apple-Mail-83-431809713 Date: Thu, 30 Jun 2011 18:31:31 +0200 In-Reply-To: To: eman@ietf.org References: Message-Id: X-Mailer: Apple Mail (2.1084) Subject: Re: [eman] draft-tychon-eman-applicability-statement-02.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: Thu, 30 Jun 2011 16:31:40 -0000 --Apple-Mail-83-431809713 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii For those it may concern: 1) can you please make sure we have not missed any important use case = in this version of the applicability statement? 2) do we have all the information to decide what to do with the = entity-MIB and move on? Thanks, Emmanuel On 24 Jun 2011, at 23:09, Emmanuel Tychon wrote: >=20 > A major revision of the EMAN-AS applicability statement draft has been = posted.=20 >=20 > Here's the link to the new version: > = http://tools.ietf.org/html/draft-tychon-eman-applicability-statement-02=20= >=20 > The diff can be viewed here: > = http://tools.ietf.org/rfcdiff?difftype=3D--hwdiff&url2=3Ddraft-tychon-eman= -applicability-statement-02.txt > Changes: >=20 > - A new section on Use cases with examples and target devices in = the scope of EMAN has been included.=20 >=20 > - A section of use case contexts as an abstraction of the example = scenarios is included >=20 > These two sections can be useful to continue the discussion from = the EMAN WG discussion @ Prague = http://www.ietf.org/proceedings/80/minutes/eman.txt >=20 > -Can Entity MIB be used to model the EMAN scenarios ? =20 >=20 > - The relevant standards for EMAN have been updated with = information on how these standards have been reused and also how these = influence EMAN is presented >=20 > - The introduction section has been reorganized and would make it = easier for a relative newcomer to understand and participate in the = Energy work @ EMAN WG. >=20 > - Many rewording to improve readability >=20 > Your comments are welcome. >=20 > Thanks, >=20 > Emmanuel, Mouli, and Brad >=20 >=20 --Apple-Mail-83-431809713 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii

A = major revision of the EMAN-AS applicability statement draft has been = posted. 

Here's the link to the new version:

The = diff can be viewed here:

Changes:

-    A new section on Use cases = with examples and target devices in the scope of EMAN has been = included. 

-    A section of use case contexts = as an abstraction of the example scenarios is = included

   These = two sections can be useful to continue the discussion from the EMAN WG = discussion @ Prague  http://www.ietf.org/proceedings/80/minutes/eman.txt

-Can Entity MIB be used to model the EMAN scenarios ? =  

-    The = relevant standards for EMAN have been updated with information on how = these standards have been reused and also how these influence EMAN is = presented

-    The introduction section has = been reorganized and would make it easier for a relative newcomer to = understand and participate in the Energy work @ EMAN = WG.

-    Many = rewording to improve readability

Your comments are welcome.

Thanks,

Emmanuel, Mouli, and = Brad



= --Apple-Mail-83-431809713--