< draft-ietf-eman-battery-mib-19.txt   draft-ietf-eman-battery-mib-20.txt >
Network Working Group J. Quittek Network Working Group J. Quittek
Internet-Draft R. Winter Internet-Draft R. Winter
Intended status: Standards Track T. Dietz Intended status: Standards Track T. Dietz
Expires: October 16, 2015 NEC Europe Ltd. Expires: October 19, 2015 NEC Europe Ltd.
April 14, 2015 April 17, 2015
Definition of Managed Objects for Battery Monitoring Definition of Managed Objects for Battery Monitoring
draft-ietf-eman-battery-mib-19 draft-ietf-eman-battery-mib-20
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it defines managed objects that provide information on In particular, it defines managed objects that provide information on
the status of batteries in managed devices. the status of batteries in managed devices.
Status of This Memo Status of This Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 16, 2015. This Internet-Draft will expire on October 19, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 21 skipping to change at page 2, line 21
3.2. Battery Technologies . . . . . . . . . . . . . . . . . . 8 3.2. Battery Technologies . . . . . . . . . . . . . . . . . . 8
3.2.1. Guidelines for Adding Battery Technologies . . . . . 9 3.2.1. Guidelines for Adding Battery Technologies . . . . . 9
3.3. Battery Identification . . . . . . . . . . . . . . . . . 9 3.3. Battery Identification . . . . . . . . . . . . . . . . . 9
3.4. Charging Cycles . . . . . . . . . . . . . . . . . . . . . 10 3.4. Charging Cycles . . . . . . . . . . . . . . . . . . . . . 10
3.5. Charge Control . . . . . . . . . . . . . . . . . . . . . 10 3.5. Charge Control . . . . . . . . . . . . . . . . . . . . . 10
3.6. Imported Definitions . . . . . . . . . . . . . . . . . . 11 3.6. Imported Definitions . . . . . . . . . . . . . . . . . . 11
4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11
5. Security Considerations . . . . . . . . . . . . . . . . . . . 33 5. Security Considerations . . . . . . . . . . . . . . . . . . . 33
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 36
6.1. SMI Object Identifier Registration . . . . . . . . . . . 36 6.1. SMI Object Identifier Registration . . . . . . . . . . . 36
6.2. Battery Technology Registration . . . . . . . . . . . . . 37 6.2. Battery Technology Registration . . . . . . . . . . . . . 36
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 37 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 37
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 37
8.1. Normative References . . . . . . . . . . . . . . . . . . 37 8.1. Normative References . . . . . . . . . . . . . . . . . . 37
8.2. Informative References . . . . . . . . . . . . . . . . . 38 8.2. Informative References . . . . . . . . . . . . . . . . . 38
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 39 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 38
1. Introduction 1. Introduction
Today, more and more managed devices contain batteries that supply Today, more and more managed devices contain batteries that supply
them with power when disconnected from electrical power distribution them with power when disconnected from electrical power distribution
grids. Common examples are nomadic and mobile devices, such as grids. Common examples are nomadic and mobile devices, such as
notebook computers, netbooks, and smart phones. The status of notebook computers, netbooks, and smart phones. The status of
batteries in such a device, particularly the charging status is batteries in such a device, particularly the charging status is
typically controlled by automatic functions that act locally on the typically controlled by automatic functions that act locally on the
device and manually by users of the device. device and manually by users of the device.
skipping to change at page 11, line 6 skipping to change at page 11, line 6
situation. situation.
Setting the value of object batteryChargingAdminState may result in Setting the value of object batteryChargingAdminState may result in
not changing the state of the battery to this value or even in not changing the state of the battery to this value or even in
setting the charging state to another value than the requested one. setting the charging state to another value than the requested one.
Due to operational conditions and limitations of the implementation Due to operational conditions and limitations of the implementation
of the BATTERY-MIB module, changing the battery status according to a of the BATTERY-MIB module, changing the battery status according to a
set value of object batteryChargingAdminState might not be possible. set value of object batteryChargingAdminState might not be possible.
For example, the charging controller might at any time decide to For example, the charging controller might at any time decide to
enter state using(6), if there is an operational need to use the enter state discharging(5), if there is an operational need to use
battery for supplying power. the battery for supplying power.
The object batteryChargingAdminState will not automatically change The object batteryChargingAdminState will not automatically change
when the object batteryChargingOperState changes. If the operational when the object batteryChargingOperState changes. If the operational
state is changed, e.g. to the state using(6) due to operational state is changed, e.g. to the state discharging(5) due to operational
conditions, the admin state will remain in its current state. The conditions, the admin state will remain in its current state. The
charging controller SHOULD change the operational state to the state charging controller SHOULD change the operational state to the state
indicated by the object batteryChargingAdminState as soon as indicated by the object batteryChargingAdminState as soon as
operational conditions allow this change. operational conditions allow this change.
If a state change of the object batteryChargingAdminState is desired If a state change of the object batteryChargingAdminState is desired
upon change of the operational state, the object upon change of the operational state, the object
batteryChargingOperState must be polled or the notification batteryChargingOperState must be polled or the notification
batteryChargingStateNotification must be used to get notified about batteryChargingStateNotification must be used to get notified about
the state change. This could be used, e.g. if maintaining charge is the state change. This could be used, e.g. if maintaining charge is
skipping to change at page 12, line 6 skipping to change at page 12, line 6
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC3411 FROM SNMP-FRAMEWORK-MIB -- RFC3411
DateAndTime DateAndTime
FROM SNMPv2-TC -- RFC2579 FROM SNMPv2-TC -- RFC2579
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC2580 FROM SNMPv2-CONF -- RFC2580
entPhysicalIndex entPhysicalIndex
FROM ENTITY-MIB; -- RFC6933 FROM ENTITY-MIB; -- RFC6933
batteryMIB MODULE-IDENTITY batteryMIB MODULE-IDENTITY
LAST-UPDATED "201504141200Z" -- 14 April 2015 LAST-UPDATED "201504171200Z" -- 17 April 2015
ORGANIZATION "IETF EMAN Working Group" ORGANIZATION "IETF EMAN Working Group"
CONTACT-INFO CONTACT-INFO
"General Discussion: eman@ietf.org "General Discussion: eman@ietf.org
To Subscribe: http://www.ietf.org/mailman/listinfo/eman To Subscribe: http://www.ietf.org/mailman/listinfo/eman
Archive: http://www.ietf.org/mail-archive/web/eman Archive: http://www.ietf.org/mail-archive/web/eman
Editor: Editor:
Juergen Quittek Juergen Quittek
NEC Europe Ltd. NEC Europe Ltd.
NEC Laboratories Europe NEC Laboratories Europe
skipping to change at page 12, line 43 skipping to change at page 12, line 43
License set forth in Section 4.c of the IETF Trust's Legal License set forth in Section 4.c of the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info). (http://trustee.ietf.org/license-info).
This version of this MIB module is part of RFC yyyy; see This version of this MIB module is part of RFC yyyy; see
the RFC itself for full legal notices." the RFC itself for full legal notices."
-- replace yyyy with actual RFC number & remove this notice -- replace yyyy with actual RFC number & remove this notice
-- Revision history -- Revision history
REVISION "201504141200Z" -- 14 April 2015 REVISION "201504171200Z" -- 17 April 2015
DESCRIPTION DESCRIPTION
"Initial version, published as RFC yyyy." "Initial version, published as RFC yyyy."
-- replace yyyy with actual RFC number & remove this notice -- replace yyyy with actual RFC number & remove this notice
::= { mib-2 zzz } ::= { mib-2 zzz }
-- zzz to be assigned by IANA. -- zzz to be assigned by IANA.
--****************************************************************** --******************************************************************
-- Top Level Structure of the MIB module -- Top Level Structure of the MIB module
--****************************************************************** --******************************************************************
skipping to change at page 19, line 27 skipping to change at page 19, line 27
For batteries of type primary(1) the value of this object is For batteries of type primary(1) the value of this object is
always '0000000000000000'H." always '0000000000000000'H."
::= { batteryEntry 12 } ::= { batteryEntry 12 }
batteryChargingOperState OBJECT-TYPE batteryChargingOperState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(1), unknown(1),
charging(2), charging(2),
maintainingCharge(3), maintainingCharge(3),
noCharging(4), noCharging(4),
discharging(5), discharging(5)
using(6)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the current charging state of the "This object indicates the current charging state of the
battery. battery.
Value unknown(1) indicates that the charging state of the Value unknown(1) indicates that the charging state of the
battery cannot be determined. battery cannot be determined.
skipping to change at page 20, line 4 skipping to change at page 19, line 52
being charged with a low average current that compensates being charged with a low average current that compensates
self-discharging. This includes trickle charging, float self-discharging. This includes trickle charging, float
charging and other methods for maintaining the current charging and other methods for maintaining the current
charge of a battery. In typical implementations of charging charge of a battery. In typical implementations of charging
controllers, state maintainingCharge(3) is only applied controllers, state maintainingCharge(3) is only applied
if the battery is fully charged or almost fully charged. if the battery is fully charged or almost fully charged.
Value noCharging(4) indicates that the battery is not being Value noCharging(4) indicates that the battery is not being
charged or discharged by electric current between the charged or discharged by electric current between the
battery and electric circuits external to the battery. battery and electric circuits external to the battery.
Note that the battery may still be subject to Note that the battery may still be subject to
self-discharging. self-discharging.
Value discharging(5) indicates that the battery is being Value discharging(5) indicates that the battery is either
intentionally discharged by the charging controller for the used as the power source for electric circuits external to
purpose of battery maintenace. Thus, the charge of the the battery or being discharged intentionally by the
battery decreases. charging controller, e.g., for the purpose of battery
maintenace. In any case, the charge of the battery
Value using(6) indicates that the battery is used as the decreases."
power source for the electric circuits external to the
battery. As a consequence the battery is discharging and
the charge of the battery decreases."
::= { batteryEntry 13 } ::= { batteryEntry 13 }
batteryChargingAdminState OBJECT-TYPE batteryChargingAdminState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
notSet(1), notSet(1),
charge(2), charge(2),
doNotCharge(3), doNotCharge(3),
discharge(4) discharge(4)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
skipping to change at page 20, line 50 skipping to change at page 20, line 45
When the batteryChargingAdminState object is set, then the When the batteryChargingAdminState object is set, then the
BATTERY-MIB implementation must try to set the battery BATTERY-MIB implementation must try to set the battery
to the indicated state. The result will be indicated by to the indicated state. The result will be indicated by
object batteryChargingOperState. object batteryChargingOperState.
Setting object batteryChargingAdminState to value notSet(1) Setting object batteryChargingAdminState to value notSet(1)
is a request to the charging controller to operate is a request to the charging controller to operate
autonomously and choose the operational state that is autonomously and choose the operational state that is
suitable. suitable.
Setting object batteryChargingAdminState to value Setting object batteryChargingAdminState to value charge(2)
charge(2) is a request for first entering operational is a request to enter the operational state charging(2) until
state charging(2) until the battery is fully charged. If the battery is fully charged. When the battery is fully
the charging controller and the battery support the charged, or if the battery was already fully charged or
functionality of maintaining the charge the operational almost fully charged at the time of the request, the
state will change to maintainingCharge(3). Otherwise the operational state will change to maintainingCharge(3) if the
operational state will change to noCharging(4). charging controller and the battery support the functionality
If the battery is already fully charged or almost fully of maintaining the charge, or will change to noCharging(4)
charged, then setting object batteryChargingAdminState otherwise.
to value charge(2) is a request for entering state
maintainingCharge(3) if the charging controller and the
battery support the functionality of maintaining the
charge or the state noCharging(4) otherwise.
Setting object batteryChargingAdminState to value Setting object batteryChargingAdminState to value
doNotCharge(3) is a request for entering operational doNotCharge(3) is a request for entering operational
state noCharging(4). state noCharging(4).
Setting object batteryChargingAdminState to value Setting object batteryChargingAdminState to value
discharge(4) is a request for entering operational discharge(4) is a request for entering operational
state discharging(5). If the battery is empty or almost state discharging(5). Discharging can be accomplished
empty the operational state will change to noCharging(4). by ordinary use, applying a dedicated load, or any other
mean. An example for applying this state is battery
maintenance. If the battery is empty or almost empty the
operational state will change to noCharging(4).
The charging controller will decide which charge condition The charging controller will decide which charge condition
will be considered empty dependent on the battery will be considered empty dependent on the battery
technology used. This is done to avoid damage on the technology used. This is done to avoid damage on the
battery due to deep discharge. battery due to deep discharge.
Due to operational conditions and limitations of the Due to operational conditions and limitations of the
implementation of the BATTERY-MIB module, changing the implementation of the BATTERY-MIB module, changing the
battery status according to a set value of object battery status according to a set value of object
batteryChargingAdminState may not be possible. batteryChargingAdminState may not be possible.
Setting the value of object batteryChargingAdminState Setting the value of object batteryChargingAdminState
may result in not changing the state of the battery may result in not changing the state of the battery
to this value or even in setting the charging state to this value or even in setting the charging state
to another value than the requested one. For example, to another value than the requested one. For example,
the charging controller might at any time decide to the charging controller might at any time decide to
enter state using(6), if there is an operational need enter state using(6), if there is an operational need
to use the battery for supplying power." to use the battery for supplying power."
::= { batteryEntry 14 } ::= { batteryEntry 14 }
batteryActualCharge OBJECT-TYPE batteryActualCharge OBJECT-TYPE
 End of changes. 15 change blocks. 
39 lines changed or deleted 32 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/