[eman] #39: Energy Control not effectively drawn out in the use cases, or defined

"eman issue tracker" <trac+eman@trac.tools.ietf.org> Thu, 18 July 2013 15:35 UTC

Return-Path: <trac+eman@trac.tools.ietf.org>
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 8AB4A11E80FC for <eman@ietfa.amsl.com>; Thu, 18 Jul 2013 08:35:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 cP8x4rNEXXQK for <eman@ietfa.amsl.com>; Thu, 18 Jul 2013 08:35:45 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id D51DC11E814E for <eman@ietf.org>; Thu, 18 Jul 2013 08:34:45 -0700 (PDT)
Received: from localhost ([127.0.0.1]:47483 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+eman@trac.tools.ietf.org>) id 1UzqDy-0008Ov-V2; Thu, 18 Jul 2013 17:34:34 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: eman issue tracker <trac+eman@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-eman-applicability-statement@tools.ietf.org, b.hedstrom@cablelabs.com
X-Trac-Project: eman
Date: Thu, 18 Jul 2013 15:34:34 -0000
X-URL: http://tools.ietf.org/eman/
X-Trac-Ticket-URL: http://tools.ietf.org/wg/eman/trac/ticket/39
Message-ID: <063.f798c30dac13e134c4422d863fa66c86@trac.tools.ietf.org>
X-Trac-Ticket-ID: 39
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-eman-applicability-statement@tools.ietf.org, b.hedstrom@cablelabs.com, eman@ietf.org
X-SA-Exim-Mail-From: trac+eman@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: bnordman@lbl.gov, brad.schoening@verizon.net, moulchan@cisco.com
Resent-Message-Id: <20130718153445.D51DC11E814E@ietfa.amsl.com>
Resent-Date: Thu, 18 Jul 2013 08:34:45 -0700
Resent-From: trac+eman@trac.tools.ietf.org
Cc: eman@ietf.org
Subject: [eman] #39: Energy Control not effectively drawn out in the use cases, or defined
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 18 Jul 2013 15:35:48 -0000

#39: Energy Control not effectively drawn out in the use cases, or defined

 In the Applicability Statement, the "Control/Controlling" pattern is not
 drawn out in each use case, like the Metering/Powering/Reporting are.

 Use Case Section Description:
         In this section a selection of scenarios for energy management
         are presented.  The fundamental objective of the use cases is to
         list important network scenarios that the EMAN framework should
         solve.  These use cases then drive the requirements for the EMAN
         framework.

         Each scenario lists target devices for which the energy
         management framework can be applied, how the reported-on devices
         are powered, and how the reporting is accomplished.  While there
         is some overlap between some of the use cases, the use cases
         illustrate network scenarios that the EMAN framework supports.

 Each Use Case has:
 The essential properties of this use case are:

           . Target devices: network devices such as routers and
              switches as well as their components.
           . How powered: typically by a Power Distribution Unit (PDU)
              on a rack or from a wall outlet.  The components of a
              device are powered by the device chassis.
           . Reporting: direct power measurement can be performed at a
              device level.  Components can report their power
              consumption directly or the chassis/device that can report
              on behalf of some components.
 In addition, I do not see a thorough definition of control in the draft to
 explain the meaning in this context.  The definitions draft draft-parello-
 eman-definitions-08 provides a definition for Energy Control. This draft
 should reference that definition and use this term.  The term definition
 in the Definitions draft does not appear to restrict the definition of
 Control to changing the energy/power state of a device.  Is there a
 disconnect between these drafts in the meaning of "Control"?

-- 
-------------------------------------+-------------------------------------
 Reporter:                           |      Owner:  draft-ietf-eman-
  b.hedstrom@cablelabs.com           |  applicability-
     Type:  defect                   |  statement@tools.ietf.org
 Priority:  major                    |     Status:  new
Component:  applicability-statement  |  Milestone:
 Severity:  -                        |    Version:  2.0
                                     |   Keywords:
-------------------------------------+-------------------------------------

Ticket URL: <http://tools.ietf.org/wg/eman/trac/ticket/39>
eman <http://tools.ietf.org/eman/>