Great news, and big thanks for the hard effort you (and many others) put into it!
Jim On Wed, Aug 10, 2022, 13:03 Roger Price <[email protected]> wrote: > It is a pleasure to report that RFC 9271 is now available at > https://www.rfc-editor.org/info/rfc9271 > > My thanks to everyone who contributed the documentation on which the RFC > is > based. I hope that RFC 9271 will help give the NUT Project the visibility > that > it deserves. The IANA port number registry will be updated shortly. > > https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=3493 > > Roger > > -----Original Message----- > From: IETF-Announce <[email protected]> On Behalf Of > [email protected] > Sent: 10 August 2022 00:35 > To: [email protected]; [email protected] > Cc: [email protected]; [email protected] > Subject: RFC 9271 on Uninterruptible Power Supply (UPS) Management > Protocol -- Commands and Responses > > A new Request for Comments is now available in online RFC libraries. > > RFC 9271 > > Title: Uninterruptible Power Supply (UPS) Management > Protocol -- Commands and Responses > Author: R. Price, Ed. > Status: Informational > Stream: Independent > Date: August 2022 > Mailbox: [email protected] > Pages: 52 > Updates/Obsoletes/SeeAlso: None > I-D Tag: draft-rprice-ups-management-protocol-15.txt > URL: https://www.rfc-editor.org/info/rfc9271 > DOI: 10.17487/RFC9271 > > This document describes the command/response protocol currently used > in the management of Uninterruptible Power Supply (UPS) units and > other power devices often deployed in small offices and in IT > installations subject to an erratic public power supply. The UPS > units typically interface to an Attachment Daemon in the system they > protect. This daemon is in turn polled by a Management Daemon that > notifies users and system administrators of power supply incidents > and automates system shutdown decisions. The commands and responses > described by this document are exchanged between the UPS Attachment > Daemon and the Management Daemon. The practice current when this > protocol was first developed risks weak security, and this is > addressed in the Security Considerations sections of this document. > > 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/retrieve/bulk > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to [email protected]. Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > The RFC Editor Team > Association Management Solutions, LLC > _______________________________________________ > IETF-Announce mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/ietf-announce > > > _______________________________________________ > Nut-upsuser mailing list > [email protected] > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser >
_______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
