Re: [eman] Feedback on draft-ietf-eman-requirements-05
Ira McDonald <blueroofmusic@gmail.com> Thu, 09 February 2012 16:16 UTC
Return-Path: <blueroofmusic@gmail.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 7AF7621F86F0 for <eman@ietfa.amsl.com>; Thu, 9 Feb 2012 08:16:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.658
X-Spam-Level:
X-Spam-Status: No, score=-2.658 tagged_above=-999 required=5 tests=[AWL=0.940, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
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 muYY-pTB-yrK for <eman@ietfa.amsl.com>; Thu, 9 Feb 2012 08:16:53 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id EC4AE21F86E5 for <eman@ietf.org>; Thu, 9 Feb 2012 08:16:52 -0800 (PST)
Received: by wgbdt10 with SMTP id dt10so1404366wgb.13 for <eman@ietf.org>; Thu, 09 Feb 2012 08:16:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=246R5mJc+U3se389fBa0Wd/6FtYB5juA1Q5uEcmqobg=; b=t38RcRFQFmShH9P81rU/7GJV4elq2Z3RNxKkxVB6/MIv58cHq/5SZzalHWC3D7B56X QZORfBvhSS4z1whkLWuE6FkBrGHRUWEDRFsDKPVqHmnUPTKsMt/emqWEHrgcMYHlm1yy qwH/YjEsuppwSGrFet/kx+wJxA367eVkanAF0=
MIME-Version: 1.0
Received: by 10.180.92.73 with SMTP id ck9mr3842976wib.2.1328804212022; Thu, 09 Feb 2012 08:16:52 -0800 (PST)
Received: by 10.223.96.73 with HTTP; Thu, 9 Feb 2012 08:16:51 -0800 (PST)
In-Reply-To: <E9B25823FA871E4AA9EDA7B163E5D8A907848F61@XMB-RCD-106.cisco.com>
References: <14803CE6B7CFE0439D9346D27557A82A5967AFEB1E@EMBX02-HQ.jnpr.net> <E9B25823FA871E4AA9EDA7B163E5D8A907848F61@XMB-RCD-106.cisco.com>
Date: Thu, 09 Feb 2012 11:16:51 -0500
Message-ID: <CAN40gSvrLuTug3DUJQh=oRwHrbYafrRY8AUztHbRwROCqC4avg@mail.gmail.com>
From: Ira McDonald <blueroofmusic@gmail.com>
To: "Mouli Chandramouli (moulchan)" <moulchan@cisco.com>, Ira McDonald <blueroofmusic@gmail.com>
Content-Type: multipart/alternative; boundary="f46d043892c5089bd004b88a574f"
Cc: quittek@neclab.edu, eman@ietf.org
Subject: Re: [eman] Feedback on draft-ietf-eman-requirements-05
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: Thu, 09 Feb 2012 16:16:57 -0000
Hi Daniel, Relevant to your questions, you might want to look at our IEEE-ISTO Printer Working Group candidate standards for Printers and MFDs: "Power Management Model for Imaging Systems v1.0" ftp://ftp.pwg.org/pub/pwg/candidates/cs-wimspower10-20110214-5106.4.pdf "PWG Imaging System Power MIB v1.0" ftp://ftp.pwg.org/pub/pwg/candidates/cs-wimspowermib10-20110214-5106.5.pdf "PWG-IMAGING-SYSTEM-POWER-MIB" - ASN.1 source ftp://ftp.pwg.org/pub/pwg/candidates/cs-wimspowermib10-20110214-5106.5.mib The PowerLog group defines a FIFO list of state transitions with time stamps. The PowerTrap group defines a notification to report state transitions. The PowerSupport group defines objects about the capabilities of the device (or component/subunit) in a given state. The PowerTransition group defines objects for nominal state transition times between any two supported power states. The Power[Calendar/Timeout/Event] groups define objects for configured power transitions for device or component based on calendar (like IETF Schedule MIB), timeout, or event triggers. BTW - This MIB uses the standard DMTF CIM power states, but allows vendor extension substates (e.g., fine-grained Suspend substates). And this MIB defines explicit light sleep (Standby) and deep sleep (Suspend) states and their standard behaviors - note that Bruce Nordman does not like the use of these terms, but all Printers/MFDs that support power management have always made this distinction in the their private MIBs and embedded web servers. Cheers, - Ira (editor of the PWG power standards) Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Secretary - IEEE-ISTO Printer Working Group Co-Chair - IEEE-ISTO PWG IPP WG Co-Chair - TCG Trusted Mobility Solutions WG Chair - TCG Embedded Systems Hardcopy SG IETF Designated Expert - IPP & Printer MIB Blue Roof Music/High North Inc http://sites.google.com/site/blueroofmusic http://sites.google.com/site/highnorthinc mailto:blueroofmusic@gmail.com Winter 579 Park Place Saline, MI 48176 734-944-0094 Summer PO Box 221 Grand Marais, MI 49839 906-494-2434 On Thu, Feb 9, 2012 at 6:42 AM, Mouli Chandramouli (moulchan) < moulchan@cisco.com> wrote: > > Hello Daniel, > > Reply inline. > > Thanks > Mouli > > -----Original Message----- > From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of > Daniel Kharitonov > Sent: Wednesday, February 08, 2012 7:43 AM > To: quittek@neclab.edu > Cc: eman@ietf.org > Subject: [eman] Feedback on draft-ietf-eman-requirements-05 > > Apologies if this has surfaced before as I did not have time to read the > full eman discussions archive. > I have two notes regarding the aforementioned draft: > > > 2) Section 5.2 "Power State" > > Since the document correctly links reduced power states to tradeoffs in > performance, service or capacity, it would be logical to report the > characteristics of available states along same lines. > > For example, an operator of energy NMS might be interested in knowing > that device supports not only power states A, B, C with expected > consumption {a,b,c} watts but also operates at {100,50,30} capacity in > those with expected in-out transition time not to exceed X/Y seconds. > > YCM>> Currently from a requirements point of view, for every entity, we > have requirements to report the power state of an entity, (req. 5.2.1), > YCM>> its power consumption (req. 5.4.1) and statistics for each power > state (req. 5.2.6.) > YCM>> There are notifications when power states changes occur (req > 5.2.8) and from the time stamps of notifications, it should be possible > to estimate the transition times. > YCM>> As of now, we do not have requirements on the transition times > from a power state to another state. > > Merely describing power states in not enough as energy savings in > reduced power states must be necessarily weighted against the drawbacks. > > YCM>> The energy management standard provides the data and I would think > the network manager should make the trade-offs from the information ? > > -- > Daniel Kharitonov > Juniper Networks Inc > 1194 N Mathilda Ave > Sunnyvale CA > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman >
- [eman] Feedback on draft-ietf-eman-requirements-05 Daniel Kharitonov
- Re: [eman] Feedback on draft-ietf-eman-requiremen… Mouli Chandramouli (moulchan)
- Re: [eman] Feedback on draft-ietf-eman-requiremen… Ira McDonald
- Re: [eman] Feedback on draft-ietf-eman-requiremen… Daniel Kharitonov
- Re: [eman] Feedback on draft-ietf-eman-requiremen… Benoit Claise
- Re: [eman] Feedback on draft-ietf-eman-requiremen… Daniel Kharitonov
- Re: [eman] Feedback on draft-ietf-eman-requiremen… Benoit Claise
- Re: [eman] Feedback on draft-ietf-eman-requiremen… Daniel Kharitonov