The following errata report has been submitted for RFC8555, "Automatic Certificate Management Environment (ACME)".
-------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid6276 -------------------------------------- Type: Editorial Reported by: James Manger <ja...@manger.com.au> Section: 2 Original Text ------------- For example, the CA might require a client requesting example.com to provision a DNS record under example.com or an HTTP resource under http://example.com. Corrected Text -------------- For example, the CA might require a client requesting example.org to provision a DNS record under example.org or an HTTP resource under http://example.org. Notes ----- The spec consistently uses example.com for an ACME CA server, and example.org for a site requesting a certificate -- except in this sentence. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC8555 (draft-ietf-acme-acme-18) -------------------------------------- Title : Automatic Certificate Management Environment (ACME) Publication Date : March 2019 Author(s) : R. Barnes, J. Hoffman-Andrews, D. McCarney, J. Kasten Category : PROPOSED STANDARD Source : Automated Certificate Management Environment Area : Security Stream : IETF Verifying Party : IESG _______________________________________________ Acme mailing list Acme@ietf.org https://www.ietf.org/mailman/listinfo/acme
