[eman] Review of draft-tychon-eman-applicability-statement-00
Benoit Claise <bclaise@cisco.com> Thu, 04 November 2010 13:42 UTC
Return-Path: <bclaise@cisco.com>
X-Original-To: eman@core3.amsl.com
Delivered-To: eman@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A3D6A3A6A0B for <eman@core3.amsl.com>; Thu, 4 Nov 2010 06:42:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y9+lue5nNTbx for <eman@core3.amsl.com>; Thu, 4 Nov 2010 06:42:48 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id 41D443A69FD for <eman@ietf.org>; Thu, 4 Nov 2010 06:42:48 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oA4DgvMX008785 for <eman@ietf.org>; Thu, 4 Nov 2010 14:42:57 +0100 (CET)
Received: from [10.55.43.53] (ams-bclaise-8714.cisco.com [10.55.43.53]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id oA4DgvUb012598 for <eman@ietf.org>; Thu, 4 Nov 2010 14:42:57 +0100 (CET)
Message-ID: <4CD2B860.8080507@cisco.com>
Date: Thu, 04 Nov 2010 14:42:56 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: eman mailing list <eman@ietf.org>
Content-Type: multipart/alternative; boundary="------------090402050802060408010105"
Subject: [eman] Review of draft-tychon-eman-applicability-statement-00
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions about the creation of an Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Nov 2010 13:42:50 -0000
Emmanuel, Matt, Brad, Speaking as a contributor, I reviewed draft-tychon-eman-applicability-statement-00 <http://datatracker.ietf.org/doc/draft-tychon-eman-applicability-statement/> Thanks for this first draft. A couple of high levels points (more editorial notes will be sent separately) - the Abstract speaks about "describe the relevant information elements for these applications". I'm not sure what you refer to - by convention, when a term is capitalized, it's defined in the terminology section. For example, I see Energy - Not sure what you mean by "as traditional methods such as SNMP have proved not to be sufficient" because this charter is specified to define MIB modules ;-) - this draft would benefit from some references * to other EMAN documents This might imply that we have a generic section for all EMAN documents, referring to each other. See section 1.2 in http://tools.ietf.org/html/rfc5470 for an IPFIX example A typical example: "in other cases, there are intermediate power levels between off and on, such as standby, sleep or deep sleep mode". It would be good to refer to the others EMAN documents where this is specified. * to external documents from other organisations. - in section 1.3 "examples", I believe that the primary example should be "IT". In section 1.3.1 "building networks", you mention: laptops, phone, desktop. IMHO, these are part of the IT examples. - IMHO, building networks is a specific case that requires a proxy... while waiting for the IP protocol to be more ubiquitous. - by convention acronyms should be explained. Example: HEG, EPA, EISA You should write "Home Energy Gateways (HEG)" the first time you mention it - while [PARELLO] is certainly a very nice reference, it would certainly be more appropriate to cite the reference within the book ;-) - the sections 2.x are interesting, but I'm sometimes missing the link with EMAN A good example is section 2.2 "The IETF effort would be complementary" For the other sections, I don't clearly see the link, i.e: none, complimentary, overlap, can be used together, etc... Examples: IEC -> we should try to reuse it as much as possible DMTF "power utilization management profile" -> explain the overlap/complementarity with EMAN DASH -> could be used to configure the Power Monitor Child from the Power Monitor Parent etc... - section 4.2 "energywise" Not sure what the share secret is used for. We deal with MIB modules here. Looking at the charter description, 6. Applicability statement The EMAN WG will develop an applicability statement, describing the variety of applications that can use the energy framework and associated MIB modules. Potential examples are building networks, home energy gateway, etc. Finally, the document will also discuss relationships of the framework to other architectures and frameworks (such as smartgrid). The applicability statement will explain the relationship between the work in this WG and the other existing standards such as those from the IEC, ANSI, DMTF, and others. Maybe what we would need to cover: - described the applications ( 1. monitoring energy 1.1 smart metering ... 2. management energy 2.1 just for the sake of consuming less 2.2 to avoid blackout 2.3 to flatten the demand/response ... - also the link between the smartgrid use cases and these energy-aware devices should be explained. Regards, Benoit.
- [eman] Review of draft-tychon-eman-applicability-… Benoit Claise