[Nut-upsuser] New Version Notification for draft-rprice-ups-management-protocol-00.txt (fwd)

[Roger Price]

I have received the attached message from the IETF Secretariat.  The submission 
was encoded in XML, and rendered in .txt and .html by the IETF tool xml2rfc. 
The preferred format for reading is HTML.  Roger

---------- Forwarded message ----------
Date: Mon, 01 Feb 2021 04:03:36 -0800
From: internet-drafts at ietf.org
To: Roger Price <IETF at rogerprice.org>
Subject: New Version Notification for
     draft-rprice-ups-management-protocol-00.txt

A new version of I-D, draft-rprice-ups-management-protocol-00.txt
has been successfully submitted by Roger Price and posted to the
IETF repository.

Name:		draft-rprice-ups-management-protocol
Revision:	00
Title:		Uninterruptible Power Supply (UPS) Management Protocol Commands and Responses
Document date:	2021-02-01
Group:		Individual Submission
Pages:		34
URL:            https://www.ietf.org/archive/id/draft-rprice-ups-management-protocol-00.txt
Status:         https://datatracker.ietf.org/doc/draft-rprice-ups-management-protocol/
Html:           https://www.ietf.org/archive/id/draft-rprice-ups-management-protocol-00.html
Htmlized:       https://tools.ietf.org/html/draft-rprice-ups-management-protocol-00

Abstract:
    This text describes current practice for the command/response
    protocol used in the management of Uninterruptible Power Supply (UPS)
    units and other power devices often used 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 which
    notifies users and system administrators of power supply incidents,
    and takes system shutdown decisions.  The commands and responses
    described by this text are exchanged between the UPS Attachment
    Daemon and the Management Daemon.  Current practice leads to weak
    security and this is addressed in the Security and IANA
    Considerations.

The IETF Secretariat