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

Benoit Claise <bclaise@cisco.com> Tue, 24 May 2011 08:20 UTC

Return-Path: <bclaise@cisco.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 0F194E0716 for <eman@ietfa.amsl.com>; Tue, 24 May 2011 01:20:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.558
X-Spam-Level:
X-Spam-Status: No, score=-1.558 tagged_above=-999 required=5 tests=[AWL=1.040, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 keq8s+XpW506 for <eman@ietfa.amsl.com>; Tue, 24 May 2011 01:20:08 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id 28A33E0703 for <eman@ietf.org>; Tue, 24 May 2011 01:20:08 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p4O7xltY027786; Tue, 24 May 2011 09:59:47 +0200 (CEST)
Received: from [10.55.43.53] (ams-bclaise-8714.cisco.com [10.55.43.53]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id p4O7xlMI001825; Tue, 24 May 2011 09:59:47 +0200 (CEST)
Message-ID: <4DDB6573.6030800@cisco.com>
Date: Tue, 24 May 2011 09:59:47 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Duanxiaoling <duanxiaoling@huawei.com>
References: <A6503E69A5D367479F35DE23AAD2377907901932@szxeml509-mbx.china.huawei.com>
In-Reply-To: <A6503E69A5D367479F35DE23AAD2377907901932@szxeml509-mbx.china.huawei.com>
Content-Type: multipart/alternative; boundary="------------010506020502000308020002"
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: Tue, 24 May 2011 08:20:09 -0000

Hi,

Please comment on the official EMAN document, i.e.
http://tools.ietf.org/html/draft-ietf-eman-framework-01
draft-claise-power-management-arch-02 draft is old.
Let me addresse your questions below
>
> 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 )?
>
The decision for the WG was to create MIB modules, to be used with SNMP.
However, if we do our job right in terms of information modelling,
multiple data models could be deduced from it.
Reference: RFC3444
>
> 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.
>
Yes, EMAN doesn't impose that you support all power states.

Regards, Benoit
>
> 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!
> *****************************************************************************************
>
>