NOTE: This charter is a snapshot of that in effect at the time of the 38th IETF Meeting in Memphis, Tennessee. It may now be out-of-date.
Jeff Case <case@snmp.com>
Operational Requirements Area Director(s):
Scott Bradner <sob@harvard.edu>
Michael O'Dell <mo@uu.net>
Deirdre Kostick <kostick@qsun.att.com>
General Discussion:ups-mib@cs.utk.edu
To Subscribe: ups-mib-request@cs.utk.edu
Archive: ucs.utk.edu:~/pub/ups-mib/mail-archive
This working group will produce a document that defines MIB objects for use in monitoring and (possibly) controlling both high- and low-end UPSs and related systems (e.g., power distribution systems or power conditioning systems). Related devices may be addressed in this effort to the extent that the primary focus on UPSs is not compromised.
The MIB object definitions produced will be for use by SNMP and will be consistent with existing SNMP standards and framework.
At its discretion, the working group may fulfill its charter by the development of distinct MIB definitions for UPS systems of differing capabilities, but the number of MIB definitions produced by the working group will not exceed two.
At its discretion, the working group may produce an additional document defining traps that support the management of UPSs.
Although the working group may choose to solicit input or expertise from other relevant standards bodies, no extant standards efforts or authorities are known with which alignment of this work is required.
Because the structure of UPS implementations varies widely, the working group shall take special care that its definitions reflect a generic and consistent architectural model of UPS management rather than the structure of particular UPS implementations.
Goals and Milestones:
Request For Comments:
|
RFC |
Status |
Title |
|
RFC1628 |
PS |
UPS Management Information Base |