IETF Logo Mail Archive

Re: [eman] New draft on eman requirements - issue 1 - Device type

"Mouli Chandramouli (moulchan)" <moulchan@cisco.com> Fri, 01 July 2011 11:08 UTC

Return-Path: <moulchan@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 CD66A11E80CF for <eman@ietfa.amsl.com>; Fri, 1 Jul 2011 04:08:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZBWM6VcsPWy7 for <eman@ietfa.amsl.com>; Fri, 1 Jul 2011 04:08:23 -0700 (PDT)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by ietfa.amsl.com (Postfix) with ESMTP id 2155011E8086 for <eman@ietf.org>; Fri, 1 Jul 2011 04:08:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=moulchan@cisco.com; l=1877; q=dns/txt; s=iport; t=1309518503; x=1310728103; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=1hmm33COJCI0zz1yei49u1mRKjmu/aL5fxq8LmEY4V8=; b=lp/uulLs/8x1va3twkzLBDIJ3cdWMQXQbwBpExkZWMtrnYzURHA7x3+K 1iIcNfBL8ksUrdrri3OvNDzU4HvH/xsVqinw1HSmltFMSBCFtVpt53V48 Km6OghPbQYK1lP4xjMnBeCUvL0N7Maf9pxLZGg/WFhzq6qbvpKS4WZCBh Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvEAAAOqDU6tJV2Z/2dsb2JhbABEDpgrjzR3q2CeBIMfgxMEhz6Pc4tQ
X-IronPort-AV: E=Sophos;i="4.65,457,1304294400"; d="scan'208";a="389942338"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by sj-iport-2.cisco.com with ESMTP; 01 Jul 2011 11:08:22 +0000
Received: from xbh-rcd-101.cisco.com (xbh-rcd-101.cisco.com [72.163.62.138]) by rcdn-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p61B8M7C032570; Fri, 1 Jul 2011 11:08:22 GMT
Received: from xmb-rcd-106.cisco.com ([72.163.62.148]) by xbh-rcd-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 1 Jul 2011 06:08:21 -0500
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: Fri, 01 Jul 2011 06:08:18 -0500
Message-ID: <E9B25823FA871E4AA9EDA7B163E5D8A9059555F1@XMB-RCD-106.cisco.com>
In-Reply-To: <CA320DCE.16CC6%quittek@neclab.eu>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [eman] New draft on eman requirements - issue 1 - Device type
Thread-Index: Acw2bEgLUSQNJgXDjE6Pk4zAd/RgeAAm3TUGADU3dJA=
References: <CA3108FE.16C09%quittek@neclab.eu> <CA320DCE.16CC6%quittek@neclab.eu>
From: "Mouli Chandramouli (moulchan)" <moulchan@cisco.com>
To: Juergen Quittek <Quittek@neclab.eu>, eman mailing list <eman@ietf.org>
X-OriginalArrivalTime: 01 Jul 2011 11:08:21.0800 (UTC) FILETIME=[30829280:01CC37DF]
Subject: Re: [eman] New draft on eman requirements - issue 1 - Device type
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, 01 Jul 2011 11:08:23 -0000

Hello,

As Juergen has mentioned, while the first version has been released to
solicit feedback, some of the concepts are still debated.
The perspectives from the email list would be useful to shape the draft.

I shall post some of the discussion points. 

Thanks
Mouli

------------

There is a requirement -
http://www.ietf.org/internet-drafts/draft-ietf-eman-requirements-03.txt


5.1.1.  Type of powered entity

   The energy management standard must provide means to retrieve and
   report the type of powered entities.

I think it would be useful to expand this requirement. Device Type could
be inferred as "IP Phone" or "Line Card 3", ...

One possibility is to consider is a description of the device and then
the type of device. 

Powered Devices Description

   The energy management standard must provide means for identifying the
   entity with a powered device description, the domain to which the
   device belongs.

Powered Entity Type

   The energy management standard must provide means to identify the
   powered device type such as consumer, provider, meter.





-----Original Message-----
From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of
Juergen Quittek
Sent: Thursday, June 30, 2011 2:56 PM
To: eman mailing list
Subject: Re: [eman] New draft on eman requirements

Dear all,

I am sorry for posting another version just one day after the previous
one.
Now out is version -03 to be found at
 
http://www.ietf.org/internet-drafts/draft-ietf-eman-requirements-03.txt

The reason was that a change in terminology ("powered device" ->
"powered
entity") was not done consistently in all sections, particularly not in
the
battery section.

There are no further changes, particularly no technical changes compared
to
the previous version.

Thanks,

    Juergen

v2.23.0 | Report a Bug | By Email