Re: [eman] Way forward for EMAN Framework
Nevil Brownlee <n.brownlee@auckland.ac.nz> Thu, 03 October 2013 21:14 UTC
Return-Path: <n.brownlee@auckland.ac.nz>
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 D296621E80C0 for <eman@ietfa.amsl.com>; Thu, 3 Oct 2013 14:14:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 ukiZxI9RICWs for <eman@ietfa.amsl.com>; Thu, 3 Oct 2013 14:14:16 -0700 (PDT)
Received: from mx2.auckland.ac.nz (mx2.auckland.ac.nz [130.216.125.245]) by ietfa.amsl.com (Postfix) with ESMTP id 7D36321F9425 for <eman@ietf.org>; Thu, 3 Oct 2013 14:02:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=uoa; t=1380834177; x=1412370177; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=gsX1ETep5WNpBeh+6N+v5H6rcjwgh1WSpKKP4hcXVlc=; b=W8ss/kHOr1RpzS/qJVEvpinNTEuFCWy1+oaIT6EdbWE8dStpRBxkOzwI JDawfgzkuf7EOiPv/qwu6+OttfLQ+vdgepykplAFA4Y2Iyq5uARYJWavy HzsOspWpg0pTEPc4YKc7LkRtf53E2hJFWs9vluEdQQeTjrHe5TVRO9izv 8=;
X-IronPort-AV: E=Sophos;i="4.90,1028,1371038400"; d="scan'208";a="215779982"
X-Ironport-HAT: UNIVERSITY - $RELAY-THROTTLE
X-Ironport-Source: 130.216.38.131 - Outgoing - Outgoing-SSL
Received: from nevil-laptop1.sfac.auckland.ac.nz (HELO [130.216.38.131]) ([130.216.38.131]) by mx2-int.auckland.ac.nz with ESMTP; 04 Oct 2013 10:02:55 +1300
Message-ID: <524DDB7E.1030105@auckland.ac.nz>
Date: Fri, 04 Oct 2013 10:02:54 +1300
From: Nevil Brownlee <n.brownlee@auckland.ac.nz>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Bruce Nordman <bnordman@lbl.gov>
References: <CAK+eDP824y7W5h4=RFsqdKZ=P1r5smy8kffrM=i3MDE+WiOVUA@mail.gmail.com> <C6C6EB33-0275-4AD7-B5BC-C4F2E871FBE9@juniper.net>
In-Reply-To: <C6C6EB33-0275-4AD7-B5BC-C4F2E871FBE9@juniper.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: eman mailing list <eman@ietf.org>, Ted Ghose <tghose@juniper.net>
Subject: Re: [eman] Way forward for EMAN Framework
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, 03 Oct 2013 21:14:27 -0000
Hi Bruce: It's good to see some useful feedback from the Framework draft's WGLC, especially feedback that includes suggestions for improved text. However, the notion of "starting again" is unhelpful. Let me remind you of what the EMAN WG's charter says about the framework: 2. Energy management framework. The EMAN WG will create a framework document that will describe extensions to current management framework, required for energy management. This includes: power and energy monitoring, power states, power state control, and potential power state transitions. The framework will focus on energy management for IP-based network equipment (routers, switches, PCs, IP cameras, phones and the like). Particularly, the relationships between reporting devices, remote devices, and monitoring probes (such as might be used in low-power and lossy networks) need to be elaborated. For the case of a device reporting on behalf of other devices and controlling those devices, the framework will address the issues of discovery and identification of remote devices. That is, the WG focus is on extending Network Management to work effectively for network devices - and that's what the current draft, after three years of work, adresses. Cheers, Nevil (EMAN co-chair) On 3/10/13 1:18 PM, Ted Ghose wrote: > Why not fix the existing one rather starting a discussion on a new draft? Something I missed? > > Thanks > > -tg- > Sent from my iPhone > > On Oct 2, 2013, at 3:15 PM, Bruce Nordman <bnordman@lbl.gov<mailto:bnordman@lbl.gov>> wrote: > > As my previous email noted, and as per Juergen Quittek's recent review > http://www.ietf.org/mail-archive/web/eman/current/msg02007.html > there are still many many outstanding problems with the > current Framework draft. This draft has been out for consideration > and evolving for over three years, so having so many outstanding > problems is troubling. The the pace of improvement over these > years has been quite slow. It seems unlikely that continuing on > the process of trying to fix this document will lead to it being > suitable as an RFC in a reasonable timeframe. It would be better > to produce no result than to produce a substandard one. > > That said, there are alternatives. One good one is to use the > "Energy Reporting (ER) Framework" -- draft-nordman-eman-er-framework-01 > -- as the basis for the framework work item from EMAN. A key next > step is for that draft to receive critical review by EMAN participants > to directly compare it to the current EMAN Framework draft. This > would productively move EMAN forward. > > My assessment of the two is that the ER Framework: > * Is simpler to read and understand - for a variety of audiences > * Will be simpler to implement (for end devices and management systems) > * Lacks many ambiguities present in the EMAN Framework > * More fully and directly implements the EMAN Requirements > * Has features and capabilities not in the EMAN Framework > These all make it more suitable as an RFC and more likely to be > successful as a standard. > > EMAN is not the only organization considering energy management > data models and so to be successful will need to be clearly superior > to alternatives. > > I look forward to more detailed and productive discussion on the list. > Thank you, > > --Bruce > > > -- > Bruce Nordman > Lawrence Berkeley National Laboratory > nordman.lbl.gov<http://nordman.lbl.gov> > BNordman@LBL.gov<mailto:BNordman@LBL.gov> > 510-486-7089 > m: 510-501-7943 > _______________________________________________ > eman mailing list > eman@ietf.org<mailto:eman@ietf.org> > https://www.ietf.org/mailman/listinfo/eman > > > > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman > -- --------------------------------------------------------------------- Nevil Brownlee Computer Science Department Phone: +64 9 373 7599 x88941 The University of Auckland FAX: +64 9 373 7453 Private Bag 92019, Auckland 1142, New Zealand
- [eman] Way forward for EMAN Framework Bruce Nordman
- Re: [eman] Way forward for EMAN Framework Ted Ghose
- Re: [eman] Way forward for EMAN Framework Nevil Brownlee