I'm not sure the best mechanism to share them, so I've posted my notes and review here: https://gist.github.com/dzomaya/876d4f8f14db0c7fc04cfec220ac9a36 Also shared with the ISE editor. I may be missing something process-wise, so just let me know. Thanks for all the work on this Roger! ______________________________________________________________________ From: David Zomaya Sent: Sunday, December 26, 2021 11:22 AM To: Roger Price; Ted Mittelstaedt; Nut-upsdev at alioth-lists.debian.net Subject: Re: [EXTERNAL] Re: [Nut-upsdev] NUT RFC progress I ball dropped. I have review notes I never sent. I'll clean them up and send tonight. From: Nut-upsdev <nut-upsdev-bounces+david_zomaya=tripplite.com at alioth-lists.debian.net> on behalf of Roger Price <roger at rogerprice.org> Sent: Sunday, December 26, 2021 11:03:18 AM To: Ted Mittelstaedt; Nut-upsdev at alioth-lists.debian.net Subject: [EXTERNAL] Re: [Nut-upsdev] NUT RFC progress This is an EXTERNAL email. Please take a moment and think before clicking any links or opening any attachments from this email. If suspicious, please forward to ishelpdesk at tripplite.com for review. ______________________________________________________________________ On Sun, 26 Dec 2021, Ted Mittelstaedt wrote:> Would you send me a link to this, please? > Thanks, > TedI should have included the link https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Drprice-2Dups-2Dmanagement-2Dprotocol_&d=DwIDaQ&c=f9s1WCuF-N6cmD_YaZ7gBg&r=lhr3k4au5dVQgHY_iS-v_t9g8PHVkn8Px_wyaupZGfQ&m=3AiaC4aFyRjngSy30S6BFKGonduR1GuJbOlhoCmzu5Mdc2y3NkBVxrl7NbXRWg7y&s=URPmnIeP6_AcZlOLX7D0GVi3RlB69YNBTu7uvyRKUHE&eRoger> On 12/26/2021 12:46 AM, Roger Price wrote: >> My apologies to the list for falling asleep in front of the draft RFC. I >> have been prodded by the IETF for rapid action. >> >> Are there any further comments from the reviewers? (David ?) If not I will >> proceed to the next stage. >> >> Roger________________________________ This message is for the addressee's use only. It may contain confidential information. If you receive this message in error, please delete it and notify the sender. Tripp Lite disclaims all warranties and liabilities, and assumes no responsibility for viruses which may infect an email sent to you from Tripp Lite and which damage your electronic systems or information. It is your responsibility to maintain virus detection systems to prevent damage to your electronic systems and information.
On Mon, 27 Dec 2021, David Zomaya wrote:> I'm not sure the best mechanism to share them, so I've posted my notes and review here: > https://gist.github.com/dzomaya/876d4f8f14db0c7fc04cfec220ac9a36 > > Also shared with the ISE editor. I may be missing something process-wise, so just let me know.The NUT RFC process: Since there are so few of us, I choose the lightweight "Informational" process rather than the much heavier "Standards Track" process which requires a separate mailing list, and lots of formality. I also choose, in order to keep things simple, to use the regular NUT mailing list rather than create something new. I propose to continue with this simplicity. Our "Document Shepherd" has agreed with this. If at some later stage, with much manufacturer involvement, a formal standards track RFC were needed then it would be perfectly possible to go through the formal process with the (then) existing text. When this mailing list has reached "rough consensus and working code", I submit the text to the IETF process and the ISE get involved. (Note: rough consensus means 95% agreement and not 50% as in the ISO/IEC.) In the short term, I will release a new draft this week in order to satisfy an IETF timeout. Could you please submit your comments, suggestions, text, recommendations, ideas, ... to this list. I will pick up comments which I have received privately and introduce them to the list. Roger