[eman] Document Action: 'Requirements for Energy Management' to Informational RFC (draft-ietf-eman-requirements-14.txt)
The IESG <iesg-secretary@ietf.org> Tue, 04 June 2013 16:11 UTC
Return-Path: <iesg-secretary@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 47BD521E80CE; Tue, 4 Jun 2013 09:11:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.477
X-Spam-Level:
X-Spam-Status: No, score=-102.477 tagged_above=-999 required=5 tests=[AWL=0.123, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 F5g9tlNR+c9Y; Tue, 4 Jun 2013 09:11:20 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 429BF21F9B8C; Tue, 4 Jun 2013 07:01:19 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 4.50
Message-ID: <20130604140119.27892.78840.idtracker@ietfa.amsl.com>
Date: Tue, 04 Jun 2013 07:01:19 -0700
Cc: eman mailing list <eman@ietf.org>, eman chair <eman-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [eman] Document Action: 'Requirements for Energy Management' to Informational RFC (draft-ietf-eman-requirements-14.txt)
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: Tue, 04 Jun 2013 16:11:30 -0000
The IESG has approved the following document: - 'Requirements for Energy Management' (draft-ietf-eman-requirements-14.txt) as Informational RFC This document is the product of the Energy Management Working Group. The IESG contact persons are Joel Jaeggli and Benoit Claise. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-eman-requirements/ Technical Summary: This document defines requirements for standards specifications for energy management. These concern monitoring functions as well as control functions: Monitoring functions include identification of energy-managed devices and their components, monitoring of their power states, power inlets, power outlets, actual power, power properties, received energy, provided energy, and contained batteries. Control functions serve for controlling power supply and power state of energy-managed devices and their components. Working Group Summary: Version -08 of this draft was presented in the EMAN session at IETF 84 (Vancouver). The authors published -09, resolving the open issues discussed at that meeting. The draft's Working Group Last Call ran from 4 October to 22 October this year, and raised several more issues. After IETF-85, the authors published its -10 version; we believe it is now ready to submit to IESG. Document Quality: Are there existing implementations of the protocol? This is a requirements draft, not a protocol. Have a significant number of vendors indicated their plan to implement the specification? At least two vendors have implemented Energy Management systems, and - presumably - will make them EMAN-compliant. Are there any reviewers that merit special mention as having done a thorough review, e.g., one that resulted in important changes or a conclusion that the document had no substantive issues? Since September the following have contributed comments on the EMAN list: Ira McDonald, John Parello, Brad Schoening, Georgios Karagian. However, the draft's authors/editors have done most of the work in developing it. If there was a MIB Doctor, Media Type or other expert review, what was its course (briefly)? The draft hasn't had any kind of expert review. Personnel: Who is the Document Shepherd? Who is the Responsible Area Director? Shepherd: Nevil Brownlee Area Director: Joel Jaeggli