Draft 10 highlight reel for the tl;dr crowd: - Clarification of JWS serialization. ACME now requires flattened JSON serialization - https://github.com/ietf-wg-acme/acme/pull/410 - Clarification of object status fields and state model (incl. new "ready" state for orders): https://github.com/ietf-wg-acme/acme/pull/400 - Clarification that pre-authorization doesn't allow wildcard identifiers - https://github.com/ietf-wg-acme/acme/pull/412 - Removal of unnecessary KeyAuthorization in challenge update/responses - https://github.com/ietf-wg-acme/acme/pull/375
Thank you to the folks that contributed PRs, reviews, and discussion. - Daniel / cpu On Mon, Mar 5, 2018 at 5:39 PM, <[email protected]> wrote: > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Automated Certificate Management > Environment WG of the IETF. > > Title : Automatic Certificate Management Environment > (ACME) > Authors : Richard Barnes > Jacob Hoffman-Andrews > Daniel McCarney > James Kasten > Filename : draft-ietf-acme-acme-10.txt > Pages : 81 > Date : 2018-03-05 > > Abstract: > Certificates in PKI using X.509 (PKIX) are used for a number of > purposes, the most significant of which is the authentication of > domain names. Thus, certificate authorities in the Web PKI are > trusted to verify that an applicant for a certificate legitimately > represents the domain name(s) in the certificate. Today, this > verification is done through a collection of ad hoc mechanisms. This > document describes a protocol that a certification authority (CA) and > an applicant can use to automate the process of verification and > certificate issuance. The protocol also provides facilities for > other certificate management functions, such as certificate > revocation. > > RFC EDITOR: PLEASE REMOVE THE FOLLOWING PARAGRAPH: The source for > this draft is maintained in GitHub. Suggested changes should be > submitted as pull requests at https://github.com/ietf-wg-acme/acme > [1]. Instructions are on that page as well. Editorial changes can > be managed in GitHub, but any substantive change should be discussed > on the ACME mailing list ([email protected]). > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-acme-acme/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-acme-acme-10 > https://datatracker.ietf.org/doc/html/draft-ietf-acme-acme-10 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-acme-acme-10 > > > Please note that it may take a couple of minutes from the time of > submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > Acme mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/acme >
_______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
