Re: [eman] two questions to draft-claise-power-management-arch-02 draft

Brad Schoening <bschoening@noveda.com> Wed, 18 May 2011 02:38 UTC

Return-Path: <bschoening@noveda.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 E891DE06F0 for <eman@ietfa.amsl.com>; Tue, 17 May 2011 19:38:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.653
X-Spam-Level:
X-Spam-Status: No, score=0.653 tagged_above=-999 required=5 tests=[AWL=-3.252, BAYES_00=-2.599, HTML_MESSAGE=0.001, MANGLED_SAVELE=2.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r471Qo2F5ZFA for <eman@ietfa.amsl.com>; Tue, 17 May 2011 19:38:45 -0700 (PDT)
Received: from cal3-mh481-a.smtproutes.com (cal3-mh481-a.smtproutes.com [208.70.89.235]) by ietfa.amsl.com (Postfix) with ESMTP id DACCFE0696 for <eman@ietf.org>; Tue, 17 May 2011 19:38:44 -0700 (PDT)
X-Katharion-ID: 1305686304.29619.cal3-mh481
Received: from ex01.noveda.com ([66.198.105.170]) by cal3-mh481.smtproutes.com [(208.70.89.155)] with ESMTP via TCP; 17 May 2011 19:38:24 -0700
Received: from EX01.noveda.com ([::1]) by ex01.noveda.com ([::1]) with mapi; Tue, 17 May 2011 22:38:23 -0400
From: Brad Schoening <bschoening@noveda.com>
To: Duanxiaoling <duanxiaoling@huawei.com>, "bclaise@cisco.com" <bclaise@cisco.com>
Thread-Topic: [eman] two questions to draft-claise-power-management-arch-02 draft
Thread-Index: AQHMEEGPY+x/sA54z0abzWr6eayCaJSJrbsAgAh0WQD//8EdoA==
Date: Wed, 18 May 2011 02:38:21 +0000
Message-ID: <22B2909DCC2E62418BE369A1F104889937A033BA@ex01.noveda.com>
References: <A6503E69A5D367479F35DE23AAD2377907901932@szxeml509-mbx.china.huawei.com> <22B2909DCC2E62418BE369A1F104889937A00FA0@ex01.noveda.com> <A6503E69A5D367479F35DE23AAD237790790597B@szxeml509-mbx.china.huawei.com>
In-Reply-To: <A6503E69A5D367479F35DE23AAD237790790597B@szxeml509-mbx.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_22B2909DCC2E62418BE369A1F104889937A033BAex01novedacom_"
MIME-Version: 1.0
Cc: eman mailing list <eman@ietf.org>
Subject: Re: [eman] two questions to draft-claise-power-management-arch-02 draft
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: Wed, 18 May 2011 02:38:46 -0000

The power levels are designed to be sparse.   So, your platform can implement those EMAN levels 1..12 which made sense for it.  Figure 6 of the EMAN Framework v-01 gives an example of this mapping to a device supporting four fictitious power states:

              Power State / Name       Manufacturer Power State / Name
               1 / Mech Off             0 / none
               2 / Soft Off             0 / none
               3 / Hibernate            0 / none
               4 / Sleep, Save-to-RAM   0 / none
               5 / Standby              0 / none
               6 / Ready                1 / short
               7 / LowMinus             1 / short
               8 / Low                  1 / short
               9 / MediumMinus          2 / tall
               10 / Medium              2 / tall
               11 / HighMinus           3 / grande
               12 / High                4 / venti

                          Figure 6: Mapping Example 3

This is similar to the DMTF and ACPI models which define many states, but devices are not required to implement them all.

Reference:

http://tools.ietf.org/html/draft-ietf-eman-framework-01

From: Duanxiaoling [mailto:duanxiaoling@huawei.com]
Sent: Tuesday, May 17, 2011 10:03 PM
To: Brad Schoening; bclaise@cisco.com
Cc: eman mailing list
Subject: Re: [eman] two questions to draft-claise-power-management-arch-02 draft


Thanks for your answer!

I recognize that other protocols besides SNMP are not in our scope from your answer.

But how about the second question? Would you like to give us an answer?



Thanks!




best regards!
notes:duanxiaoling 00160662@notesmail.huawei.com
Phone number:13751010110
******************************************************************************************
 This email and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
 *****************************************************************************************

________________________________
发件人: Brad Schoening [bschoening@noveda.com]
发送时间: 2011年5月13日 5:18
到: Duanxiaoling; bclaise@cisco.com
Cc: eman mailing list
主题: RE: [eman] two questions to draft-claise-power-management-arch-02 draft
Yes, the EMAN data model uses the Simple Network Management Protocol (SNMP).  Our draft management information base (MIB) inherits data types and textual conventions from the SNMP standard.  It’s not really adaptable to other protocols that don’t support SNMP data types.

There is no standard data format for FTP, hence its not useful by itself as a data transfer protocol without another layer of interpretation such as an XML schema or CSV format.  As for the other protocols you mention, they seem to be domain specific, but I’m not familiar with them.

Regards,

Brad Schoening

From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of Duanxiaoling
Sent: Wednesday, May 11, 2011 9:35 PM
To: bclaise@cisco.com
Cc: eman mailing list
Subject: [eman] two questions to draft-claise-power-management-arch-02 draft


1,The protocol between NMS and device is SNMP, but how about other protocol, such as FTP, TL1 or Qx ?  Is these protocol prohibited  or out of eman's scope?  Now lots of SDH, MSTP devices is managed by NMS in protocol Qx or TL1. Also, lots of core network device is  managed by NMS in protocol MML, and so on.  Will our draft fit for these devices(wireless device, core network device, transfer device )?

2,The power level is defind in the draft is [0...12], how will we use it? All device must have all the power level? or different NE can select different part of them. For example, A can select [0...7], B can select [8,10,12], and so on.



How about other memeber's thought?


best regards!
email:duanxiaoling@huawei.com
Phone number:+086-0755-13751010110
******************************************************************************************
 This email and its attachments contain confidential information from HUAWEI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!
 *****************************************************************************************