attachment
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Mike,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">There is a typo in the introduction, 2<sup>nd</sup> paragraph.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New";color:black">Introduction<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New";color:black"> IoT devices are common on local networks and often utilize TLS<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New";color:black"> [RFC8446] with self-signed X.509 certificates [RFC5280] to provide<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New";color:black"> HTTPS [RFC2818] based web pages and services. Unfortunately, web<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New";color:black"> browsers typically do not trust such certificates and show error<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New";color:black"> messages intended to deter usage.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New";color:black"> This document defines a extensions to the Automatic Certificate<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New";color:black"> Management Environment (ACME) [RFC8555], a DHCP [RFC2131] option that<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New";color:black"> provides the host name of the local ACME service, a DNS-SD [RFC6763]<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New";color:black"> service for the local ACME service, and implementation guidance for<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Courier New";color:black"> client devices and software.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Regards<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.75pt;text-autospace:none"><b><span style="color:black">Uli Wehner<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin-left:.75pt;text-autospace:none"><span style="color:black">Sr Technology Specialist, Technology Solutions Support (TSS)<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.75pt;text-autospace:none"><span style="color:black">Gemba Engineering & Development Center<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.75pt;text-autospace:none"><b><span style="color:black">RICOH Digital Services<o:p></o:p></span></b></p>
<p class="MsoNormal" style="margin-left:.75pt;text-autospace:none"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;color:black"><img width="88" height="29" style="width:.9166in;height:.302in" id="Picture_x0020_1" src="cid:image001.jpg@01D85323.87D71450" alt="Ricoh-JPG4"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> ipp <ipp-bounces@pwg.org> <b>On Behalf Of </b>ISTO-PWG Internet Printing Protocol workgroup discussion forum via ipp<br>
<b>Sent:</b> Monday, April 18, 2022 12:22 PM<br>
<b>To:</b> ipp@pwg.org; Michael Sweet <msweet@msweet.org>; Ira McDonald <blueroofmusic@gmail.com><br>
<b>Subject:</b> [IPP] Fwd: New Version Notification for draft-sweet-iot-acme-00.txt[EXTERNAL]<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">Hi,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">We'll talk about this new IETF draft at this Thursday's IPP WG call.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Cheers,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">- Ira<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">---------- Forwarded message ---------<br>
From: <b>Michael Sweet</b> <<a href="mailto:msweet@msweet.org">msweet@msweet.org</a>><br>
Date: Wed, Apr 6, 2022 at 12:16 PM<br>
Subject: Fwd: New Version Notification for draft-sweet-iot-acme-00.txt<br>
To: Ira McDonald <<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>>, Kennedy, Smith (Wireless & IPP Standards) <<a href="mailto:smith.kennedy@hp.com">smith.kennedy@hp.com</a>><o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Ira/Smith,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I don't know if this is going to get anywhere in the IETF (hoping to get the IoT Operations workgroup interested), but I've been puttering with this for a few weeks as a solution for getting trusted X.509 certificates for printers...<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">Begin forwarded message:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><b><span style="font-family:"Helvetica",sans-serif">From: </span>
</b><span style="font-family:"Helvetica",sans-serif"><a href="mailto:internet-drafts@ietf.org" target="_blank">internet-drafts@ietf.org</a></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Helvetica",sans-serif">Subject: New Version Notification for draft-sweet-iot-acme-00.txt</span></b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Helvetica",sans-serif">Date: </span>
</b><span style="font-family:"Helvetica",sans-serif">April 6, 2022 at 12:12:43 PM EDT</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Helvetica",sans-serif">To: </span>
</b><span style="font-family:"Helvetica",sans-serif">"Michael Sweet" <<a href="mailto:msweet@msweet.org" target="_blank">msweet@msweet.org</a>></span><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
A new version of I-D, draft-sweet-iot-acme-00.txt<br>
has been successfully submitted by Michael Sweet and posted to the<br>
IETF repository.<br>
<br>
Name: draft-sweet-iot-acme<br>
Revision: 00<br>
Title: ACME-Based Provisioning of IoT Devices<br>
Document date: 2022-04-06<br>
Group: Individual Submission<br>
Pages: 10<br>
URL: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_archive_id_draft-2Dsweet-2Diot-2Dacme-2D00.txt&d=DwMFaQ&c=5hYF0Zu0Yz-C6S-kaHDIt4ADo8NP5Dtlv81GI_RNZig&r=Kf2OsKTEH35gSgu0U6HqdHzbU1TrLWRQF9AyGiFJjds&m=zfQciHLrqKJORMB6H5dSKUWXHNfODcVNbVDNwzPtmZUW6IR4FVEOEhfLaVtsMqzF&s=ev7spH4_1oMv-hDzbaC2faj1RxnX4aubSeJPXjZ8WY4&e=" target="_blank">https://www.ietf.org/archive/id/draft-sweet-iot-acme-00.txt</a><br>
Status: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dsweet-2Diot-2Dacme_&d=DwMFaQ&c=5hYF0Zu0Yz-C6S-kaHDIt4ADo8NP5Dtlv81GI_RNZig&r=Kf2OsKTEH35gSgu0U6HqdHzbU1TrLWRQF9AyGiFJjds&m=zfQciHLrqKJORMB6H5dSKUWXHNfODcVNbVDNwzPtmZUW6IR4FVEOEhfLaVtsMqzF&s=iBfRMLRiZSno_c3pWQx4F4zSvanbNUXoZ9i_FOYrJvI&e=" target="_blank">https://datatracker.ietf.org/doc/draft-sweet-iot-acme/</a><br>
Html: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_archive_id_draft-2Dsweet-2Diot-2Dacme-2D00.html&d=DwMFaQ&c=5hYF0Zu0Yz-C6S-kaHDIt4ADo8NP5Dtlv81GI_RNZig&r=Kf2OsKTEH35gSgu0U6HqdHzbU1TrLWRQF9AyGiFJjds&m=zfQciHLrqKJORMB6H5dSKUWXHNfODcVNbVDNwzPtmZUW6IR4FVEOEhfLaVtsMqzF&s=Ajh9lrRoVVq-b4S7fvviQzypBBiigTtRk9_xpLCQp5s&e=" target="_blank">https://www.ietf.org/archive/id/draft-sweet-iot-acme-00.html</a><br>
Htmlized: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_html_draft-2Dsweet-2Diot-2Dacme&d=DwMFaQ&c=5hYF0Zu0Yz-C6S-kaHDIt4ADo8NP5Dtlv81GI_RNZig&r=Kf2OsKTEH35gSgu0U6HqdHzbU1TrLWRQF9AyGiFJjds&m=zfQciHLrqKJORMB6H5dSKUWXHNfODcVNbVDNwzPtmZUW6IR4FVEOEhfLaVtsMqzF&s=LfZ-JAg5pZ7-QeXNvHrDn_a0N9A-JWljWAkeTzStezo&e=" target="_blank">https://datatracker.ietf.org/doc/html/draft-sweet-iot-acme</a><br>
<br>
<br>
Abstract:<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>
<br>
The IETF Secretariat<br>
<br>
<o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">________________________<br>
Michael Sweet<br>
<br>
<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>