Alternative name for module

[Sp1l]

Suggest to rename the module to mod_acme as it implements the ACME protocol. This name was also suggested by Mozilla. It looks like the module leaves the addition alternative certificate management protocols open for now which would be an indication to not use mod_acme.

The added callback-mechanisms in mod_ssl would allow other certificate auto-renewal mechanisms to be implemented by other parties.

For me personally, md is Message Digest (md5. libmd) and the module doesn't manage the domain for me, only the certificate.

Old Directive	New Directive
MDCertificateAgreement	AcmeAgreement
MDCertificateAuthority	AcmeCertificateAuthority
MDCertificateProtocol	AcmeCertificateProtocol
MDDriveMode	AcmeDriveMode
MDRenewWindow	AcmeRenewWindow
MDMember	AcmeMember

AcmeCertificateProtocol ACME is redundant...

[icing]

I can see at minimum also a 'external' provider where mod_md monitors certificate expiry and allows simpler configuration and certificate updates are imported via a2md into the local store.

In that way, I see it as more than an ACME implementation and I find the name too restricting. If md is a good name, well, that can of course be argued. Probably all short names have overlaps with some tech abbreviations, so that should not really hinder us.

And besides the certificate, it should offer management of all security related configurations of an MD. Which is a little bit more high level concept than what mod_ssl is dealing with, as it applies across VirtualHosts (potentially). Also, migration support from http: to https: get addresses at the moment.

HTTP Alternate Services is another topic that would fit.

[Sp1l]

Makes sense :D Let's close this.