All, I finally got a chance to update this draft based on the feedback from various folks. Changes are mostly in the security considerations, but I also added an example for the root certificate generation and clarified root certificate validation/acceptance on the client device.
> Begin forwarded message: > > From: [email protected] > Subject: New Version Notification for draft-sweet-iot-acme-05.txt > Date: January 30, 2024 at 11:03:43 AM EST > To: "Michael Sweet" <[email protected]> > > A new version of Internet-Draft draft-sweet-iot-acme-05.txt has been > successfully submitted by Michael Sweet and posted to the > IETF repository. > > Name: draft-sweet-iot-acme > Revision: 05 > Title: ACME-Based Provisioning of IoT Devices > Date: 2024-01-30 > Group: Individual Submission > Pages: 13 > URL: https://www.ietf.org/archive/id/draft-sweet-iot-acme-05.txt > Status: https://datatracker.ietf.org/doc/draft-sweet-iot-acme/ > HTML: https://www.ietf.org/archive/id/draft-sweet-iot-acme-05.html > HTMLized: https://datatracker.ietf.org/doc/html/draft-sweet-iot-acme > Diff: https://author-tools.ietf.org/iddiff?url2=draft-sweet-iot-acme-05 > > Abstract: > > This document extends the Automatic Certificate Management > Environment (ACME) [RFC8555] to provision X.509 certificates for > local Internet of Things (IoT) devices that are accepted by existing > web browsers and other software running on End User client devices. > > > > The IETF Secretariat > > ________________________ Michael Sweet
_______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
