[eman] Rolf.Winter - draft-ietf-eman-framework-10: WGLC comments
"John Parello (jparello)" <jparello@cisco.com> Sun, 13 October 2013 21:56 UTC
Return-Path: <jparello@cisco.com>
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 0DAD921F9D0A for <eman@ietfa.amsl.com>; Sun, 13 Oct 2013 14:56:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.502
X-Spam-Level:
X-Spam-Status: No, score=-9.502 tagged_above=-999 required=5 tests=[AWL=1.096, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rBYpL3HnDPIk for <eman@ietfa.amsl.com>; Sun, 13 Oct 2013 14:56:31 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id A5FC111E8143 for <eman@ietf.org>; Sun, 13 Oct 2013 14:56:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8786; q=dns/txt; s=iport; t=1381701390; x=1382910990; h=from:to:cc:subject:date:message-id:mime-version; bh=McLkNg+yBsWavPee/vL9VsTjrzypI2hiuv9rdmc4LQw=; b=CaT2j86z3frji779S470OUJqXK8xyEp93b8X2x1XBWYH6w5ur8apuaar cyVUEuhM5jgFtwQi0LYkYtAd0UWFcDFqXJn74xQjWznwv0upPwvawDqQE et9fV9loOWrpwZ2nYvgWqcu049m8h7B/ZKHIOEy85R0hvZ77GIJ52ksWw o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlkGAE0WW1KtJXHB/2dsb2JhbABZgkNEgQrBbYEaFm0HgicBBHIHEgEqViYBBA4Nh368do4DF4EHMYMmgQQDiQSLJJVfgySCKQ
X-IronPort-AV: E=Sophos; i="4.93,487,1378857600"; d="scan'208,217"; a="271647953"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-3.cisco.com with ESMTP; 13 Oct 2013 21:56:27 +0000
Received: from xhc-rcd-x07.cisco.com (xhc-rcd-x07.cisco.com [173.37.183.81]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r9DLuROS019814 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 13 Oct 2013 21:56:27 GMT
Received: from xmb-aln-x04.cisco.com ([169.254.9.229]) by xhc-rcd-x07.cisco.com ([173.37.183.81]) with mapi id 14.02.0318.004; Sun, 13 Oct 2013 16:56:27 -0500
From: "John Parello (jparello)" <jparello@cisco.com>
To: "eman@ietf.org" <eman@ietf.org>
Thread-Topic: Rolf.Winter - draft-ietf-eman-framework-10: WGLC comments
Thread-Index: Ac7IXxCtsmVkrfYnQcSjeFSKsHqBhg==
Date: Sun, 13 Oct 2013 21:56:26 +0000
Message-ID: <9C213D38848B89428F46808B16F6F08601667923@xmb-aln-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.21.78.193]
Content-Type: multipart/alternative; boundary="_000_9C213D38848B89428F46808B16F6F08601667923xmbalnx04ciscoc_"
MIME-Version: 1.0
Subject: [eman] Rolf.Winter - draft-ietf-eman-framework-10: WGLC comments
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Sun, 13 Oct 2013 21:56:37 -0000
Hi Rolf, Thanks again, this is the followup to the first rev I did. I applied the changes see inline. You should be good in rev-11. Jp > ! weird spelling (e.g. Battery is capitalized in the abstract) ! > inconsistent spelling (e.g. "Energy Management System" and "energy > management system" are both used throughout the text without apparent > reason, same applies to "power", "demand" and a whole bunch of other > terms) > > JP : Yeah I'm not comfortable with the capitalization either. When we > started the draft all the comments we had were to capitalize > everything in the terminology section. You're facing the same issue in > the requirements. In order to help with this I am publishing a new > version of the terminology draft with a proposed capitalization scheme > that is more sane. Terms that are common are lower case and anything > that originates in our WG is capitalized. Let's discuss / open a thread > in that context them apply those minor edits to both drafts. This is what the requirements draft converged to as well. ! JP - Great we definitely agree here. See thread on terminology and caps summary. I'll make the changes after that discussion closes. > - measured in kilowatt hours... I personally would write "measured in > watt hours" as kilo is merely an SI prefix. Kilo is certainly a common > prefix but I am sure there are consumers that are measured in other SI > prefixes... > > JP : direct quote so I left it kilo. I agree with you but it's a direct > quote. If that's the case, I think it should be actually put in quotation marks to show that. + JP : I added a note in the definition to indicate this. "While IEEE100 defines Demand in kilo measurements for EMAN we use watts with any suitable metric prefix ." > > + I think the rule regarding SI unit and numerical value is that there > is a space in between the two. In either case, use one scheme > consistently. > > JP : I don't see a rule for space but the prefixes from use are clearly > non spaced kilometer, miligram, picowatt. Scrubbed. That's not what I meant. I meant between numerical value and the SI unit. So it is not 3mW but 3 mW. That's still in the document (both forms, so it is still inconsistent). + JP : Thanks didn't follow before, done now > > + "Limitation (curtailment) of the power used by an Energy Object in a > state is specified by" I would add an "e.g." here, since not all of > them have to be used at the same time. > > JP - I changed "is" to "may" to indicate the choice Then you should add a "be" + JP : Done > + This sentence "Since one point of a power distribution system may > cover many Devices with a complex wiring topology, this relationship > type can be seen as an arbitrary set." sounds strange to me. Why can > this be seen as an arbitrary set. Complex != arbitrary. > > JP - "Since one point of a power distribution system may cover many > Devices within a wiring topology" Sure, but why would one call this arbitrary I still don't get. + JP: Yep I removed arbitrary, it's a set. > - regarding the PDU in section 6, shouldn't "among the inlets or > outlet" be "among the inlet or outlets" > > JP - A PDU or (any device) may have multiple inlets (very common) so > that was intentionally made plural. But then I still don't get why you insist on a single outlet because a PDU surely has more than one? + JP : We agree. it was always meant to be multiple inlets and outlets. Both are plural now. Thanks again for the details! Thanks! Jp
- [eman] Rolf.Winter - draft-ietf-eman-framework-10… John Parello (jparello)