attachment-0001
<div dir="ltr"><br>
<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">The IESG</b> <span dir="ltr"><<a href="mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a>></span><br>
Date: Tue, Jun 4, 2013 at 10:01 AM<br>Subject: [eman] Document Action: 'Requirements for Energy Management' to Informational RFC (draft-ietf-eman-requirements-14.txt)<br>To: IETF-Announce <<a href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>><br>
Cc: eman mailing list <<a href="mailto:eman@ietf.org">eman@ietf.org</a>>, eman chair <<a href="mailto:eman-chairs@tools.ietf.org">eman-chairs@tools.ietf.org</a>>, RFC Editor <<a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a>><br>
<br><br>The IESG has approved the following document:<br>
- 'Requirements for Energy Management'<br>
(draft-ietf-eman-requirements-14.txt) as Informational RFC<br>
<br>
This document is the product of the Energy Management Working Group.<br>
<br>
The IESG contact persons are Joel Jaeggli and Benoit Claise.<br>
<br>
A URL of this Internet Draft is:<br>
<a href="http://datatracker.ietf.org/doc/draft-ietf-eman-requirements/" target="_blank">http://datatracker.ietf.org/doc/draft-ietf-eman-requirements/</a><br>
<br>
<br>
<br>
<br>
Technical Summary:<br>
<br>
This document defines requirements for standards specifications for<br>
energy management. These concern monitoring functions as well as<br>
control functions: Monitoring functions include identification of<br>
energy-managed devices and their components, monitoring of their power<br>
states, power inlets, power outlets, actual power, power properties,<br>
received energy, provided energy, and contained batteries. Control<br>
functions serve for controlling power supply and power state of<br>
energy-managed devices and their components.<br>
<br>
Working Group Summary:<br>
<br>
Version -08 of this draft was presented in the EMAN session at<br>
IETF 84 (Vancouver). The authors published -09, resolving the<br>
open issues discussed at that meeting. The draft's Working Group<br>
Last Call ran from 4 October to 22 October this year, and raised<br>
several more issues. After IETF-85, the authors published its<br>
-10 version; we believe it is now ready to submit to IESG.<br>
<br>
Document Quality:<br>
<br>
Are there existing implementations of the protocol?<br>
This is a requirements draft, not a protocol.<br>
Have a significant number of vendors indicated their plan to implement<br>
the specification?<br>
At least two vendors have implemented Energy Management systems,<br>
and - presumably - will make them EMAN-compliant.<br>
Are there any reviewers that merit special mention as having done a<br>
thorough review, e.g., one that resulted in important changes or a<br>
conclusion that the document had no substantive issues?<br>
Since September the following have contributed comments on the<br>
EMAN list: Ira McDonald, John Parello, Brad Schoening, Georgios<br>
Karagian.<br>
However, the draft's authors/editors have done most of the work<br>
in developing it.<br>
If there was a MIB Doctor, Media Type or other expert review, what was<br>
its course (briefly)?<br>
The draft hasn't had any kind of expert review.<br>
<br>
Personnel:<br>
<br>
Who is the Document Shepherd? Who is the Responsible Area Director?<br>
Shepherd: Nevil Brownlee<br>
Area Director: Joel Jaeggli<br>
<br>
<br>
_______________________________________________<br>
eman mailing list<br>
<a href="mailto:eman@ietf.org">eman@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/eman" target="_blank">https://www.ietf.org/mailman/listinfo/eman</a><br>
</div><br></div>
<br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.