Opened 6 years ago

#39 new defect

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

Reported by: b.hedstrom@… Owned by: draft-ietf-eman-applicability-statement@…
Priority: major Milestone:
Component: applicability-statement Version: 2.0
Severity: - Keywords:


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

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"?

Change History (0)

Note: See TracTickets for help on using tickets.