From Manuel.Paul@telekom.de Mon Jun 18 02:54:24 2012 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 6F29A21F855E for ; Mon, 18 Jun 2012 02:54:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.835 X-Spam-Level: X-Spam-Status: No, score=-0.835 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1] 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 mnWVDxhAqJ0r for ; Mon, 18 Jun 2012 02:54:24 -0700 (PDT) Received: from tcmail53.telekom.de (tcmail53.telekom.de [217.5.214.110]) by ietfa.amsl.com (Postfix) with ESMTP id A466D21F8599 for ; Mon, 18 Jun 2012 02:54:22 -0700 (PDT) Received: from he101250.emea1.cds.t-internal.com ([10.125.92.153]) by tcmail51.telekom.de with ESMTP/TLS/AES128-SHA; 18 Jun 2012 11:54:12 +0200 Received: from HE113558.emea1.cds.t-internal.com (10.125.65.100) by HE101250.emea1.cds.t-internal.com (10.125.92.153) with Microsoft SMTP Server (TLS) id 8.3.245.1; Mon, 18 Jun 2012 11:54:03 +0200 Received: from HE101452.emea1.cds.t-internal.com ([10.125.92.148]) by HE113558.emea1.cds.t-internal.com ([2002:7cd:4164::7cd:4164]) with mapi; Mon, 18 Jun 2012 11:54:03 +0200 From: To: Date: Mon, 18 Jun 2012 11:53:57 +0200 Thread-Topic: [eman] Support for time series of measured values (eman requirements) Thread-Index: Ac0sNtl2CMXmtQXgRtCsfzG4CeVrAAg9A9zA Message-ID: <9435EDACD941174099E143BCA2BCD615FA12400C80@HE101452.emea1.cds.t-internal.com> References: <92A5C8A0221B31479EB7913C528ACC59017DA34DFE6B@EXMAIL01.jp.ykgw.net> In-Reply-To: <92A5C8A0221B31479EB7913C528ACC59017DA34DFE6B@EXMAIL01.jp.ykgw.net> Accept-Language: de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: de-DE Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 Cc: Dirk.von-Hugo@telekom.de Subject: [eman] Support for time series of measured values (eman requirements) X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 09:54:24 -0000 SGksDQoNCkNvbnNpZGVyaW5nIHJlY2VudCBkaXNjdXNzaW9ucywgaGVyZSBhcmUgc29tZSB0aG91 Z2h0cyByZWxhdGVkIHRvIGlzc3VlcyBzdGlsbCBvcGVuIGluIHRoZSBlbWFuIHJlcXVpcmVtZW50 cyBkb2N1bWVudCwgaW4gcGFydGljdWxhciBmb3IgdGhlIHRpbWUgc2VyaWVzIHJlcXVpcmVtZW50 cy4NCg0KDQoxKSBSZXF1aXJlbWVudCBsZXZlbHMgLyBsYW5ndWFnZQ0KV291bGQgaXQgbWFrZSBz ZW5zZSB0byB1c2UgdGhlIHJlcXVpcmVtZW50IGxhbmd1YWdlICgiTVVTVCIsICJTSE9VTEQiLCBl dGMuKSBhY2NvcmRpbmcgdG8gUkZDMjExOSBpbiB0aGlzIGRyYWZ0IG9yIGhhcyBpdCBiZWVuIGRl Y2lkZWQgZWFybGllciBieSB0aGUgZ3JvdXAgdG8gbm90IGRvIHNvLCBmb3IgYSBzcGVjaWZpYyBy ZWFzb24/ICBXaGlsZSB0aGlzIGlzIGNlcnRhaW5seSBtb3JlIGFwcGxpY2FibGUgdG8gYWN0dWFs IHByb3RvY29sIGRlc2lnbiwgdGhlcmUgYXJlIHNvbWUgZXhhbXBsZXMgaW4gdGhlIElFVEYgd2hl cmUgdGhlIHVzZSBvZiBSRkMyMTE5IGxhbmd1YWdlIGhlbHBlZCB0byBmb3N0ZXIgY2xhcml0eSBv ZiByZXF1aXJlbWVudHMgZG9jdW1lbnRzLg0KSGVyZSwgSSBhbHNvIGRvbuKAmXQgdGhpbmsgdXNp bmcgUkZDMjExOSBsYW5ndWFnZSB3b3VsZCBiZSBjb250cmFkaWN0b3J5IHRvIHRoZSB0ZXh0IGlu IHNlY3Rpb24gMSAodGhlIGRyYWZ04oCZcyBtaXNzaW9uKSwgYXMgaXQgd291bGRu4oCZdCBpbXBs eSBpbXBsZW1lbnRhdGlvbiByZXEgbGV2ZWxzLCBidXQganVzdCBwb2ludHMgb3V0IG1vcmUgY2xl YXJseSwgd2hpY2ggZmVhdHVyZXMgbmVlZGVkIHRvIGJlIGNvdmVyZWQgYW5kIHNwZWNpZmllZCBi eSBzdWJzZXF1ZW50IHNvbHV0aW9uIGRyYWZ0cy4NCg0KDQoyKSBUaW1lIHNlcmllcyBvZiBtZWFz dXJlZCB2YWx1ZXMNClJlZ2FyZGluZyB0aGUgb3BlbiBpc3N1ZSBvZiB0aW1lIGludGVydmFsIHR5 cGVzLCB3ZSB0aGluayB0aGF0IGFsbCBpbnRlcnZhbCB0eXBlcyAodG90YWwsIGRlbHRhLCBzbGlk aW5nIHdpbmRvdykgYXJlIHJlbGV2YW50LiBXZSB3b3VsZCBzZWUgdG90YWwgYW5kIGRlbHRhIGFz IG1hbmRhdG9yeSAoTVVTVCkgYW5kIFNsaWRpbmcgYXMgb3B0aW9uYWwgKFNIT1VMRCkgdG8gYmUg Y292ZXJlZCBieSBzb2x1dGlvbnMuIEFzIG9mIG5vdywgd2UgZG9u4oCZdCBzZWUgYSBuZWVkIHRv IGluY2x1ZGUgYW4gb3ZlcmxhcHBpbmcgc2VyaWVzIG9mIG1lYXN1cmVtZW50cy4NCkZvciB0aGUg bWVhc3VyZW1lbnQgbWV0aG9kcywgY29udGludW91cyB3b3VsZCBiZSBwcmlvcml0eSwgd2hpbGUg c2FtcGxlZCBjYW4gYmUgbGVmdCBvcHRpb25hbC4NCkJvdGggcmVwb3J0aW5nIG1vZGVscyAocHVz aCAmIHB1bGwpIHNob3VsZCBiZSBjb3ZlcmVkIChNVVNUKS4gSXQgc2hvdWxkIGJlIG5vdGVkIGhl cmUsIHRoYXQgcGFydGljdWxhcmx5IHNtYWxsIC8gYmF0dGVyeSBwb3dlcmVkIChlLmcuIG1vYmls ZSkgZGV2aWNlcyBjb3VsZCBiZW5lZml0IG1vc3QgZnJvbSBhIHB1c2ggbW9kZWwsIGFzIGEgcHVs bCBtb2RlbCB3b3VsZCByZXF1aXJlIHRoZW0gdG8gc3RheSBvbiAoY29ubmVjdGVkIHRvIHRoZSBu ZXR3b3JrKSBhbmQgYnVybiBiYXR0ZXJ5LCB3aGlsZSBpbiB0aGUgcHVzaCBtb2RlbCB0aGV54oCZ ZCBiZSBhYmxlIHRvIHNoaXAgdGhlIGRhdGEgYXMgc29vbiBhcyBhcHByb3ByaWF0ZS4NCg0KDQpC ZXN0IFJlZ2FyZHMNCk1hbnVlbA0K From n.brownlee@auckland.ac.nz Mon Jun 18 16:48:13 2012 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 F091611E8079 for ; Mon, 18 Jun 2012 16:48:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.599 X-Spam-Level: X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 74a-PenylNkC for ; Mon, 18 Jun 2012 16:48:12 -0700 (PDT) Received: from mx2.auckland.ac.nz (mx2.auckland.ac.nz [130.216.12.44]) by ietfa.amsl.com (Postfix) with ESMTP id 02D4D11E809A for ; Mon, 18 Jun 2012 16:48:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=n.brownlee@auckland.ac.nz; q=dns/txt; s=uoa; t=1340063292; x=1371599292; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=kpma2SkpjJhsrahL0JlICVnO650+C2KFIwbYufC8E0A=; b=LCsEgNzMSuTExW/XJMQFxwuLpO0Hcf4QFxMwObpip+C04t9EaTmbF6oR ex/gd0eQyysJK9eFrrJth/ZT13HKtZ7dt7pGOkz+4Kaag06Z3OJ/SZ8NE nIdxFVeUU1G4jQ9McaG6OTGGmiVO5k6UXpU7hYbe3DtFAtilK4KKghy7V 4=; X-IronPort-AV: E=Sophos;i="4.77,433,1336305600"; d="scan'208";a="128399430" X-Ironport-HAT: UNIVERSITY - $RELAY-THROTTLE X-Ironport-Source: 130.216.38.131 - Outgoing - Outgoing-SSL Received: from nevil-laptop1.sfac.auckland.ac.nz (HELO [130.216.38.131]) ([130.216.38.131]) by mx2-int.auckland.ac.nz with ESMTP; 19 Jun 2012 11:48:10 +1200 Message-ID: <4FDFBE3A.20503@auckland.ac.nz> Date: Tue, 19 Jun 2012 11:48:10 +1200 From: Nevil Brownlee User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: eman@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [eman] Current state of EMAN Internet Drafts X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 23:48:13 -0000 Hi all: I'm starting to look ahead to IETF 84 in Vancouver, starting 29 July. Seems to me that we should be edging towards consensus on some of our Internet Drafts; in particular I'd like to move ahead with the Requirements and Framework drafts. Could the authors of those two publish new versions, incorporating changes presented to the Paris meeting (IETF 83), please? Once that's done, I'd like to start Working Group Last Calls for them, which - maybe - could be completed before the Vancouver meeting. Cheers, Nevil (EMAN co-chair) -- --------------------------------------------------------------------- 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 internet-drafts@ietf.org Mon Jun 18 23:08:34 2012 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 A5D1F11E80F2; Mon, 18 Jun 2012 23:08:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id su0-nTazgoDy; Mon, 18 Jun 2012 23:08:34 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00E2711E80A5; Mon, 18 Jun 2012 23:08:33 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.20 Message-ID: <20120619060833.30824.97392.idtracker@ietfa.amsl.com> Date: Mon, 18 Jun 2012 23:08:33 -0700 Cc: eman@ietf.org Subject: [eman] I-D Action: draft-ietf-eman-applicability-statement-01.txt X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jun 2012 06:08:34 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Energy Management Working Group of the IE= TF. Title : Energy Management (EMAN) Applicability Statement Author(s) : Brad Schoening Mouli Chandramouli Bruce Nordman Filename : draft-ietf-eman-applicability-statement-01.txt Pages : 30 Date : 2012-06-18 Abstract: The objective of Energy Management (EMAN) is to provide an energy management framework for networked devices. This document presents the applicability of the EMAN framework for a variety of scenarios. This document lists use cases and target devices that can potentially implement the EMAN framework and associated SNMP MIB modules. These use cases are useful for identifying requirements for the framework. Further, we describe the relationship of the EMAN framework to relevant other energy monitoring standards and architectures. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-eman-applicability-statement There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-eman-applicability-statement-01 A diff from previous version is available at: http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-eman-applicability-statemen= t-01 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From moulchan@cisco.com Mon Jun 18 23:29:51 2012 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 93C2F11E8073 for ; Mon, 18 Jun 2012 23:29:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yY92UFkNo1xZ for ; Mon, 18 Jun 2012 23:29:50 -0700 (PDT) Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id D6EB821F8629 for ; Mon, 18 Jun 2012 23:29:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3197; q=dns/txt; s=iport; t=1340087390; x=1341296990; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=H4GnCAMEvzS2fy6LBGBPbayBN7kJcvGgiNAhLIBjQZ8=; b=GETUmbHSsf2kKWfvdSXceIGE/Mkk/QvTY4Kxi90Wm9+N8fJ+w8yqLg+5 38rfxr7Yi8hFmTIrAUgdXQ3ChTGpFygTv3/xsPlLPE0UkF9ff2kBxTbf3 cEVs4sgu123+64rmLGc7dEWRqyohDK3lRiankW+F01UUXVZvSHGp1P/5e o=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av8EAJ8b4E+tJV2d/2dsb2JhbABFtXGBB4IYAQEBBAEBAQ8BHQo0BBMEAgEZBAEBCwYXAQYBJh8JCAEBBBMIGodpC5kAoBeLKYJ+gjtgA4hCjXSNBYFmgn4 X-IronPort-AV: E=Sophos;i="4.75,795,1330905600"; d="scan'208";a="90668427" Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-9.cisco.com with ESMTP; 19 Jun 2012 06:29:49 +0000 Received: from xbh-rcd-201.cisco.com (xbh-rcd-201.cisco.com [72.163.62.200]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id q5J6Tnoh002847 for ; Tue, 19 Jun 2012 06:29:49 GMT Received: from xmb-rcd-106.cisco.com ([72.163.62.148]) by xbh-rcd-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 19 Jun 2012 01:29:49 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 19 Jun 2012 01:29:45 -0500 Message-ID: In-Reply-To: <20120619060833.30824.97392.idtracker@ietfa.amsl.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: draft-ietf-eman-applicability-statement-01.txt Thread-Index: Ac1N4ffl8ItgWYiKSd+1KIHC/0/M3QAAHAaw References: <20120619060833.30824.97392.idtracker@ietfa.amsl.com> From: "Mouli Chandramouli (moulchan)" To: X-OriginalArrivalTime: 19 Jun 2012 06:29:49.0602 (UTC) FILETIME=[ED7F0820:01CD4DE4] Subject: [eman] draft-ietf-eman-applicability-statement-01.txt X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jun 2012 06:29:51 -0000 Hello all, An updated version of the EMAN Applicability Statement has been submitted.=20 http://tools.ietf.org/html/draft-ietf-eman-applicability-statement-01 Most open issues from the previous version of the draft have been closed at the IETF 83 WG meeting. =20 The remaining open issues are:=20 1. Relevance of ASHRAE SPC201P to EMAN standards (comment from Dave Robin @ WG meeting)=20 ASHRAE standard has not been released for public review yet and should be available in a month or so.=20 Hopefully, the next version of the applicability statement draft shall have a discussion on this topic. 2. Scope of Applicability Statement draft=20 This was discussed in the last WG meeting and some overlap of among cases was considered fine.=20 Secondly, the Applicability Statement draft should describe how the technology developed in the other drafts can be applied/implemented. In that sense, Applicability Statement can be completed after Requirements, Framework, MIB modules are stable.=20 Please let us know if you have any comments, suggestions to improve the draft.=20 Thanks Bruce, Brad and Mouli =20 -----Original Message----- From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org Sent: Tuesday, June 19, 2012 11:39 AM To: i-d-announce@ietf.org Cc: eman@ietf.org Subject: [eman] I-D Action: draft-ietf-eman-applicability-statement-01.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Energy Management Working Group of the IETF. Title : Energy Management (EMAN) Applicability Statement Author(s) : Brad Schoening Mouli Chandramouli Bruce Nordman Filename : draft-ietf-eman-applicability-statement-01.txt Pages : 30 Date : 2012-06-18 Abstract: The objective of Energy Management (EMAN) is to provide an energy management framework for networked devices. This document presents the applicability of the EMAN framework for a variety of scenarios. This document lists use cases and target devices that can potentially implement the EMAN framework and associated SNMP MIB modules. These use cases are useful for identifying requirements for the framework. Further, we describe the relationship of the EMAN framework to relevant other energy monitoring standards and architectures. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-eman-applicability-statement There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-eman-applicability-statement-01 A diff from previous version is available at: http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-eman-applicability-statem= e nt-01 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ eman mailing list eman@ietf.org https://www.ietf.org/mailman/listinfo/eman From Quittek@neclab.eu Fri Jun 22 05:00:55 2012 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 69EA121F86C1 for ; Fri, 22 Jun 2012 05:00:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id djL-gtSU3ari for ; Fri, 22 Jun 2012 05:00:55 -0700 (PDT) Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id D21A921F86C4 for ; Fri, 22 Jun 2012 05:00:54 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id B2ED81015FB for ; Fri, 22 Jun 2012 14:04:36 +0200 (CEST) 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 798w9Aq3jj3V for ; Fri, 22 Jun 2012 14:04:36 +0200 (CEST) Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id 990DE1015D6 for ; Fri, 22 Jun 2012 14:04:31 +0200 (CEST) Received: from PALLENE.office.hd ([169.254.1.191]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Fri, 22 Jun 2012 14:01:28 +0200 From: Juergen Quittek To: eman mailing list Thread-Topic: power interface vs. energy interface Thread-Index: AQHNUG7BaddK/rVqvU6lhEeXsj3cMQ== Date: Fri, 22 Jun 2012 12:01:27 +0000 Message-ID: Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.14.0.111121 x-originating-ip: [10.7.0.92] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [eman] power interface vs. energy interface 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, 22 Jun 2012 12:00:55 -0000 Dear all, At the last session in Paris we discussed renaming "power interface" to "energy interface". According to the minutes I proposed this, but now I'm not sure it is a good idea. The power interface is either a power inlet or a power outlet. Terms "power inlet" and "power outlet" are used as well. If we rename "power interface" to "energy interface" we should consistently also rename "power outlet" to "energy outlet". However, "power outlet" is already a commonly used term outside our WG and it would probably be better to keep it than renaming it to "energy outlet". Also at power interfaces we talk about "power characteristics" and not "energy characteritics". Seeing all this I propose to keep the term "power interface" and to not rename it. What do people think about it? Thanks, Juergen From Stefan.Schraub@telekom.de Fri Jun 22 07:35:14 2012 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 1F9F921F8568 for ; Fri, 22 Jun 2012 07:35:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.949 X-Spam-Level: X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1] 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 rAuk1+Mw7mKS for ; Fri, 22 Jun 2012 07:35:12 -0700 (PDT) Received: from tcmail53.telekom.de (tcmail53.telekom.de [217.5.214.110]) by ietfa.amsl.com (Postfix) with ESMTP id 0D77321F858D for ; Fri, 22 Jun 2012 07:35:11 -0700 (PDT) Received: from he113472.emea1.cds.t-internal.com ([10.134.93.130]) by tcmail51.telekom.de with ESMTP/TLS/AES128-SHA; 22 Jun 2012 16:35:03 +0200 Received: from HE113676.emea1.cds.t-internal.com (10.134.99.29) by HE113472.emea1.cds.t-internal.com (10.134.93.130) with Microsoft SMTP Server (TLS) id 8.3.245.1; Fri, 22 Jun 2012 16:35:03 +0200 Received: from HE111649.emea1.cds.t-internal.com ([10.134.93.18]) by HE113676.emea1.cds.t-internal.com ([::1]) with mapi; Fri, 22 Jun 2012 16:35:03 +0200 From: To: Date: Fri, 22 Jun 2012 16:35:02 +0200 Thread-Topic: [eman] power interface vs. energy interface Thread-Index: AQHNUG7BaddK/rVqvU6lhEeXsj3cMZcGX2lA Message-ID: References: In-Reply-To: Accept-Language: en-US, de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [eman] power interface vs. energy interface 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, 22 Jun 2012 14:35:14 -0000 Dear all, I agree with Juergen. To rename "power interface" to "energy interface" is = not useful. It is also confirmed by ist self-chosen examples (e. g. "The power interfac= e is either a power inlet or a power outlet"). So you can only find the reference of the word "power"= in technical literature. BR Stefan Schraub -----Urspr=FCngliche Nachricht----- Von: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] Im Auftrag von Ju= ergen Quittek Gesendet: Freitag, 22. Juni 2012 14:01 An: eman mailing list Betreff: [eman] power interface vs. energy interface Dear all, At the last session in Paris we discussed renaming "power interface" to "energy interface". According to the minutes I proposed this, but now I'm not sure it is a good idea. The power interface is either a power inlet or a power outlet. Terms "power inlet" and "power outlet" are used as well. If we rename "power interface" to "energy interface" we should consistently also rename "power outlet" to "energy outlet". However, "power outlet" is already a commonly used term outside our WG and it would probably be better to keep it than renaming it to "energy outlet". Also at power interfaces we talk about "power characteristics" and not "energy characteritics". Seeing all this I propose to keep the term "power interface" and to not rename it. What do people think about it? Thanks, Juergen _______________________________________________ eman mailing list eman@ietf.org https://www.ietf.org/mailman/listinfo/eman From bclaise@cisco.com Fri Jun 22 07:43:55 2012 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 09B6A21F861A for ; Fri, 22 Jun 2012 07:43:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.078 X-Spam-Level: X-Spam-Status: No, score=-10.078 tagged_above=-999 required=5 tests=[AWL=0.521, 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 y8W8eChLCKtl for ; Fri, 22 Jun 2012 07:43:54 -0700 (PDT) Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id E940921F8613 for ; Fri, 22 Jun 2012 07:43:53 -0700 (PDT) X-TACSUNS: Virus Scanned Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q5MEhnNp012877; Fri, 22 Jun 2012 16:43:49 +0200 (CEST) Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id q5MEhmAR026734; Fri, 22 Jun 2012 16:43:48 +0200 (CEST) Message-ID: <4FE484A4.8010204@cisco.com> Date: Fri, 22 Jun 2012 16:43:48 +0200 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Juergen Quittek References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: eman mailing list Subject: Re: [eman] power interface vs. energy interface 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, 22 Jun 2012 14:43:55 -0000 Juergen, While I understand the initial justification for Energy Interface, i.e. the comparison to the network element interface counter, I agree that Energy Inlet/Oulet terms don't sound right. So basically, I agree with you. Regards, Benoit (as a contributor) > Dear all, > > At the last session in Paris we discussed renaming "power interface" to > "energy interface". According to the minutes I proposed this, but now I'm > not sure it is a good idea. The power interface is either a power inlet > or a power outlet. Terms "power inlet" and "power outlet" are used as > well. If we rename "power interface" to "energy interface" we should > consistently also rename "power outlet" to "energy outlet". However, > "power outlet" is already a commonly used term outside our WG and it would > probably be better to keep it than renaming it to "energy outlet". > > Also at power interfaces we talk about "power characteristics" and not > "energy characteritics". > > Seeing all this I propose to keep the term "power interface" and to not > rename it. > > What do people think about it? > > Thanks, > Juergen > > > > > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman > > From karagian@cs.utwente.nl Fri Jun 22 08:06:43 2012 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 EB07721F8713 for ; Fri, 22 Jun 2012 08:06:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.504 X-Spam-Level: X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545] 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 dPLS5ICdp-Nn for ; Fri, 22 Jun 2012 08:06:43 -0700 (PDT) Received: from EXEDGE01.ad.utwente.nl (exedge01.ad.utwente.nl [130.89.5.48]) by ietfa.amsl.com (Postfix) with ESMTP id 23BFF21F86F7 for ; Fri, 22 Jun 2012 08:06:42 -0700 (PDT) Received: from EXHUB02.ad.utwente.nl (130.89.4.229) by EXEDGE01.ad.utwente.nl (130.89.5.48) with Microsoft SMTP Server (TLS) id 14.1.339.1; Fri, 22 Jun 2012 17:06:42 +0200 Received: from EXMBX04.ad.utwente.nl ([169.254.4.97]) by EXHUB02.ad.utwente.nl ([130.89.4.229]) with mapi id 14.01.0339.001; Fri, 22 Jun 2012 17:06:40 +0200 From: To: , Thread-Topic: power interface vs. energy interface Thread-Index: AQHNUG7BaddK/rVqvU6lhEeXsj3cMZcGb5rZ Date: Fri, 22 Jun 2012 15:06:40 +0000 Message-ID: References: In-Reply-To: Accept-Language: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [130.89.12.129] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [eman] power interface vs. energy interface 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, 22 Jun 2012 15:06:44 -0000 Hi Juergen, I agree that the terms "energy outlet" and "energy inlet" do not make sense= ! So it is probably necessary to keep the term "power interface". Best regards, Georgios ________________________________________ Van: eman-bounces@ietf.org [eman-bounces@ietf.org] namens Juergen Quittek [= Quittek@neclab.eu] Verzonden: vrijdag 22 juni 2012 14:01 Aan: eman mailing list Onderwerp: [eman] power interface vs. energy interface Dear all, At the last session in Paris we discussed renaming "power interface" to "energy interface". According to the minutes I proposed this, but now I'm not sure it is a good idea. The power interface is either a power inlet or a power outlet. Terms "power inlet" and "power outlet" are used as well. If we rename "power interface" to "energy interface" we should consistently also rename "power outlet" to "energy outlet". However, "power outlet" is already a commonly used term outside our WG and it would probably be better to keep it than renaming it to "energy outlet". Also at power interfaces we talk about "power characteristics" and not "energy characteritics". Seeing all this I propose to keep the term "power interface" and to not rename it. What do people think about it? Thanks, Juergen _______________________________________________ eman mailing list eman@ietf.org https://www.ietf.org/mailman/listinfo/eman= From karagian@cs.utwente.nl Sun Jun 24 12:39:09 2012 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 DE53F21F85B4 for ; Sun, 24 Jun 2012 12:39:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.504 X-Spam-Level: X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545] 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 QdquLhQNJ3zj for ; Sun, 24 Jun 2012 12:39:09 -0700 (PDT) Received: from EXEDGE01.ad.utwente.nl (exedge01.ad.utwente.nl [130.89.5.48]) by ietfa.amsl.com (Postfix) with ESMTP id B274221F85A5 for ; Sun, 24 Jun 2012 12:39:07 -0700 (PDT) Received: from EXHUB02.ad.utwente.nl (130.89.4.229) by EXEDGE01.ad.utwente.nl (130.89.5.48) with Microsoft SMTP Server (TLS) id 14.1.339.1; Sun, 24 Jun 2012 21:39:08 +0200 Received: from EXMBX04.ad.utwente.nl ([169.254.4.97]) by EXHUB02.ad.utwente.nl ([130.89.4.229]) with mapi id 14.01.0339.001; Sun, 24 Jun 2012 21:39:06 +0200 From: To: , Thread-Topic: draft-ietf-eman-applicability-statement-01.txt Thread-Index: AQHNTeTyBMB5CR/1NEyD9O4B5F56YZcJ5TzK Date: Sun, 24 Jun 2012 19:39:06 +0000 Message-ID: References: <20120619060833.30824.97392.idtracker@ietfa.amsl.com>, In-Reply-To: Accept-Language: nl-NL, en-US Content-Language: nl-NL X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [80.60.223.107] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [eman] draft-ietf-eman-applicability-statement-01.txt X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jun 2012 19:39:10 -0000 Hi Mouli, Hi all, During the IETF eman WG meeting in Paris I had promissed to send a proposal= text for a new section that describes the neighborhood energy gateways. This text can be found below: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 2.x. Neighborhood Energy Gateways=20 This use case describes the scenario of energy management of a neighborhood= , where a neighborhood energy gateway operates as a proxy that interfaces t= o the home energy gateways. It is expected that the number of photovoltaic stations (PV) on the roofs = of the houses in towns will increase significantly during the next years. = Moreover, a large scale deployment of some renewable energy sources, namely= wind and solar, imposes system integration challenges due to their variab= le and often unpredictable characteristics. Furthermore, current central s= ystems used for energy management are not able to efficiently=20 coordinate distributed renewable energy in higher penetration. In order to increase the overall energy efficiency including the producers = and consumers, neighborhood energy gateways can be used to manage the consu= mption of the locally produced energy as locally as possible, within the ne= ighborhood and between the individual buildings/homes.=20 If the energy produced by an individual building/home cannot be consumed by= the same building/home, then either another building/home in the neighborh= ood could be found to consume the energy or means need to be found to store= it. This can be supported using the neighborhood energy gateways that moni= tor and manage the home energy gateways. The EMAN information model can be applied to the protocols under considerat= ion for energy management of a neighborhood. =20 =20 The essential properties of this use case are: =20 =20 . Target devices: Neighborhood Energy Gateways and Home energy ga= teways=20 . How powered: Any method.=20 . Reporting: Neighborhood Energy Gateways can collect power consu= mption of a home via the home energy gateway and possibly report the meteri= ng reading to the utility. =20 This use case illustrates the aggregation of the energy use in neighborhood= s. In particular, this use case differs from the Home Energy Gateway use ca= se from the point of how the aggregation of energy needs to be managed, how= frequent the energy objects need to be monitored and how they need to be m= anaged. =3D=3D=3D=3D=3D=3D=3D=3D=3D Best regards, Georgios ________________________________________ Van: eman-bounces@ietf.org [eman-bounces@ietf.org] namens Mouli Chandramoul= i (moulchan) [moulchan@cisco.com] Verzonden: dinsdag 19 juni 2012 8:29 Aan: eman@ietf.org Onderwerp: [eman] draft-ietf-eman-applicability-statement-01.txt Hello all, An updated version of the EMAN Applicability Statement has been submitted. http://tools.ietf.org/html/draft-ietf-eman-applicability-statement-01 Most open issues from the previous version of the draft have been closed at the IETF 83 WG meeting. The remaining open issues are: 1. Relevance of ASHRAE SPC201P to EMAN standards (comment from Dave Robin @ WG meeting) ASHRAE standard has not been released for public review yet and should be available in a month or so. Hopefully, the next version of the applicability statement draft shall have a discussion on this topic. 2. Scope of Applicability Statement draft This was discussed in the last WG meeting and some overlap of among cases was considered fine. Secondly, the Applicability Statement draft should describe how the technology developed in the other drafts can be applied/implemented. In that sense, Applicability Statement can be completed after Requirements, Framework, MIB modules are stable. Please let us know if you have any comments, suggestions to improve the draft. Thanks Bruce, Brad and Mouli -----Original Message----- From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org Sent: Tuesday, June 19, 2012 11:39 AM To: i-d-announce@ietf.org Cc: eman@ietf.org Subject: [eman] I-D Action: draft-ietf-eman-applicability-statement-01.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Energy Management Working Group of the IETF. Title : Energy Management (EMAN) Applicability Statement Author(s) : Brad Schoening Mouli Chandramouli Bruce Nordman Filename : draft-ietf-eman-applicability-statement-01.txt Pages : 30 Date : 2012-06-18 Abstract: The objective of Energy Management (EMAN) is to provide an energy management framework for networked devices. This document presents the applicability of the EMAN framework for a variety of scenarios. This document lists use cases and target devices that can potentially implement the EMAN framework and associated SNMP MIB modules. These use cases are useful for identifying requirements for the framework. Further, we describe the relationship of the EMAN framework to relevant other energy monitoring standards and architectures. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-eman-applicability-statement There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-eman-applicability-statement-01 A diff from previous version is available at: http://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-eman-applicability-stateme nt-01 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 _______________________________________________ eman mailing list eman@ietf.org https://www.ietf.org/mailman/listinfo/eman=