>>> At the interim, we had strong consensus to adopt Alexsey’s draft (was one, >>> is now two) on ACME challenges and certs for email services and users: >>> >>> https://datatracker.ietf.org/doc/draft-melnikov-acme-email-smime/ >>> <https://datatracker.ietf.org/doc/draft-melnikov-acme-email-smime/> >> Why is the email address limited to all ASCII? The LAMPS WG is almost done >> with the document for a certificate to include internationalized email >> addresses in certificates, so I would like to see them included here too. > > I've done the quickest job I could do to get something published before the > ACME Interim. As email addresses require new ACME identity type anyway, > supporting Internationalized Emails should be relatively straightforward. > So yes, I am happy to do that. >> >>> https://datatracker.ietf.org/doc/draft-melnikov-acme-email-tls/ >>> <https://datatracker.ietf.org/doc/draft-melnikov-acme-email-tls/> >> I hope we are not depended in any way on AUTH=SCRAM-SHA-1. > > There is no obvious dependency on SCRAM at this point. If you are talking > about example EHLO response, it includes all sort of other capabilities that > are not relevant. I am happy to clarify this in the document.
Good. I’m pleased to see these documents become the starting point for the WG. Russ
_______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
