This came up during IESG/IETF last calls.
Most of the changes are editorial, such as changing some of the field names in
the JSON structures etc (e.g., recurrent to auto-renewal). But a couple are
operational and CA/B forum compliance.
Quoting the summary of changes:
On 17/09/2019, 16:02, "Acme on behalf of internet-dra...@ietf.org"
wrote:
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-acme-star/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-acme-star-09
>
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 : Support for Short-Term, Automatically-Renewed (STAR)
Certificates in Automated Certificate
Reviewer: Martin Thomson
Review result: Ready with Nits
This is a clear description of a simple protocol that addresses a well-defined
problem. I didn't find any real issues, though I have some suggestions that
might improve the document a little. My view is that publication without these
would
