attachment
<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">The main pushback at the last IETF was concern over use on public networks, so I added terminology and discussion of only using this on private networks...<div><br><div><div><br><blockquote type="cite"><div>Begin forwarded message:</div><br class="Apple-interchange-newline"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);"><b>From: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;">internet-drafts@ietf.org<br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);"><b>Subject: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;"><b>New Version Notification for draft-sweet-iot-acme-06.txt</b><br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);"><b>Date: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;">August 9, 2024 at 4:34:08 PM EDT<br></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;"><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);"><b>To: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;">"Michael Sweet" <msweet@msweet.org><br></span></div><br><div><div>A new version of Internet-Draft draft-sweet-iot-acme-06.txt has been<br>successfully submitted by Michael Sweet and posted to the<br>IETF repository.<br><br>Name: draft-sweet-iot-acme<br>Revision: 06<br>Title: ACME-Based Provisioning of IoT Devices<br>Date: 2024-08-09<br>Group: Individual Submission<br>Pages: 14<br>URL: https://www.ietf.org/archive/id/draft-sweet-iot-acme-06.txt<br>Status: https://datatracker.ietf.org/doc/draft-sweet-iot-acme/<br>HTML: https://www.ietf.org/archive/id/draft-sweet-iot-acme-06.html<br>HTMLized: https://datatracker.ietf.org/doc/html/draft-sweet-iot-acme<br>Diff: https://author-tools.ietf.org/iddiff?url2=draft-sweet-iot-acme-06<br><br>Abstract:<br><br> This document extends the Automatic Certificate Management<br> Environment (ACME) [RFC8555] to provision X.509 certificates for<br> local Internet of Things (IoT) devices that are accepted by existing<br> web browsers and other software running on End User client devices.<br><br><br><br>The IETF Secretariat<br><br><br></div></div></blockquote></div><br><div>
<div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">________________________<br>Michael Sweet<br></div>
</div>
<br></div></div></body></html>