This version incorporates the feedback from the IESG, most notably moving from to GET to POST-as-GET.
Chairs / ADs - Where to from here? On Tue, Sep 25, 2018 at 11:02 PM Richard Barnes <r...@ipv.sx> wrote: > This version incorporates the feedback from the IESG, most notably moving > from to GET to POST-as-GET. > > Chairs / ADs - Where to from here? > > On Tue, Sep 25, 2018 at 10:50 PM <internet-dra...@ietf.org> wrote: > >> >> A new version of I-D, draft-ietf-acme-acme-15.txt >> has been successfully submitted by Richard Barnes and posted to the >> IETF repository. >> >> Name: draft-ietf-acme-acme >> Revision: 15 >> Title: Automatic Certificate Management Environment (ACME) >> Document date: 2018-09-25 >> Group: acme >> Pages: 89 >> URL: >> https://www.ietf.org/internet-drafts/draft-ietf-acme-acme-15.txt >> Status: https://datatracker.ietf.org/doc/draft-ietf-acme-acme/ >> Htmlized: https://tools.ietf.org/html/draft-ietf-acme-acme-15 >> Htmlized: >> https://datatracker.ietf.org/doc/html/draft-ietf-acme-acme >> Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-acme-acme-15 >> >> Abstract: >> Public Key Infrastructure X.509 (PKIX) certificates are used for a >> number of purposes, the most significant of which is the >> authentication of domain names. Thus, certification authorities >> (CAs) 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 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 (acme@ietf.org). >> >> >> >> >> 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. >> >> The IETF Secretariat >> >>
_______________________________________________ Acme mailing list Acme@ietf.org https://www.ietf.org/mailman/listinfo/acme
