datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Definition of Managed Objects for Battery Monitoring
draft-ietf-eman-battery-mib-08

Active Internet-Draft (eman WG)
Document Stream: IETF
Last updated: 2013-02-25
Replaces: draft-quittek-eman-battery-mib
Intended RFC status: (None)
Other versions: plain text, pdf, html

IETF State: WG Document (eman)
Document shepherd:Dan Romascanu
Shepherd writeup
Consensus:Unknown

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Network Working Group                                         J. Quittek
Internet-Draft                                                 R. Winter
Intended status: Standards Track                                T. Dietz
Expires: August 29, 2013                                 NEC Europe Ltd.
                                                       February 25, 2013

          Definition of Managed Objects for Battery Monitoring
                     draft-ietf-eman-battery-mib-08

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.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 29, 2013.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Quittek, et al.          Expires August 29, 2013                [Page 1]
Internet-Draft                 Battery MIB                 February 2013

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3

   2.  The Internet-Standard Management Framework . . . . . . . . . .  4

   3.  Design of the Battery MIB Module . . . . . . . . . . . . . . .  5
     3.1.  MIB Module Structure . . . . . . . . . . . . . . . . . . .  5
     3.2.  Battery Technologies . . . . . . . . . . . . . . . . . . .  6
     3.3.  Charging Cycles  . . . . . . . . . . . . . . . . . . . . .  7

   4.  Definitions  . . . . . . . . . . . . . . . . . . . . . . . . .  8

   5.  Security Considerations  . . . . . . . . . . . . . . . . . . . 25

   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 27
     6.1.  SMI Object Identifier Registration . . . . . . . . . . . . 27
     6.2.  Battery Technology Registration  . . . . . . . . . . . . . 27

   7.  Open Issues  . . . . . . . . . . . . . . . . . . . . . . . . . 28
     7.1.  Entity MIB augmentation  . . . . . . . . . . . . . . . . . 28
     7.2.  Kind of entity . . . . . . . . . . . . . . . . . . . . . . 28
     7.3.  Voltage and temperature per cell?  . . . . . . . . . . . . 28
     7.4.  Notifications for removable batteries  . . . . . . . . . . 28
     7.5.  Notification for battery charging state changes? . . . . . 28
     7.6.  Support for ACPI critical battery state? . . . . . . . . . 28

   8.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 28

   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 29
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 29
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 29

   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30

Quittek, et al.          Expires August 29, 2013                [Page 2]
Internet-Draft                 Battery MIB                 February 2013

1.  Introduction

   Today, more and more managed devices contain batteries that supply
   them with power when disconnected from electrical power distribution
   grids.  Common examples are nomadic and mobile devices, such as
   notebook computers, netbooks, and smart phones.  The status of
   batteries in such a device, particularly the charging status is
   typically controlled by automatic functions that act locally on the
   device and manually by users of the device.

   In addition to this, there is a need to monitor battery status of
   these devices by network management systems.  This document defines a