[eman] Authors - draft-ietf-eman-framework-10: WGLC comments

"John Parello (jparello)" <jparello@cisco.com> Mon, 14 October 2013 05:37 UTC

From: "John Parello (jparello)" <jparello@cisco.com>
To: "eman@ietf.org" <eman@ietf.org>
Thread-Topic: Authors - draft-ietf-eman-framework-10: WGLC comments
Thread-Index: Ac7Inz/7R3qVc61VRsGPcvbes8mfag==
Date: Mon, 14 Oct 2013 05:37:21 +0000
Message-ID: <9C213D38848B89428F46808B16F6F08601667AFA@xmb-aln-x04.cisco.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: multipart/alternative; boundary="_000_9C213D38848B89428F46808B16F6F08601667AFAxmbalnx04ciscoc_"
MIME-Version: 1.0
Subject: [eman] Authors - draft-ietf-eman-framework-10: WGLC comments
Precedence: list

Hi,

These are the review comments we had among the authors on 10/8 and applied:

* 10/8 Author's call
Nevil, Benoit, Brad, John

** Discussed specific points from reviews and concluded…..

*** Capitalization
Move modeling (class) into section 4
only power / energy not capitalize
See txt
+ JP : Done, had the option to lower case common terms went with that will review 10/15 before publishing

*** Scalar vs Vector
Category - overloaded if vectore { cons, prod, meter, distributor, store }
Primary is better received
ex: car { biz, pleasure, commute }
Role - need semantic not vector
Location? (new) - clearly not vector but semantic like rfc4776 better geo-priv
Domain - no problem we discussed and went with single
Experience in filed is that scalar was only needed for these.
ref point lldp : brad

+ JP : Done

*** Section 3.3 Bullet list
Editing trying to get a sane list not pages. What would we like there?
put back or better description..

+ JP : Agree with JQ I consolidate those sections to main points and unless we want that section I deleted it. Serves no purpose any longer with requirements draft and applicability IMO.Any objections??

*** Context in device versus in NMS
Ask and answered we can discuss again

+ JP : nothing to do here agreed on device and not hidden in mms

*** Should state be in a section on control if they can be used for monitoring
We talked about this in authors call and said ok in control, everything can be monitored and seemed a better location.
we are ok with in control. "add sentence that while power state in control they can be used for monitoring wihout any change ..."

+ JP : Added sentence

*** Demand, Energy when power is not actual
relates to caliber.
IF power isn't actual demand and energy is not applicable. Thought exercise that you can report energy and demand and not provide power but that's mental exercise. could ignore this but that was the point
ask for improvement txt

+ JP : asked in comment and clarified in sections after definition move.

*** Better description of physical
physical strict border between sections on physcal and modelled
Only physical before section 6
physical: inlet outlet "electrical connection"
modeling: power interface

+ JP : used scheme below

*** Section 6.2 Metering
Should be for a "METER" Case 2 not just because an interface measures energy. That would clear up the controversy.
S.B. one case not two was confusing people

+ JP : Consolidated to only use for a meter

*** Feedback: lost from uml link to interfaces and components
Added

+JP: PowerInterface powerInterfaces[0..n] Component components[0..n]
Note: Component could sub-class Device. May confuse the non modelers so leaving as siblings and can remove.

*** Make sure the text doesn't read energy object as instance but as class.

+ JP : Done went with this scheme strictly

"""
I) This physical thing IRL,
II)Is described by
III) and represented by this

I)Physical II) Modeling (Meta Data) III)Instance
---------------------------------------------------------

equipment Energy Object (Class) Energy Object
device Device (Class) Device
component Component (Class) Component
inlet / outlet Power Interface (Class) Power Interface
"""

Thanks!
Jp

[eman] Authors - draft-ietf-eman-framework-10: WG… John Parello (jparello)
[eman] draft-ietf-eman-applicability-statement-03 Mouli Chandramouli (moulchan)
Re: [eman] draft-ietf-eman-applicability-statemen… Ira McDonald
Re: [eman] draft-ietf-eman-applicability-statemen… John Parello (jparello)
Re: [eman] draft-ietf-eman-applicability-statemen… Brad Schoening
Re: [eman] draft-ietf-eman-applicability-statemen… Ira McDonald