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

Duanxiaoling <duanxiaoling@huawei.com> Thu, 12 May 2011 01:35 UTC

Return-Path: <duanxiaoling@huawei.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 1DBA2E08A4 for <eman@ietfa.amsl.com>; Wed, 11 May 2011 18:35:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
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 Kds7RnNtGpTg for <eman@ietfa.amsl.com>; Wed, 11 May 2011 18:35:29 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id 6D4B9E0873 for <eman@ietf.org>; Wed, 11 May 2011 18:35:29 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LL200B9Y73419@szxga04-in.huawei.com> for eman@ietf.org; Thu, 12 May 2011 09:35:28 +0800 (CST)
Received: from szxeml202-edg.china.huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LL200BH2734P8@szxga04-in.huawei.com> for eman@ietf.org; Thu, 12 May 2011 09:35:28 +0800 (CST)
Received: from SZXEML404-HUB.china.huawei.com (10.82.67.59) by szxeml202-edg.china.huawei.com (172.24.2.42) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 12 May 2011 09:35:19 +0800
Received: from SZXEML509-MBX.china.huawei.com ([169.254.9.178]) by szxeml404-hub.china.huawei.com ([fe80::75b7:3db9:fedc:a56d%13]) with mapi id 14.01.0270.001; Thu, 12 May 2011 09:35:28 +0800
Date: Thu, 12 May 2011 01:35:26 +0000
From: Duanxiaoling <duanxiaoling@huawei.com>
X-Originating-IP: [10.70.38.155]
To: "bclaise@cisco.com" <bclaise@cisco.com>
Message-id: <A6503E69A5D367479F35DE23AAD2377907901932@szxeml509-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_5mw+Ywd9N/seb1S9nbsphQ)"
Content-language: zh-CN
Accept-Language: zh-CN, en-US
Thread-topic: two questions to draft-claise-power-management-arch-02 draft
Thread-index: AQHMEEGPY+x/sA54z0abzWr6eayCaA==
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Cc: eman mailing list <eman@ietf.org>
Subject: [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: Thu, 12 May 2011 01:35:30 -0000

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!
 *****************************************************************************************