Paul Wouters has entered the following ballot position for draft-ietf-acme-integrations-13: No Objection
When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-acme-integrations/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- The document is a good read, and the figures in it make the process very clear. Thanks for that work. Just some minor comments: | | Publish DNS TXT | | | | "example.com" | | | | Delete DNS TXT | | | | "example.com" | | This reads a little as if a TXT record with the content "example.com" needs to be published and deleted. Maybe use 'Publish ACME DNS challange in "example.com"' ? This ownership proof could have been by fulfilling an authorization challenge against the explicit identifier "pledge.example.com", Where does "pledge" come from? Is this a normative reference to something? If it is made up here, add some "for example" text to clarify this. And use at least "_pledge" to avoid clashing with potential real hostnames called pledge ? NITS: which it will issue certificates. s/\.$/ for./ _______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
