> For "DNSName" authorizations, the same constraints still hold - there is > a defined DNS name, and the challenges apply to that specific name. This looks good. Only a slight nitpick — the label "DNSName" seems out-of-kilter with the naming convention used by the rest of the standard. "dns-name" or "dnsName" would be more appropriate?
We should also consider allowing people to use URIs, or some sort of vendor-prefixed types for authorizations and challenges, to avoid collisions. e.g. "http://example.ca/account-funding-01"; or "vnd.exampleca.account-funding-01" or "ca.example.account-funding-01". _______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
