Re: [eman] EMAN-REQ: the notion of importance

"John Parello (jparello)" <jparello@cisco.com> Mon, 27 February 2012 16:42 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 358FD21F8647 for <eman@ietfa.amsl.com>; Mon, 27 Feb 2012 08:42:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.993
X-Spam-Level:
X-Spam-Status: No, score=-8.993 tagged_above=-999 required=5 tests=[AWL=1.606, 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 ICIgot8-KX84 for <eman@ietfa.amsl.com>; Mon, 27 Feb 2012 08:42:58 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 6AB4921F85AD for <eman@ietf.org>; Mon, 27 Feb 2012 08:42:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jparello@cisco.com; l=5137; q=dns/txt; s=iport; t=1330360978; x=1331570578; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=HqJLPjhENXFnDAaVLn0Hbh7jgCUTctnVzYaR5iEJTGA=; b=LYGcIGWdseHF6EwoRLwKH6lIpZMBInb1ucJyKEjoORc3B+mG1cRXBfoK xKvl8rStu5qEoRWvLM6hHZ0PW3T/iFJDY8+Y+VcTkl1N7xDuf29oD3NXK aFSzTXSbGOo/+d+LbV1B08vWfvhG4tEccVhtVz8QSHgOZrPXgMkrTejBV 0=;
X-IronPort-AV: E=Sophos;i="4.73,491,1325462400"; d="scan'208";a="30674954"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 27 Feb 2012 16:42:58 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id q1RGgwFE010770; Mon, 27 Feb 2012 16:42:58 GMT
Received: from xmb-sjc-21b.amer.cisco.com ([171.70.151.143]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 27 Feb 2012 08:42:41 -0800
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: Mon, 27 Feb 2012 08:42:40 -0800
Message-ID: <EDCAE188ADBDC045AB6E7BC54D532C8A10BBC29E@xmb-sjc-21b.amer.cisco.com>
In-Reply-To: <791AD3077F94194BB2BDD13565B6295D2502B50E@DAPHNIS.office.hd>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [eman] EMAN-REQ: the notion of importance
Thread-Index: AQHM9UFw8dbGmgfXW0qrcsXzXFqgppZQrFgAgAAmNDCAAB3mMA==
References: <4F4B6644.2030503@cisco.com><CAN40gStVGSzSg5PctnTX1HwwpabkWUGwcerLj70xhL_-C6tWmQ@mail.gmail.com> <791AD3077F94194BB2BDD13565B6295D2502B50E@DAPHNIS.office.hd>
From: "John Parello (jparello)" <jparello@cisco.com>
To: Rolf Winter <Rolf.Winter@neclab.eu>, Ira McDonald <blueroofmusic@gmail.com>, "Benoit Claise (bclaise)" <bclaise@cisco.com>
X-OriginalArrivalTime: 27 Feb 2012 16:42:41.0326 (UTC) FILETIME=[D27914E0:01CCF56E]
Cc: eman mailing list <eman@ietf.org>
Subject: Re: [eman] EMAN-REQ: the notion of importance
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: Mon, 27 Feb 2012 16:42:59 -0000

-1

If you remove context variables such as role: what a device is use for,
and a way to compare devices (importance) how will you determine which
ones you can shed power usage from in times of peak.

I agree this is something that should be in general network management.
Fault correlation and problem tracking would be easier. For power
management of a system the notion of context becomes more critical. For
example if during a peak demand time you want to shed power from you
lighting system and you have no notion of context how would you
determine which lights were decorative, emergency, task, or ambient
lights? 

The argument that this should be in the management system can be said
for any attribute, it becomes more useful if the devices have these
attributes in them. 

For example compare this to location attributes. You could argue that a
device need not have  a location attribute and this is part of the NMS -
but look at the usefulness of systems that have been developed when a
standardized location is put in the devices themselves versus a central
NMS.

If you remove context you remove any notion of being able to have
devices work on their own or in concert to control power. You relegate
it to a central system which will become proprietary an intractable with
the IoT.

So if you remove this you remove the core usefulness of the system.
Jp


-----Original Message-----
From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of
Rolf Winter
Sent: Monday, February 27, 2012 8:08 AM
To: Ira McDonald; Benoit Claise (bclaise)
Cc: eman mailing list
Subject: Re: [eman] EMAN-REQ: the notion of importance

Hi,

I agree. I personally also think that importance can be removed. It is
ill defined in the current document, if _really_ needed it seems like a
more general concept and I wonder why it should be part of the MIB as
opposed to something that is part of the management system. Regarding
role, if it is to stay in the MIB (as opposed to the EnMS) then it also
need a better definition and a good justification why it should be
stored on the device itself.

Best,

Rolf


NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road,
London W3 6BL | Registered in England 2832014 


> -----Original Message-----
> From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf 
> Of Ira McDonald
> Sent: Montag, 27. Februar 2012 14:29
> To: Benoit Claise; Ira McDonald
> Cc: eman mailing list
> Subject: Re: [eman] EMAN-REQ: the notion of importance
> 
> Hi Benoit,
> 
> That quote equates "powered entity's role" with "importance".
> 
> This sounds largely useless and subjective.
> 
> There seems to be no interest in having standardized "role"
> values in the EMAN community (and I'm not sure it's a tractable 
> problem, anyway).
> 
> How about dropping the "importance" terminology entirely and sticking 
> to "role as an energy consumer"?
> 
> Cheers,
> - Ira
> 
> Ira McDonald (Musician / Software Architect) Chair - Linux Foundation 
> Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair 
> - IEEE-ISTO PWG IPP WG Co-Chair - TCG Trusted Mobility Solutions WG 
> Chair
> - TCG Embedded Systems Hardcopy SG IETF Designated Expert - IPP & 
> Printer MIB Blue Roof Music/High North Inc 
> http://sites.google.com/site/blueroofmusic
> http://sites.google.com/site/highnorthinc
> mailto:blueroofmusic@gmail.com
> Winter  579 Park Place  Saline, MI  48176  734-944-0094 Summer  PO Box
> 221  Grand Marais, MI 49839  906-494-2434
> 
> 
> 
> On Mon, Feb 27, 2012 at 6:17 AM, Benoit Claise <bclaise@cisco.com>
> wrote:
> 
> 
> 	Dear all,
> 
> 	There is a discussion amongst the "EMAN requirements" authors
right 
> now about the notion of importance.
> 	We're trying to evaluate the requirements related to the 
> "importance".
> 
> 	The current draft version
<http://tools.ietf.org/html/draft-ietf-
> eman-requirements-05>  only mentions:
> 
> 
> 
> 
> 	5.1.2.  Context information on powered entities
> 
> 	   The energy management standard must provide means for
retrieving 
> and
> 	   reporting context information on powered entities, for
example, 
> tags
> 	   associated with a powered entity that indicate the powered 
> entity's
> 	   role, or importance.
> 
> 	So there are no justifications why the importance is required.
> 	The people who want this, please provide some more 
> text/justifications
> 
> 	Some extra questions:
> 	- Is this importance specific to EMAN or is this generic also
for non 
> Energy Objects?
> 	- Importance is important related to ...?
> 
> 	Regards, Benoit (as a contributor for the EMAN-REQ)
> 
> 
> 
> 
> 
> 	_______________________________________________
> 	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