<div dir="auto"><div>Sorry, forgot to update the News entries.<div dir="auto"><br></div><div dir="auto"> And stumbled on terminology: since this I-D is "from community" and "not an imternet standard", how should I correctly refer to it? :) Is the following OK?</div><div dir="auto"><br></div><div dir="auto"> <span style="color:rgb(36,41,47);font-family:-apple-system,blinkmacsystemfont,"segoe ui",helvetica,arial,sans-serif,"apple color emoji","segoe ui emoji";font-size:16px;background-color:rgb(255,255,255)">NUT protocol RFC published at </span><a href="https://www.rfc-editor.org/info/rfc9271" style="background-color:rgb(255,255,255);text-decoration-line:none;font-family:-apple-system,blinkmacsystemfont,"segoe ui",helvetica,arial,sans-serif,"apple color emoji","segoe ui emoji";font-size:16px">https://www.rfc-editor.org/info/rfc9271</a></div><br>Thanks,</div><div dir="auto">Jim<br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Wed, Aug 10, 2022, 13:03 Roger Price <<a href="mailto:roger@rogerprice.org">roger@rogerprice.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It is a pleasure to report that RFC 9271 is now available at <br>
<a href="https://www.rfc-editor.org/info/rfc9271" rel="noreferrer noreferrer" target="_blank">https://www.rfc-editor.org/info/rfc9271</a><br>
<br>
My thanks to everyone who contributed the documentation on which the RFC is <br>
based. I hope that RFC 9271 will help give the NUT Project the visibility that <br>
it deserves. The IANA port number registry will be updated shortly. <br>
<a href="https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=3493" rel="noreferrer noreferrer" target="_blank">https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=3493</a><br>
<br>
Roger<br>
<br>
-----Original Message-----<br>
From: IETF-Announce <<a href="mailto:ietf-announce-bounces@ietf.org" target="_blank" rel="noreferrer">ietf-announce-bounces@ietf.org</a>> On Behalf Of <a href="mailto:rfc-editor@rfc-editor.org" target="_blank" rel="noreferrer">rfc-editor@rfc-editor.org</a><br>
Sent: 10 August 2022 00:35<br>
To: <a href="mailto:ietf-announce@ietf.org" target="_blank" rel="noreferrer">ietf-announce@ietf.org</a>; <a href="mailto:rfc-dist@rfc-editor.org" target="_blank" rel="noreferrer">rfc-dist@rfc-editor.org</a><br>
Cc: <a href="mailto:rfc-editor@rfc-editor.org" target="_blank" rel="noreferrer">rfc-editor@rfc-editor.org</a>; <a href="mailto:drafts-update-ref@iana.org" target="_blank" rel="noreferrer">drafts-update-ref@iana.org</a><br>
Subject: RFC 9271 on Uninterruptible Power Supply (UPS) Management Protocol -- Commands and Responses<br>
<br>
A new Request for Comments is now available in online RFC libraries.<br>
<br>
RFC 9271<br>
<br>
Title: Uninterruptible Power Supply (UPS) Management<br>
Protocol -- Commands and Responses<br>
Author: R. Price, Ed.<br>
Status: Informational<br>
Stream: Independent<br>
Date: August 2022<br>
Mailbox: <a href="mailto:ietf@rogerprice.org" target="_blank" rel="noreferrer">ietf@rogerprice.org</a><br>
Pages: 52<br>
Updates/Obsoletes/SeeAlso: None<br>
I-D Tag: draft-rprice-ups-management-protocol-15.txt<br>
URL: <a href="https://www.rfc-editor.org/info/rfc9271" rel="noreferrer noreferrer" target="_blank">https://www.rfc-editor.org/info/rfc9271</a><br>
DOI: 10.17487/RFC9271<br>
<br>
This document describes the command/response protocol currently used<br>
in the management of Uninterruptible Power Supply (UPS) units and<br>
other power devices often deployed in small offices and in IT<br>
installations subject to an erratic public power supply. The UPS<br>
units typically interface to an Attachment Daemon in the system they<br>
protect. This daemon is in turn polled by a Management Daemon that<br>
notifies users and system administrators of power supply incidents<br>
and automates system shutdown decisions. The commands and responses<br>
described by this document are exchanged between the UPS Attachment<br>
Daemon and the Management Daemon. The practice current when this<br>
protocol was first developed risks weak security, and this is<br>
addressed in the Security Considerations sections of this document.<br>
<br>
INFORMATIONAL: This memo provides information for the Internet community.<br>
It does not specify an Internet standard of any kind. Distribution of<br>
this memo is unlimited.<br>
<br>
This announcement is sent to the IETF-Announce and rfc-dist lists.<br>
To subscribe or unsubscribe, see<br>
<a href="https://www.ietf.org/mailman/listinfo/ietf-announce" rel="noreferrer noreferrer" target="_blank">https://www.ietf.org/mailman/listinfo/ietf-announce</a><br>
<a href="https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist" rel="noreferrer noreferrer" target="_blank">https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist</a><br>
<br>
For searching the RFC series, see <a href="https://www.rfc-editor.org/search" rel="noreferrer noreferrer" target="_blank">https://www.rfc-editor.org/search</a><br>
For downloading RFCs, see <a href="https://www.rfc-editor.org/retrieve/bulk" rel="noreferrer noreferrer" target="_blank">https://www.rfc-editor.org/retrieve/bulk</a><br>
<br>
Requests for special distribution should be addressed to either the<br>
author of the RFC in question, or to <a href="mailto:rfc-editor@rfc-editor.org" target="_blank" rel="noreferrer">rfc-editor@rfc-editor.org</a>. Unless<br>
specifically noted otherwise on the RFC itself, all RFCs are for<br>
unlimited distribution.<br>
<br>
The RFC Editor Team<br>
Association Management Solutions, LLC<br>
_______________________________________________<br>
IETF-Announce mailing list<br>
<a href="mailto:IETF-Announce@ietf.org" target="_blank" rel="noreferrer">IETF-Announce@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/ietf-announce" rel="noreferrer noreferrer" target="_blank">https://www.ietf.org/mailman/listinfo/ietf-announce</a><br>
<br>
<br>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@alioth-lists.debian.net" target="_blank" rel="noreferrer">Nut-upsuser@alioth-lists.debian.net</a><br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
</blockquote></div></div></div>