From prao96@stanford.edu Fri Nov 1 10:31:31 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7E9F11E80F8 for ; Fri, 1 Nov 2013 10:31:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.232 X-Spam-Level: X-Spam-Status: No, score=-4.232 tagged_above=-999 required=5 tests=[AWL=0.255, BAYES_05=-1.11, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G0EYc6XiKnUS for ; Fri, 1 Nov 2013 10:31:26 -0700 (PDT) Received: from smtp.stanford.edu (smtp3.Stanford.EDU [171.67.219.83]) by ietfa.amsl.com (Postfix) with ESMTP id 7BF7E21E809A for ; Fri, 1 Nov 2013 10:30:55 -0700 (PDT) Received: from smtp.stanford.edu (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 3F218100F4C for ; Fri, 1 Nov 2013 10:30:55 -0700 (PDT) Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by smtp.stanford.edu (Postfix) with ESMTPS id C6613100CD1 for ; Fri, 1 Nov 2013 10:30:53 -0700 (PDT) Received: by mail-wi0-f173.google.com with SMTP id ey11so1408131wid.0 for ; Fri, 01 Nov 2013 10:30:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=PQauhHYT0hM4hRUbZjYMAmTBb2UxXOq6wD4zQZN4JVs=; b=eB5Nx0KxdCR7Gfa+UjoO9fvDTsDVolsESfBDGsvZnYW1MXxqvEkGnBI6O6gxby1r37 paB270xI0/28/ELBajJjql2J4a+FBV41ARXWgI2r0HgUONSVzjX027/FuqbVdQcgA2Vk tpAgaULyaC7j7/mnGivoYzMvcTeuQY9gqRB8XE9IVJsvNSja++sO16b9Y/IJpRRskfdT 2HoODRqFdAN0GRQipAB8Np6YLKuhRy2ijz9fMp/7yv+eLq1PTC44JT6a5wNqcZaULlSo KDoA2Cn4SLotRnBXN+zx6XHiGykT4S32RosbVWOAaELW2OaLv818CByerAKNKXb8Szkb KXvg== X-Gm-Message-State: ALoCoQmkb/1VWde2pSSEfcVqy96X53S556q85FqG+wI2hREIiOgolOxTQVKptBU9/CDExFlHZtcsUCjHby4PNdVJNwK3KX2kxXWQlaXu3WFutxnjvF/zskU49Vf0fIkV4+eQp055FNgZ X-Received: by 10.180.182.193 with SMTP id eg1mr3268401wic.49.1383327052378; Fri, 01 Nov 2013 10:30:52 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.182.193 with SMTP id eg1mr3268392wic.49.1383327052281; Fri, 01 Nov 2013 10:30:52 -0700 (PDT) Received: by 10.217.127.3 with HTTP; Fri, 1 Nov 2013 10:30:52 -0700 (PDT) Date: Fri, 1 Nov 2013 10:30:52 -0700 Message-ID: From: Priyanka Rao To: eman@ietf.org Content-Type: multipart/alternative; boundary=089e016340ce8f4d6404ea20ed2c Subject: [eman] Python Implementation 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, 01 Nov 2013 17:31:31 -0000 --089e016340ce8f4d6404ea20ed2c Content-Type: text/plain; charset=ISO-8859-1 Hi all, I emailed last week about a python implementation for energy management systems that I have been working on. Just wanted to thank everyone for the helpful feedback and send out an update on where I am now. I was able to get the Python implementation going, although I had some minor issues modifying my implementation to parse live data. Once I finished the CSV parser, I had no problems with actually feeding the data into the implementation. My next step is to complete my analysis of how the implementation fits with current systems and format my paper per standards. Would love to hear any other thoughts on things I can look at! Thanks, Priyanka Rao Stanford '16 --089e016340ce8f4d6404ea20ed2c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi all,=A0

I emailed last week ab= out a python implementation for energy management systems that I have been = working on. =A0Just wanted to thank everyone for the helpful feedback and s= end out an update on where I am now.

I was able to get the Python implementation= going, although I had some minor issues modifying my implementation to par= se live data. =A0Once I finished the CSV parser, I had no problems with act= ually feeding the data into the implementation. =A0My next step is to compl= ete my analysis of how the implementation fits with current systems and for= mat my paper per standards. =A0Would love to hear any other thoughts on thi= ngs I can look at!

Thanks,=A0
Priyanka Rao=A0<= /div>
Stanford '16
--089e016340ce8f4d6404ea20ed2c-- From luchuk@snmp.com Fri Nov 1 12:24:14 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A817F11E8179 for ; Fri, 1 Nov 2013 12:24:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.185 X-Spam-Level: X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XYd3uqAaLyhT for ; Fri, 1 Nov 2013 12:24:10 -0700 (PDT) Received: from mailbox.snmp.com (mailbox.snmp.com [192.147.142.80]) by ietfa.amsl.com (Postfix) with ESMTP id 168AF11E80DE for ; Fri, 1 Nov 2013 12:24:10 -0700 (PDT) Received: from adminfs.snmp.com (adminfs.snmp.com [192.147.142.39]) by mailbox.snmp.com (8.9.3p2-20030922/m.0080228) with ESMTP id PAA19944; Fri, 1 Nov 2013 15:24:07 -0400 (EDT) Received: (from luchuk@localhost) by adminfs.snmp.com (8.9.3p2-20030922/snmpclient.mc-990525) id PAA09600; Fri, 1 Nov 2013 15:24:06 -0400 (EDT) Date: Fri, 1 Nov 2013 15:24:06 -0400 (EDT) From: Alan Luchuk Message-Id: <201311011924.PAA09600@adminfs.snmp.com> To: eman@ietf.org Subject: [eman] Updated EMAN prototype 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, 01 Nov 2013 19:24:14 -0000 Hello, SNMP Research's EMAN prototype has been updated to implement the latest MIBs from: rfc6933.txt draft-ietf-eman-energy-aware-mib-10.txt draft-ietf-eman-energy-monitoring-mib-07.txt draft-ietf-eman-battery-mib-10.txt If you are interested, you can try out the prototype by following the instructions in: http://www.ietf.org/mail-archive/web/eman/current/msg01802.html Due to other development priorities, the minimum changes were added to the prototype, so the updated prototype looks amazingly similar to the earlier prototype. The easily-noticed changes include the addition of the batteryCellIdentifier object and the changes to the object names from powerACPwrCharacteristicsYYY to eoACPwrAttributesYYY. We have not yet studied the updated documents, so we do not yet have significant technical comments. At this time, our only comments are: 1) In draft-ietf-eman-energy-monitoring-mib-07, fix the spacing in "POWER- ATTRIBUTES -MIB DEFINITIONS" so that the MIB name is "POWER-ATTRIBUTES-MIB". 2) For walking the EMAN MIBs, in constrast to registering each EMAN MIB with an OID subordinate to mib-2, it would be helpful if a single "root" OID were registered with IANA, and all of the individual EMAN MIBs were subordinate to root OID. This would allow a single OID to be registered with IANA, and would simplify "walking" the EMAN MIBs by iterating through all of the OIDs under the root. We hope these efforts and comments are helpful to the EMAN WG. Regards, --Alan ------------------------------------------------------------------------------ Alan Luchuk SNMP Research, Inc. Voice: +1 865 573 1434 Senior Software Engineer 3001 Kimberlin Heights Road FAX: +1 865 573 9197 luchuk at snmp.com Knoxville, TN 37920-9716 http://www.snmp.com/ ------------------------------------------------------------------------------ From tnadeau@lucidvision.com Fri Nov 1 16:13:25 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0662311E80E9 for ; Fri, 1 Nov 2013 16:13:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.203 X-Spam-Level: X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XT1Eq8sQFvaG for ; Fri, 1 Nov 2013 16:13:20 -0700 (PDT) Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 8A43C11E8136 for ; Fri, 1 Nov 2013 16:13:20 -0700 (PDT) Received: from [10.89.40.64] (mobile-198-228-199-073.mycingular.net [198.228.199.73]) by lucidvision.com (Postfix) with ESMTP id 9E63625CFA17; Fri, 1 Nov 2013 19:13:14 -0400 (EDT) References: <201311011924.PAA09600@adminfs.snmp.com> Mime-Version: 1.0 (1.0) In-Reply-To: <201311011924.PAA09600@adminfs.snmp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <219CD146-15F9-4FAA-8B99-F8FC891B8AB3@lucidvision.com> X-Mailer: iPhone Mail (11B511) From: "Thomas D. Nadeau" Date: Fri, 1 Nov 2013 19:13:12 -0400 To: Alan Luchuk Cc: "eman@ietf.org" Subject: Re: [eman] Updated EMAN prototype 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, 01 Nov 2013 23:13:25 -0000 very cool. thanks for the update. Tom Von meinem iPhone gesendet > On Nov 1, 2013, at 3:24 PM, Alan Luchuk wrote: >=20 > Hello, >=20 > SNMP Research's EMAN prototype has been updated to implement the latest =20= > MIBs from: >=20 > rfc6933.txt > draft-ietf-eman-energy-aware-mib-10.txt > draft-ietf-eman-energy-monitoring-mib-07.txt > draft-ietf-eman-battery-mib-10.txt >=20 > If you are interested, you can try out the prototype by following the > instructions in: >=20 > http://www.ietf.org/mail-archive/web/eman/current/msg01802.html >=20 > Due to other development priorities, the minimum changes were added to > the prototype, so the updated prototype looks amazingly similar to the > earlier prototype. The easily-noticed changes include the addition of > the batteryCellIdentifier object and the changes to the object names > from powerACPwrCharacteristicsYYY to eoACPwrAttributesYYY. >=20 > We have not yet studied the updated documents, so we do not yet have > significant technical comments. At this time, our only comments are: >=20 > 1) In draft-ietf-eman-energy-monitoring-mib-07, fix the spacing in > "POWER- ATTRIBUTES -MIB DEFINITIONS" so that the MIB name is > "POWER-ATTRIBUTES-MIB". >=20 > 2) For walking the EMAN MIBs, in constrast to registering each EMAN MIB > with an OID subordinate to mib-2, it would be helpful if a single > "root" OID were registered with IANA, and all of the individual EMAN > MIBs were subordinate to root OID. This would allow a single OID > to be registered with IANA, and would simplify "walking" the EMAN MIBs > by iterating through all of the OIDs under the root. >=20 > We hope these efforts and comments are helpful to the EMAN WG. >=20 > Regards, > --Alan >=20 > --------------------------------------------------------------------------= ---- > Alan Luchuk SNMP Research, Inc. Voice: +1 865 573 1= 434 > Senior Software Engineer 3001 Kimberlin Heights Road FAX: +1 865 573 9= 197 > luchuk at snmp.com Knoxville, TN 37920-9716 http://www.snmp.com= / > --------------------------------------------------------------------------= ---- >=20 > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman >=20 From david.prantl@joulex.net Mon Nov 4 02:48:15 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 247BC11E82D8 for ; Mon, 4 Nov 2013 02:48:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.691 X-Spam-Level: X-Spam-Status: No, score=-0.691 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_ILLEGAL_IP=1.908] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K+zksg75knTs for ; Mon, 4 Nov 2013 02:48:06 -0800 (PST) Received: from mx-relay06.cloudservice.ag (mx-relay06.cloudservice.ag [81.20.94.248]) by ietfa.amsl.com (Postfix) with ESMTP id 61BAD11E8104 for ; Mon, 4 Nov 2013 02:45:57 -0800 (PST) Received: from fw1.hostedoffice.ag ([81.20.90.82]) by mx-gate06.cloudservice.ag; Mon, 04 Nov 2013 11:45:47 +0100 Received: from EX10HUB4.hosting.inetserver.de (unknown [10.20.10.72]) by qhexrelay2.hosting.inetserver.de (Postfix) with ESMTP id A41D11870DE; Mon, 4 Nov 2013 11:45:47 +0100 (CET) Received: from qhexhub6.hosting.inetserver.de (10.20.10.25) by EX10HUB4.hosting.inetserver.de (10.20.10.72) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 4 Nov 2013 11:45:47 +0100 Received: from QHEXMBOX2.hosting.inetserver.de ([fe80:0000:0000:0000:d926:a88f:242.116.230.85]) by qhexhub6.hosting.inetserver.de ([10.20.10.225]) with mapi; Mon, 4 Nov 2013 11:45:47 +0100 From: David Prantl To: "eman@ietf.org" Date: Mon, 4 Nov 2013 11:45:38 +0100 Thread-Topic: Current Eman Draft/draft-ietf-eman-framework Thread-Index: AQHO2Ur//rSBSSUpK0iv1+fh5j/Uqw== Message-ID: <7B9BC0FC24CECF4A840DB64B5C5B77851165C38705@QHEXMBOX2.hosting.inetserver.de> Accept-Language: de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-EXCLAIMER-MD-CONFIG: e299f49b-79fd-4cde-afcd-99df35de8a6e X-cloud-security-sender: david.prantl@joulex.net X-cloud-security-recipient: eman@ietf.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mx-gate06 with 5910C2B8002 X-cloud-security-connect: fw1.hostedoffice.ag[81.20.90.82], TLS=, IP=81.20.90.82 X-cloud-security: scantime:.1557 X-Mailman-Approved-At: Mon, 04 Nov 2013 08:51:26 -0800 Subject: [eman] Current Eman Draft/draft-ietf-eman-framework 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, 04 Nov 2013 10:57:45 -0000 Dear all, I have been on this list since 2011, we built a commercial Energy Managemen= s System - the Joulex Energy Manager which is now being used by over 220 cu= stomers across the world. We found the eman information model reasonable for devices (it would be gre= at if all devices used it) and built our Energy Management System based on = it. We like the ability to have common generic attributes such as keywords, imp= ortance, caliber, relationships, etc I believe the the Eman framework is good to go for a standard information m= odel for devices and Energy Management Systems. Regards, David Prantl= From bnordman@lbl.gov Mon Nov 4 10:05:05 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30E7E11E8209 for ; Mon, 4 Nov 2013 10:05:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.444 X-Spam-Level: X-Spam-Status: No, score=-5.444 tagged_above=-999 required=5 tests=[AWL=0.532, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4-ijEmagpli3 for ; Mon, 4 Nov 2013 10:05:00 -0800 (PST) Received: from fe1.lbl.gov (fe1.lbl.gov [128.3.41.133]) by ietfa.amsl.com (Postfix) with ESMTP id B8DD411E812B for ; Mon, 4 Nov 2013 10:04:52 -0800 (PST) X-Ironport-SBRS: 4.8 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AkkEAO/gd1LRVaA2lGdsb2JhbABWA4JDfFOtD4loiEeBIQgWDgEBAQEHCwsJEiqCJQEBBAFnCwcFCwsLOyISAQUBHAYTh3sGBQigEZ40jhkBBoEoEAcRhB0DiUCOSoEvjm4YKYRyG4EsAR8 X-IronPort-AV: E=Sophos;i="4.93,634,1378882800"; d="scan'208";a="32325967" Received: from mail-pb0-f54.google.com ([209.85.160.54]) by fe1.lbl.gov with ESMTP; 04 Nov 2013 10:04:49 -0800 Received: by mail-pb0-f54.google.com with SMTP id ro12so1952208pbb.41 for ; Mon, 04 Nov 2013 10:04:49 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=phxgB1VdjHuQBXz4YRn5WWvsKrBFzjEF5MTR2y3vlao=; b=PtvxoL4DcqZrHbjKr3GJiEf7lGiEaKmlbxwcNrWULGJM/gjvs+L9I7TViVNa21TKXd MlAH7U9ZtXB4El+DY6y6jhh9V7VeJaszHp+nK67od8ykLaNAJcEOFB6SCvydQ8pVTwkw 7O1FpIqwfnTNCZIWhIB4smWhuCqi1ooUGuS2+uWF0egPOXiUc3e6jZo+PfYwqlFUyJYt wVYLRH5FIkuAoWC88W6uiza/G6UBE+x39sPaTSKHz6JviDC+yO8cy2KCe0sPam1SWE5J cOY5OjhVgKJiRgm5zF71Y4KP2xttSkG6sMdl4vbg52aJeT3YEcR3AG659DB1VHEANaHA Atpg== X-Gm-Message-State: ALoCoQn0jzg1LRRiK2FfeJZ8v1VCpb72/b443aP22Z4vsZEZmB64ZBAahXDno88s423bUARqReFOD6ARRKBkJuahtTIJEznFOUzS1sQFAAYeuxL6GjB5IV5GVpOzoObVpGhepaFDGtl3 X-Received: by 10.68.130.234 with SMTP id oh10mr19200333pbb.0.1383588289610; Mon, 04 Nov 2013 10:04:49 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.68.130.234 with SMTP id oh10mr19200312pbb.0.1383588289459; Mon, 04 Nov 2013 10:04:49 -0800 (PST) Received: by 10.68.148.134 with HTTP; Mon, 4 Nov 2013 10:04:49 -0800 (PST) In-Reply-To: <9C213D38848B89428F46808B16F6F0860166795D@xmb-aln-x04.cisco.com> References: <9C213D38848B89428F46808B16F6F0860166795D@xmb-aln-x04.cisco.com> Date: Mon, 4 Nov 2013 10:04:49 -0800 Message-ID: From: Bruce Nordman To: "John Parello (jparello)" Content-Type: multipart/alternative; boundary=047d7b10cb7582495d04ea5dc087 Cc: "eman@ietf.org" Subject: Re: [eman] BNordman - draft-ietf-eman-framework-09: WGLC comments 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, 04 Nov 2013 18:05:05 -0000 --047d7b10cb7582495d04ea5dc087 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable John-- Thanks much for carefully considering and replying to my comments. While the document is improving, as you note, there are still many major issues where we don't agree. I do agree with you that further discussion is not likely to change either of our minds so no need to invest time in that. I still think that starting from the Energy Reporting draft draft-nordman-eman-er-framework-02 would get us to a framework document suitable for passing WGLC faster and with a higher quality result. My concerns are still such that I don't think this version is suitable for WGLC. However, if I am the only one on the list stating that then that is not sufficient to block progress. I trust you will all have a good and productive meeting. Best regards, --Bruce On Sun, Oct 13, 2013 at 3:02 PM, John Parello (jparello) wrote: > Hi Bruce, > > Thanks so much for your comments. Considering your position on the draft > I'll limit the comments applied to those that are or are near editorial. > Those that indicate a previously stated approach counter to your proposal > I'll leave so we don't have unnecessary debate or lobbying. > > (+) Applied in the draft > (-) Regretfully not applied for the reasons listed > (!) Not applied needing more clarification and/or see further comment or > thread > > > Thanks > Jp > > --------------------------------- > > > The EMAN Framework draft is improving, as has been noted. That said, > the comments below plus those in the review a few days ago from Juergen > Quittek indicate that the document still has far to go. This list > is not comprehensive--that is not feasible with so much to address. > In addition, fixes that these comments lead to are likely to introduce > new issues or make clear existing ones that are not now readily apparent. > As this document has changed considerably over the past three+ years, > new issues continue to crop up. > > > Conceptual issues: > > The mechanisms described for importance and role are non-standard and > arbitrary. We might do well to have standard mechanisms for some > of these, but creating an anecdotal set solely in the context of EMAN > seems unlikely to contribute to that. Until such time as there is some > basis for incorporating specific content, these should be left as > free-form keywords encoded in some standard syntax. > > - JP : We gave guidance on that field. Moving this to keywords with no > standard syntax only moves your point to another attribute?. > > The "relationship" concept is not necessary. Simpler methods can express > what is required. It makes the document harder to understand, and so > is a barrier to it being widely adopted. > > - JP : We receive feedback that this was useful and we've carried this > approach for some time > > It is stated that a device should be labeled as "a consumer, producer, > or meter, distributor, or store of energy". It isn't explained what the > value of making this distinction is. > > ! JP : we can expand on that but though the category was enough. > Suggestions? > > The concept of "caliber"is not needed; accuracy is sufficient. > > - JP : This was our most asked for attributes. Accuracy for a device that > does not use statistical nor physical (H/W) means to measure power is > meaningless. We need a way to indicate which devices can or can't measure > power (some based on table lookups for example) See any EnMS on their > "power ratings" Joulex, Nimsoft, Schneider etc. Also device manufacturer= s > embraced this notion at ODVA and the Cisco implementation. Very much need= ed. > > The draft states that a device must have at least two states: one > on state and one off state. There are devices for sale that have > two states, on and sleep (but no off) and devices with only one > state. Why have this restriction? and why require a device to > report power states at all? most will certainly but some might > appropriately not do so. > > + JP : should > > > The explanation of power state semantics in 4.5 is not consistent > with general usage of the concept of power state. Power limitation > may be useful, but it is a different concept from power state and > should not be conflated. > > 4.5.4. These are arbitrary. It would be better to specify registration > of the Cisco power state set since that is presumably already in use. > > 4.6. Power Source Relationship and Metering Relationship are redundant. > As the text points out, both are about wiring topologies. > > 4.6.3. The second and last paragraphs seem to be contradictory as > to whether two non-connected PIs can have a Power Source Relationship. > > 4.6.3. It is not clear how metering is to be applied. > > 4.6.4. It is stated that "Establishing aggregation relationships within > the same device would make modeling more complex=E2=80=A6". The ER Frame= work > accomplishes this without any complexity burden, so the statement in > general is not true. It may be true of the EMAN Framework but that is > simply a flaw in the document. > > 4.6.5. The text leaves "proxy" relationships for future development, > but there are requirements (8.1) for proxy control that the framework > seems to not cover. > > 6. It is stated that some products cannot support power interfaces. > Any device can and could simply report "unknown" for data they do not kno= w. > > 6.1. The draft indicates that power interfaces can be between devices and > components. This adds a lot of complexity to the PI concept. It would > be much simpler to not allow PIs between components. For those niche > applications that desire that, the component in question could be modeled > as a distinct device. Thus, complexity of EMAN could be reduced without > sacrificing capability. > > Aggregation: > > 4.6. It is completely unclear how the Aggregation Relationship mentioned > is supposed to operate. > > 4.6.4. It is suggested that a device can report only a single aggregatio= n. > Is that true? > > 6.3. explains what aggregation is, but not how it actually works. > The two sentences in the middle paragraph contradict each other. > > Corrections: > > The introductions states that "The framework introduces the concept of > a power interface". This is not true. The power interface concept > was introduced in draft-quittek-eman-reference-model-02, over two > years ago. Also, the definition provided for Power Interface doesn't > make sense, and does not correspond to the concept described in the > Reference Model, or the ER Framework. The latter has a clear explanation= , > the first sentence of which could be a definition. > > ! JP : We merged that document with this and the authors are on this > document. @Chairs can we reference a non-wg item that is expired, best wa= y > to footnote this? > > The bulleted text under 4.5.2 on IEEE 1621 is wrong. I have pointed > this out many many times without it being fixed. Also, for 4.5.5, > IEEE 1621 does NOT say that hibernate is a form of sleep; it says that > hibernate should be presented as a form of off. This error has also > been pointed out many times. > > + JP : changed to off in 4.5.5. Section 4.5.2 now directly quotes > IEEE1621 4.1 > """ > The IEEE1621 Power State Set [IEEE1621] consists of 3 rudimentary states: > on, off or sleep. > In IEEE1621 devices are limited to the three basic power states =97 on, > sleep, and off. Any additional power states are variants of one of the > basic states rather than a fourth state. > """ > > Details: > > 2. Definition of "Meter". Change "intended to measure" to "that measures= ". > In general, what is the difference intended when "are intended to" is > used as opposed to what the referenced concepts actually do? > > - JP : see IEC60050 > > Unnecessary text: > > The document is burdened throughout by text that is unnecessary to > accomplish what is needed. This makes reading it more difficult and > so would impede use of the standard. An example is defining and > discussing Non-Electrical Equipment. This is more appropriate to > an application/implementation discussion document, not a framework. > Other examples include the list of target devices in Section 3.1, all > of Section 3.4, sections 4.3.3, 4.3.4, 4.3.5, the second half of 4.3.6, > and the middle two paragraphs of 4.4. > > The requirements RFC says: > 5.5.1. Energy Measurement > The standard must provide means for reporting measured values of > energy and the direction of the energy flow received or provided by > an entity. The standard must also provide the means to report the > energy passing through each Power Interface. > The Framework says: > 4.4.3. Measurements: Energy > Optionally, an Energy Object that can report actual power > readings will have energy attributes that provide the > energy used, produced, or stored in kWh. > Aside from noting that kWh are to be used, what is the point of saying > this at all? and if this is about reporting energy, why does the text > talk about power? > > ! JP : Not sure how you can have energy values if you can't measure actua= l > power. ANything you can suggest to make that clearer as you read it? > > Thanks! > Jp > > > --=20 *Bruce Nordman* Lawrence Berkeley National Laboratory *nordman.lbl.gov * BNordman@LBL.gov 510-486-7089 m: 510-501-7943 --047d7b10cb7582495d04ea5dc087 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable
John--
= =A0 Thanks much for carefully considering and replying to my comments.
<= /div>While the document is improving, as you note, there are still many maj= or
issues where we don't agree.=A0 I do agree with you that further discus= sion
is not likely to change either of our minds so no need to invest ti= me in that.
=A0 I still think that starting from the Energy Report= ing draft
=A0=A0=A0=A0=A0 draft-nordman-eman-er-framework-02
would get= us to a framework document suitable for passing WGLC faster
and with a = higher quality result.=A0 My concerns are still such that I don't think=
this version is suitable for WGLC.=A0 However, if I am the only one on the = list
stating that then that is not sufficient to block progress.
=A0 I trust you will all have a good and productive meeting.
=A0 Best regards,
--Bruce

=
On Sun, Oct 13, 2013 at 3:02 PM, John Parell= o (jparello) <jparello@cisco.com> wrote:
Hi Bruce,
Thanks so much for your comments. Considering your position on the draft I&= #39;ll limit the comments applied to those that are or are near editorial. = Those that indicate a previously stated approach counter to your proposal I= 'll leave so we don't have unnecessary debate or lobbying.

(+) Applied in the draft
(-) Regretfully not applied for the reasons listed
(!) Not applied needing more clarification and/or see further comment or th= read


Thanks
Jp

---------------------------------


The EMAN Framework draft is improving, as has been noted.=A0 That said,
the comments below plus those in the review a few days ago from Juergen
Quittek indicate that the document still has far to go.=A0 This list
is not comprehensive--that is not feasible with so much to address.
In addition, fixes that these comments lead to are likely to introduce
new issues or make clear existing ones that are not now readily apparent. As this document has changed considerably over the past three+ years,
new issues continue to crop up.


Conceptual issues:

The mechanisms described for importance and role are non-standard and
arbitrary.=A0 We might do well to have standard mechanisms for some
of these, but creating an anecdotal set solely in the context of EMAN
seems unlikely to contribute to that.=A0 Until such time as there is some basis for incorporating specific content, these should be left as
free-form keywords encoded in some standard syntax.

- JP : We gave guidance on that field.=A0 Moving this to keywords with no s= tandard syntax only moves your point to another attribute?.
=A0
The "relationship" concept is not necessary.=A0 Simpler methods c= an express
what is required.=A0 It makes the document harder to understand, and so
is a barrier to it being widely adopted.

- JP : We receive feedback that this was useful and we've carried this = approach for some time

It is stated that a device should be labeled as "a consumer, producer,=
or meter, distributor, or store of energy".=A0 It isn't explained = what the
value of making this distinction is.

! JP : we can expand on that but though the category was enough. Suggestion= s?

The concept of "caliber"is not needed; accuracy is sufficient.
- JP : This was our most asked for attributes. Accuracy for a device that d= oes not use statistical nor physical (H/W) means to measure power is meanin= gless. We need a way to indicate which devices can or can't measure pow= er (some based on table lookups for example) See any EnMS on their "power ratings"=A0 Joulex, Nimsof= t, Schneider etc. Also device manufacturers embraced this notion at ODVA an= d the Cisco implementation. Very much needed.

The draft states that a device must have at least two states: one
on state and one off state.=A0 There are devices for sale that have
two states, on and sleep (but no off) and devices with only one
state.=A0 Why have this restriction?=A0 and why require a device to
report power states at all?=A0 most will certainly but some might
appropriately not do so.

+ JP :=A0 should


The explanation of power state semantics in 4.5 is not consistent
with general usage of the concept of power state.=A0 Power limitation
may be useful, but it is a different concept from power state and
should not be conflated.

4.5.4. These are arbitrary.=A0 It would be better to specify registration of the Cisco power state set since that is presumably already in use.

4.6. Power Source Relationship and Metering Relationship are redundant.
As the text points out, both are about wiring topologies.

4.6.3. The second and last paragraphs seem to be contradictory as
to whether two non-connected PIs can have a Power Source Relationship.

4.6.3. It is not clear how metering is to be applied.

4.6.4. It is stated that "Establishing aggregation relationships withi= n
the same device would make modeling more complex=E2=80=A6".=A0 The ER = Framework
accomplishes this without any complexity burden, so the statement in
general is not true.=A0 It may be true of the EMAN Framework but that is simply a flaw in the document.

4.6.5. The text leaves "proxy" relationships for future developme= nt,
but there are requirements (8.1) for proxy control that the framework
seems to not cover.

6. It is stated that some products cannot support power interfaces.
Any device can and could simply report "unknown" for data they do= not know.

6.1. The draft indicates that power interfaces can be between devices and components.=A0 This adds a lot of complexity to the PI concept.=A0 It would=
be much simpler to not allow PIs between components.=A0 For those niche
applications that desire that, the component in question could be modeled as a distinct device.=A0 Thus, complexity of EMAN could be reduced without<= br> sacrificing capability.

Aggregation:

4.6. It is completely unclear how the Aggregation Relationship mentioned is supposed to operate.

4.6.4.=A0 It is suggested that a device can report only a single aggregatio= n.
Is that true?

6.3. explains what aggregation is, but not how it actually works.
The two sentences in the middle paragraph contradict each other.
=A0
Corrections:

The introductions states that "The framework introduces the concept of=
a power interface".=A0 This is not true.=A0 The power interface concep= t
was introduced in draft-quittek-eman-reference-model-02, over two
years ago.=A0 Also, the definition provided for Power Interface doesn't=
make sense, and does not correspond to the concept described in the
Reference Model, or the ER Framework.=A0 The latter has a clear explanation= ,
the first sentence of which could be a definition.

! JP : We merged that document with this and the authors are on this docume= nt. @Chairs can we reference a non-wg item that is expired, best way to foo= tnote this?

The bulleted text under 4.5.2 on IEEE 1621 is wrong.=A0 I have pointed
this out many many times without it being fixed.=A0 Also, for 4.5.5,
IEEE 1621 does NOT say that hibernate is a form of sleep; it says that
hibernate should be presented as a form of off.=A0 This error has also
been pointed out many times.

+ JP : changed to off in 4.5.5.=A0 Section 4.5.2 now directly quotes IEEE16= 21 4.1
"""
The IEEE1621 Power State Set [IEEE1621] consists of 3 rudimentary states: o= n, off or sleep.
In IEEE1621 devices are limited to the three basic power states =97 on, sle= ep, and off. Any additional power states are variants of one of the basic s= tates rather than a fourth state.
"""

Details:

2. Definition of "Meter".=A0 Change "intended to measure&quo= t; to "that measures".
In general, what is the difference intended when "are intended to"= ; is
used as opposed to what the referenced concepts actually do?

- JP : see IEC60050

Unnecessary text:

The document is burdened throughout by text that is unnecessary to
accomplish what is needed.=A0 This makes reading it more difficult and
so would impede use of the standard.=A0 An example is defining and
discussing Non-Electrical Equipment.=A0 This is more appropriate to
an application/implementation discussion document, not a framework.
Other examples include the list of target devices in Section 3.1, all
of Section 3.4, sections 4.3.3, 4.3.4, 4.3.5, the second half of 4.3.6,
and the middle two paragraphs of 4.4.

The requirements RFC says:
5.5.1.=A0 Energy Measurement
=A0=A0 The standard must provide means for reporting measured values of
=A0=A0 energy and the direction of the energy flow received or provided by<= br> =A0=A0 an entity.=A0 The standard must also provide the means to report the=
=A0=A0 energy passing through each Power Interface.
The Framework says:
=A0=A0=A0 4.4.3. Measurements: Energy
=A0=A0=A0=A0=A0=A0=A0 Optionally, an Energy Object that can report actual p= ower
=A0=A0=A0=A0=A0=A0=A0 readings will have energy attributes that provide the=
=A0=A0=A0=A0=A0=A0=A0 energy used, produced, or stored in kWh.=A0
Aside from noting that kWh are to be used, what is the point of saying
this at all?=A0 and if this is about reporting energy, why does the text talk about power?

! JP : Not sure how you can have energy values if you can't measure act= ual power. ANything you can suggest to make that clearer as you read it?
Thanks!
Jp





--
Bru= ce Nordman
Lawrence Berkel= ey National Laboratory
nordman.lbl.gov=
BNordman@LBL.gov
510-486-7089
m: 510-501-7943
--047d7b10cb7582495d04ea5dc087-- From tnadeau@lucidvision.com Mon Nov 4 13:20:08 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3978A21F9FAB for ; Mon, 4 Nov 2013 13:20:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5HF55B0MVypz for ; Mon, 4 Nov 2013 13:19:49 -0800 (PST) Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id B567211E81A7 for ; Mon, 4 Nov 2013 13:19:48 -0800 (PST) Received: from dhcp-b531.meeting.ietf.org (dhcp-b531.meeting.ietf.org [31.133.181.49]) by lucidvision.com (Postfix) with ESMTP id 62A1D25D8BB9; Mon, 4 Nov 2013 16:19:47 -0500 (EST) From: Thomas Nadeau Content-Type: multipart/signed; boundary="Apple-Mail=_9F4A847F-31EE-4920-A759-F03375B20010"; protocol="application/pgp-signature"; micalg=pgp-sha512 Date: Mon, 4 Nov 2013 13:19:45 -0800 Message-Id: <70DA66D0-4C50-49AB-9D6F-4E24E38E0856@lucidvision.com> To: eman@ietf.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\)) X-Mailer: Apple Mail (2.1816) Subject: [eman] Slides Needed for Presentations 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, 04 Nov 2013 21:20:08 -0000 --Apple-Mail=_9F4A847F-31EE-4920-A759-F03375B20010 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Presenters, If you have not sent the chairs your slides, please do so today. = We need your slides ahead of the meeting. Thanks, --Tom --Apple-Mail=_9F4A847F-31EE-4920-A759-F03375B20010 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJSeA9xAAoJEPcO+I7eiUJZf8AP/315zrD8hsrNS/mYikC7k+19 8YMe1oM/DFuMf3IgembOzYSIRhlPovE4PmqOsbnvp9rTF/EsUjjvDzbz8SQddJfM jV88rYIbb1gYsChi+MEarTIxZPhu5xuJ+cg9kJUlBhEe7TynToKYEFVClsw3mij2 DQ0l/4gYD9T3J6mc9wmj8gTZFst21PrtqvHAWpDA/VnXVeFdcSPAWO2JiG6E9UBF h95emJZbqWGToNCttyql/8tJvizT/XnnhmBoGeUkppeFchg84XACrqhztd9neM/m gMeBxT9r/dCwbjMz8kylKT9Z+NX9KdeXmP0ciKcOi6Sq9SaPoI6Nyt1n5EyvM4oU LE+Dvp/dsF1FZhLvZjS23O51E9xlk3nIWdOu6bIANWFJ/f3gLNOHk9U4qS+FlxTh DYP++iWgQ2ZA6b58dL1psVOwcGzM56j8arhCQ73yVv4sMfXueUA+uToxd2EFTMDH PPKuHeUNUL5nkN38iDAVH5i0NRFf58aVlmRgXZb35GupG4owU1a6CtaXoBsrW6p9 kmwjb8JDqM27AO0gV70VxEFRwiz4V7JkxAzyDeHFSbYea4R6lCqG1xphsFsZQ+d9 FJeT992lE9EvrnO4roov/kCUlzqTS/m8QwO2ClBXwjYBcCseJrlh/SdMtuL9iZ3Y 07f2aSjbJzTOmbXhkzxO =zvvc -----END PGP SIGNATURE----- --Apple-Mail=_9F4A847F-31EE-4920-A759-F03375B20010-- From tnadeau@lucidvision.com Mon Nov 4 16:18:04 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9FBE11E824E for ; Mon, 4 Nov 2013 16:18:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j-ubWQyoN4eE for ; Mon, 4 Nov 2013 16:18:00 -0800 (PST) Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 13A0A21E80A5 for ; Mon, 4 Nov 2013 16:17:59 -0800 (PST) Received: from [31.133.181.197] (dhcp-b5c5.meeting.ietf.org [31.133.181.197]) by lucidvision.com (Postfix) with ESMTP id F1A9A25D92CC; Mon, 4 Nov 2013 19:17:58 -0500 (EST) References: <52782E44.5030707@auckland.ac.nz> Mime-Version: 1.0 (1.0) In-Reply-To: <52782E44.5030707@auckland.ac.nz> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <45C163BC-C609-4D6A-A3F9-7C1E3233CEAF@lucidvision.com> X-Mailer: iPad Mail (11B511) From: Thomas D Nadeau Date: Mon, 4 Nov 2013 16:17:56 -0800 To: Nevil Brownlee Cc: eman@ietf.org, "eman-chairs@tools.ietf.org" Subject: Re: [eman] Agenda for tomorrow afternoon's meeting at IETF-88 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, 05 Nov 2013 00:18:05 -0000 Resending to the EMAN list. Also, that link does not seem to work. *) Ple= ase try this one: https://datatracker.ietf.org/meeting/88/agenda/eman/ > On Nov 4, 2013, at 3:31 PM, Nevil Brownlee wro= te: >=20 >=20 > Hi all: >=20 > I've updated the agenda for tomorrow, you can see it at > https://datatracker.ietf.org/meeting/88 >=20 > Thanks to the authors/editors who have already sent in their slides, > others please send them to me as soon as you can. >=20 > Cheers, Nevil >=20 > --=20 > --------------------------------------------------------------------- > Nevil Brownlee Computer Science Department | ITS > Phone: +64 9 373 7599 x88941 The University of Auckland > FAX: +64 9 373 7453 Private Bag 92019, Auckland 1142, New Zealand >=20 From jparello@cisco.com Mon Nov 4 16:24:30 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E3A021E811A for ; Mon, 4 Nov 2013 16:24:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6ZilYAj7cuMg for ; Mon, 4 Nov 2013 16:24:25 -0800 (PST) Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 378A221E823D for ; Mon, 4 Nov 2013 16:24:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1220; q=dns/txt; s=iport; t=1383611065; x=1384820665; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=AsGext/Z0nPcdpuAY5jmjcWKz3X9yibKAnRV0Hr3w+U=; b=ltwjSj9jB7g+J2jLwGX/crNZUov4vkPBqOH3HM9YtZIwIOcFchgkATSJ SyVO36f7zAGgfcB8ajZvdsqqE9BCpLB/w836dcCg3nm0xBP8tCTZc0aHq +zZoz3DxopXy2TndVqbfIl2Z3cc6t86gwSjWefoKoRpX+hQ9v6eSAwNJP Y=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhIFAMA5eFKtJXG//2dsb2JhbABZgwc4wAuBJxZ0giUBAQEDAQEBATc0CwUJAgIBCBgeEBsMCyUCBA4Fh3sGDb4mBASPITMHgyCBDgOYCpIJgyY X-IronPort-AV: E=Sophos;i="4.93,636,1378857600"; d="scan'208";a="280644985" Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-8.cisco.com with ESMTP; 05 Nov 2013 00:24:24 +0000 Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id rA50OORq013310 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 5 Nov 2013 00:24:24 GMT Received: from xmb-aln-x04.cisco.com ([169.254.9.227]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.03.0123.003; Mon, 4 Nov 2013 18:24:24 -0600 From: "John Parello (jparello)" To: Thomas D Nadeau Thread-Topic: [eman] Agenda for tomorrow afternoon's meeting at IETF-88 Thread-Index: AQHO2byBL2sYa/hKYka5fEemhOYXxpoVx0iM Date: Tue, 5 Nov 2013 00:24:23 +0000 Message-ID: <809E2438-A961-41F3-B88E-BECB49F50077@cisco.com> References: <52782E44.5030707@auckland.ac.nz>, <45C163BC-C609-4D6A-A3F9-7C1E3233CEAF@lucidvision.com> In-Reply-To: <45C163BC-C609-4D6A-A3F9-7C1E3233CEAF@lucidvision.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "eman@ietf.org" , "eman-chairs@tools.ietf.org" Subject: Re: [eman] Agenda for tomorrow afternoon's meeting at IETF-88 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, 05 Nov 2013 00:24:30 -0000 Hi Thomas, Thanks. Just FYI the framework draft is rev-11 Jp Sent from my iPad=20 (expect ridiculous spelling mistakes)=20 On Nov 4, 2013, at 4:18 PM, "Thomas D Nadeau" wro= te: > Resending to the EMAN list. Also, that link does not seem to work. *) = Please try this one: >=20 > https://datatracker.ietf.org/meeting/88/agenda/eman/ >=20 >> On Nov 4, 2013, at 3:31 PM, Nevil Brownlee w= rote: >>=20 >>=20 >> Hi all: >>=20 >> I've updated the agenda for tomorrow, you can see it at >> https://datatracker.ietf.org/meeting/88 >>=20 >> Thanks to the authors/editors who have already sent in their slides, >> others please send them to me as soon as you can. >>=20 >> Cheers, Nevil >>=20 >> --=20 >> --------------------------------------------------------------------- >> Nevil Brownlee Computer Science Department | ITS >> Phone: +64 9 373 7599 x88941 The University of Auckland >> FAX: +64 9 373 7453 Private Bag 92019, Auckland 1142, New Zealand >>=20 > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman From n.brownlee@auckland.ac.nz Mon Nov 4 18:08:16 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6AD311E826B for ; Mon, 4 Nov 2013 18:08:16 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZaAMNanMAS-9 for ; Mon, 4 Nov 2013 18:08:12 -0800 (PST) Received: from mx2.auckland.ac.nz (mx2.auckland.ac.nz [130.216.125.245]) by ietfa.amsl.com (Postfix) with ESMTP id 50C4D11E8267 for ; Mon, 4 Nov 2013 18:08:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=uoa; t=1383617292; x=1415153292; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=3IgS7OSc5bzXjVzAq2G15nJJBon0bm2U+l0qrXlbqwU=; b=cBzalfxOGJYu5JbZe0vaOlmyswYlxolEZrIh5IXXg8sDxbGbRiNbKFXv +HlYG792ZYp0g8i3KxHGDzzIzLivWfEwj+26csJexgcozINmYS9Iz2PKt 9HJ9MHvyx/PdNWPZFoY4Kc1RQoYNV5GoBkw4BCDdUk+sl9/RYRnyuI3Qf Q=; X-IronPort-AV: E=Sophos;i="4.93,637,1378814400"; d="scan'208";a="221335889" X-Ironport-HAT: None - $RELAY-AUTH X-Ironport-Source: 31.133.160.224 - Outgoing - Outgoing-SSL Received: from dhcp-a0e0.meeting.ietf.org (HELO [31.133.160.224]) ([31.133.160.224]) by mx2-int.auckland.ac.nz with ESMTP; 05 Nov 2013 15:08:09 +1300 Message-ID: <52785306.4030901@auckland.ac.nz> Date: Tue, 05 Nov 2013 15:08:06 +1300 From: Nevil Brownlee User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: eman@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [eman] Agenda -03 (this time for sure!) 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, 05 Nov 2013 02:08:17 -0000 Hi all: I've updated the agenda again, the URL for the meeting materials, i.e. agenda, slides and - eventually - minutes is https://datatracker.ietf.org/meeting/88/materials.html (search for EMAN in the Operations and Management Area) See you at the meeting tomorrow, Nevil -- --------------------------------------------------------------------- Nevil Brownlee Computer Science Department | ITS Phone: +64 9 373 7599 x88941 The University of Auckland FAX: +64 9 373 7453 Private Bag 92019, Auckland 1142, New Zealand From david@prantl.name Mon Nov 4 22:35:06 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 609EA21F9FC7 for ; Mon, 4 Nov 2013 22:35:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mpvEtJZWRPTo for ; Mon, 4 Nov 2013 22:35:05 -0800 (PST) Received: from mailgw1.uni-kl.de (mailgw1.uni-kl.de [IPv6:2001:638:208:120::220]) by ietfa.amsl.com (Postfix) with ESMTP id 9BC6621E8123 for ; Mon, 4 Nov 2013 22:34:59 -0800 (PST) Received: from t530shadow (173-38-208-169.cisco.com [173.38.208.169]) (authenticated bits=0) by mailgw1.uni-kl.de (8.14.3/8.14.3/Debian-9.4) with ESMTP id rA56Yu55021614 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for ; Tue, 5 Nov 2013 07:34:57 +0100 From: "David Prantl" To: Date: Tue, 5 Nov 2013 07:35:37 +0100 Message-ID: <001b01ced9f1$3dba2c40$b92e84c0$@prantl.name> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001C_01CED9F9.9F7FA5B0" X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac7Z8SaX80x4rjb6RDOitpXesP8jdQ== Content-Language: de Subject: [eman] Eman Draft/Joulex 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, 05 Nov 2013 06:35:06 -0000 This is a multipart message in MIME format. ------=_NextPart_000_001C_01CED9F9.9F7FA5B0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Dear all, I have been on this list since 2011 working for Joulex, we built a commercial Energy Managemens System - the Joulex Energy Manager which is now being used by over 220 customers across the world. We found the eman information model reasonable for devices (it would be great if all devices used it) and built our Energy Management System based on it. We like the ability to have common generic attributes such as keywords, importance, caliber, relationships, etc I believe the the Eman framework is good to go for a standard information model for devices and Energy Management Systems. Regards, David Prantl ------=_NextPart_000_001C_01CED9F9.9F7FA5B0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Dear = all,

 

I have been on this list since 2011 working for = Joulex, we built a commercial Energy Managemens System – the = Joulex Energy Manager which is now being used by over 220 customers = across the world.

We found the = eman information model reasonable for devices (it would be great if all = devices used it) and built our Energy Management System based on = it.

We like the ability to have = common generic attributes such as keywords, importance, caliber, = relationships, etc I believe the the Eman framework is good to go for a = standard information model for devices and Energy Management = Systems.

 

Regards,

David Prantl

 

------=_NextPart_000_001C_01CED9F9.9F7FA5B0-- From n.brownlee@auckland.ac.nz Tue Nov 5 08:08:06 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0621821E8085 for ; Tue, 5 Nov 2013 08:08:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.999 X-Spam-Level: X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_21=0.6, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q-lzYInZ4kWs for ; Tue, 5 Nov 2013 08:08:01 -0800 (PST) Received: from mx2.auckland.ac.nz (mx2.auckland.ac.nz [130.216.125.245]) by ietfa.amsl.com (Postfix) with ESMTP id C16A521E811C for ; Tue, 5 Nov 2013 08:08:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=uoa; t=1383667681; x=1415203681; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=6680me96GbPPHYAhwUhHsIyhVH1HIPWovoDzEPSxnIA=; b=C77IV98WTTBi194whzi51dkMmk+7a4+MXQ/B5CVjHOmjUMmut/aTKOya rTWIU6ONfL4xPt+j8tTkz7IfzrefeSHcIZ3bvU5jOIezte3n+HW/kBjYc 1QzuENFLGXD92H/uMh6EfzBDneUCwiGZlVWKiFFlwkvqHkUVC/Uj2Ywjj c=; X-IronPort-AV: E=Sophos;i="4.93,640,1378814400"; d="scan'208";a="221408579" X-Ironport-HAT: None - $RELAY-AUTH X-Ironport-Source: 64.114.24.114 - Outgoing - Outgoing-SSL Received: from unknown (HELO [142.131.17.14]) ([64.114.24.114]) by mx2-int.auckland.ac.nz with ESMTP; 06 Nov 2013 05:07:59 +1300 Message-ID: <527917D7.8030406@auckland.ac.nz> Date: Wed, 06 Nov 2013 05:07:51 +1300 From: Nevil Brownlee User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: eman@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [eman] Slides for today's EMAN meeting X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Nov 2013 16:08:06 -0000 Hi all: The slides are now on th3e meeting materials page, all except the Battery MIB. Who's presenting that? Please send its slides. Cheers, Nevil -- --------------------------------------------------------------------- Nevil Brownlee Computer Science Department | ITS Phone: +64 9 373 7599 x88941 The University of Auckland FAX: +64 9 373 7453 Private Bag 92019, Auckland 1142, New Zealand From tnadeau@lucidvision.com Tue Nov 5 17:24:13 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F37621E80CA for ; Tue, 5 Nov 2013 17:24:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.25 X-Spam-Level: X-Spam-Status: No, score=-2.25 tagged_above=-999 required=5 tests=[AWL=0.349, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oY756HJziq-O for ; Tue, 5 Nov 2013 17:24:07 -0800 (PST) Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 77D1921E808F for ; Tue, 5 Nov 2013 17:24:07 -0800 (PST) Received: from dhcp-b272.meeting.ietf.org (dhcp-b272.meeting.ietf.org [31.133.178.114]) by lucidvision.com (Postfix) with ESMTP id C127425DC5DF for ; Tue, 5 Nov 2013 20:24:05 -0500 (EST) From: Thomas Nadeau Content-Type: multipart/signed; boundary="Apple-Mail=_E081F2E5-A9A8-43DE-83C0-C6033E2899EC"; protocol="application/pgp-signature"; micalg=pgp-sha512 Message-Id: <1711CEBE-36F6-436B-8D85-9D0B29A1845E@lucidvision.com> Date: Tue, 5 Nov 2013 17:24:03 -0800 To: eman@ietf.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1816\)) X-Mailer: Apple Mail (2.1816) Subject: [eman] draft-ietf-eman-framework-11 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, 06 Nov 2013 01:24:13 -0000 --Apple-Mail=_E081F2E5-A9A8-43DE-83C0-C6033E2899EC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii The consensus of the WG today was to have a 2 week comment = period starting tomorrow, prior to moving the document forward to the = IESG. The period will end on Tuesday, November 19 at 5PM PDT. The chairs = will constrain comments on the document to those things that have = changed since the last revision (10), and the one statement from Rolf on = optional versus mandatory elements. Thank you, --Tom --Apple-Mail=_E081F2E5-A9A8-43DE-83C0-C6033E2899EC Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJSeZozAAoJEPcO+I7eiUJZT64P/RR7+qcSnY5ENC6iSjy7sBDX Z8wLX8XDdGN5ybxcjtS7ENg8q67XfxTeGfO9y7mRh2ceaY1uS/qLKTF6UwfY2iCb C1/0EU9MzrzeIKYDsv75ZvaT5Ge2fRwCr950rcZjySaIx8NgUYZPpvjBzwsWL42p Qhq9NtlW3Ar/FlfQyFDW2JSdfp0bBf/T0757/T5+LHeC9XeH7FH+xTxlTVjQ10xE +qmdBMG2u8jcciPGtQ3MRVhbCN83mRicuo1dtjEwqaFLWaGyRNu/q2YPsjxexKXK LMtPOEuFVHq6f/On4J1m+8KvgbcDUgpR+kARFmh76lvFqfHEGr2uCvz9AdGxZBvZ X1pM8oBaNFOeffTgS75D7OmAFqABwFmofFhfuBhzh2urbfZVaAiNjJ6IHWSbewPv ISHPM0OyuLTLSvBFUK67o236LLtSOxPQXtzHqlfyO7RV1njnsdCwsqsBRb8gBAmd kFoYZylZOKRPk3B+BDYIVgFQBUDe9a6lZT4XzTjfDwS4h4px++4Ea/h+OZ3FiuzA wY9yGd9lvgglTEJ40TVndAvlh8zL92dTB/tBcTjJonGfKbAZCo2aowYyTdKHUT6M RyK0ELCU8vQEoAqd/W9bh9IUB9OkKgDL3Zi6Zph3bTgEngE3Yb4zZBKZwBhjplyA 6+2pDyC5jpJ4i9q44oCQ =w1tH -----END PGP SIGNATURE----- --Apple-Mail=_E081F2E5-A9A8-43DE-83C0-C6033E2899EC-- From Rolf.Winter@neclab.eu Wed Nov 6 13:04:09 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A873821E8193 for ; Wed, 6 Nov 2013 13:04:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.724 X-Spam-Level: X-Spam-Status: No, score=-102.724 tagged_above=-999 required=5 tests=[AWL=0.875, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E2yQfobFFv4Z for ; Wed, 6 Nov 2013 13:04:04 -0800 (PST) Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id DD9CB21E81A2 for ; Wed, 6 Nov 2013 13:04:00 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 5C098105F49 for ; Wed, 6 Nov 2013 21:57:47 +0100 (CET) X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de) Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EzDnVIWSaU9X for ; Wed, 6 Nov 2013 21:57:47 +0100 (CET) Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id 44734105F3F for ; Wed, 6 Nov 2013 21:57:42 +0100 (CET) Received: from PALLENE.office.hd ([169.254.1.11]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Wed, 6 Nov 2013 22:03:55 +0100 From: Rolf Winter To: "eman@ietf.org" Thread-Topic: one-liner for the framework Thread-Index: Ac7akpqle/0FE7PYQ6aUbw87babaTg== Date: Wed, 6 Nov 2013 21:03:55 +0000 Message-ID: <791AD3077F94194BB2BDD13565B6295D63AE936A@PALLENE.office.hd> Accept-Language: en-US, de-DE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.7.0.197] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [eman] one-liner for the framework 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, 06 Nov 2013 21:04:09 -0000 Hi, could we add a line to the framework (maybe at the end of the intro or some= where else but early in the text) that states that the framework does not s= pecify which of these concepts and underlying data elements are mandatory o= r optional to implement? Here's a suggestion for it: Note that not all concepts and data items described in this document are ma= ndatory for implementations. Specifications describing implementation of th= is framework need to be explicit about which of these are mandatory and whi= ch are optional to implement. ...or similar.=20 Best, Rolf NEC Europe Ltd | Registered Office: Athene, Odyssey Business Park, West End= Road, London, HA4 6QE, GB | Registered in England 2832014 From jparello@cisco.com Wed Nov 6 14:03:08 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4A1A11E80E2 for ; Wed, 6 Nov 2013 14:03:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.524 X-Spam-Level: X-Spam-Status: No, score=-10.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WRgrJRP+gVS4 for ; Wed, 6 Nov 2013 14:03:03 -0800 (PST) Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 74E2821F9F9D for ; Wed, 6 Nov 2013 14:03:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1128; q=dns/txt; s=iport; t=1383775383; x=1384984983; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=rLNqVt/047vrlLZzD5DRKtbQkaFetoPgUMiENLlBUeE=; b=btvbNsrkd8IgAjTFkqlyIgSIw4vzBRk4KWA6F71AzNtLKKbZrJJPVyby jIN7djV32Gf3pl7O+zdTjHDnUDJObbQNZfO0YTOO6fnldX4L9EeARcA5f 3M8/twLagHTkPo1mfB3sOJE3THc+EHHqo53YXnb6W5uRPFgacOAyWW+hk c=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhEFALO7elKtJV2c/2dsb2JhbABbgwc4U78tgSYWdIIlAQEBBAEBATc0FwQCAQgRBAEBCxQJBycLFAkIAQEEARIIh3gBDb8TBI4egQo4BoMagRADqhaDJoIq X-IronPort-AV: E=Sophos;i="4.93,647,1378857600"; d="scan'208";a="281667962" Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-3.cisco.com with ESMTP; 06 Nov 2013 22:03:02 +0000 Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id rA6M329W017230 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 6 Nov 2013 22:03:02 GMT Received: from xmb-aln-x04.cisco.com ([169.254.9.227]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.03.0123.003; Wed, 6 Nov 2013 16:03:02 -0600 From: "John Parello (jparello)" To: Rolf Winter , "eman@ietf.org" Thread-Topic: one-liner for the framework Thread-Index: Ac7akpqle/0FE7PYQ6aUbw87babaTgAqVsww Date: Wed, 6 Nov 2013 22:03:01 +0000 Message-ID: <9C213D38848B89428F46808B16F6F08601697FAE@xmb-aln-x04.cisco.com> References: <791AD3077F94194BB2BDD13565B6295D63AE936A@PALLENE.office.hd> In-Reply-To: <791AD3077F94194BB2BDD13565B6295D63AE936A@PALLENE.office.hd> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [171.71.223.71] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [eman] one-liner for the framework 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, 06 Nov 2013 22:03:08 -0000 Awesome. Thanks! Jp -----Original Message----- From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of Rol= f Winter Sent: Wednesday, November 06, 2013 1:04 PM To: eman@ietf.org Subject: [eman] one-liner for the framework Hi, could we add a line to the framework (maybe at the end of the intro or some= where else but early in the text) that states that the framework does not s= pecify which of these concepts and underlying data elements are mandatory o= r optional to implement? Here's a suggestion for it: Note that not all concepts and data items described in this document are ma= ndatory for implementations. Specifications describing implementation of th= is framework need to be explicit about which of these are mandatory and whi= ch are optional to implement. ...or similar.=20 Best, Rolf NEC Europe Ltd | Registered Office: Athene, Odyssey Business Park, West End= Road, London, HA4 6QE, GB | Registered in England 2832014 _______________________________________________ eman mailing list eman@ietf.org https://www.ietf.org/mailman/listinfo/eman From bnordman@lbl.gov Wed Nov 6 14:08:08 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99F7A21E81A7 for ; Wed, 6 Nov 2013 14:07:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.533 X-Spam-Level: X-Spam-Status: No, score=-5.533 tagged_above=-999 required=5 tests=[AWL=0.444, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v-oW3Kh8NwPX for ; Wed, 6 Nov 2013 14:07:39 -0800 (PST) Received: from fe1.lbl.gov (fe1.lbl.gov [128.3.41.133]) by ietfa.amsl.com (Postfix) with ESMTP id CC13821E819F for ; Wed, 6 Nov 2013 14:07:34 -0800 (PST) X-Ironport-SBRS: 4.8 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AskDAKS8elLRVYArlGdsb2JhbABYA4JDfFO2aohDgR4IFg4BAQEBBwsLCRIqgiUBAQEDAQEBAWsLBQsLBAc7IgUNAQUBHAYTh3sGBQigSp5Bjh6BKwwEBxGEHwOJQI5MgS+ObxgphHIb X-IronPort-AV: E=Sophos;i="4.93,647,1378882800"; d="scan'208";a="32586755" Received: from mail-qe0-f43.google.com ([209.85.128.43]) by fe1.lbl.gov with ESMTP; 06 Nov 2013 14:07:33 -0800 Received: by mail-qe0-f43.google.com with SMTP id nc12so158226qeb.16 for ; Wed, 06 Nov 2013 14:07:33 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=orJOJeIcwatw6086YVTSbE1Ewqa+p3QsvMxOII22PFA=; b=H1vElxCwYxc3rdDSQr9PHBPCocERCM0Ip5kUexOr0qD6irQjBDlRxUT26EZu8hlici pcDqFIiZn62gBTkXIPmlLU09+knGFMh8s8XwOWO23iplF3l2jA/KNkXwvIJnVsjVtk8B cVaE49L7S52tt+Jnndhwh9AibAi0izMstze6b4XWftV3C/LCwQeQEiHj5uoMRlFqJYi0 XVEhd5A0x+v0bkwMhEU4YcNkSSuQ47l0uqv+6XTG1kVLizdMoYnikMSn35bSeVWeAc4V M0uv9ShTkAm27Gd4LH2nj81cmEM/TGztbZAOi5nw2RnOS4lLW1wOFldl+Vz37Jt2Hm7C Sung== X-Gm-Message-State: ALoCoQlIz7EsxvIzr5/UmeGIcUtk4YFksUpQ0EQxn9fT3HL/dxAECtdI7BwMKr5sbq1XlbgaSM+G3KRfur0vvqspaMriLFSkk0dWLb0PERAJlcaRkFgywseIarb1FvfWDgT6P70hNUjF X-Received: by 10.224.161.146 with SMTP id r18mr8952271qax.57.1383775653606; Wed, 06 Nov 2013 14:07:33 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.224.161.146 with SMTP id r18mr8952261qax.57.1383775653455; Wed, 06 Nov 2013 14:07:33 -0800 (PST) Received: by 10.140.80.212 with HTTP; Wed, 6 Nov 2013 14:07:33 -0800 (PST) In-Reply-To: <791AD3077F94194BB2BDD13565B6295D63AE936A@PALLENE.office.hd> References: <791AD3077F94194BB2BDD13565B6295D63AE936A@PALLENE.office.hd> Date: Wed, 6 Nov 2013 14:07:33 -0800 Message-ID: From: Bruce Nordman To: Rolf Winter Content-Type: multipart/alternative; boundary=089e0149beee461e1204ea89606b Cc: "eman@ietf.org" Subject: Re: [eman] one-liner for the framework 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, 06 Nov 2013 22:08:08 -0000 --089e0149beee461e1204ea89606b Content-Type: text/plain; charset=ISO-8859-1 Probably best to use Rolf's text, but in thinking about this earlier, I concluded that the only truly mandatory items should be a UUID and the type of an energy object. Any implementation would certainly have more than that, but could be different in different ones. --Bruce On Wed, Nov 6, 2013 at 1:03 PM, Rolf Winter wrote: > Hi, > > could we add a line to the framework (maybe at the end of the intro or > somewhere else but early in the text) that states that the framework does > not specify which of these concepts and underlying data elements are > mandatory or optional to implement? > > Here's a suggestion for it: > > Note that not all concepts and data items described in this document are > mandatory for implementations. Specifications describing implementation of > this framework need to be explicit about which of these are mandatory and > which are optional to implement. > > ...or similar. > > Best, > > Rolf > > NEC Europe Ltd | Registered Office: Athene, Odyssey Business Park, West > End Road, London, HA4 6QE, GB | Registered in England 2832014 > > > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman > -- *Bruce Nordman* Lawrence Berkeley National Laboratory *nordman.lbl.gov * BNordman@LBL.gov 510-486-7089 m: 510-501-7943 --089e0149beee461e1204ea89606b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Probably best to use Rolf's text, but in thi= nking about this earlier,
I concluded that the only truly mandator= y items should be
a UUID and the type of an energy object.=A0 Any implem= entation
would certainly have more than that, but could be different in
different ones.
--Bruce

=
On Wed, Nov 6, 2013 at 1:03 PM, Rolf Winter = <Rolf.Winter@neclab.eu> wrote:
Hi,

could we add a line to the framework (maybe at the end of the intro or some= where else but early in the text) that states that the framework does not s= pecify which of these concepts and underlying data elements are mandatory o= r optional to implement?

Here's a suggestion for it:

Note that not all concepts and data items described in this document are ma= ndatory for implementations. Specifications describing implementation of th= is framework need to be explicit about which of these are mandatory and whi= ch are optional to implement.

...or similar.

Best,

Rolf

NEC Europe Ltd | Registered Office: Athene, Odyssey Business Park, West End= =A0Road, London, HA4 6QE, GB | Registered in England 2832014


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



--
Bru= ce Nordman
Lawrence Berkel= ey National Laboratory
nordman.lbl.gov=
BNordman@LBL.gov
510-486-7089
m: 510-501-7943
--089e0149beee461e1204ea89606b-- From n.brownlee@auckland.ac.nz Wed Nov 6 22:34:22 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E9B421E8106 for ; Wed, 6 Nov 2013 22:34:22 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.299 X-Spam-Level: X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zZ+YTHJAO0Gy for ; Wed, 6 Nov 2013 22:34:17 -0800 (PST) Received: from mx2.auckland.ac.nz (mx2.auckland.ac.nz [130.216.125.245]) by ietfa.amsl.com (Postfix) with ESMTP id E309921E80CD for ; Wed, 6 Nov 2013 22:34:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=uoa; t=1383806057; x=1415342057; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=VxkVcmKtlXAbpcfOgESS5w0y00zjrunZFUXAnF1fda4=; b=LI+NPcSDDaItcIa7Jri7CdJCyenZNtjZTmA92uRka7xQwJWsrDVsn2w/ hXQkfW51foE2f1ES1Varl59J8CwWMMtOVBkZDtsNB1Q1E+mSv/MK0C1dj nOudf4v2SMXXdewDArxZnn+wXoScuDlpa/73a4uVnaOxEfLGTDsCjXpA3 U=; X-IronPort-AV: E=Sophos;i="4.93,650,1378814400"; d="scan'208";a="221687464" X-Ironport-HAT: None - $RELAY-AUTH X-Ironport-Source: 64.114.24.114 - Outgoing - Outgoing-SSL Received: from unknown (HELO [142.131.17.14]) ([64.114.24.114]) by mx2-int.auckland.ac.nz with ESMTP; 07 Nov 2013 19:34:15 +1300 Message-ID: <527B345F.3090406@auckland.ac.nz> Date: Thu, 07 Nov 2013 19:34:07 +1300 From: Nevil Brownlee User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: eman@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [eman] **DRAFT** minutes of EMAN meeting at IETF-88 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, 07 Nov 2013 06:34:22 -0000 Hi all: Here are the draft minutes, please send me any corrections or comments. Cheers, Nevil Minutes of the EMAN meeting at IETF 88 in Vancouver About 20 people attended the meeting + several on jabber Scribes: Nevil Brownlee and Thomas Nadeau WG Status --------- - EMAN Requirements approved, published as RFC 6988. Energy Reporting Framework -02 ------------------------------ Rolf Winter presented Bruce Norman's draft. - This draft provides a simpler view of energy management, it focuses on energy usage reporting. - Joel Jaegli explained why Bruce produced this draft, and pointed out that comments on it are welcome on the list. Energy Management Framework -11 ------------------------------- Presented by John Parello. - This drafts WGLC ran from 11 to 27 September. Response on the list was good, with four detailed reviews posted. The authors have worked through the issues raised, 66 edits and 29 clarifications have been made. - Another 15 suggestions were considered and declined. - Rolf asked about sub-meters, John explained that "a meter by itself can be used for billing, but a sub-meter is simply a device with some metering capabilities. - ETSI approached the authors, that liaison has been helpful to both EMAN and ETSI. The authors will send an email to the list reporting on that liaison work. <== - Issues 1. Should the Framework mark sections as Mandatory or Optional? = Yes; Rolf will send the authors a suitable statement for this. 2: Batteries have charging states, could they have power states as well? = They may. 2: The information model is expressed in pseudocode, would a set of tables be better? = Include tables in an Appendix. 3: The Security Considerations would be better if it had a list of "the things you need to worry about" = Include such a list, and a reference to the SNMPv3 RFC. 5: Would a list of implementations be useful? = Include it with note to RFC Editor, "delete when RFC is published" - With all the above changes, the meeting's consensus was to have a 2 week comment period starting tomorrow, prior to moving the document forward to the IESG. The period will end on Tuesday, November 19 at 5PM PDT. The chairs will constrain comments on the document to those things that have changed since the last revision (10), and the one statement from Rolf on optional versus mandatory elements. - Issues 2 to 5 above will help to address concerns raised by sector reviews while the draft is in IETF Last Call. Energy-aware- MIB -09, Power and Energy Monitoring MIB -06 ---------------------------------------------------------- Presented by Benoit Claise. = No change since last meeting Battery MIB -09 --------------- - No slides, no presentation, but a brief discussion: . Rolf reported that one small change is needed, to handle IDs of individual cells within a battery. Applicability Statement -04 --------------------------- Presented by Nevil Brownlee - Could add section on use cases for the framework. Next Steps for EMAN ------------------- - 2-week comment period for the Framework under way, submit it to IESG shortly after that. - Should the three MIBs be children of a single OID under MIB-2? Agreed, this is sensible. - The chairs will start WGLCs on all three MIB drafts soon after the Framework is submitted. There were no objections in the room. Other Presentations ------------------- Satoru Izumi presented the results of experiments in a University Computer Laboratory, using this MIB (draft-suganuma-greenmib-02) plotting power usage for devices in the lab. - Comments/suggestion for further work are welcome on the EMAN list. The meeting finished at 1748. -- --------------------------------------------------------------------- Nevil Brownlee Computer Science Department | ITS Phone: +64 9 373 7599 x88941 The University of Auckland FAX: +64 9 373 7453 Private Bag 92019, Auckland 1142, New Zealand From tnadeau@lucidvision.com Thu Nov 21 04:46:21 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D6011ADEAE for ; Thu, 21 Nov 2013 04:46:21 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.275 X-Spam-Level: X-Spam-Status: No, score=0.275 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.525] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s7n0AX63l4Zk for ; Thu, 21 Nov 2013 04:46:19 -0800 (PST) Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 2546A1AD8F1 for ; Thu, 21 Nov 2013 04:46:19 -0800 (PST) Received: from [192.168.1.107] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 0BCC02617A12; Thu, 21 Nov 2013 07:46:12 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\)) From: Thomas Nadeau In-Reply-To: <1711CEBE-36F6-436B-8D85-9D0B29A1845E@lucidvision.com> Date: Thu, 21 Nov 2013 07:46:11 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: References: <1711CEBE-36F6-436B-8D85-9D0B29A1845E@lucidvision.com> To: eman@ietf.org X-Mailer: Apple Mail (2.1822) Subject: Re: [eman] draft-ietf-eman-framework-11 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 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, 21 Nov 2013 12:46:21 -0000 This email confirms the conclusion of the final working group = last call on draft-ietf-eman-framework. I have gone through the emails = on the list to double-check and it does not seem that we have received = any WG last call comments during this last and final period. However, = there were some comments made during the WG meeting a few weeks back, = specifically in terms of improving the security section, so co-authors = please go ahead and make those and publish one last version. Once this = is done Nevile and I will prepare the document shepherd information and = move this forward to the IESG for their review. Thank you all for the time, effort (and patience!) on this = document. This is a great achievement for the WG. Tom/Nevil On Nov 5, 2013:8:24 PM, at 8:24 PM, Thomas Nadeau = wrote: >=20 > The consensus of the WG today was to have a 2 week comment = period starting tomorrow, prior to moving the document forward to the = IESG. The period will end on Tuesday, November 19 at 5PM PDT. The chairs = will constrain comments on the document to those things that have = changed since the last revision (10), and the one statement from Rolf on = optional versus mandatory elements. >=20 > Thank you, >=20 > --Tom >=20 From jparello@cisco.com Thu Nov 21 07:12:10 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB22F1AE19C for ; Thu, 21 Nov 2013 07:12:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.026 X-Spam-Level: X-Spam-Status: No, score=-10.026 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bzgHys61SSC7 for ; Thu, 21 Nov 2013 07:12:09 -0800 (PST) Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) by ietfa.amsl.com (Postfix) with ESMTP id 82EBE1ADFB6 for ; Thu, 21 Nov 2013 07:12:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1951; q=dns/txt; s=iport; t=1385046723; x=1386256323; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=BnoFi6aRWg0Rp3/yHDGf8tEeeuqUOzx/6/7mTrPQnes=; b=AfuHZYVP53UF2sbaOeFGvJChW196CCl7Kv1wVPF3bQOISpC9l9AVAXy8 JJaIVB+ZOaxJhe/IjfjFV9nQOF/fxsvVOQ0vdQxnqwrXQ2IZHYGUiQnP5 p0tCuL9BSUfQjszN7tC6zUvzOe8NuTySBkRZcNIngz3jo7+JE6kNxdtC1 8=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhoFAIAijlKtJXHB/2dsb2JhbABZgwc4U7xWgSMWdIIlAQEBAwEBAQE3NBsCAQgOAwQBAQsUECcLHQgCBAESCIdzBg3AaxMEjh8RAYEJOIMggRIDqiKDKIFxOQ X-IronPort-AV: E=Sophos;i="4.93,745,1378857600"; d="scan'208";a="1228228" Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by alln-iport-7.cisco.com with ESMTP; 21 Nov 2013 15:12:00 +0000 Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id rALFBxLr001960 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 21 Nov 2013 15:11:59 GMT Received: from xmb-aln-x04.cisco.com ([169.254.9.168]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.03.0123.003; Thu, 21 Nov 2013 09:11:59 -0600 From: "John Parello (jparello)" To: Thomas Nadeau , "eman@ietf.org" Thread-Topic: [eman] draft-ietf-eman-framework-11 Thread-Index: AQHO2o7ryVQlAe1jmUKcmp+zuEJ6g5owHseA///D+60= Date: Thu, 21 Nov 2013 15:11:59 +0000 Message-ID: <9C213D38848B89428F46808B16F6F086016A2330@xmb-aln-x04.cisco.com> References: <1711CEBE-36F6-436B-8D85-9D0B29A1845E@lucidvision.com>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.21.86.164] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [eman] draft-ietf-eman-framework-11 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 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, 21 Nov 2013 15:12:11 -0000 THanks Tom/Nevil!=0A= =0A= Thanks everyone for the feedback. We'll get a new draft out to close the wo= rk!=0A= =0A= Jp=0A= =0A= ________________________________________=0A= From: eman [eman-bounces@ietf.org] on behalf of Thomas Nadeau [tnadeau@luci= dvision.com]=0A= Sent: Thursday, November 21, 2013 4:46 AM=0A= To: eman@ietf.org=0A= Subject: Re: [eman] draft-ietf-eman-framework-11=0A= =0A= This email confirms the conclusion of the final working group last = call on draft-ietf-eman-framework. I have gone through the emails on the li= st to double-check and it does not seem that we have received any WG last c= all comments during this last and final period. However, there were some co= mments made during the WG meeting a few weeks back, specifically in terms o= f improving the security section, so co-authors please go ahead and make th= ose and publish one last version. Once this is done Nevile and I will prepa= re the document shepherd information and move this forward to the IESG for = their review.=0A= =0A= Thank you all for the time, effort (and patience!) on this document= . This is a great achievement for the WG.=0A= =0A= Tom/Nevil=0A= =0A= =0A= =0A= On Nov 5, 2013:8:24 PM, at 8:24 PM, Thomas Nadeau = wrote:=0A= =0A= >=0A= > The consensus of the WG today was to have a 2 week comment period s= tarting tomorrow, prior to moving the document forward to the IESG. The per= iod will end on Tuesday, November 19 at 5PM PDT. The chairs will constrain = comments on the document to those things that have changed since the last r= evision (10), and the one statement from Rolf on optional versus mandatory = elements.=0A= >=0A= > Thank you,=0A= >=0A= > --Tom=0A= >=0A= =0A= _______________________________________________=0A= eman mailing list=0A= eman@ietf.org=0A= https://www.ietf.org/mailman/listinfo/eman=0A= From internet-drafts@ietf.org Fri Nov 29 06:45:37 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 773EE1AE006; Fri, 29 Nov 2013 06:45:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kDEN0snS7fWY; Fri, 29 Nov 2013 06:45:36 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A2C51A1F54; Fri, 29 Nov 2013 06:45:36 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.83.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20131129144535.8200.90902.idtracker@ietfa.amsl.com> Date: Fri, 29 Nov 2013 06:45:35 -0800 Cc: eman@ietf.org Subject: [eman] I-D Action: draft-ietf-eman-energy-aware-mib-11.txt X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Nov 2013 14:45:37 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Energy Management Working Group of the IE= TF. Title : Energy Object Context MIB Author(s) : John Parello Benoit Claise Mouli Chandramouli Filename : draft-ietf-eman-energy-aware-mib-11.txt Pages : 32 Date : 2013-11-29 Abstract: This document defines a subset of a Management Information Base (MIB) for energy management of devices. The module addresses device identification, context information, and the relationships between reporting devices, remote devices, and monitoring devices. = The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-eman-energy-aware-mib There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-eman-energy-aware-mib-11 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eman-energy-aware-mib-11 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From bclaise@cisco.com Fri Nov 29 07:51:36 2013 Return-Path: X-Original-To: eman@ietfa.amsl.com Delivered-To: eman@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09B221AD7BF for ; Fri, 29 Nov 2013 07:51:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.501 X-Spam-Level: X-Spam-Status: No, score=-9.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IcZMlMUoud73 for ; Fri, 29 Nov 2013 07:51:34 -0800 (PST) Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 506EA1ACCE2 for ; Fri, 29 Nov 2013 07:51:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5942; q=dns/txt; s=iport; t=1385740292; x=1386949892; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=bVvaUw090GpDXcx7IpgFEFGfyms1fvbC2cVo4tLW/gM=; b=LLY6jsve7W4zt97hTGiucuBh/q7Ecjz6Ijgbhu9aaUzdQa+llVSeFy1B pXsCy+ZRo55tcf2/p7tM6MRNswDn0HuruUZcZnjZfO51QlktCd0NR51Pe TqVBA4xdLGJCj5pBO1tm7VQDSfLZJPweCARwekuHT2Y2SEna9rZ9uXX8R 0=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmkFACW3mFKQ/khN/2dsb2JhbABZgwc4TYhcsASBIRZ0giUBAQEEAQEBawQGAQwEHAMBAgoWDwkDAgECARUmAggGDQEFAgEBBYd4CAXAKxeOZhERBwYDhCoDmBSBMIUVi06DKjs X-IronPort-AV: E=Sophos;i="4.93,798,1378857600"; d="scan'208,217";a="1439122" Received: from ams-core-4.cisco.com ([144.254.72.77]) by aer-iport-1.cisco.com with ESMTP; 29 Nov 2013 15:51:31 +0000 Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id rATFpMc0011650; Fri, 29 Nov 2013 15:51:24 GMT Message-ID: <5298B7FA.1010509@cisco.com> Date: Fri, 29 Nov 2013 16:51:22 +0100 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: eman mailing list References: <20131129144535.8200.90902.idtracker@ietfa.amsl.com> In-Reply-To: <20131129144535.8200.90902.idtracker@ietfa.amsl.com> X-Forwarded-Message-Id: <20131129144535.8200.90902.idtracker@ietfa.amsl.com> Content-Type: multipart/alternative; boundary="------------050700040607020607090405" Subject: [eman] Fwd: I-D Action: draft-ietf-eman-energy-aware-mib-11.txt X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.15 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, 29 Nov 2013 15:51:36 -0000 This is a multi-part message in MIME format. --------------050700040607020607090405 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Dear all, This version should be good for WGLC. Regards, Benoit -------- Original Message -------- Subject: [eman] I-D Action: draft-ietf-eman-energy-aware-mib-11.txt Date: Fri, 29 Nov 2013 06:45:35 -0800 From: To: CC: A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Energy Management Working Group of the IETF. Title : Energy Object Context MIB Author(s) : John Parello Benoit Claise Mouli Chandramouli Filename : draft-ietf-eman-energy-aware-mib-11.txt Pages : 32 Date : 2013-11-29 Abstract: This document defines a subset of a Management Information Base (MIB) for energy management of devices. The module addresses device identification, context information, and the relationships between reporting devices, remote devices, and monitoring devices. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-eman-energy-aware-mib There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-eman-energy-aware-mib-11 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-eman-energy-aware-mib-11 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ eman mailing list eman@ietf.org https://www.ietf.org/mailman/listinfo/eman . --------------050700040607020607090405 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Dear all,

This version should be good for WGLC.

Regards, Benoit


-------- Original Message --------
Subject: [eman] I-D Action: draft-ietf-eman-energy-aware-mib-11.txt
Date: Fri, 29 Nov 2013 06:45:35 -0800
From: <internet-drafts@ietf.org>
To: <i-d-announce@ietf.org>
CC: <eman@ietf.org> 


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Energy Management Working Group of the IETF.

	Title           : Energy Object Context MIB
	Author(s)       : John Parello
                          Benoit Claise
                          Mouli Chandramouli
	Filename        : draft-ietf-eman-energy-aware-mib-11.txt
	Pages           : 32
	Date            : 2013-11-29

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

     

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-eman-energy-aware-mib

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-eman-energy-aware-mib-11

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-eman-energy-aware-mib-11


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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


--------------050700040607020607090405--