Extensions to Automatic Certificate Management Environment for End-User S/MIME Certificates
Draft of message to be sent after approval:
From: The IESG <email@example.com> To: IETF-Announce <firstname.lastname@example.org> Cc: Rich Salz <email@example.com>, The IESG <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org Subject: Document Action: 'Extensions to Automatic Certificate Management Environment for end-user S/MIME certificates' to Informational RFC (draft-ietf-acme-email-smime-14.txt) The IESG has approved the following document: - 'Extensions to Automatic Certificate Management Environment for end- user S/MIME certificates' (draft-ietf-acme-email-smime-14.txt) as Informational RFC This document is the product of the Automated Certificate Management Environment Working Group. The IESG contact persons are Benjamin Kaduk and Roman Danyliw. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-acme-email-smime/
Technical Summary This document specifies identifiers and challenges required to enable the Automated Certificate Management Environment (ACME) to issue certificates for use by email users that want to use S/MIME. Working Group Summary The document was first adopted by the WG in June 2017. It has been discussed in-person at several IETF’s, and there has been light email discussion in the 2.75 years since. There was never any discussion about not moving this work forward. During the meetings, and on the email list, several technical issuers were discussed, probably around a dozen WG participants total. Some of the discussions included “Should this just use HTML” and the interaction/dependency on DKIM header protection. Discussion was low-key and productive and resolving issues was non-controversial. Some participants were highly involved in email/applications area. Since -00, the document status in the text of the document was informational. This was confirmed with the WG during AD Review (prior to LC). However, the datatracker status was erroneously listed as PS and the IETF Last Call was issued as such. Prior to the issuance of this ballot, the datatracker status was corrected. Document Quality The WG has reviewed this document and feels it is ready. Work is still ongoing within the CA industry around establishing requirements around the issuance and validation of S/MIME certificates which could consider implementation of this protocol extension. Personnel The shepherd is Rich Salz. The responsible AD is Roman Danyliw.