Re: [eman] Read-Only or Read-Write EMAN MIBs
"David Prantl" <david@prantl.name> Mon, 17 February 2014 08:42 UTC
Return-Path: <david@prantl.name>
X-Original-To: eman@ietfa.amsl.com
Delivered-To: eman@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65F641A011B for <eman@ietfa.amsl.com>; Mon, 17 Feb 2014 00:42:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level:
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qbwJ5uzBadS4 for <eman@ietfa.amsl.com>; Mon, 17 Feb 2014 00:42:50 -0800 (PST)
Received: from mailgw1.uni-kl.de (mailgw1.uni-kl.de [IPv6:2001:638:208:120::220]) by ietfa.amsl.com (Postfix) with ESMTP id 264D51A00BE for <eman@ietf.org>; Mon, 17 Feb 2014 00:42:49 -0800 (PST)
Received: from t530shadow (p549C40ED.dip0.t-ipconnect.de [84.156.64.237]) (authenticated bits=0) by mailgw1.uni-kl.de (8.14.3/8.14.3/Debian-9.4) with ESMTP id s1H8giZ3010572 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 17 Feb 2014 09:42:45 +0100
From: David Prantl <david@prantl.name>
To: 'Thomas Nadeau' <tnadeau@lucidvision.com>, 'eman mailing list' <eman@ietf.org>
References: <88A474D1-677D-4BA0-8399-0429A095AE45@lucidvision.com>
In-Reply-To: <88A474D1-677D-4BA0-8399-0429A095AE45@lucidvision.com>
Date: Mon, 17 Feb 2014 09:42:45 +0100
Message-ID: <001801cf2bbc$3b43f870$b1cbe950$@prantl.name>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHC6u7uBAKsxvXaYoAFJCbQSShBjJrRolsw
Content-Language: de
Archived-At: http://mailarchive.ietf.org/arch/msg/eman/vSOtCMFXF8UK-JQNUVkbKChEGd0
Subject: Re: [eman] Read-Only or Read-Write EMAN MIBs
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 17 Feb 2014 08:42:52 -0000
Hi, Currently the Cisco Energywise Manager/Joulex Energy Manager only has been used with read-only implementations of the EMAN-MIB. Thanks Mouli -----Original Message----- From: eman [mailto:eman-bounces@ietf.org] On Behalf Of Thomas Nadeau Sent: Dienstag, 11. Februar 2014 17:03 To: eman mailing list Subject: [eman] Read-Only or Read-Write EMAN MIBs EMAN WG: The EMAN WG currently has three MIBs that are WG drafts: draft-ietf-eman-battery-mib-11 draft-ietf-eman-energy-aware-mib-14 draft-ietf-eman-energy-monitoring-mib-08 At present Benoit as AD, the Ops Directorate and MIB Doctors are preparing a statement to WGs that strongly recommends against MIBs with writable objects unless the working group has a strong consensus to do so. The current *draft* of the statement is listed here for your information: The OPS area recommends the use of NETCONF/YANG standards for configuration. IETF working groups are therefore encouraged to use the NETCONF/YANG standards for configuration, specifically in new charters. SNMP MIB modules modifying persistent configuration state should only be produced by working groups in cases of clear utility and overwhelming consensus to use SNMP write operations for configuration. In an effort to head off any potential snafus during the IESG review of the three EMAN MIBs, I want to poll the WG for consensus on whether or not to make the current list of WG documents read-write or read-only. If there is not strong consensus to leave them read-write, Nevil and I will instruct the editors to edit the documents to remove writable objects. Please post comments on this matter by Friday, February 14, 2014 at 9AM EDT. Tom EMAN WG Co-Chair
- [eman] Read-Only or Read-Write EMAN MIBs Thomas Nadeau
- Re: [eman] Read-Only or Read-Write EMAN MIBs Romascanu, Dan (Dan)
- Re: [eman] Read-Only or Read-Write EMAN MIBs Juergen Schoenwaelder
- Re: [eman] Read-Only or Read-Write EMAN MIBs Romascanu, Dan (Dan)
- Re: [eman] Read-Only or Read-Write EMAN MIBs Juergen Schoenwaelder
- Re: [eman] Read-Only or Read-Write EMAN MIBs Thomas Nadeau
- Re: [eman] Read-Only or Read-Write EMAN MIBs Thomas Nadeau
- Re: [eman] Read-Only or Read-Write EMAN MIBs Juergen Schoenwaelder
- Re: [eman] Read-Only or Read-Write EMAN MIBs Thomas Nadeau
- Re: [eman] Read-Only or Read-Write EMAN MIBs Bruce Nordman
- Re: [eman] Read-Only or Read-Write EMAN MIBs Mouli Chandramouli (moulchan)
- Re: [eman] Read-Only or Read-Write EMAN MIBs David Prantl
- Re: [eman] Read-Only or Read-Write EMAN MIBs Romascanu, Dan (Dan)
- Re: [eman] Read-Only or Read-Write EMAN MIBs Juergen Schoenwaelder
- Re: [eman] Read-Only or Read-Write EMAN MIBs Romascanu, Dan (Dan)
- Re: [eman] Read-Only or Read-Write EMAN MIBs Thomas D. Nadeau
- Re: [eman] Read-Only or Read-Write EMAN MIBs John Parello (jparello)