Subject: [eman] RFC 7577 on Definition of Managed Objects for Battery Monitoring

From: [email-masked]
Date: Thu, 23 Jul 2015 06:36:48 -0700 (PDT)

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

        RFC 7577

        Title:      Definition of Managed Objects for 
                    Battery Monitoring 
        Author:     J. Quittek, R. Winter, T. Dietz
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2015
        Mailbox:    [email-masked], 
                    [email-masked], 
                    [email-masked]
        Pages:      40
        Characters: 86505
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-eman-battery-mib-20.txt

        URL:        https://www.rfc-editor.org/info/rfc7577

        DOI:        http://dx.doi.org/10.17487/RFC7577

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.

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

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  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 [email-masked].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC