[eman] eman framework issue: Lacking differentiation between devices, components, and interfaces

Juergen Quittek <ietf@quittek.at> Fri, 30 August 2013 17:37 UTC

Return-Path: <ietf@quittek.at>
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 89E2021F9E04 for <eman@ietfa.amsl.com>; Fri, 30 Aug 2013 10:37:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.853
X-Spam-Level:
X-Spam-Status: No, score=-0.853 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 FH4QrMCx5+bx for <eman@ietfa.amsl.com>; Fri, 30 Aug 2013 10:37:12 -0700 (PDT)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by ietfa.amsl.com (Postfix) with ESMTP id 0C76221F9E12 for <eman@ietf.org>; Fri, 30 Aug 2013 10:37:08 -0700 (PDT)
Received: from [10.42.187.143] (tmo-097-25.customers.d1-online.com [80.187.97.25]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0Lu2Cs-1VywWD0bHq-011W5J; Fri, 30 Aug 2013 19:37:07 +0200
From: Juergen Quittek <ietf@quittek.at>
Content-Type: text/plain; charset="us-ascii"
X-Mailer: iPhone Mail (10B329)
Message-Id: <2D7EBF2B-D82C-49ED-BC96-159C5326233F@quittek.at>
Date: Fri, 30 Aug 2013 19:37:01 +0200
To: eman mailing list <eman@ietf.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
X-Provags-ID: V02:K0:moWKL0Caou4a8l/uoGjbfA+JX2Ze3U4yNCEfXB8rpV8 jKhLS2nqNUhc66ZTc+WcbsFinBvMzsJRz4OPpPfceHCAZCgqx+ erzmW1fC7AEFzhGlwANhRq835Pc47Zr8f7f2frasB6vhfhekAJ jhTmZJHCoHVWy1vuwvzD/Yb3Xm8Nh/hJIF3jLktMJmfu82EXCU fEzRcfphkhddjvrJKsKAUBzhjd8gszsnL69bG9j9imAh6xsL3z YBxuLwcEqkYEgn/rbqcJ3E4L3yL4DJtx1pF5Rt1bMg0G1kILQZ ENcwTxAJaNNXXEyWYraj7tjMuVqkaLlX3dCaZ7hRAS8o9sygKD FRcP8NZMMUExHfJ06ump09bsVjgV/wQ/Ao9vjS0D6
Subject: [eman] eman framework issue: Lacking differentiation between devices, components, and interfaces
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: Fri, 30 Aug 2013 17:37:18 -0000

Dear all, 

Here is another framework issue: Do we report the same Information for devices, interfaces, and components?

Our framework draft (draft-ietf-eman-framework-08) uses an object-oriented model for describing the Information model for eman. The model has classes for devices, components, meters and the classes have attributes for carrying information on UUIDs, power values, etc. 

My issue with the model is that it uses the same set of attributes for all kinds of energy objects (device, component, power interface).

The only exception is a single category/type object that varies among the different classes. (Ironically, here I would use the same attribute for all classes in oder to use the same mechanism for all energy objects to retrieve their type.)

In the requirements document (draft-ietf-eman-requirements-14) there are clear differences between the sets of information elements to be reported for devices, components, and interfaces. The current model does not reflect this.

This is different for the model in draft-nordman-eman-er-framework-01. Here the model is fully aligned with the requirements and supports different sets of information provided for different kinds of energy objects. It uses simple tables to show which information needs to be reported for which type of energy object. 

I think the differentiation between devices, components, and power interfaces as it is made in the requirements draft needs to be reflected by the eman framework. 

Cheers,
 Juergen