From internet-drafts@ietf.org Tue Feb 12 03:26:22 2013 Return-Path: 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 3143321F8CE8; Tue, 12 Feb 2013 03:26:22 -0800 (PST) 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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NCie1AYWw1bx; Tue, 12 Feb 2013 03:26:21 -0800 (PST) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7939521F8D00; Tue, 12 Feb 2013 03:26:21 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.37 Message-ID: <20130212112621.12992.45020.idtracker@ietfa.amsl.com> Date: Tue, 12 Feb 2013 03:26:21 -0800 Cc: eman@ietf.org Subject: [eman] I-D Action: draft-ietf-eman-rfc4133bis-06.txt X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2013 11:26:22 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Energy Management Working Group of the IE= TF. Title : Entity MIB (Version 4) Author(s) : Andy Bierman Dan Romascanu Juergen Quittek Mouli Chandramouli Filename : draft-ietf-eman-rfc4133bis-06.txt Pages : 76 Date : 2013-02-12 Abstract: This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing multiple logical and physical entities managed by a single SNMP agent. This document specifies version 4 of the Entity MIB. This memo obsoletes version 3 of Entity MIB module published as RFC 4133. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-eman-rfc4133bis There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-eman-rfc4133bis-06 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eman-rfc4133bis-06 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From moulchan@cisco.com Tue Feb 12 03:31:12 2013 Return-Path: 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 D6F2A21F8D17 for ; Tue, 12 Feb 2013 03:31:12 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 4NZo9ER-9Ttp for ; Tue, 12 Feb 2013 03:31:12 -0800 (PST) Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 0187621F8D15 for ; Tue, 12 Feb 2013 03:31:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2059; q=dns/txt; s=iport; t=1360668672; x=1361878272; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=t0+oTvOKaBMTsyKX4ZIiJkLINRDIbOq4aGLkleCmlxA=; b=lWl2w76jH5CfBS1+IkI/vVnwuQyijLZ4xl+w21d23fg6H4F6IZziXk5L FEztEjv9JQO6O7napco4HshiUHGLXevp59OtmHj8kEyU1/RgAXjdm96TJ Xvi0GzI18dMR7e8QM29B9vC4UU1xVrCQ7zwbvpwLb23kngKplHFgEZje1 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgEFAGgnGlGtJV2Z/2dsb2JhbABEg3m9OhZzgh8BAQEEAQEBNzQXBAIBCBEEAQELFAkHJwsUCQgCBBMIAQuHfgcFrw2QDZEmYQOXQY82gwaCJw X-IronPort-AV: E=Sophos;i="4.84,648,1355097600"; d="scan'208";a="176122718" Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-5.cisco.com with ESMTP; 12 Feb 2013 11:31:11 +0000 Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r1CBVB1O031678 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Tue, 12 Feb 2013 11:31:11 GMT Received: from xmb-rcd-x08.cisco.com ([169.254.8.192]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.02.0318.004; Tue, 12 Feb 2013 05:31:11 -0600 From: "Mouli Chandramouli (moulchan)" To: "eman@ietf.org" Thread-Topic: [eman] I-D Action: draft-ietf-eman-rfc4133bis-06.txt Thread-Index: AQHOCRPKzfYZLWTFb0WYDCMvM/yHN5h2FZKg Date: Tue, 12 Feb 2013 11:31:10 +0000 Message-ID: <852AF0ED49D9F24BBBFA1B4DEEBE3BA4286BA0FB@xmb-rcd-x08.cisco.com> References: <20130212112621.12992.45020.idtracker@ietfa.amsl.com> In-Reply-To: <20130212112621.12992.45020.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.142.100.140] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [eman] I-D Action: draft-ietf-eman-rfc4133bis-06.txt X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2013 11:31:13 -0000 Hello all,=20 An updated version of the draft has been submitted based on an extensive MI= B-DOCTOR review by Juergen Schoenwaelder and the AD review.=20 Thanks for the comment from Scott Bradner and it has been addressed in this= version.=20 Thanks=20 Dan, Juergen, Andy and Mouli=20 -----Original Message----- From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of int= ernet-drafts@ietf.org Sent: Tuesday, February 12, 2013 4:56 PM To: i-d-announce@ietf.org Cc: eman@ietf.org Subject: [eman] I-D Action: draft-ietf-eman-rfc4133bis-06.txt A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Energy Management Working Group of the IE= TF. Title : Entity MIB (Version 4) Author(s) : Andy Bierman Dan Romascanu Juergen Quittek Mouli Chandramouli Filename : draft-ietf-eman-rfc4133bis-06.txt Pages : 76 Date : 2013-02-12 Abstract: This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing multiple logical and physical entities managed by a single SNMP agent. This document specifies version 4 of the Entity MIB. This memo obsoletes version 3 of Entity MIB module published as RFC 4133. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-eman-rfc4133bis There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-eman-rfc4133bis-06 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eman-rfc4133bis-06 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ eman mailing list eman@ietf.org https://www.ietf.org/mailman/listinfo/eman From trac+eman@trac.tools.ietf.org Tue Feb 12 15:08:08 2013 Return-Path: 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 7D4CA21F8A6F for ; Tue, 12 Feb 2013 15:08:08 -0800 (PST) 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 ppuFNcX5nGNs for ; Tue, 12 Feb 2013 15:08:07 -0800 (PST) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id A200D21F8A6C for ; Tue, 12 Feb 2013 15:08:06 -0800 (PST) Received: from localhost ([127.0.0.1]:52607 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1U5OxA-0006jP-HY; Wed, 13 Feb 2013 00:07:56 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "eman issue tracker" X-Trac-Version: 0.12.3 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.3, by Edgewall Software To: bnordman@lbl.gov, n.brownlee@auckland.ac.nz, jparello@cisco.com X-Trac-Project: eman Date: Tue, 12 Feb 2013 23:07:56 -0000 X-URL: http://tools.ietf.org/eman/ X-Trac-Ticket-URL: http://tools.ietf.org/wg/eman/trac/ticket/21#comment:7 Message-ID: <079.70f2c5b5c848248b97650b2db9dcb636@trac.tools.ietf.org> References: <064.71cdaa9804b4d5542ef8cf6433ee0054@trac.tools.ietf.org> X-Trac-Ticket-ID: 21 In-Reply-To: <064.71cdaa9804b4d5542ef8cf6433ee0054@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: bnordman@lbl.gov, n.brownlee@auckland.ac.nz, jparello@cisco.com, eman@ietf.org X-SA-Exim-Mail-From: trac+eman@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: eman@ietf.org Subject: Re: [eman] #21: h. Clarify the intended application of the Domain concept? X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2013 23:08:08 -0000 #21: h. Clarify the intended application of the Domain concept? Comment (by jparello@cisco.com): propose to close this has been done an we are on v14. -- ---------------------------------------+------------------------------- Reporter: n.brownlee@auckland.ac.nz | Owner: bnordman@lbl.gov Type: defect | Status: new Priority: minor | Milestone: milestone1 Component: framework | Version: 1.0 Severity: - | Resolution: Keywords: | ---------------------------------------+------------------------------- Ticket URL: eman From trac+eman@trac.tools.ietf.org Tue Feb 12 15:08:49 2013 Return-Path: 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 4303021F8A6F for ; Tue, 12 Feb 2013 15:08:49 -0800 (PST) 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 7vczo6mJfNOf for ; Tue, 12 Feb 2013 15:08:48 -0800 (PST) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id B61B121F8A6C for ; Tue, 12 Feb 2013 15:08:48 -0800 (PST) Received: from localhost ([127.0.0.1]:52619 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1U5Oxx-00041p-TU; Wed, 13 Feb 2013 00:08:45 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "eman issue tracker" X-Trac-Version: 0.12.3 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.3, by Edgewall Software To: bclaise@cisco.com, jparello@cisco.com, n.brownlee@auckland.ac.nz X-Trac-Project: eman Date: Tue, 12 Feb 2013 23:08:45 -0000 X-URL: http://tools.ietf.org/eman/ X-Trac-Ticket-URL: http://tools.ietf.org/wg/eman/trac/ticket/17#comment:6 Message-ID: <079.69bbaa19feb02ed452bea05f2f6ff26b@trac.tools.ietf.org> References: <064.056e9f519f85063bc7514e0a8142259d@trac.tools.ietf.org> X-Trac-Ticket-ID: 17 In-Reply-To: <064.056e9f519f85063bc7514e0a8142259d@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: bclaise@cisco.com, jparello@cisco.com, n.brownlee@auckland.ac.nz, eman@ietf.org X-SA-Exim-Mail-From: trac+eman@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Cc: eman@ietf.org Subject: Re: [eman] #17: d. Is aggregation a relationship, or just a function? X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2013 23:08:49 -0000 #17: d. Is aggregation a relationship, or just a function? Comment (by jparello@cisco.com): propose to close - incorporated in draft -- ---------------------------------------+-------------------------------- Reporter: n.brownlee@auckland.ac.nz | Owner: bclaise@cisco.com Type: defect | Status: new Priority: minor | Milestone: milestone1 Component: framework | Version: 1.0 Severity: - | Resolution: Keywords: | ---------------------------------------+-------------------------------- Ticket URL: eman From trac+eman@trac.tools.ietf.org Tue Feb 12 17:25:00 2013 Return-Path: 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 3854C21F8692 for ; Tue, 12 Feb 2013 17:25:00 -0800 (PST) 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 OYlKnrbFG+12 for ; Tue, 12 Feb 2013 17:24:59 -0800 (PST) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id B9C8021F8689 for ; Tue, 12 Feb 2013 17:24:56 -0800 (PST) Received: from localhost ([127.0.0.1]:37271 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1U5R5Y-00026V-N8; Wed, 13 Feb 2013 02:24:44 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "eman issue tracker" X-Trac-Version: 0.12.3 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.3, by Edgewall Software To: draft-ietf-eman-applicability-statement@tools.ietf.org, jparello@cisco.com X-Trac-Project: eman Date: Wed, 13 Feb 2013 01:24:44 -0000 X-URL: http://tools.ietf.org/eman/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/eman/trac/ticket/28 Message-ID: <057.dbd6944b8f5806e048437d9d1a1d8708@trac.tools.ietf.org> X-Trac-Ticket-ID: 28 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-eman-applicability-statement@tools.ietf.org, jparello@cisco.com, eman@ietf.org X-SA-Exim-Mail-From: trac+eman@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: bnordman@lbl.gov, brad.schoening@verizon.net, moulchan@cisco.com Resent-Message-Id: <20130213012458.B9C8021F8689@ietfa.amsl.com> Resent-Date: Tue, 12 Feb 2013 17:24:56 -0800 (PST) Resent-From: trac+eman@trac.tools.ietf.org Cc: eman@ietf.org Subject: [eman] #28: Ensure information in deleted section req and use cases in other documents X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Feb 2013 01:25:00 -0000 #28: Ensure information in deleted section req and use cases in other documents From last framework authors call section 3 (req and use cases) proposed to be deleted. Deleted it form current rev but including the text here. IF this section is not needed then the use cases and requirements need to be checked in other drafts so we don't lose information. -- -------------------------+------------------------------------------------- Reporter: | Owner: draft-ietf-eman-applicability- jparello@cisco.com | statement@tools.ietf.org Type: defect | Status: new Priority: major | Milestone: Component: | Version: applicability- | Keywords: statement | Severity: - | -------------------------+------------------------------------------------- Ticket URL: eman From trac+eman@trac.tools.ietf.org Wed Feb 13 10:47:24 2013 Return-Path: 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 5479D21E8041 for ; Wed, 13 Feb 2013 10:47:24 -0800 (PST) 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=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 zFH7Z64Rtiyl for ; Wed, 13 Feb 2013 10:47:22 -0800 (PST) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 960FD21E8034 for ; Wed, 13 Feb 2013 10:47:19 -0800 (PST) Received: from localhost ([127.0.0.1]:51307 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1U5hMO-0000sC-A9; Wed, 13 Feb 2013 19:47:12 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "eman issue tracker" X-Trac-Version: 0.12.3 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.3, by Edgewall Software To: draft-ietf-eman-applicability-statement@tools.ietf.org, jparello@cisco.com X-Trac-Project: eman Date: Wed, 13 Feb 2013 18:47:12 -0000 X-URL: http://tools.ietf.org/eman/ X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/eman/trac/ticket/28#comment:1 Message-ID: <072.40f509660bb866ad5040e5c5d6213306@trac.tools.ietf.org> References: <057.dbd6944b8f5806e048437d9d1a1d8708@trac.tools.ietf.org> X-Trac-Ticket-ID: 28 In-Reply-To: <057.dbd6944b8f5806e048437d9d1a1d8708@trac.tools.ietf.org> X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-eman-applicability-statement@tools.ietf.org, jparello@cisco.com, eman@ietf.org X-SA-Exim-Mail-From: trac+eman@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: bnordman@lbl.gov, brad.schoening@verizon.net, moulchan@cisco.com Resent-Message-Id: <20130213184722.960FD21E8034@ietfa.amsl.com> Resent-Date: Wed, 13 Feb 2013 10:47:19 -0800 (PST) Resent-From: trac+eman@trac.tools.ietf.org Cc: eman@ietf.org Subject: Re: [eman] #28: Ensure information in deleted section req and use cases in other documents X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Feb 2013 18:47:24 -0000 #28: Ensure information in deleted section req and use cases in other documents Comment (by jparello@cisco.com): from meeting bruce, brad, jq, can you check against you other drafts then close. -- -------------------------+------------------------------------------------- Reporter: | Owner: draft-ietf-eman-applicability- jparello@cisco.com | statement@tools.ietf.org Type: defect | Status: new Priority: major | Milestone: Component: | Version: applicability- | Resolution: statement | Severity: - | Keywords: | -------------------------+------------------------------------------------- Ticket URL: eman From luchuk@snmp.com Wed Feb 13 13:38:33 2013 Return-Path: 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 7A18E21F8578 for ; Wed, 13 Feb 2013 13:38:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] 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 duCFAszhuQVH for ; Wed, 13 Feb 2013 13:38:32 -0800 (PST) Received: from mailbox.snmp.com (mailbox.snmp.com [192.147.142.80]) by ietfa.amsl.com (Postfix) with ESMTP id 0EF4821F8598 for ; Wed, 13 Feb 2013 13:38:31 -0800 (PST) Received: from adminfs.snmp.com (adminfs.snmp.com [192.147.142.39]) by mailbox.snmp.com (8.9.3p2-20030922/m.0080228) with ESMTP id QAA25600; Wed, 13 Feb 2013 16:38:28 -0500 (EST) Received: (from luchuk@localhost) by adminfs.snmp.com (8.9.3p2-20030922/snmpclient.mc-990525) id QAA16717; Wed, 13 Feb 2013 16:38:27 -0500 (EST) Date: Wed, 13 Feb 2013 16:38:27 -0500 (EST) From: Alan Luchuk Message-Id: <201302132138.QAA16717@adminfs.snmp.com> To: eman@ietf.org X-Mailman-Approved-At: Thu, 14 Feb 2013 16:59:10 -0800 Cc: luchuk@snmp.com Subject: [eman] Review of draft-ietf-eman-battery-mib-07 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Feb 2013 21:38:33 -0000 Hello, I'm trying to work my way through the Energy Management documents and review the MIBs, so I started with the easiest one, the BATTERY-MIB. Overall, it is clear that much work has been put into the all of the Energy Management WG documents. Draft-ietf-eman-battery-mib-07 is in generally good shape. I've organized the comments in descending order by severity. The comments are in broad categories of "PROBLEMS", "ERRORS", "SPELLING ERRORS", "TECHNICAL COMMENTS", "CLARIFICATIONS", and finally "WORDING". I think the PROBLEMS, ERRORS, and SPELLING ERRORS should be addressed, and are quick to fix. It would be good to look at the TECHNICAL COMMENTS and CLARIFICATIONS sections and incorporate the suggestions if appropriate. In many cases, the comments in the WORDING section are matters of personal preference, and can safely be ignored or discarded. Hope these are of use to the working group. Regards, --Alan PROBLEMS -------- Page 10 ------- batteryActualCharge Unsigned64, Unsigned64 is not a valid SMIv2 type. Page 17, batteryActualCharge ---------------------------- SYNTAX Unsigned64 Unsigned64 is not a valid SMIv2 type. Page 20, batteryAlarmLowTemperature DESCRIPTION ----------------------------------------------- s/batteryTemperature rises above this/batteryTemperature falls below this/ Page 22, batteryCompliance DESCRIPTION -------------------------------------- s/POWER-STATE-MIB/BATTERY-MIB/ ERRORS ------ Page 8 ------ LAST-UPDATED "201106261200Z" -- 26 june 2010 The LAST-UPDATED date does not match the comment. Page 9 ------ REVISION "201106261200Z" -- 26 June 2010 The REVISION date does not match the comment. SPELLING ERRORS --------------- Page 19, batteryAlarmHighCycleCount DESCRIPTION ----------------------------------------------- s/batteryAgingtNotification/batteryAgingNotification/ ^ Page 25, Paragraph under batteryAlarmLowCapacity and batteryAlarmHighCycleCount ------------------------------------------------------------------------------- s/and potentially loose data/and potentially lose data/ TECHNICAL COMMENTS ------------------ Page 11, batteryIdentifier -------------------------- The description clause for the batteryIdentifier suggests it is used like a serial number. Would it make sense to add an object that is the battery model number? The battery model number would allow the lookup of the battery characteristics, and the battery serial number would allow the battery to be traced if the battery is moved. If another object is added for the battery model number, would the object names "batteryModelNumber" and "batterySerialNumber" make better sense? Would it make sense that the "batteryModelNumber" is an OID, or something derived from an OID? CLARIFICATIONS -------------- Page 4, Paragraph 2 ------------------- s/motherboard to run the clock/motherboard to run the real-time clock/ Page 4, Paragraph 3, Sentences 3 and 4 -------------------------------------- Change from: ------------ This module includes managed objects for monitoring the batteries contained in an UPS system. However, the information provided by these objects is limited and tailored the particular needs of UPS systems. To: --- The UPS MIB module includes managed objects for monitoring the batteries contained in an UPS system. However, the information provided by the UPS MIB objects is limited and tailored the particular needs of UPS systems. IMHO, this change clarifies the text a little about which MIB was intended. When I first read this paragraph, it wasn't clear to me whether the words "This module" meant the BATTERY-MIB or the UPS MIB. Similarly, when I read the words "these objects", it wasn't clear whether it meant the BATTERY-MIB objects or the UPS MIB objects. I had to read the paragraph a second time. Page 12, batteryTechnology -------------------------- What value should the batteryTechnology have when the batteryType is capacitor(5)? Page 12, batteryLastChargingCycleTime ------------------------------------- The description clause starts: "The date and time of the last charging cycle." Is that the starting time of the last charging cycle or the ending time? WORDING ------- Page 3, Paragraph 4 ------------------- s/certain threshold in order to inform/certain threshold to inform/ Page 4, Paragraph 1 ------------------- s/The former allows to trace a battery/The former allows tracing a battery/ Page 11, DESCRIPTION for batteryIdentifier ------------------------------------------ s/by a device at which a battery/by a device in which a battery/ s/re-installed at the same or/re-installed in the same or/ Page 25, Paragraph under batteryChargingAdminState -------------------------------------------------- s/can e.g. be used by an attacker/can be used by an attacker/ Page 25, Paragraph under batteryAlarmLowCapacity and batteryAlarmHighCycleCount ------------------------------------------------------------------------------- s/weak batteries are used/weak batteries being used/ s/and potentially loose data/and potentially lose data/ Page 26, Paragraph under batteryAlarmHighTemperature/batteryAlarmLowTemperature ------------------------------------------------------------------------------- Change text from: ----------------- The result may e.g. be an unnecessary shutdown of a device if batteryAlarmHighTemperature is set to too low or damage to the device by too high temperatures if switched off or set to too high values or by damage to the battery when it e.g. is being charged. Batteries can also be damaged e.g. in an attempt to charge them at too low temperatures. To: --- The result may be an unnecessary shutdown of a device if the batteryAlarmHighTemperature is set to too low. The device or batteries may be damaged if the batteryAlarmHighTemperature is switched off or set to too high a value. Batteries can be damaged if charged at too low a temperature. Page 26, Paragraph 4 -------------------- s/even then, // Page 26, Last Paragraph ----------------------- s/it is RECOMMENDED to deploy SNMPv3/SNMPv3 deployment is RECOMMENDED/ Page 27, Section 7.1, "Entity MIB augmentation" ----------------------------------------------- s/version 4 is need as soon/version 4 is needed as soon/ s/it is RECOMMENDED to deploy SNMPv3/SNMPv3 deployment is RECOMMENDED/ Page 28, Section 7.2, "Kind of entity" -------------------------------------- s/we recommend to use/we recommend using/ s/sections needs to be updates/section needs to be updated/ Page 28, Section 7.4, "Notifications for removable batteries" ------------------------------------------------------------- s/for added a batteries and removed/for adding and removing/ s/management system should get informed/management system should be informed/ OTHER ----- Page 6: ------- The overview of the BATTERY-MIB schema is nice! From trac+eman@trac.tools.ietf.org Wed Feb 20 10:27:00 2013 Return-Path: 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 6A71E21F8925 for ; Wed, 20 Feb 2013 10:27:00 -0800 (PST) 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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zcTl8N-PqK6A for ; Wed, 20 Feb 2013 10:26:59 -0800 (PST) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id B8B1421F88F1 for ; Wed, 20 Feb 2013 10:26:45 -0800 (PST) Received: from localhost ([127.0.0.1]:58300 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1U8ENC-0003yW-PE; Wed, 20 Feb 2013 19:26:30 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "eman issue tracker" X-Trac-Version: 0.12.3 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.3, by Edgewall Software To: draft-ietf-eman-framework@tools.ietf.org, n.brownlee@auckland.ac.nz X-Trac-Project: eman Date: Wed, 20 Feb 2013 18:26:30 -0000 X-URL: http://tools.ietf.org/eman/ X-Trac-Ticket-URL: http://tools.ietf.org/wg/eman/trac/ticket/29 Message-ID: <064.716466cc60ff414a38d13249506e9ab3@trac.tools.ietf.org> X-Trac-Ticket-ID: 29 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-eman-framework@tools.ietf.org, n.brownlee@auckland.ac.nz, eman@ietf.org X-SA-Exim-Mail-From: trac+eman@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: bclaise@cisco.com, bnordman@lbl.gov, brad.schoening@verizon.net, jparello@cisco.com, quittek@netlab.nec.de Resent-Message-Id: <20130220182645.B8B1421F88F1@ietfa.amsl.com> Resent-Date: Wed, 20 Feb 2013 10:26:45 -0800 (PST) Resent-From: trac+eman@trac.tools.ietf.org Cc: eman@ietf.org Subject: [eman] #29: IANA Considerations section needs more detail X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Feb 2013 18:27:00 -0000 #29: IANA Considerations section needs more detail Section 12, IANA Considerations, is only a placeholder now. It needs to ask IANA to create a Registry for EMAN, in particular to list power states. -- -------------------------------------+------------------------------------- Reporter: | Owner: draft-ietf-eman- n.brownlee@auckland.ac.nz | framework@tools.ietf.org Type: defect | Status: new Priority: blocker | Milestone: milestone1 Component: framework | Version: Severity: Active WG Document | Keywords: -------------------------------------+------------------------------------- Ticket URL: eman From trac+eman@trac.tools.ietf.org Wed Feb 20 10:43:09 2013 Return-Path: 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 3941B21F888A for ; Wed, 20 Feb 2013 10:43:09 -0800 (PST) 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=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 tFTB9fPqwMXG for ; Wed, 20 Feb 2013 10:43:08 -0800 (PST) Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 534ED21F880B for ; Wed, 20 Feb 2013 10:43:08 -0800 (PST) Received: from localhost ([127.0.0.1]:59383 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from ) id 1U8Ed2-00024N-HK; Wed, 20 Feb 2013 19:42:52 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "eman issue tracker" X-Trac-Version: 0.12.3 Precedence: bulk Auto-Submitted: auto-generated X-Mailer: Trac 0.12.3, by Edgewall Software To: draft-ietf-eman-framework@tools.ietf.org, n.brownlee@auckland.ac.nz X-Trac-Project: eman Date: Wed, 20 Feb 2013 18:42:52 -0000 X-URL: http://tools.ietf.org/eman/ X-Trac-Ticket-URL: http://tools.ietf.org/wg/eman/trac/ticket/30 Message-ID: <064.8f201006117e8f657bd861e1408c12db@trac.tools.ietf.org> X-Trac-Ticket-ID: 30 X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Rcpt-To: draft-ietf-eman-framework@tools.ietf.org, n.brownlee@auckland.ac.nz, eman@ietf.org X-SA-Exim-Mail-From: trac+eman@trac.tools.ietf.org X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false Resent-To: bclaise@cisco.com, bnordman@lbl.gov, brad.schoening@verizon.net, jparello@cisco.com, quittek@netlab.nec.de Resent-Message-Id: <20130220184308.534ED21F880B@ietfa.amsl.com> Resent-Date: Wed, 20 Feb 2013 10:43:08 -0800 (PST) Resent-From: trac+eman@trac.tools.ietf.org Cc: eman@ietf.org Subject: [eman] #30: Power State and Power State Sets in Terminology section X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Feb 2013 18:43:09 -0000 #30: Power State and Power State Sets in Terminology section EMAN uses power states from other standards, the Terminology section needs to explain what they actually are. -- -------------------------------------+------------------------------------- Reporter: | Owner: draft-ietf-eman- n.brownlee@auckland.ac.nz | framework@tools.ietf.org Type: defect | Status: new Priority: major | Milestone: milestone1 Component: framework | Version: Severity: Active WG Document | Keywords: -------------------------------------+------------------------------------- Ticket URL: eman From bnordman@lbl.gov Wed Feb 20 22:59:10 2013 Return-Path: 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 9F18C21F8DF1 for ; Wed, 20 Feb 2013 22:59:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.976 X-Spam-Level: X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 S-l6zT2IUive for ; Wed, 20 Feb 2013 22:59:10 -0800 (PST) Received: from fe2.lbl.gov (fe2.lbl.gov [128.3.41.134]) by ietfa.amsl.com (Postfix) with ESMTP id 200F621F8DEF for ; Wed, 20 Feb 2013 22:59:10 -0800 (PST) X-Ironport-SBRS: 4.4 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AigDAEDEJVHRVdtIkGdsb2JhbABCA4JDgz8BqSEBiSQBiB99CBYOAQEBAQcLFBQnghYtXB4BB10SAQUBIhOIEqIRnhKOfhAYgy8DiGaNTIEdjV8WKYRL X-IronPort-AV: E=Sophos;i="4.84,706,1355126400"; d="scan'208";a="11650670" Received: from mail-oa0-f72.google.com ([209.85.219.72]) by fe2.lbl.gov with ESMTP; 20 Feb 2013 22:59:09 -0800 Received: by mail-oa0-f72.google.com with SMTP id j6so44978706oag.7 for ; Wed, 20 Feb 2013 22:59:09 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:x-received:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=g11+lOE5+gsx29KE76ZUfCQRqsIdIzMWT38WIJfXGFU=; b=hTYg8r7hKu9NFY/aGuBoD7vkhFho7zhNh+1aoyk5JvZubCffVUMOr5k6hooUsaHAI3 fY9RMQADwtEXh1XgLIcQxl0lRfthBN0h6waAtSWHJf2ltO5gQLeDbvwG21wJGCcKzPpi zo/DsCXvLpqifFFHyhA+K7mv4K9hXrZ5bnlrji8v0m/0TbAOkN8NWZq4PbgpB/eGfA3F RsQKwTlHh2k7xY9vbg1LughDLxsJC7OYyqh3ScArdcKPMrKqmK0VrUjcxdHm0WIscfv5 tSYZaJThX24zGjBiNKeQRvtfdJsU6XQSDAWg4tp4qCDIW56KI8a0Z9jWUPTBNaSariJ2 ZW0w== X-Received: by 10.50.7.231 with SMTP id m7mr631758iga.0.1361429949060; Wed, 20 Feb 2013 22:59:09 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.50.7.231 with SMTP id m7mr631755iga.0.1361429948951; Wed, 20 Feb 2013 22:59:08 -0800 (PST) Received: by 10.50.136.164 with HTTP; Wed, 20 Feb 2013 22:59:08 -0800 (PST) Date: Wed, 20 Feb 2013 22:59:08 -0800 Message-ID: From: Bruce Nordman To: eman mailing list Content-Type: multipart/alternative; boundary=f46d04462dd87e88a904d6369c89 X-Gm-Message-State: ALoCoQneWkFnxALj3kFGbp1zQSTjngrvHtdgce563vF9c3twVHVjgz0YVzqt8/ZPYq451ac6nR25HufgJo/5Dsi4rBSmjBTWYXxT0jMEhD8z0Yfg98pnoQnQZ5wemaXmw49upqlxA2sA Subject: [eman] EMAN - Call for Agenda items X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Feb 2013 06:59:10 -0000 --f46d04462dd87e88a904d6369c89 Content-Type: text/plain; charset=ISO-8859-1 Please send any requests for agenda time to Nevil and myself. While we can't guarantee time for non-charter drafts, last time we were able to accommodate all requests. Thanks, --Bruce -- *Bruce Nordman* Lawrence Berkeley National Laboratory *nordman.lbl.gov* BNordman@LBL.gov 510-486-7089 m: 510-501-7943 --f46d04462dd87e88a904d6369c89 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Please send any requests for agenda time to
Nevil and myself.=A0 While w= e can't guarantee
time for non-charter drafts, last time we were
= able to accommodate all requests.

Thanks,

--Bruce

--
Bruce Nordman
Lawrence Berkeley National Laboratory
nordman.lbl.gov
BNordman@LBL.gov
510-486-7089
m: 510-501-7943
--f46d04462dd87e88a904d6369c89-- From B.Hedstrom@CableLabs.com Thu Feb 21 10:29:38 2013 Return-Path: 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 F1DF121F8F2B for ; Thu, 21 Feb 2013 10:29:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.463 X-Spam-Level: X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, 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 Lvvb5J4VMUlQ for ; Thu, 21 Feb 2013 10:29:38 -0800 (PST) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id 5D85521F8F08 for ; Thu, 21 Feb 2013 10:29:38 -0800 (PST) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.5/8.14.5) with ESMTP id r1LITXQW022953 for ; Thu, 21 Feb 2013 11:29:33 -0700 Received: from exchange.cablelabs.com (10.5.0.19) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com); Thu, 21 Feb 2013 11:29:33 -0700 (MST) X-Virus-Status: clean(F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com) Received: from EXCHANGE.cablelabs.com ([fe80::797a:96d1:3c53:18ee]) by EXCHANGE.cablelabs.com ([fe80::797a:96d1:3c53:18ee%11]) with mapi id 14.02.0328.009; Thu, 21 Feb 2013 11:29:33 -0700 From: Brian Hedstrom To: "eman@ietf.org" Thread-Topic: Questions/Comments on EMAN MIBs Thread-Index: AQHOEGFlPS8kr/pc7EiVW5LqLSb8WQ== Date: Thu, 21 Feb 2013 18:29:33 +0000 Message-ID: <686B406F73B0F245AB30195F4E80E2D517F143B8@EXCHANGE.cablelabs.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.1.130117 x-originating-ip: [10.5.0.27] Content-Type: multipart/alternative; boundary="_000_686B406F73B0F245AB30195F4E80E2D517F143B8EXCHANGEcablela_" MIME-Version: 1.0 X-Approved: ondar Subject: [eman] Questions/Comments on EMAN MIBs X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Feb 2013 18:29:39 -0000 --_000_686B406F73B0F245AB30195F4E80E2D517F143B8EXCHANGEcablela_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable EMAN WG, I have some comments/questions on the EMAN MIBs. batteryEntry: There is only a batteryIndex for this table. How do you corr= elate which battery you are querying with respect the the device in the net= work? For example, if I query batteryType.5, what does 5 correlate to when= I potentially have 5 million batteries in my network that I am monitoring.= Most of the other tables in the EMAN MIB set include the EntPhysicalIndex= as a Table Index. eoEnergyParametersTable: The indexing is confusing on this table. The firs= t object in the table, eoEnergyObjectIndex, is not an index to the table. = This is confusing alone since generally MIBs are constructing with the inde= xes listed first in the tables. The second object in the table, eoEnergyPa= rametersIndex, is listed as an index to the table, but does not have it's M= AX-ACCESS listed as Not-Accessible. eoPowerStateEnterReason: should this be a read-create object? The table do= es not have a row-status object to support read-create for the table. eoProxyID: This is read-only. I'M not clear on how this table is used. Shou= ld this table be a RowStatus read-create table to dynamically create Relati= onships? eoEnergyParametersIntervalMode INTEGER, <-- Corrected line Thanks, Brian Hedstrom Senior Architect, Business & Operational Support Systems CableLabs, Inc. 858 Coal Creek Circle Louisville, CO 80027 Direct: 303.661.3829 eFax: 303.664.8120 Google+: brian.hedstrom Skype IM: brian.hedstrom b.hedstrom@cablelabs.com --_000_686B406F73B0F245AB30195F4E80E2D517F143B8EXCHANGEcablela_ Content-Type: text/html; charset="us-ascii" Content-ID: <40664464DA6C14408D2385057F0CF522@cablelabs.com> Content-Transfer-Encoding: quoted-printable
EMAN WG,
I have some comments/questions on the EMAN MIBs.
batteryEntry: There is onl= y a batteryIndex for this table.  How do you correlate which battery y= ou are querying with respect the the device in the network?  For examp= le, if I query batteryType.5, what does 5 correlate to when I potentially have 5 million batteries in my network that&n= bsp;I am monitoring.  Most of the other tables in the EMAN MIB se= t include the EntPhysicalIndex as a Table Index.

eoEnergyParametersTable: The indexin= g is confusing on this table.  The first object in the table, eoEnergyObjectIndex, is not an index = to the table.  This is confusing alone since generally MIBs are constructing with the indexes listed first in the tables.  T= he second object in the table, eoEnergyParametersIndex, is listed as an index to the table, but does not= have it's MAX-ACCESS listed as Not-Accessible.

eoPowerStateEnterReason: should this= be a read-create object?  The table does not have a row-status object= to support read-create for the table.

eoProxyID: This is read-only. I= 'M not clear on how this table is used. Should this table be a RowStat= us read-create table to dynamically create Relationships?

eoEnergyParametersIntervalMode= INTEGER, <-- Corrected line


Thanks,

Brian Hedstrom
Senior Architect, Business & Operational Support Systems
CableLabs, Inc.
858 Coal Creek Circle
Louisville, CO 80027
Direct: 303.661.3829
eFax: 303.664.8120
Google+: brian.hedstrom
Skype IM: brian.hedstrom 
b.hedstrom@cablelabs.com=

To: "eman mailing list" References: In-Reply-To: Date: Fri, 22 Feb 2013 14:42:13 +0900 Message-ID: <003501ce10bf$5f73b6e0$1e5b24a0$@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHOEADkzPYESo/jAUiiImz8OerK5ZiFXetg Content-Language: ko Subject: Re: [eman] EMAN - Call for Agenda items X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Feb 2013 05:42:19 -0000 Hello Bruce and Nevil, We have published a document regarding network proxy protocol. It is a 00-version and we will publish a revised 01-version soon. If there is a room in agenda, I would like to request a slot in order to discuss this document in Orlando. The link for the document is below. (http://datatracker.ietf.org/doc/draft-jeong-eman-network-proxy-protocol/) Best regards, Sangjin > From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of Bruce Nordman > Sent: Thursday, February 21, 2013 3:59 PM > To: eman mailing list > Subject: [eman] EMAN - Call for Agenda items > > Please send any requests for agenda time to > Nevil and myself. While we can't guarantee > time for non-charter drafts, last time we were > able to accommodate all requests. > > Thanks, > > --Bruce > > -- > Bruce Nordman > Lawrence Berkeley National Laboratory > nordman.lbl.gov > BNordman@LBL.gov > 510-486-7089 > m: 510-501-7943 From Quittek@neclab.eu Fri Feb 22 02:50:35 2013 Return-Path: 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 E8B3221F8E46 for ; Fri, 22 Feb 2013 02:50:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.588 X-Spam-Level: X-Spam-Status: No, score=-103.588 tagged_above=-999 required=5 tests=[AWL=0.011, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] 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 GLmssxEYFlL9 for ; Fri, 22 Feb 2013 02:50:34 -0800 (PST) Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 0F9D821F8E22 for ; Fri, 22 Feb 2013 02:50:34 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 1B3311033CB; Fri, 22 Feb 2013 11:50:33 +0100 (CET) X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de) Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TyvLjtu13ivu; Fri, 22 Feb 2013 11:50:33 +0100 (CET) Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id 0310C1033C9; Fri, 22 Feb 2013 11:50:23 +0100 (CET) Received: from PALLENE.office.hd ([169.254.1.80]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Fri, 22 Feb 2013 11:50:22 +0100 From: Juergen Quittek To: Brian Hedstrom Thread-Topic: [eman] Questions/Comments on EMAN MIBs Thread-Index: AQHOEGFlPS8kr/pc7EiVW5LqLSb8WZiFtA+A Date: Fri, 22 Feb 2013 10:49:31 +0000 Message-ID: In-Reply-To: <686B406F73B0F245AB30195F4E80E2D517F143B8@EXCHANGE.cablelabs.com> Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.14.0.111121 x-originating-ip: [10.1.2.219] Content-Type: text/plain; charset="us-ascii" Content-ID: <9A4C2E362299604A8B6912116551D890@office.hd> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: eman mailing list Subject: Re: [eman] Questions/Comments on EMAN MIBs X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Feb 2013 10:50:35 -0000 Hi Brian, Am 21.02.13 19:29 schrieb "Brian Hedstrom" unter : > >EMAN WG, >I have some comments/questions on the EMAN MIBs. >batteryEntry: There is only a batteryIndex for this table. How do you >correlate which battery you are querying with respect the the device in >the network? For example, if I query batteryType.5, what does 5 >correlate to > when I potentially have 5 million batteries in my network that I am >monitoring. Most of the other tables in the EMAN MIB set include the >EntPhysicalIndex as a Table Index. We are working on what you ask for already concerning the Battery MIB module, see below. However, I do not get your point. If you have 5 million batteries in your network that you are monitoring, you will probably as well have five million network interfaces or five million hard drives in your network. And current management systems give you all what you need to distinguish them well. Obviously, there are sufficient means available to distinguish line card 5 at host A from line card 5 at host B. So what you are missing is not clear to me at all. Anyway, the integration with the entity MIB is the only mayor remaining open issue for the Battery MIB module. We are revising the Entity MIB v3 in the eman WG and will come up with Entity MIB v4 soon, see http://datatracker.ietf.org/doc/draft-ietf-eman-rfc4133bis/ With this in place we will use it also in the Battery MIB module. >eoEnergyParametersTable: The indexing is confusing on this table. The >first object in the table, eoEnergyObjectIndex, is not an index to the >table. This is confusing alone since generally > MIBs are constructing with the indexes listed first in the tables. The >second object in the table, eoEnergyParametersIndex, is listed as an >index to the table, but does not have it's MAX-ACCESS listed as >Not-Accessible. Thank you for pointing out these two issues. Please note that we are currently focussing on the eman framework. The MIB modules may undergo a significant revisions after the framework is agreed. Coming back to your points: Yes , I agree that 1. The eoEnergyObjectIndex is missign as first index in the INDEX statement of object eoEnergyParametersEntry 2. The MAX-ACCESS clauses of objects eoEnergyObjectIndex and eoEnergyParametersIndex should have the value "not-accessible". There are rare cases where index values can have other MAX-ACCESS values, here we do not have such a case. >eoPowerStateEnterReason: should this be a read-create object? The table >does not have a row-status object to support read-create for the table. I fully agree. Thew value of this MAX-ACCESS clause must be either read-write or read-only. >eoProxyID: This is read-only. I'M not clear on how this table is used. >Should this table be a RowStatus read-create table to dynamically create >Relationships? I see no need for having this object being read-only. Probably not-accessible would be OK. >eoEnergyParametersIntervalMode INTEGER, <-- Corrected line Thank you again. Yes, this needs to be fixed in object EoEnergyParametersEntry. Best regards, Juergen > >Thanks, >Brian Hedstrom >Senior Architect, Business & Operational Support Systems >CableLabs, Inc. >858 Coal Creek Circle >Louisville, CO 80027 >Direct: 303.661.3829 >eFax: 303.664.8120 >Google+: brian.hedstrom >Skype IM: brian.hedstrom >b.hedstrom@cablelabs.com >=20 > > > > > >_______________________________________________ >eman mailing list >eman@ietf.org >https://www.ietf.org/mailman/listinfo/eman From B.Hedstrom@CableLabs.com Fri Feb 22 08:00:11 2013 Return-Path: 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 0D6CB21F8DF8 for ; Fri, 22 Feb 2013 08:00:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.463 X-Spam-Level: X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368] 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 kEK9+zU91e+r for ; Fri, 22 Feb 2013 08:00:10 -0800 (PST) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id 4966721F8E98 for ; Fri, 22 Feb 2013 08:00:10 -0800 (PST) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.5/8.14.5) with ESMTP id r1MG09x8025795; Fri, 22 Feb 2013 09:00:09 -0700 Received: from exchange.cablelabs.com (10.5.0.19) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com); Fri, 22 Feb 2013 09:00:09 -0700 (MST) X-Virus-Status: clean(F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com) Received: from EXCHANGE.cablelabs.com ([fe80::797a:96d1:3c53:18ee]) by EXCHANGE.cablelabs.com ([fe80::797a:96d1:3c53:18ee%11]) with mapi id 14.02.0328.009; Fri, 22 Feb 2013 09:00:08 -0700 From: Brian Hedstrom To: Juergen Quittek Thread-Topic: [eman] Questions/Comments on EMAN MIBs Thread-Index: AQHOEGFlPS8kr/pc7EiVW5LqLSb8WZiFtA+AgABWjoA= Date: Fri, 22 Feb 2013 16:00:08 +0000 Message-ID: <686B406F73B0F245AB30195F4E80E2D517F15A87@EXCHANGE.cablelabs.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.1.130117 x-originating-ip: [10.5.0.27] Content-Type: text/plain; charset="us-ascii" Content-ID: <8AD044F28CD87245BF4F03CB9F9BC91A@cablelabs.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Approved: ondar Cc: eman mailing list Subject: Re: [eman] Questions/Comments on EMAN MIBs X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Feb 2013 16:00:11 -0000 Are you thinking about modeling a Battery like a Sensor? entPhySensorTable OBJECT-TYPE SYNTAX SEQUENCE OF EntPhySensorEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains one row per physical sensor represented by an associated row in the entPhysicalTable." ::=3D { entitySensorObjects 1 } entPhySensorEntry OBJECT-TYPE SYNTAX EntPhySensorEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about a particular physical sensor. An entry in this table describes the present reading of a sensor, the measurement units and scale, and sensor operational status. Entries are created in this table by the agent. An entry for each physical sensor SHOULD be created at the same time as the associated entPhysicalEntry. An entry SHOULD be destroyed if the associated entPhysicalEntry is destroyed." INDEX { entPhysicalIndex } -- SPARSE-AUGMENTS ::=3D { entPhySensorTable 1 } Brian Hedstrom Senior Architect, Business & Operational Support Systems CableLabs, Inc. 858 Coal Creek Circle Louisville, CO 80027 Direct: 303.661.3829 eFax: 303.664.8120 Google+: brian.hedstrom Skype IM: brian.hedstrom b.hedstrom@cablelabs.com =20 On 2/22/13 3:49 AM, "Juergen Quittek" wrote: >Hi Brian, > > >Am 21.02.13 19:29 schrieb "Brian Hedstrom" unter >: > >> >>EMAN WG, >>I have some comments/questions on the EMAN MIBs. >>batteryEntry: There is only a batteryIndex for this table. How do you >>correlate which battery you are querying with respect the the device in >>the network? For example, if I query batteryType.5, what does 5 >>correlate to >> when I potentially have 5 million batteries in my network that I am >>monitoring. Most of the other tables in the EMAN MIB set include the >>EntPhysicalIndex as a Table Index. > >We are working on what you ask for already concerning the Battery MIB >module, see below. > >However, I do not get your point. If you have 5 million batteries in your >network that you are monitoring, you will probably as well have five >million network interfaces or five million hard drives in your network. >And current management systems give you all what you need to distinguish >them well. Obviously, there are sufficient means available to distinguish >line card 5 at host A from line card 5 at host B. > >So what you are missing is not clear to me at all. > >Anyway, the integration with the entity MIB is the only mayor remaining >open issue for the Battery MIB module. We are revising the Entity MIB v3 >in the eman WG and will come up with Entity MIB v4 soon, see >http://datatracker.ietf.org/doc/draft-ietf-eman-rfc4133bis/ With this in >place we will use it also in the Battery MIB module. > > >>eoEnergyParametersTable: The indexing is confusing on this table. The >>first object in the table, eoEnergyObjectIndex, is not an index to the >>table. This is confusing alone since generally >> MIBs are constructing with the indexes listed first in the tables. The >>second object in the table, eoEnergyParametersIndex, is listed as an >>index to the table, but does not have it's MAX-ACCESS listed as >>Not-Accessible. > >Thank you for pointing out these two issues. Please note that we are >currently focussing on the eman framework. The MIB modules may undergo a >significant revisions after the framework is agreed. > >Coming back to your points: Yes , I agree that >1. The eoEnergyObjectIndex is missign as first index in the INDEX >statement of object eoEnergyParametersEntry >2. The MAX-ACCESS clauses of objects eoEnergyObjectIndex and >eoEnergyParametersIndex should have the value "not-accessible". There are >rare cases where index values can have other MAX-ACCESS values, here we do >not have such a case. > >>eoPowerStateEnterReason: should this be a read-create object? The table >>does not have a row-status object to support read-create for the table. > >I fully agree. Thew value of this MAX-ACCESS clause must be either >read-write or read-only. > >>eoProxyID: This is read-only. I'M not clear on how this table is used. >>Should this table be a RowStatus read-create table to dynamically create >>Relationships? > >I see no need for having this object being read-only. Probably >not-accessible would be OK. > >>eoEnergyParametersIntervalMode INTEGER, <-- Corrected line > >Thank you again. Yes, this needs to be fixed in object >EoEnergyParametersEntry. > >Best regards, > Juergen > > >> >>Thanks, >>Brian Hedstrom >>Senior Architect, Business & Operational Support Systems >>CableLabs, Inc. >>858 Coal Creek Circle >>Louisville, CO 80027 >>Direct: 303.661.3829 >>eFax: 303.664.8120 >>Google+: brian.hedstrom >>Skype IM: brian.hedstrom >>b.hedstrom@cablelabs.com >>=20 >> >> >> >> >> >>_______________________________________________ >>eman mailing list >>eman@ietf.org >>https://www.ietf.org/mailman/listinfo/eman > From bnordman@lbl.gov Sun Feb 24 09:45:23 2013 Return-Path: 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 7B11621F9090 for ; Sun, 24 Feb 2013 09:45:23 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.976 X-Spam-Level: X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, 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 xGFIodv9MMYn for ; Sun, 24 Feb 2013 09:45:23 -0800 (PST) Received: from fe1.lbl.gov (fe1.lbl.gov [128.3.41.133]) by ietfa.amsl.com (Postfix) with ESMTP id 0D1E421F848D for ; Sun, 24 Feb 2013 09:45:23 -0800 (PST) X-Ironport-SBRS: 4.7 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ArcBALFQKlHRVdjGk2dsb2JhbABBA4JDrUIBiSYBiSgIFg4BAQEBCQkLCRQEI4M+B10SAQUBIhOIE5w7gnKdHY03F4FYgy8DiGmNVIEdjWYWKYRL X-IronPort-AV: E=Sophos;i="4.84,728,1355126400"; d="scan'208";a="10240976" Received: from mail-qc0-f198.google.com ([209.85.216.198]) by fe1.lbl.gov with ESMTP; 24 Feb 2013 09:45:21 -0800 Received: by mail-qc0-f198.google.com with SMTP id e18so4624965qch.5 for ; Sun, 24 Feb 2013 09:45:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:x-received:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=qzVC9hYNquZpq9RDTfiIawEca9MLjYZEZkPDk8sWLVU=; b=lAuuUpRJnv8rRxI62OQVDrFGhthfacTTfPGhkwUN3zSZU/0uMpn1BO8o7cSDSdrAUK 8NuT9kuYAvLzD/r+HnDAJkxuBzWGjJhMVL3K/GmtUi5j+2JRYR9P6/r+Sh1xqvkMRDLR XNIbEtPJbeLqpelqgmqMFR8iIP64fGBVuZR2t3je4NGTHZ9wqpeXzIyludO+jxGpEuQH WFXxRKF4rMDVXBkAbeCyBNmSwmKBCvbP2X1XUzTz1y7f8y1c23jSrkuBtvQzEr15U1i7 nmClrLR1Kks9qMozcsfudswZQkfdtFWI8Jydbi5wpRgB/kGhE/zDpbfyZFyoe8uftA6p tClw== X-Received: by 10.220.149.11 with SMTP id r11mr8561218vcv.44.1361727921283; Sun, 24 Feb 2013 09:45:21 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.220.149.11 with SMTP id r11mr8561215vcv.44.1361727921168; Sun, 24 Feb 2013 09:45:21 -0800 (PST) Received: by 10.220.210.12 with HTTP; Sun, 24 Feb 2013 09:45:21 -0800 (PST) Date: Sun, 24 Feb 2013 09:45:21 -0800 Message-ID: From: Bruce Nordman To: eman mailing list Content-Type: multipart/alternative; boundary=f46d0434c0ac05bae704d67bfd8e X-Gm-Message-State: ALoCoQnfUyz/+dxc5AjRtGn0FVJ1yhkZsPDADjsxTjPiF10kWLIUruEvNY7SnAJOzVSE4Fexo12lJXbP2tlhQq80Md80VudiKysldxprla3ohRMbeLQq8X+mtoO/MMS2GJLpCLUiJBwx Subject: [eman] EMAN Draft Agenda X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Feb 2013 17:45:23 -0000 --f46d0434c0ac05bae704d67bfd8e Content-Type: text/plain; charset=ISO-8859-1 A draft EMAN agenda has been posted and is duplicated below. Please send me any edits, comments, etc. --Bruce EMAN agenda, IETF 86 Monday, 11 March 2013, Caribbean 6 1. Note well, agenda bashing, note takers, blue sheets, 5 min 2. Update from last meeting / WG Status 5 min 3. Requirements for Energy Management, draft-ietf-eman-requirements-11, Juergen Quittek, 15 min 4. Energy Management Framework, draft-ietf-eman-framework-07, John Parello, 30 min 5. MIBs 5.a. Energy-aware Networks and Devices MIB draft-ietf-eman-energy-aware-mib-07, John Parello, 10 min 5.b. Power and Energy Monitoring MIB draft-ietf-eman-energy-monitoring-mib-04, Mouli Chandramouli (presented by Nevil), 10 min 5.c. Definition of Managed Objects for Battery Monitoring draft-ietf-eman-battery-mib-07, Juergen Quitte, 10 min 6. Energy Management (EMAN) Applicability Statement, draft-ietf-eman-applicability-statement-02, Mouli Chandramouli (presented by Bruce), 5 min 7. Review Milestones 8. Non-charter drafts (if time) 8.a. Network Proxy Protocol draft-jeong-eman-network-proxy-protocol-00 , Sangjin Jeong, 10 min 8.d. Green Usage Monitoring Information Base draft-suganuma-greenmib-01, Satoru Izumi, 10 min 9. Open microphone: whatever time is left Note: Entity MIB (Version 4) draft-ietf-eman-rfc4133bis-06 has been approved by the IESG. -- *Bruce Nordman* Lawrence Berkeley National Laboratory *nordman.lbl.gov* BNordman@LBL.gov 510-486-7089 m: 510-501-7943 --f46d0434c0ac05bae704d67bfd8e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable A draft EMAN agenda has been posted and is duplicated below.
Please send= me any edits, comments, etc.
--Bruce


EMAN agenda, IETF =
86
Monday, 11 March 2013, Caribbean 6

1. Note well, agenda bashing, note takers, blue sheets, 5 min

2. Update from last meeting / WG Status                 5 min

3. Requirements for Energy Management,
   draft-ietf-eman-requirements-11, Juergen Quittek, 15 min

4. Energy Management Framework,=20
   draft-ietf-eman-framework-07, John Parello, 30 min

5. MIBs

  5.a. Energy-aware Networks and Devices MIB
  draft-ietf-eman-energy-aware-mib-07, John Parello, 10 min
 =20
  5.b. Power and Energy Monitoring MIB
  draft-ietf-eman-energy-monitoring-mib-04, Mouli Chandramouli
  (presented by Nevil), 10 min

  5.c. Definition of Managed Objects for Battery Monitoring
  draft-ietf-eman-battery-mib-07, Juergen Quitte, 10 min

6. Energy Management (EMAN) Applicability Statement,
   draft-ietf-eman-applicability-statement-02, Mouli Chandramouli
   (presented by Bruce), 5 min
  =20
7. Review Milestones

8. Non-charter drafts (if time)

   8.a. Network Proxy Protocol
        draft-jeong-eman-network-proxy-protocol-00 , Sangjin Jeong, 10 min

   8.d. Green Usage Monitoring Information Base
        draft-suganuma-greenmib-01, Satoru Izumi, 10 min


9. Open microphone: whatever time is left

Note:  Entity MIB (Version 4) draft-ietf-eman-rfc4133bis-06=20
has been approved by the IESG.


--
Bruce Nordman
Lawrence Berkeley National Labor= atory
nordman.lbl.gov
BNordman@LBL.gov
510-486-7089
m: 510-501-7943
--f46d0434c0ac05bae704d67bfd8e-- From moulchan@cisco.com Mon Feb 25 03:17:11 2013 Return-Path: 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 A800A21F92AD for ; Mon, 25 Feb 2013 03:17:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 Gt-ZB0ZqL6+p for ; Mon, 25 Feb 2013 03:17:10 -0800 (PST) Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id A507B21F92A6 for ; Mon, 25 Feb 2013 03:17:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2338; q=dns/txt; s=iport; t=1361791030; x=1363000630; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=IRaBWmEKnTWqvTx9YuHl9Rf2ZuKkf3ulE7rwQMmL1UM=; b=MWv95SCOliLLbaajq89MONZEB6vJJ/ObPnQC1e1TyoAt9/kfTZdmXCc0 vFQ1YCabpgaKPPAjbGs6T5FUtHU/AqgqzuyK2rJE/LBPMyeVwBGCnAoj+ THEcuqElrTif0NDKblwebpljRTtnxdhSc9GWGhAw9+tpRLNmz9yy04Xuj 8=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgEFANFHK1GtJV2c/2dsb2JhbABCA8FTgQQWc4IfAQEBBDo4EwQCAQgOAwQBAQsUCQcyFAkIAgQBEggBiAoMvieNTYEQIQUNBQYLgk5hA6cigweBcjU X-IronPort-AV: E=Sophos;i="4.84,733,1355097600"; d="scan'208";a="180775795" Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-6.cisco.com with ESMTP; 25 Feb 2013 11:17:10 +0000 Received: from xhc-aln-x07.cisco.com (xhc-aln-x07.cisco.com [173.36.12.81]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id r1PBH9Xs032416 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 25 Feb 2013 11:17:10 GMT Received: from xmb-rcd-x08.cisco.com ([169.254.8.192]) by xhc-aln-x07.cisco.com ([173.36.12.81]) with mapi id 14.02.0318.004; Mon, 25 Feb 2013 05:17:09 -0600 From: "Mouli Chandramouli (moulchan)" To: Brian Hedstrom , "eman@ietf.org" Thread-Topic: Questions/Comments on EMAN MIBs Thread-Index: AQHOEGFlPS8kr/pc7EiVW5LqLSb8WZiKYHyg Date: Mon, 25 Feb 2013 11:17:08 +0000 Message-ID: <852AF0ED49D9F24BBBFA1B4DEEBE3BA4286C30B4@xmb-rcd-x08.cisco.com> References: <686B406F73B0F245AB30195F4E80E2D517F143B8@EXCHANGE.cablelabs.com> In-Reply-To: <686B406F73B0F245AB30195F4E80E2D517F143B8@EXCHANGE.cablelabs.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.142.100.140] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [eman] Questions/Comments on EMAN MIBs X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2013 11:17:11 -0000 Hello Brian, Replies inline.=20 Thanks Mouli=20 -----Original Message----- From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of Bri= an Hedstrom Sent: Friday, February 22, 2013 12:00 AM To: eman@ietf.org Subject: [eman] Questions/Comments on EMAN MIBs EMAN WG, I have some comments/questions on the EMAN MIBs. eoEnergyParametersTable: The indexing is confusing on this table. The firs= t object in the table, eoEnergyObjectIndex, is not an index to the table. = This is confusing alone since generally MIBs are constructing with the inde= xes listed first in the tables. The second object in the table, eoEnergyPa= rametersIndex, is listed as an index to the table, but does not have it's M= AX-ACCESS listed as Not-Accessible. [ycm] eoParametersIndex was introduced based on feedback from the WG http:/= /www.ietf.org/mail-archive/web/eman/current/msg01378.html [ycm] on the need for collection of energy measurement using multiple windo= wing schemes.=20 [ycm] With this indexing, for the same energy object with the same eoEnergy= ObjectIndex , it is possible to have two different eoEnergyParametersIndex = =20 [ycm] for each eoEnergyParametersIndex it is possible to have a specific w= indowing mechanism (total, or sliding, ...) for energy measurement collecti= on.=20 [ycm] I believe it is permissible to have to index of the table is accessib= le.=20 eoPowerStateEnterReason: should this be a read-create object? The table do= es not have a row-status object to support read-create for the table=20 [ycm] Yes, the MAX-ACCESS for this object can be read-write with the ownet= string syntax. =20 eoProxyID: This is read-only. I'M not clear on how this table is used. Shou= ld this table be a RowStatus read-create table to dynamically create Relati= onships? eoEnergyParametersIntervalMode INTEGER, <-- Corrected line [ycm] Currently, it is defined as eoEnergyParametersIntervalMode Intege= r32,=20 [ycm] and we shall update in the definition. =20 Thanks, Brian Hedstrom Senior Architect, Business & Operational Support Systems CableLabs, Inc. 858 Coal Creek Circle Louisville, CO 80027 Direct: 303.661.3829 eFax: 303.664.8120 Google+: brian.hedstrom Skype IM: brian.hedstrom b.hedstrom@cablelabs.com =20 From internet-drafts@ietf.org Mon Feb 25 08:25:04 2013 Return-Path: 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 D37C821F956B; Mon, 25 Feb 2013 08:25:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.523 X-Spam-Level: X-Spam-Status: No, score=-102.523 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 UE+sgdsVEFZZ; Mon, 25 Feb 2013 08:25:04 -0800 (PST) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DD8421F955F; Mon, 25 Feb 2013 08:25:04 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.40 Message-ID: <20130225162504.724.73004.idtracker@ietfa.amsl.com> Date: Mon, 25 Feb 2013 08:25:04 -0800 Cc: eman@ietf.org Subject: [eman] I-D Action: draft-ietf-eman-framework-07.txt X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2013 16:25:05 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Energy Management Working Group of the IE= TF. Title : Energy Management Framework Author(s) : Benoit Claise John Parello Brad Schoening Juergen Quittek Bruce Nordman Filename : draft-ietf-eman-framework-07.txt Pages : 65 Date : 2013-02-25 Abstract: This document defines a framework for providing Energy Management for devices and device components within or connected to communication networks. The framework defines an Energy Management Domain as a set of Energy Objects, for which each Energy Object is identified, classified and given context. Energy Objects can be monitored and/or controlled with respect to Power, Power State, Energy, Demand, Power Attributes, and Battery. Additionally the framework models relationships and capabilities between Energy Objects. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-eman-framework There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-eman-framework-07 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eman-framework-07 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From jparello@cisco.com Mon Feb 25 08:38:30 2013 Return-Path: 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 4A96421F9564 for ; Mon, 25 Feb 2013 08:38:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.599 X-Spam-Level: X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8] 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 B6MkFKz1L8ob for ; Mon, 25 Feb 2013 08:38:29 -0800 (PST) Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 7DB3121F9561 for ; Mon, 25 Feb 2013 08:38:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3354; q=dns/txt; s=iport; t=1361810309; x=1363019909; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=Q7eLIiEJe8qF0KHbeXrAn6OCzMjueM/d41EmBAAeTwQ=; b=UVR8B5JO7yS9BStsxwWEPgZRmCnLq3gZ2z6ojgBS9Rf977NS0EwwQSjH AKdQw2Q3YwLg0BTya6anRX33oWOwz7ohRtI0WsNuPEgC/Qti8rckwJnw+ oog1e7Xlf3Kft5esoUOl9ZrdRCDzX3NbuYwjvmqf0X7qfJ5TCX2TGWjoj 8=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgUFAGKSK1GtJXG8/2dsb2JhbABFg3iCV7sGDXgWc4IfAQEBBCMRPgUOBAIBCBEEAQEDAgYdAwICAjAUAQYBAQUDAgQTCAGHeAMOAQcFrVORT4EjixSBABeBDw8XEgaCJzJhA5daj0iDB4In X-IronPort-AV: E=Sophos;i="4.84,735,1355097600"; d="scan'208";a="180887115" Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-6.cisco.com with ESMTP; 25 Feb 2013 16:38:29 +0000 Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id r1PGcTR3016805 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Mon, 25 Feb 2013 16:38:29 GMT Received: from xmb-aln-x04.cisco.com ([169.254.9.127]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.02.0318.004; Mon, 25 Feb 2013 10:38:28 -0600 From: "John Parello (jparello)" To: "eman@ietf.org" Thread-Topic: New Version Notification for draft-ietf-eman-framework-07.txt Thread-Index: AQHOE3StcM1De6cr40SlLhHHrxGb2ZiKwkkg Date: Mon, 25 Feb 2013 16:38:28 +0000 Message-ID: <9C213D38848B89428F46808B16F6F0861F7E2C@xmb-aln-x04.cisco.com> References: <20130225162504.724.55600.idtracker@ietfa.amsl.com> In-Reply-To: <20130225162504.724.55600.idtracker@ietfa.amsl.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [171.71.223.136] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 Subject: [eman] FW: New Version Notification for draft-ietf-eman-framework-07.txt X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2013 16:38:30 -0000 SGksDQoNCldlJ3ZlIHBvc3RlZCBhIG5ldyB2ZXJzaW9uIGZvciByZXZpZXcgYXQgSUVURi04Ni4g V2UndmUgbWFkZSBhIGxvdCBvZiBwcm9ncmVzcyBjbG9zaW5nIGlzc3Vlcy4gTm90YWJsZSBjaGFu Z2VzIGFyZToNCi0gcmV2aXNlZCBvdXRsaW5lDQotIGNsYXJpZmljYXRpb24gb2YgYWdncmVnYXRp b24NCi0gcmV2aXNlZCBVTUwgZm9yIHRoZSBpbmZvcm1hdGlvbiBtb2RlbA0KLSB1c2Ugb2YgYXR0 cmlidXRlcyBmb3IgcG93ZXINCg0KU2VlIGhlcmUgZm9yIGFsbCBjbG9zZWQgaXNzdWVzOg0KaHR0 cDovL3Rvb2xzLmlldGYub3JnL3dnL2VtYW4vdHJhYy9yZXBvcnQvNg0KDQpXZSBoYXZlIHRoZSBm b2xsb3dpbmcgb3BlbiBpc3N1ZXM6DQpodHRwOi8vdG9vbHMuaWV0Zi5vcmcvd2cvZW1hbi90cmFj L3JlcG9ydC8xDQoNCldlIGhhdmUgYWJvdXQgMjArIGNvbW1lbnRzIGFtb25nIHRoZSBhdXRob3Jz IHRvIHJlc29sdmUgYXMgcGFydCBvZiBJc3N1ZSAjNCAgd2hpY2ggaXMgdGhlIHJlb3JnYW5pemF0 aW9uIGFuZCBjb25zb2xpZGF0aW9uIHRhc2suDQoNCkZvciB5b3VyIGNvbnZlbmllbmNlIHRoZSBk aWZmIGlzIGhlcmU6DQpodHRwczovL3d3dy5pZXRmLm9yZy9yZmNkaWZmP3VybDE9ZHJhZnQtaWV0 Zi1lbWFuLWZyYW1ld29yay0wNiZkaWZmdHlwZT0tLWh0bWwmc3VibWl0PUdvISZ1cmwyPWRyYWZ0 LWlldGYtZW1hbi1mcmFtZXdvcmstMDcNCg0KUGxlYXNlIGRvIHNlbmQgdXMgeW91ciBmZWVkYmFj ayENClRoYW5rcw0KSnANCg0KDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206 IGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZyBbbWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9y Z10gDQpTZW50OiBNb25kYXksIEZlYnJ1YXJ5IDI1LCAyMDEzIDg6MjUgQU0NClRvOiBKb2huIFBh cmVsbG8gKGpwYXJlbGxvKQ0KQ2M6IEJlbm9pdCBDbGFpc2UgKGJjbGFpc2UpOyBicmFkLnNjaG9l bmluZ0B2ZXJpem9uLm5ldDsgYm5vcmRtYW5AbGJsLmdvdjsgcXVpdHRla0BuZXRsYWIubmVjLmRl DQpTdWJqZWN0OiBOZXcgVmVyc2lvbiBOb3RpZmljYXRpb24gZm9yIGRyYWZ0LWlldGYtZW1hbi1m cmFtZXdvcmstMDcudHh0DQoNCg0KQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LWlldGYtZW1h bi1mcmFtZXdvcmstMDcudHh0IGhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQgYnkgSm9o biBQYXJlbGxvIGFuZCBwb3N0ZWQgdG8gdGhlIElFVEYgcmVwb3NpdG9yeS4NCg0KRmlsZW5hbWU6 CSBkcmFmdC1pZXRmLWVtYW4tZnJhbWV3b3JrDQpSZXZpc2lvbjoJIDA3DQpUaXRsZToJCSBFbmVy Z3kgTWFuYWdlbWVudCBGcmFtZXdvcmsNCkNyZWF0aW9uIGRhdGU6CSAyMDEzLTAyLTI0DQpHcm91 cDoJCSBlbWFuDQpOdW1iZXIgb2YgcGFnZXM6IDY1DQpVUkw6ICAgICAgICAgICAgIGh0dHA6Ly93 d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWlldGYtZW1hbi1mcmFtZXdvcmstMDcu dHh0DQpTdGF0dXM6ICAgICAgICAgIGh0dHA6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJh ZnQtaWV0Zi1lbWFuLWZyYW1ld29yaw0KSHRtbGl6ZWQ6ICAgICAgICBodHRwOi8vdG9vbHMuaWV0 Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWVtYW4tZnJhbWV3b3JrLTA3DQpEaWZmOiAgICAgICAgICAg IGh0dHA6Ly93d3cuaWV0Zi5vcmcvcmZjZGlmZj91cmwyPWRyYWZ0LWlldGYtZW1hbi1mcmFtZXdv cmstMDcNCg0KQWJzdHJhY3Q6DQogICAgICAgIFRoaXMgZG9jdW1lbnQgZGVmaW5lcyBhIGZyYW1l d29yayBmb3IgcHJvdmlkaW5nIEVuZXJneQ0KICAgICAgICBNYW5hZ2VtZW50IGZvciBkZXZpY2Vz IGFuZCBkZXZpY2UgY29tcG9uZW50cyB3aXRoaW4gb3INCiAgICAgICAgY29ubmVjdGVkIHRvIGNv bW11bmljYXRpb24gbmV0d29ya3MuICBUaGUgZnJhbWV3b3JrIGRlZmluZXMgYW4NCiAgICAgICAg RW5lcmd5IE1hbmFnZW1lbnQgRG9tYWluIGFzIGEgc2V0IG9mIEVuZXJneSBPYmplY3RzLCBmb3Ig d2hpY2gNCiAgICAgICAgZWFjaCBFbmVyZ3kgT2JqZWN0IGlzIGlkZW50aWZpZWQsIGNsYXNzaWZp ZWQgYW5kIGdpdmVuDQogICAgICAgIGNvbnRleHQuICAgRW5lcmd5IE9iamVjdHMgY2FuIGJlIG1v bml0b3JlZCBhbmQvb3IgY29udHJvbGxlZA0KICAgICAgICB3aXRoIHJlc3BlY3QgdG8gUG93ZXIs IFBvd2VyIFN0YXRlLCBFbmVyZ3ksIERlbWFuZCwgUG93ZXINCiAgICAgICAgQXR0cmlidXRlcywg YW5kIEJhdHRlcnkuICBBZGRpdGlvbmFsbHkgdGhlIGZyYW1ld29yayBtb2RlbHMNCiAgICAgICAg cmVsYXRpb25zaGlwcyBhbmQgY2FwYWJpbGl0aWVzIGJldHdlZW4gRW5lcmd5IE9iamVjdHMuDQoN CiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICANCg0KDQpUaGUgSUVURiBTZWNyZXRhcmlhdA0KDQo= From B.Hedstrom@CableLabs.com Mon Feb 25 08:48:56 2013 Return-Path: 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 E7F2A21F94CC for ; Mon, 25 Feb 2013 08:48:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.463 X-Spam-Level: X-Spam-Status: No, score=-0.463 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368] 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 H1QpshuSeyCi for ; Mon, 25 Feb 2013 08:48:56 -0800 (PST) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id E0A0721F94B2 for ; Mon, 25 Feb 2013 08:48:55 -0800 (PST) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.5/8.14.5) with ESMTP id r1PGmsv0018029; Mon, 25 Feb 2013 09:48:54 -0700 Received: from exchange.cablelabs.com (10.5.0.19) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com); Mon, 25 Feb 2013 09:48:54 -0700 (MST) X-Virus-Status: clean(F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com) Received: from EXCHANGE.cablelabs.com ([fe80::797a:96d1:3c53:18ee]) by EXCHANGE.cablelabs.com ([fe80::797a:96d1:3c53:18ee%11]) with mapi id 14.02.0328.009; Mon, 25 Feb 2013 09:48:54 -0700 From: Brian Hedstrom To: "Mouli Chandramouli (moulchan)" , "eman@ietf.org" Thread-Topic: Questions/Comments on EMAN MIBs Thread-Index: AQHOEGFlPS8kr/pc7EiVW5LqLSb8WZiKYHyggABuxgA= Date: Mon, 25 Feb 2013 16:48:52 +0000 Message-ID: <686B406F73B0F245AB30195F4E80E2D517F18071@EXCHANGE.cablelabs.com> In-Reply-To: <852AF0ED49D9F24BBBFA1B4DEEBE3BA4286C30B4@xmb-rcd-x08.cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.1.130117 x-originating-ip: [10.5.0.27] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Approved: ondar Subject: Re: [eman] Questions/Comments on EMAN MIBs X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2013 16:48:57 -0000 For the eoEnergyParametersTable, why not create a two index table: first index being the entPhysicalIndex (same index as the eoPowerTable), second index being the eoEnergyParametersIndex with a MAX-ACCESS of Not-Accessible. How many eoEnergyParametersIndex values can be supported per entPhysicalIndex? Thanks, Brian Hedstrom Senior Architect, Business & Operational Support Systems CableLabs, Inc. 858 Coal Creek Circle Louisville, CO 80027 Direct: 303.661.3829 eFax: 303.664.8120 Google+: brian.hedstrom Skype IM: brian.hedstrom b.hedstrom@cablelabs.com =20 On 2/25/13 4:17 AM, "Mouli Chandramouli (moulchan)" wrote: >Hello Brian, > >Replies inline.=20 > >Thanks >Mouli=20 > >-----Original Message----- >From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of >Brian Hedstrom >Sent: Friday, February 22, 2013 12:00 AM >To: eman@ietf.org >Subject: [eman] Questions/Comments on EMAN MIBs > >EMAN WG, >I have some comments/questions on the EMAN MIBs. > > >eoEnergyParametersTable: The indexing is confusing on this table. The >first object in the table, eoEnergyObjectIndex, is not an index to the >table. This is confusing alone since generally MIBs are constructing >with the indexes listed first in the tables. The second object in the >table, eoEnergyParametersIndex, is listed as an index to the table, but >does not have it's MAX-ACCESS listed as Not-Accessible. >[ycm] eoParametersIndex was introduced based on feedback from the WG >http://www.ietf.org/mail-archive/web/eman/current/msg01378.html >[ycm] on the need for collection of energy measurement using multiple >windowing schemes. >[ycm] With this indexing, for the same energy object with the same >eoEnergyObjectIndex , it is possible to have two different >eoEnergyParametersIndex >[ycm] for each eoEnergyParametersIndex it is possible to have a specific >windowing mechanism (total, or sliding, ...) for energy measurement >collection.=20 >[ycm] I believe it is permissible to have to index of the table is >accessible.=20 > >eoPowerStateEnterReason: should this be a read-create object? The table >does not have a row-status object to support read-create for the table >[ycm] Yes, the MAX-ACCESS for this object can be read-write with the >ownetstring syntax. > >eoProxyID: This is read-only. I'M not clear on how this table is used. >Should this table be a RowStatus read-create table to dynamically create >Relationships? > > >eoEnergyParametersIntervalMode INTEGER, <-- Corrected line >[ycm] Currently, it is defined as eoEnergyParametersIntervalMode >Integer32,=20 >[ycm] and we shall update in the definition. > > > >Thanks, > >Brian Hedstrom >Senior Architect, Business & Operational Support Systems CableLabs, Inc. >858 Coal Creek Circle >Louisville, CO 80027 >Direct: 303.661.3829 >eFax: 303.664.8120 >Google+: brian.hedstrom >Skype IM: brian.hedstrom >b.hedstrom@cablelabs.com > >=20 > From B.Hedstrom@CableLabs.com Mon Feb 25 09:07:15 2013 Return-Path: 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 6200B21F95D4 for ; Mon, 25 Feb 2013 09:07:15 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.462 X-Spam-Level: X-Spam-Status: No, score=-0.462 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, 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 CGT5DeGDuS-6 for ; Mon, 25 Feb 2013 09:07:15 -0800 (PST) Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by ietfa.amsl.com (Postfix) with ESMTP id 0D86D21F95C2 for ; Mon, 25 Feb 2013 09:07:13 -0800 (PST) Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.5/8.14.5) with ESMTP id r1PH7Dn0020164 for ; Mon, 25 Feb 2013 10:07:13 -0700 Received: from exchange.cablelabs.com (10.5.0.19) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com); Mon, 25 Feb 2013 10:07:13 -0700 (MST) X-Virus-Status: clean(F-Secure/fsigk_smtp/407/kyzyl.cablelabs.com) Received: from EXCHANGE.cablelabs.com ([fe80::797a:96d1:3c53:18ee]) by EXCHANGE.cablelabs.com ([fe80::797a:96d1:3c53:18ee%11]) with mapi id 14.02.0328.009; Mon, 25 Feb 2013 10:07:13 -0700 From: Brian Hedstrom To: "eman@ietf.org" Thread-Topic: gumDeviceTable in draft-suganuma-greenmib-01 Thread-Index: AQHOE3qN7MQSDYnT80yitrYvhX/GSA== Date: Mon, 25 Feb 2013 17:07:12 +0000 Message-ID: <686B406F73B0F245AB30195F4E80E2D517F18203@EXCHANGE.cablelabs.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.3.1.130117 x-originating-ip: [10.5.0.27] Content-Type: multipart/alternative; boundary="_000_686B406F73B0F245AB30195F4E80E2D517F18203EXCHANGEcablela_" MIME-Version: 1.0 X-Approved: ondar Subject: [eman] gumDeviceTable in draft-suganuma-greenmib-01 X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2013 17:07:15 -0000 --_000_686B406F73B0F245AB30195F4E80E2D517F18203EXCHANGEcablela_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable EMAN WG: In examining the gumDeviceTable, it doesn't look like this table would be r= equired, as the objects in this table could be derived from other existing = RFC MIBs, such as the ENTITY-MIB and IF-MIB. I don't think we want this MIB to stand alone, we'd want this MIB to link i= nto the ENTITY-MIB and/or IF-MIB. Since it's at the device level, most lik= ely link it into the ENTITY-MIB? Since we already have a set of other EMAN MIBs, could we place the four obj= ects from gumDevUsageTable into one of the existing EMAN MIBs? Thanks, Brian Hedstrom Senior Architect, Business & Operational Support Systems CableLabs, Inc. 858 Coal Creek Circle Louisville, CO 80027 Direct: 303.661.3829 eFax: 303.664.8120 Google+: brian.hedstrom Skype IM: brian.hedstrom b.hedstrom@cablelabs.com --_000_686B406F73B0F245AB30195F4E80E2D517F18203EXCHANGEcablela_ Content-Type: text/html; charset="us-ascii" Content-ID: <520E23DE4C3CE14A98E4D25AF0E8336A@cablelabs.com> Content-Transfer-Encoding: quoted-printable
EMAN WG:

In examining the gumDeviceTable, it doesn't look like this table would= be required, as the objects in this table could be derived from other exis= ting RFC MIBs, such as the ENTITY-MIB and IF-MIB.
I don't think we want this MIB to stand alone, we'd want this MIB to l= ink into the ENTITY-MIB and/or IF-MIB.  Since it's at the device level= , most likely link it into the ENTITY-MIB?

Since we already have a set of other EMAN MIBs, could we place the fou= r objects from gumDevUsageTable into one of the existing EMAN MIBs?

Thanks,

Brian Hedstrom
Senior Architect, Business & Operational Support Systems
CableLabs, Inc.
858 Coal Creek Circle
Louisville, CO 80027
Direct: 303.661.3829
eFax: 303.664.8120
Google+: brian.hedstrom
Skype IM: brian.hedstrom 
b.hedstrom@cablelabs.com=

To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 4.40 Message-ID: <20130225220200.30258.53945.idtracker@ietfa.amsl.com> Date: Mon, 25 Feb 2013 14:02:00 -0800 Cc: eman mailing list , eman chair , RFC Editor Subject: [eman] Protocol Action: 'Entity MIB (Version 4)' to Proposed Standard (draft-ietf-eman-rfc4133bis-06.txt) X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2013 22:02:02 -0000 The IESG has approved the following document: - 'Entity MIB (Version 4)' (draft-ietf-eman-rfc4133bis-06.txt) as Proposed Standard This document is the product of the Energy Management Working Group. The IESG contact persons are Benoit Claise and Ronald Bonica. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-eman-rfc4133bis/ Technical Summary This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing multiple logical and physical entities managed by a single SNMP agent. This document specifies a new version of the Entity MIB, which obsoletes version 3 [RFC4133]. Working Group Summary EMAN's meeting at IETF 83 (Paris) identified the need for this as a generic way to manage objects using a list of URIs. Mouli Chandramouli produced the -01 version in time for IETF 84, with co-editors Andy Bierman, Dan Romascanu and Juergen Quittek. The WG decided that this would provide a sensible base for the EMAN MIBs. Since then it has been discussed on the EMAN list; its WG Last Call was of its -03 version, from 11 to 29 October. The latest revision addresses concerns arising from the WGLC, the editors consider that it's now ready to publish. Document Quality Are there existing implementations of the protocol? It obsoletes RFC 4133, Entity MIB v3. Have a significant number of vendors indicated their plan to implement the specification? Don't know. Are there any reviewers that merit special mention as having done a thorough review, e.g., one that resulted in important changes or a conclusion that the document had no substantive issues? Juergen Schoenwalder was particularly helpful as a reviewer at WGLC though the changes srising were minor. If there was a MIB Doctor, Media Type or other expert review, what was its course (briefly)? Two of the draft's editors are on the MIB Doctors list, so is Juergen Schoenwalder. Personnel Who is the Document Shepherd? Who is the Responsible Area Director? Shepherd: Nevil Brownlee Area Director: Benoit Claise RFC Editor Note OLD: Their mis-configuration or disclosure may reveal sensitive information on assets or perturb the management of entities. NEW: Their mis-configuration or disclosure may reveal sensitive information on assets or perturb the management of entities, or could cause privacy issues if they allow tracking of values that are personally identifying. OLD: These objects expose information about the physical entities within a managed system, which may be used to identify the vendor, model, and version information of each system component. NEW: These objects expose information about the physical entities within a managed system, which may be used to identify the vendor, model, version and specific device identification information of each system component. From iesg-secretary@ietf.org Mon Feb 25 14:02:02 2013 Return-Path: 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 1327421E810B for ; Mon, 25 Feb 2013 14:02:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.537 X-Spam-Level: X-Spam-Status: No, score=-102.537 tagged_above=-999 required=5 tests=[AWL=0.062, BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 tAk5w6dcnXBw; Mon, 25 Feb 2013 14:02:01 -0800 (PST) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5491D21E8105; Mon, 25 Feb 2013 14:02:00 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IANA X-Test-IDTracker: no X-IETF-IDTracker: 4.40 X-IETF-Draft-string: draft-ietf-eman-rfc4133bis X-IETF-Draft-revision: 06 Message-ID: <20130225220200.30258.20901.idtracker@ietfa.amsl.com> Date: Mon, 25 Feb 2013 14:02:00 -0800 Cc: eman mailing list , eman chair , RFC Editor Subject: [eman] Protocol Action: 'Entity MIB (Version 4)' to Proposed Standard (draft-ietf-eman-rfc4133bis-06.txt) X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: noreply@ietf.org List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2013 22:02:02 -0000 The IESG has approved the following document: - 'Entity MIB (Version 4)' (draft-ietf-eman-rfc4133bis-06.txt) as Proposed Standard This document is the product of the Energy Management Working Group. The IESG contact persons are Benoit Claise and Ronald Bonica. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-eman-rfc4133bis/ Technical Summary This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing multiple logical and physical entities managed by a single SNMP agent. This document specifies a new version of the Entity MIB, which obsoletes version 3 [RFC4133]. Working Group Summary EMAN's meeting at IETF 83 (Paris) identified the need for this as a generic way to manage objects using a list of URIs. Mouli Chandramouli produced the -01 version in time for IETF 84, with co-editors Andy Bierman, Dan Romascanu and Juergen Quittek. The WG decided that this would provide a sensible base for the EMAN MIBs. Since then it has been discussed on the EMAN list; its WG Last Call was of its -03 version, from 11 to 29 October. The latest revision addresses concerns arising from the WGLC, the editors consider that it's now ready to publish. Document Quality Are there existing implementations of the protocol? It obsoletes RFC 4133, Entity MIB v3. Have a significant number of vendors indicated their plan to implement the specification? Don't know. Are there any reviewers that merit special mention as having done a thorough review, e.g., one that resulted in important changes or a conclusion that the document had no substantive issues? Juergen Schoenwalder was particularly helpful as a reviewer at WGLC though the changes srising were minor. If there was a MIB Doctor, Media Type or other expert review, what was its course (briefly)? Two of the draft's editors are on the MIB Doctors list, so is Juergen Schoenwalder. Personnel Who is the Document Shepherd? Who is the Responsible Area Director? Shepherd: Nevil Brownlee Area Director: Benoit Claise RFC Editor Note OLD: Their mis-configuration or disclosure may reveal sensitive information on assets or perturb the management of entities. NEW: Their mis-configuration or disclosure may reveal sensitive information on assets or perturb the management of entities, or could cause privacy issues if they allow tracking of values that are personally identifying. OLD: These objects expose information about the physical entities within a managed system, which may be used to identify the vendor, model, and version information of each system component. NEW: These objects expose information about the physical entities within a managed system, which may be used to identify the vendor, model, version and specific device identification information of each system component. From internet-drafts@ietf.org Mon Feb 25 15:05:49 2013 Return-Path: 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 625DD21E8142; Mon, 25 Feb 2013 15:05:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.533 X-Spam-Level: X-Spam-Status: No, score=-102.533 tagged_above=-999 required=5 tests=[AWL=0.066, BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 na5-znXy0I+V; Mon, 25 Feb 2013 15:05:49 -0800 (PST) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2BF51F0D0A; Mon, 25 Feb 2013 15:05:47 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.40 Message-ID: <20130225230547.19882.22273.idtracker@ietfa.amsl.com> Date: Mon, 25 Feb 2013 15:05:47 -0800 Cc: eman@ietf.org Subject: [eman] I-D Action: draft-ietf-eman-battery-mib-08.txt X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2013 23:05:49 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Energy Management Working Group of the IE= TF. Title : Definition of Managed Objects for Battery Monitoring Author(s) : Juergen Quittek Rolf Winter Thomas Dietz Filename : draft-ietf-eman-battery-mib-08.txt Pages : 30 Date : 2013-02-25 Abstract: This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines managed objects that provide information on the status of batteries in managed devices. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-eman-battery-mib There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-eman-battery-mib-08 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eman-battery-mib-08 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From Rolf.Winter@neclab.eu Mon Feb 25 15:13:13 2013 Return-Path: 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 104C921F905C for ; Mon, 25 Feb 2013 15:13:13 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.932 X-Spam-Level: X-Spam-Status: No, score=-103.932 tagged_above=-999 required=5 tests=[AWL=-0.333, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] 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 YPmDZnbbzjcH for ; Mon, 25 Feb 2013 15:13:12 -0800 (PST) Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) by ietfa.amsl.com (Postfix) with ESMTP id 3694921E8125 for ; Mon, 25 Feb 2013 15:13:12 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 9EE4110342D for ; Tue, 26 Feb 2013 00:13:11 +0100 (CET) X-Virus-Scanned: Amavisd on Debian GNU/Linux (netlab.nec.de) Received: from mailer1.neclab.eu ([127.0.0.1]) by localhost (atlas-a.office.hd [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gx3GBccjABwo for ; Tue, 26 Feb 2013 00:13:11 +0100 (CET) Received: from METHONE.office.hd (methone.office.hd [192.168.24.54]) by mailer1.neclab.eu (Postfix) with ESMTP id 7E8DB103410 for ; Tue, 26 Feb 2013 00:13:06 +0100 (CET) Received: from PALLENE.office.hd ([169.254.1.80]) by METHONE.office.hd ([192.168.24.54]) with mapi id 14.01.0323.003; Tue, 26 Feb 2013 00:12:45 +0100 From: Rolf Winter To: eman mailing list Thread-Topic: [eman] I-D Action: draft-ietf-eman-battery-mib-08.txt Thread-Index: AQHOE6zLxguiPDHAAUOz7c9tLJIjgJiLM2kg Date: Mon, 25 Feb 2013 23:12:20 +0000 Message-ID: <791AD3077F94194BB2BDD13565B6295D555CE6EE@PALLENE.office.hd> References: <20130225230547.19882.22273.idtracker@ietfa.amsl.com> In-Reply-To: <20130225230547.19882.22273.idtracker@ietfa.amsl.com> Accept-Language: en-US, de-DE Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.7.0.200] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [eman] I-D Action: draft-ietf-eman-battery-mib-08.txt X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2013 23:13:13 -0000 Hi, this version fixes the Unsigned64 problem that has been pointed out as well= as a number of text edits as suggested on the list.=20 Best, Rolf NEC Europe Ltd | Registered Office: Athene, Odyssey Business Park, West End= Road, London, HA4 6QE, GB | Registered in England 2832014 > -----Original Message----- > From: eman-bounces@ietf.org [mailto:eman-bounces@ietf.org] On Behalf Of > internet-drafts@ietf.org > Sent: Dienstag, 26. Februar 2013 00:06 > To: i-d-announce@ietf.org > Cc: eman@ietf.org > Subject: [eman] I-D Action: draft-ietf-eman-battery-mib-08.txt >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Energy Management Working Group of > the IETF. >=20 > Title : Definition of Managed Objects for Battery > Monitoring > Author(s) : Juergen Quittek > Rolf Winter > Thomas Dietz > Filename : draft-ietf-eman-battery-mib-08.txt > Pages : 30 > Date : 2013-02-25 >=20 > Abstract: > This memo defines a portion of the Management Information Base (MIB) > for use with network management protocols in the Internet community. > In particular, it defines managed objects that provide information > on > the status of batteries in managed devices. >=20 >=20 > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-eman-battery-mib >=20 > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-eman-battery-mib-08 >=20 > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eman-battery-mib-08 >=20 >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman From internet-drafts@ietf.org Mon Feb 25 15:36:35 2013 Return-Path: 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 A54B621F9350; Mon, 25 Feb 2013 15:36:35 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.536 X-Spam-Level: X-Spam-Status: No, score=-102.536 tagged_above=-999 required=5 tests=[AWL=0.063, BAYES_00=-2.599, USER_IN_WHITELIST=-100] 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 nMftXbnHXH2F; Mon, 25 Feb 2013 15:36:34 -0800 (PST) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CF5B21E8150; Mon, 25 Feb 2013 15:36:20 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.40 Message-ID: <20130225233619.5710.20145.idtracker@ietfa.amsl.com> Date: Mon, 25 Feb 2013 15:36:19 -0800 Cc: eman@ietf.org Subject: [eman] I-D Action: draft-ietf-eman-requirements-12.txt X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Feb 2013 23:36:35 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Energy Management Working Group of the IE= TF. Title : Requirements for Energy Management Author(s) : Juergen Quittek Mouli Chandramouli Rolf Winter Thomas Dietz Benoit Claise Filename : draft-ietf-eman-requirements-12.txt Pages : 27 Date : 2013-02-25 Abstract: This document defines requirements for standards specifications for energy management. The requirements defined in this document concern monitoring functions as well as control functions. Monitoring functions include identification of energy-managed devices and their components, monitoring of their power states, power inlets, power outlets, actual power, power properties, received energy, provided energy, and contained batteries. Control functions serve for controlling power supply and power state of energy-managed devices and their components. This document does not specify the features that must be implemented by compliant implementations but rather features that must be supported by standards for energy management. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-eman-requirements There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-eman-requirements-12 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-eman-requirements-12 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From bclaise@cisco.com Wed Feb 27 11:13:02 2013 Return-Path: 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 9DF5721F8AB4 for ; Wed, 27 Feb 2013 11:13:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.547 X-Spam-Level: X-Spam-Status: No, score=-10.547 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8] 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 ARsnoA6dTcXE for ; Wed, 27 Feb 2013 11:13:01 -0800 (PST) Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id A24B821F8611 for ; Wed, 27 Feb 2013 11:13:01 -0800 (PST) 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 r1RJCr49012622; Wed, 27 Feb 2013 20:12:53 +0100 (CET) Received: from [10.60.67.84] (ams-bclaise-8913.cisco.com [10.60.67.84]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r1RJC3Qv012148; Wed, 27 Feb 2013 20:12:13 +0100 (CET) Message-ID: <512E5A82.30102@cisco.com> Date: Wed, 27 Feb 2013 20:12:02 +0100 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: eman mailing list Content-Type: multipart/alternative; boundary="------------060506000908070507040403" Cc: "Frank_Sandoval@cable.comcast.com" Subject: [eman] SCTE and EMAN: requesting a presentation slot. X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Feb 2013 19:13:02 -0000 This is a multi-part message in MIME format. --------------060506000908070507040403 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Dear all, I had a call with SCTE yesterday. Frank, in the copy list, sent me this SCTE description, and could add some more information if needed: The Society of Cable Telecommunications Engineers (SCTE) is addressing energy management topics for the cable industry through its Smart Energy Management Initiative (SEMI). There are several sub-committees and working groups within SEMI, one of which is addressing energy measurement and management communications protocols. The scope of this group is to describe a logical Information Model that articulates the entities, attributes, and relationships supported by a wide variety of devices used within the cable environment, define a number of encoding and transport protocols that may be used to support the model, and provide a mapping between a specific protocol definition and the Information Model. There is a lot of overlap between this activity and the work of the IETF EMAN group. It is the hope of the SCTE working group to leverage the work occurring within the IETF to the greatest degree practical. Specifically, we hope to adopt the Information Model defined within the IETF. Members of the working group plan to participate in the IETF to further refine the information model. We discussed the EMAN and SCTE scopes and agreed that the two groups want to solve the same problem (as described by http://tools.ietf.org/html/draft-ietf-eman-requirements-12). The IETF EMAN charter mentions MIB modules (data model), but we all understand that what is key is the information model definition (see RFC 3444), and that future data models could exist in the future (NETCONF, IPFIX, you name it). And the EMAN framework contains precisely an information model, which is used as input for the MIB module specifications. See http://tools.ietf.org/html/draft-ietf-eman-framework-07#section-5 Brian, also in the copy list, reverse-engineering our MIB modules to create an UML based information model. SCTE was not aware of the information model definition in the EMAN framework. To tell the truth, it's true that it is a little hidden in the series of EMAN documents. It will be very valuable for EMAN to see Brian 's UML based information model, to understand if the object semantics are correctly defined, the information model shortcomings, and finally if we lack objects or use the wrong ones. The good news is that Brian will be attending the IETF. Nevil, Bruce, can you please organize a slot for Brian to present. Based on the discussion I had with the SCTE group, that discussion will be very valuable. Regards, Benoit --------------060506000908070507040403 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Dear all,

I had a call with SCTE yesterday.
Frank, in the copy list, sent me this SCTE description, and could add some more information if needed:

The Society of Cable Telecommunications Engineers (SCTE) is addressing energy management topics for the cable industry through its Smart Energy Management Initiative (SEMI). There are several sub-committees and working groups within SEMI, one of which is addressing energy measurement and management communications protocols. The scope of this group is to describe a logical Information Model that articulates the entities, attributes, and relationships supported by a wide variety of devices used within the cable environment, define a number of encoding and transport protocols that may be used to support the model, and provide a mapping between a specific protocol definition and the Information Model. There is a lot of overlap between this activity and the work of the IETF EMAN group. It is the hope of the SCTE working group to leverage the work occurring within the IETF to the greatest degree practical. Specifically, we hope to adopt the Information Model defined within the IETF. Members of the working group plan to participate in the IETF  to further refine the information model.
We discussed the EMAN and SCTE scopes and agreed that the two groups want to solve the same problem (as described by http://tools.ietf.org/html/draft-ietf-eman-requirements-12).
The IETF EMAN charter mentions MIB modules (data model), but we all understand that what is key is the information model definition (see RFC 3444), and that future data models could exist in the future (NETCONF, IPFIX, you name it).
And the EMAN framework contains precisely an information model, which is used as input for the MIB module specifications. See http://tools.ietf.org/html/draft-ietf-eman-framework-07#section-5

Brian, also in the copy list, reverse-engineering our MIB modules to create an UML based information model.
SCTE was not aware of the information model definition in the EMAN framework. To tell the truth, it's true that it is a little hidden in the series of EMAN documents.

It will be very valuable for EMAN to see Brian 's UML based information model, to understand if the object semantics are correctly defined, the information model shortcomings, and finally if we lack objects or use the wrong ones.

The good news is that Brian will be attending the IETF.
Nevil, Bruce, can you please organize a slot for Brian to present.
Based on the discussion I had with the SCTE group, that discussion will be very valuable.

Regards, Benoit





--------------060506000908070507040403-- From bclaise@cisco.com Thu Feb 28 00:47:43 2013 Return-Path: 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 6737C21F89CE for ; Thu, 28 Feb 2013 00:47:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.548 X-Spam-Level: X-Spam-Status: No, score=-10.548 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8] 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 M5GzQ+omAELP for ; Thu, 28 Feb 2013 00:47:42 -0800 (PST) Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by ietfa.amsl.com (Postfix) with ESMTP id C477D21F8518 for ; Thu, 28 Feb 2013 00:47:41 -0800 (PST) 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 r1S8lXPL026203; Thu, 28 Feb 2013 09:47:34 +0100 (CET) Received: from [10.149.0.70] (dhcp-10-149-0-70.cisco.com [10.149.0.70]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id r1S8kgUQ022092; Thu, 28 Feb 2013 09:46:52 +0100 (CET) Message-ID: <512F1972.8020100@cisco.com> Date: Thu, 28 Feb 2013 09:46:42 +0100 From: Benoit Claise User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: eman mailing list References: <512E5A82.30102@cisco.com> In-Reply-To: <512E5A82.30102@cisco.com> Content-Type: multipart/alternative; boundary="------------020504040005080306080809" Cc: "Frank_Sandoval@cable.comcast.com" Subject: Re: [eman] SCTE and EMAN: requesting a presentation slot. X-BeenThere: eman@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Discussions about the Energy Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Feb 2013 08:47:43 -0000 This is a multi-part message in MIME format. --------------020504040005080306080809 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit And Brian is now in the copy list, just in case you're wondering which Brian I speak about. Note that Brian already subscribed to the mailing list. Regards, Benoit > Dear all, > > I had a call with SCTE yesterday. > Frank, in the copy list, sent me this SCTE description, and could add > some more information if needed: > > The Society of Cable Telecommunications Engineers (SCTE) is > addressing energy management topics for the cable industry through > its Smart Energy Management Initiative (SEMI). There are several > sub-committees and working groups within SEMI, one of which is > addressing energy measurement and management communications > protocols. The scope of this group is to describe a logical > Information Model that articulates the entities, attributes, and > relationships supported by a wide variety of devices used within > the cable environment, define a number of encoding and transport > protocols that may be used to support the model, and provide a > mapping between a specific protocol definition and the Information > Model. There is a lot of overlap between this activity and the > work of the IETF EMAN group. It is the hope of the SCTE working > group to leverage the work occurring within the IETF to the > greatest degree practical. Specifically, we hope to adopt the > Information Model defined within the IETF. Members of the working > group plan to participate in the IETF to further refine the > information model. > > We discussed the EMAN and SCTE scopes and agreed that the two groups > want to solve the same problem (as described by > http://tools.ietf.org/html/draft-ietf-eman-requirements-12). > The IETF EMAN charter mentions MIB modules (data model), but we all > understand that what is key is the information model definition (see > RFC 3444), and that future data models could exist in the future > (NETCONF, IPFIX, you name it). > And the EMAN framework contains precisely an information model, which > is used as input for the MIB module specifications. See > http://tools.ietf.org/html/draft-ietf-eman-framework-07#section-5 > > Brian, also in the copy list, reverse-engineering our MIB modules to > create an UML based information model. > SCTE was not aware of the information model definition in the EMAN > framework. To tell the truth, it's true that it is a little hidden in > the series of EMAN documents. > > It will be very valuable for EMAN to see Brian 's UML based > information model, to understand if the object semantics are correctly > defined, the information model shortcomings, and finally if we lack > objects or use the wrong ones. > > The good news is that Brian will be attending the IETF. > Nevil, Bruce, can you please organize a slot for Brian to present. > Based on the discussion I had with the SCTE group, that discussion > will be very valuable. > > Regards, Benoit > > > > > > > > _______________________________________________ > eman mailing list > eman@ietf.org > https://www.ietf.org/mailman/listinfo/eman --------------020504040005080306080809 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
And Brian is now in the copy list, just in case you're wondering which Brian I speak about.
Note that Brian already subscribed to the mailing list.

Regards, Benoit
Dear all,

I had a call with SCTE yesterday.
Frank, in the copy list, sent me this SCTE description, and could add some more information if needed:
The Society of Cable Telecommunications Engineers (SCTE) is addressing energy management topics for the cable industry through its Smart Energy Management Initiative (SEMI). There are several sub-committees and working groups within SEMI, one of which is addressing energy measurement and management communications protocols. The scope of this group is to describe a logical Information Model that articulates the entities, attributes, and relationships supported by a wide variety of devices used within the cable environment, define a number of encoding and transport protocols that may be used to support the model, and provide a mapping between a specific protocol definition and the Information Model. There is a lot of overlap between this activity and the work of the IETF EMAN group. It is the hope of the SCTE working group to leverage the work occurring within the IETF to the greatest degree practical. Specifically, we hope to adopt the Information Model defined within the IETF. Members of the working group plan to participate in the IETF  to further refine the information model.
We discussed the EMAN and SCTE scopes and agreed that the two groups want to solve the same problem (as described by http://tools.ietf.org/html/draft-ietf-eman-requirements-12).
The IETF EMAN charter mentions MIB modules (data model), but we all understand that what is key is the information model definition (see RFC 3444), and that future data models could exist in the future (NETCONF, IPFIX, you name it).
And the EMAN framework contains precisely an information model, which is used as input for the MIB module specifications. See http://tools.ietf.org/html/draft-ietf-eman-framework-07#section-5

Brian, also in the copy list, reverse-engineering our MIB modules to create an UML based information model.
SCTE was not aware of the information model definition in the EMAN framework. To tell the truth, it's true that it is a little hidden in the series of EMAN documents.

It will be very valuable for EMAN to see Brian 's UML based information model, to understand if the object semantics are correctly defined, the information model shortcomings, and finally if we lack objects or use the wrong ones.

The good news is that Brian will be attending the IETF.
Nevil, Bruce, can you please organize a slot for Brian to present.
Based on the discussion I had with the SCTE group, that discussion will be very valuable.

Regards, Benoit







_______________________________________________
eman mailing list
eman@ietf.org
https://www.ietf.org/mailman/listinfo/eman

--------------020504040005080306080809--