RFC 9271 on Uninterruptible Power Supply (UPS) Management Protocol -- Commands and Responses

rfc-editor@rfc-editor.org Tue, 09 August 2022 23:35 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 31A8BC15948A for <ietf-announce@ietfa.amsl.com>; Tue, 9 Aug 2022 16:35:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.959
X-Spam-Status: No, score=-3.959 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id UM3v4jUuf3xa for <ietf-announce@ietfa.amsl.com>; Tue, 9 Aug 2022 16:35:05 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org []) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 852D9C14F607 for <ietf-announce@ietf.org>; Tue, 9 Aug 2022 16:35:05 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 60D802262399; Tue, 9 Aug 2022 16:35:05 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDkyNzEgb24gVW5pbnRlcnJ1cHRpYmxlIFBvd2VyIFN1cHBseSAoVVBTKSBNYW5hZ2VtZW50IFByb3RvY29sIC0tIENvbW1hbmRzIGFuZCBSZXNwb25zZXM=?=
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20220809233505.60D802262399@rfcpa.amsl.com>
Date: Tue, 9 Aug 2022 16:35:05 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/iTmsJ-NQWHlt_janxsLwVbqRhZA>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2022 23:35:09 -0000

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:    ietf@rogerprice.org
        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

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 rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC