
From nobody Thu Sep  4 17:30:39 2014
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: eman@ietfa.amsl.com
Delivered-To: eman@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 913901A02E9; Thu,  4 Sep 2014 17:30:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.57
X-Spam-Level: 
X-Spam-Status: No, score=-107.57 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZVGVgHrTbulb; Thu,  4 Sep 2014 17:30:34 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id BE75E1A02F3; Thu,  4 Sep 2014 17:30:34 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id AEF5E180015; Thu,  4 Sep 2014 17:29:45 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140905002945.AEF5E180015@rfc-editor.org>
Date: Thu,  4 Sep 2014 17:29:45 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/eman/TQqmhyaIcqbcCLyxvaK5JQ7fmFM
Cc: drafts-update-ref@iana.org, eman@ietf.org, rfc-editor@rfc-editor.org
Subject: [eman] RFC 7326 on Energy Management Framework
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman/>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Sep 2014 00:30:36 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7326

        Title:      Energy Management Framework 
        Author:     J. Parello, B. Claise,
                    B. Schoening, J. Quittek
        Status:     Informational
        Stream:     IETF
        Date:       September 2014
        Mailbox:    jparello@cisco.com, 
                    bclaise@cisco.com, 
                    brad.schoening@verizon.net,
                    quittek@netlab.nec.de
        Pages:      54
        Characters: 107145
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-eman-framework-19.txt

        URL:        https://www.rfc-editor.org/rfc/rfc7326.txt

This document defines a framework for Energy Management (EMAN) for
devices and device components within, or connected to, communication
networks.  The framework presents a physical reference model and
information model.  The information model consists of an
Energy Management Domain as a set of Energy Objects.  Each Energy
Object can be attributed with identity, classification, and context.
Energy Objects can be monitored and controlled with respect to power,
Power State, energy, demand, Power Attributes, and battery.
Additionally, the framework models relationships and capabilities
between Energy Objects.

This document is a product of the Energy Management Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Mon Sep  8 20:44:47 2014
Return-Path: <n.brownlee@auckland.ac.nz>
X-Original-To: eman@ietfa.amsl.com
Delivered-To: eman@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68DA81A06E7 for <eman@ietfa.amsl.com>; Mon,  8 Sep 2014 20:44:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.253
X-Spam-Level: 
X-Spam-Status: No, score=-3.253 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jb1z-eQQz6W9 for <eman@ietfa.amsl.com>; Mon,  8 Sep 2014 20:44:44 -0700 (PDT)
Received: from mx2.auckland.ac.nz (mx2.auckland.ac.nz [130.216.125.245]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA6B91A06BC for <eman@ietf.org>; Mon,  8 Sep 2014 20:44:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=uoa; t=1410234281; x=1441770281; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=8JiVM8ESZF7RGwXq8Ti5MKMZ6NFY8tiVEPtysdOm8j0=; b=dlQ9UowlYSioBaeffX6AGRH0SvxumU3JqcYLDuNfRM4+2Z4oQmUchzSS eX6sPSfeHQ66DpMXH4nSAnkZ797+OWfZ3IRFmOTHUPEifEGJp7MEOXmqe KMwNDTUo0gd9SfD0bwjxoOGzkxjax5j+9d6vvn+BQLVPt551lAW7Ugr8T A=;
X-IronPort-AV: E=Sophos;i="5.04,490,1406548800"; d="scan'208";a="274956686"
X-Ironport-HAT: UNIVERSITY - $RELAY-THROTTLE
X-Ironport-Source: 130.216.38.131 - Outgoing - Outgoing-SSL
Received: from nevil-laptop1.sfac.auckland.ac.nz (HELO [130.216.38.131]) ([130.216.38.131]) by mx2-int.auckland.ac.nz with ESMTP; 09 Sep 2014 15:44:33 +1200
Message-ID: <540E779F.9020107@auckland.ac.nz>
Date: Tue, 09 Sep 2014 15:44:31 +1200
From: Nevil Brownlee <n.brownlee@auckland.ac.nz>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "eman@ietf.org" <eman@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/eman/vJ6HDVdPv2kpPFi1gkJJbAARcl4
Subject: [eman] Energy Management Framework is now RFC 326
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman/>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Sep 2014 03:44:46 -0000

Congratulations to the document authors, and all those who have 
contributed to its development over the last few years.

Cheers, Nevil :-)

-- 
---------------------------------------------------------------------
  Nevil Brownlee                          Computer Science Department
  Phone: +64 9 373 7599 x88941             The University of Auckland
  FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand


From nobody Mon Sep  8 20:49:52 2014
Return-Path: <n.brownlee@auckland.ac.nz>
X-Original-To: eman@ietfa.amsl.com
Delivered-To: eman@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DC8F1A06C3 for <eman@ietfa.amsl.com>; Mon,  8 Sep 2014 20:49:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.953
X-Spam-Level: 
X-Spam-Status: No, score=-5.953 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QFNL06hzLV0f for <eman@ietfa.amsl.com>; Mon,  8 Sep 2014 20:49:50 -0700 (PDT)
Received: from mx2.auckland.ac.nz (mx2.auckland.ac.nz [130.216.125.245]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 360F11A048F for <eman@ietf.org>; Mon,  8 Sep 2014 20:49:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=uoa; t=1410234590; x=1441770590; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=rY9Sd1f1VwNxaR9nXU4cOJwQhxCQkOFhmi+MjOVmlK0=; b=Ej+3eZZfCzBfVeNF1HuCol67GLkE0lRm6JBxTxpXSJo0Mcc/cwr+PMJm 0fib5uUEhwMVKV6YCU2P5aZ5bYyPOhd7ngz+CXPQQZb7OqYE9vHHFi6Vk 4q8tfBJ4fBOZgWSFJarbEkJ0QMDuyvEAEwmvGQHe4AGzpxpSbfLhoMC0Q s=;
X-IronPort-AV: E=Sophos;i="5.04,490,1406548800"; d="scan'208";a="274957669"
X-Ironport-HAT: UNIVERSITY - $RELAY-THROTTLE
X-Ironport-Source: 130.216.38.131 - Outgoing - Outgoing-SSL
Received: from nevil-laptop1.sfac.auckland.ac.nz (HELO [130.216.38.131]) ([130.216.38.131]) by mx2-int.auckland.ac.nz with ESMTP; 09 Sep 2014 15:49:48 +1200
Message-ID: <540E78DC.4040001@auckland.ac.nz>
Date: Tue, 09 Sep 2014 15:49:48 +1200
From: Nevil Brownlee <n.brownlee@auckland.ac.nz>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "eman@ietf.org" <eman@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/eman/FzmmD9vtcd6KPW-0ic7eWhV4_U0
Subject: [eman]  Energy Management Framework is now RFC 7326
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman/>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Sep 2014 03:49:51 -0000

Hi again all:

Of course my subject line should have said RFC 7326 !

Congratulations to the document authors, and all those who have 
contributed to its development over the last few years.

Cheers, Nevil

-- 
---------------------------------------------------------------------
  Nevil Brownlee                          Computer Science Department
  Phone: +64 9 373 7599 x88941             The University of Auckland
  FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand


From nobody Tue Sep  9 07:19:20 2014
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: eman@ietfa.amsl.com
Delivered-To: eman@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 338A61A0B77 for <eman@ietfa.amsl.com>; Tue,  9 Sep 2014 07:19:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.554
X-Spam-Level: 
X-Spam-Status: No, score=-3.554 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.652, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HmfHhW_zg6xD for <eman@ietfa.amsl.com>; Tue,  9 Sep 2014 07:19:16 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 80BB01A6F9D for <eman@ietf.org>; Tue,  9 Sep 2014 07:18:41 -0700 (PDT)
Received: from [10.100.150.186] (unknown [144.49.132.3]) by lucidvision.com (Postfix) with ESMTP id 004C32882696; Tue,  9 Sep 2014 10:18:40 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Thomas Nadeau <tnadeau@lucidvision.com>
X-Mailer: iPhone Mail (11D257)
In-Reply-To: <540E78DC.4040001@auckland.ac.nz>
Date: Tue, 9 Sep 2014 07:18:40 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <0F8DC82F-02C0-4FE9-A38A-DE9D0536D275@lucidvision.com>
References: <540E78DC.4040001@auckland.ac.nz>
To: Nevil Brownlee <n.brownlee@auckland.ac.nz>
Archived-At: http://mailarchive.ietf.org/arch/msg/eman/UOByfHAd2ZAU3oJ4Axc1d8_moIc
Cc: "eman@ietf.org" <eman@ietf.org>
Subject: Re: [eman] Energy Management Framework is now RFC 7326
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman/>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Sep 2014 14:19:18 -0000

Cool! Thanks for the hard work everyone !

Tom=20
=20

> On Sep 8, 2014, at 8:49 PM, Nevil Brownlee <n.brownlee@auckland.ac.nz> wro=
te:
>=20
>=20
> Hi again all:
>=20
> Of course my subject line should have said RFC 7326 !
>=20
> Congratulations to the document authors, and all those who have contribute=
d to its development over the last few years.
>=20
> Cheers, Nevil
>=20
> --=20
> ---------------------------------------------------------------------
> Nevil Brownlee                          Computer Science Department
> Phone: +64 9 373 7599 x88941             The University of Auckland
> FAX: +64 9 373 7453   Private Bag 92019, Auckland 1142, New Zealand
>=20
> _______________________________________________
> eman mailing list
> eman@ietf.org
> https://www.ietf.org/mailman/listinfo/eman
>=20


From nobody Tue Sep  9 07:39:38 2014
Return-Path: <Quittek@neclab.eu>
X-Original-To: eman@ietfa.amsl.com
Delivered-To: eman@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6E471A0AE9 for <eman@ietfa.amsl.com>; Tue,  9 Sep 2014 07:39:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.254
X-Spam-Level: 
X-Spam-Status: No, score=-4.254 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.652, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hZ6W60P24c1Y for <eman@ietfa.amsl.com>; Tue,  9 Sep 2014 07:39:35 -0700 (PDT)
Received: from mailer1.neclab.eu (mailer1.neclab.eu [195.37.70.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12B631A6FD0 for <eman@ietf.org>; Tue,  9 Sep 2014 07:39:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailer1.neclab.eu (Postfix) with ESMTP id 74329107E82; Tue,  9 Sep 2014 16:39:29 +0200 (CEST)
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 8FboKCG8b0dS; Tue,  9 Sep 2014 16:39:29 +0200 (CEST)
X-ENC: Last-Hop-TLS-encrypted
X-ENC: Last-Hop-TLS-encrypted
Received: from ENCELADUS.office.hd (enceladus.office.hd [192.168.24.52]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailer1.neclab.eu (Postfix) with ESMTPS id 57B82107E7B; Tue,  9 Sep 2014 16:39:25 +0200 (CEST)
Received: from PALLENE.office.hd ([169.254.1.182]) by ENCELADUS.office.hd ([192.168.24.52]) with mapi id 14.01.0323.003; Tue, 9 Sep 2014 16:39:25 +0200
From: Juergen Quittek <Quittek@neclab.eu>
To: Alan Luchuk <luchuk@snmp.com>, "eman@ietf.org" <eman@ietf.org>
Thread-Topic: [eman] Comments on draft-ietf-eman-battery-mib-12
Thread-Index: AQHPPhybEdWlCCzcRUOaKUrpt9HQRpv59myg
Date: Tue, 9 Sep 2014 14:39:24 +0000
Message-ID: <9AB93E4127C26F4BA7829DEFDCE5A6E894C4AADA@PALLENE.office.hd>
References: <201403121757.NAA24671@adminfs.snmp.com>
In-Reply-To: <201403121757.NAA24671@adminfs.snmp.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.99.69]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/eman/mVETSNlCdpCqz4rYpmCTcjrr6zM
Subject: Re: [eman] Comments on draft-ietf-eman-battery-mib-12
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman/>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Sep 2014 14:39:37 -0000

Dear Alan,
Here comes a very late reply on your message. It got lost in our records, b=
ecause at that time you had two sets of comments and I found a message from=
 you at that time stating "thank you for considering my comments". But you =
message was referring to another set. Fortunately, Benoit discovered that y=
our comments have not been included and I come back to them right now.=20

Your comments are highly appreciated and I agree on most of them. The next =
version -14 will include according changes.=20

There is only a comment that I am not sure how to deal with it. It concerns=
 the Unsigned64TC for capacity. Please find a reply inline below.=20

Best regards,
    Juergen


> -----Original Message-----
> From: eman [mailto:eman-bounces@ietf.org] On Behalf Of Alan Luchuk
> Sent: Mittwoch, 12. M=E4rz 2014 18:57
> To: eman@ietf.org
> Subject: [eman] Comments on draft-ietf-eman-battery-mib-12
>=20
> Hello,
>=20
> Here are comments on  draft-ietf-eman-battery-mib-12.txt.  I think only t=
he
> last issue in the list may be a true problem; it is easily fixed.  There =
is one
> technical issue that might be worthy of further consideration.  The rest =
are
> these are typos or grammatical nits.
>=20
> I hope these are helpful to the EMAN WG.
>=20
> Regards,
> --Alan
>=20
>=20
>=20
> Page 3, Introduction  (typo)
> ----------------------------
>=20
> The second paragraph from the bottom contains the sentence:
>=20
>    Many battery-driven devices have existing instrumentation for
>    monitoring the battery status, because this is already needed for
>    local control of the battery by the device.
>=20
> I think the comma is not needed; perhaps the sentence should read:
>=20
>    Many battery-driven devices have existing instrumentation for
>    monitoring the battery status because this is already needed for
>    local control of the battery by the device.
>=20
>=20
>=20
> Page 4, Introduction (typo)
> ---------------------------
>=20
> The first paragraph from the top contains the sentence:
>=20
>    The former allows tracing a battery and allows continuous monitoring
>    even if the battery is e.g. installed in another device."
>=20
> I think the "e.g." is not needed; perhaps the sentence should read:
>=20
>    The former allows tracing a battery and allows continuous monitoring
>    even if the battery is installed in another device."
>=20
>=20
>=20
> Page 5, MIB Module Structure (grammer)
> --------------------------------------
>=20
> The third paragraph from the top reads:
>=20
>    If batteries are replaced, and the replacing battery uses the same
>       ^^^^^^^^^^^^^                   ^^^^^^^^^^^^^^^^^
>    physical connector as the replaced battery, then the replacing
>    battery SHOULD be indexed with the same value of object
>    entPhysicalIndex as the replaced battery.
>=20
> In the first clause the subject is plural, in the second clause, the subj=
ect is
> singular.  Perhaps the sentence should read:
>=20
>    If a battery is replaced, and the replacing battery uses the same
>       ^^^^^^^^^^^^                   ^^^^^^^^^^^^^^^^^
>    physical connector as the replaced battery, then the replacing
>    battery SHOULD be indexed with the same value of object
>    entPhysicalIndex as the replaced battery.
>=20
> The same text appears in the description clause for the batteryTable on p=
age
> 10.
>=20
>=20
>=20
> Page 5, MIB Module Structure (nit)
> ----------------------------------
>=20
> The last paragraph on page 5 and the first paragraph on page 6 mention th=
ree
> groups of objects:  objects with OIDs ending with 1-10, objects with OIDs
> ending with 11-18, and objects with OIDs ending with 20-25.
>=20
> The  batteryCellIdentifier object ends with SID 19 and is not included in=
 any of
> the three groups.
>=20
>=20
>=20
> Page 13, DESCRIPTION for batteryTechnology
> ------------------------------------------
>=20
> The DESCRIPTION for batteryTechnology reads:
>=20
>    "This object indicates the technology used by the battery.
>    Numbers identifying battery types are registered at IANA.
>    A current list of assignments can be found at
>    <http://www.iana.org/assignments/eman>.
>=20
>    Value 0 (unknown) MUST be used if the type of battery
>    cannot be determined.
>=20
>    Value 1 (other) can be used if the battery type is known
>    but not one of the types already registered at IANA."
>=20
> I tried to access the URL shown above, and could not.  I assume it has
> not yet been created by IANA.
>=20
> Also, the values and enumeration names do not match the table shown in
> section 3.2 on page 7.  I think this part of the DESCRIPTION should read:
>=20
>    "Value 1 (unknown) MUST be used if the type of battery
>    cannot be determined.
>=20
>    Value 2 (other) can be used if the battery type is known
>    but not one of the types already registered at IANA."
>=20
>=20
>=20
> Page 14, batteryMaxChargingCurrent (possible technical issue)
> -------------------------------------------------------------
>=20
> Between drafts -11 and -12, the battery capacity values were increased
> in size from an Unsigned32 to an Unsigned64TC to accomodate very high
> capacity batteries.
>=20
> For batteries with a capacity large enough to require an Unsigned64TC
> is it sufficient to have a  batteryMaxChargingCurrent  limited to an
> Unsigned32?
>=20
> For example, if a battery is ever built that has a capacity that must be
> reported with the maximum value of the Unsigned64TC
> batteryDesignCapacity,
> the maximum allowed charging current for that battery might be too large
> to report with the Unsigned32 batteryMaxChargingCurrent.
>=20
>=20
> This same issue might apply to the  batteryTrickleChargingCurrent MIB
> object on Page 14, as well as the  batteryActualCurrent  MIB object on
> Page 19.
>=20
>=20
> Not sure what the best course of action is here.

We could do so, but then we have to change further objects related to
The current including batteryActualCurrent which is a signed integer.
We do not yet have a TC for Integer64.

>=20
> Page 16, DESCRIPTION for batteryChargingCycleCount
> --------------------------------------------------
>=20
> The second paragraph of the DESCRIPTION for batteryChargingCycleCount
> reads:
>=20
>    "For batteries of type primary(1) the value of this object is
>    always 0."
>=20
> This enumeration name/number does not match the enumerated values
> listed
> for the  batteryType  MIB object on page 12/13:
>=20
>    batteryType OBJECT-TYPE
>        SYNTAX      INTEGER {
>                        unknown(1),
>                        other(2),
>                        primary(3),
>                        rechargeable(4),
>                        capacitor(5)
>                    }
>=20
> Also, I think the charging cycle count only applies to a  batteryType  of
> rechargeable(4), so would rewording this second paragraph make sense?
>=20
>    "For batteries of any type other than rechargeable(4), the value of
>     this object is always 0."
>=20
>=20
>=20
> Page 17, DESCRIPTION for batteryChargingAdminState (nit)
> --------------------------------------------------------
>=20
> The first sentence of the first paragraph of the DESCRIPTION for
> batteryChargingAdminState reads:
>=20
>    "The value of this object indicates the desired status of
>    the charging state of the battery.
>=20
> Perhaps the following text is a little more concise:
>=20
>    "The value of this object indicates the desired charging
>    state of the battery.
>=20
>=20
>=20
> Page 28, batteryTemperatureNotification (problem)
> -------------------------------------------------
>=20
>    OBJECT batteryTemperatureNotification
>    MIN-ACCESS  read-only
>    DESCRIPTION
>        "A compliant implementation is not required
>        to support set operations to this object."
>=20
> A MIB checker squawked about  batteryTemperatureNotification  is not
> defined as an OBJECT-TYPE.
>=20
>=20
> Should this be removed from the BATTERY-MIB?

Good catch: This should have been an object.
I will replace batteryTemperatureNotification =20
with batteryAlarmHighTemperature.

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


From nobody Wed Sep 24 21:14:49 2014
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: eman@ietfa.amsl.com
Delivered-To: eman@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63FCB1A0117 for <eman@ietfa.amsl.com>; Wed, 24 Sep 2014 20:23:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.688
X-Spam-Level: 
X-Spam-Status: No, score=-102.688 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nYlL_u07yVuT for <eman@ietfa.amsl.com>; Wed, 24 Sep 2014 20:23:37 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 7A9951A0103 for <eman@ietf.org>; Wed, 24 Sep 2014 20:23:37 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D5C60181C6B; Wed, 24 Sep 2014 20:23:25 -0700 (PDT)
To: andy@yumaworks.com, dromasca@avaya.com, quittek@neclab.eu, moulchan@cisco.com, bclaise@cisco.com, joelja@bogus.com, n.brownlee@auckland.ac.nz, tnadeau@lucidvision.com
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140925032325.D5C60181C6B@rfc-editor.org>
Date: Wed, 24 Sep 2014 20:23:25 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/eman/4dTH5nCoNvZ3YyUYY454njN1yrA
X-Mailman-Approved-At: Wed, 24 Sep 2014 21:14:46 -0700
Cc: rfox@iconectiv.com, eman@ietf.org, rfc-editor@rfc-editor.org
Subject: [eman] [Technical Errata Reported] RFC6933 (4122)
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman/>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Sep 2014 03:23:39 -0000

The following errata report has been submitted for RFC6933,
"Entity MIB (Version 4)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6933&eid=4122

--------------------------------------
Type: Technical
Reported by: Robert Fox <rfox@iconectiv.com>

Section: 2.12.1

Original Text
-------------
The URN namespace for CLEIs is defined in [RFC4152], and the CLEI format
is defined in [T1.213] and [T1.213a]. For example, an entPhysicalUris 
instance may have the value of:

URN:CLEI:D4CE18B7AA

[RFC3986] and [RFC4152] identify this as a URI in the CLEI URN 
namespace. The specific CLEI code, D4CE18B7AA, is based on the 
example provided in [T1.213a].


Corrected Text
--------------
The URN namespace for CLEIs is defined in [RFC4152], and the CLEI format
is defined in [ATIS-0300213]. For example, an entPhysicalUris instance
may have the value of:

URN:CLEI:IPUIADEUAA

[RFC3986] and [RFC4152] identify this as a URI in the CLEI URN 
namespace. The specific CLEI code, IPUIADEUAA, is based on the 
example provided in [ATIS-0300213].


Notes
-----
The ATIS standards T1.213 and T1.213a are obsolete and have 
been replaced by ATIS-0300213. The example in ATIS-0300213 uses a 
different CLEI Code, IPUIADEUAA

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6933 (draft-ietf-eman-rfc4133bis-06)
--------------------------------------
Title               : Entity MIB (Version 4)
Publication Date    : May 2013
Author(s)           : A. Bierman, D. Romascanu, J. Quittek, M. Chandramouli
Category            : PROPOSED STANDARD
Source              : Energy Management
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG


From nobody Wed Sep 24 21:14:53 2014
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: eman@ietfa.amsl.com
Delivered-To: eman@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40C621A01E7 for <eman@ietfa.amsl.com>; Wed, 24 Sep 2014 20:38:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.688
X-Spam-Level: 
X-Spam-Status: No, score=-107.688 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5GI_XJJw5WJI for <eman@ietfa.amsl.com>; Wed, 24 Sep 2014 20:38:21 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 7A1641A0164 for <eman@ietf.org>; Wed, 24 Sep 2014 20:38:21 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BD5DE181C69; Wed, 24 Sep 2014 20:38:09 -0700 (PDT)
To: andy@yumaworks.com, dromasca@avaya.com, quittek@neclab.eu, moulchan@cisco.com, bclaise@cisco.com, joelja@bogus.com, n.brownlee@auckland.ac.nz, tnadeau@lucidvision.com
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140925033809.BD5DE181C69@rfc-editor.org>
Date: Wed, 24 Sep 2014 20:38:09 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/eman/fe1_5sic_FHWUSsGZnqAsS6AlWY
X-Mailman-Approved-At: Wed, 24 Sep 2014 21:14:46 -0700
Cc: rfox@iconectiv.com, eman@ietf.org, rfc-editor@rfc-editor.org
Subject: [eman] [Editorial Errata Reported] RFC6933 (4123)
X-BeenThere: eman@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussions about the Energy Management Working Group <eman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eman>, <mailto:eman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eman/>
List-Post: <mailto:eman@ietf.org>
List-Help: <mailto:eman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eman>, <mailto:eman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Sep 2014 03:38:24 -0000

The following errata report has been submitted for RFC6933,
"Entity MIB (Version 4)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6933&eid=4123

--------------------------------------
Type: Editorial
Reported by: Robert Fox <rfox@iconectiv.com>

Section: 8.2

Original Text
-------------
[T1.213] ATIS T1.213-2001, "Coded Identification of Equipment
Entities in the North American Telecommunications
System for Information Exchange", 2001, <www.ansi.org>.

[T1.213a] ATIS T1.213a, "Supplement to T1.213-2001, Coded
Identification of Equipment Entities in the North
American Telecommunications System for Information
Exchange, to Correct the Representation of the Basic
Code in Figure B.1", 2001, <www.ansi.org>.

Corrected Text
--------------
[ATIS-0300213] ATIS-0300213, "Structure for the 
Identification of Equipment Entities for Information 
Exchange", 2006, <www.ansi.org>.


Notes
-----
The ATIS standards T1.213 and T1.213a are obsolete and have 
been replaced by ATIS-0300213.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6933 (draft-ietf-eman-rfc4133bis-06)
--------------------------------------
Title               : Entity MIB (Version 4)
Publication Date    : May 2013
Author(s)           : A. Bierman, D. Romascanu, J. Quittek, M. Chandramouli
Category            : PROPOSED STANDARD
Source              : Energy Management
Area                : Operations and Management
Stream              : IETF
Verifying Party     : IESG

