Skip to main content

Automated Certificate Management Environment (ACME) Renewal Information (ARI) Extension
draft-ietf-acme-ari-06

Revision differences

Document history

Date Rev. By Action
2024-11-27
06 Jean Mahoney Request for Last Call review by GENART is assigned to Susan Hares
2024-11-26
06 David Dong IANA Experts State changed to Reviews assigned
2024-11-26
06 Shawn Emery Request for Last Call review by SECDIR Completed: Has Issues. Reviewer: Shawn Emery. Sent review to list.
2024-11-25
06 Magnus Westerlund Request for Last Call review by TSVART is assigned to Michael Tüxen
2024-11-24
06 Barry Leiba Request for Last Call review by ARTART is assigned to Joseph Yee
2024-11-24
06 Tero Kivinen Request for Last Call review by SECDIR is assigned to Shawn Emery
2024-11-23
06 Geoff Huston
Request for Last Call review by DNSDIR Completed: Ready with Nits. Reviewer: Geoff Huston. Sent review to list. Submission of review completed at an earlier …
Request for Last Call review by DNSDIR Completed: Ready with Nits. Reviewer: Geoff Huston. Sent review to list. Submission of review completed at an earlier date.
2024-11-23
06 Geoff Huston Request for Last Call review by DNSDIR Completed: Ready with Nits. Reviewer: Geoff Huston.
2024-11-22
06 Geoff Huston Request for Last Call review by DNSDIR is assigned to Geoff Huston
2024-11-22
06 Cindy Morgan IANA Review state changed to IANA - Review Needed
2024-11-22
06 Cindy Morgan
The following Last Call announcement was sent out (ends 2024-12-06):

From: The IESG
To: IETF-Announce
CC: acme-chairs@ietf.org, acme@ietf.org, debcooley1@gmail.com, draft-ietf-acme-ari@ietf.org, ynir.ietf@gmail.com …
The following Last Call announcement was sent out (ends 2024-12-06):

From: The IESG
To: IETF-Announce
CC: acme-chairs@ietf.org, acme@ietf.org, debcooley1@gmail.com, draft-ietf-acme-ari@ietf.org, ynir.ietf@gmail.com
Reply-To: last-call@ietf.org
Sender:
Subject: Last Call:  (Automated Certificate Management Environment (ACME) Renewal Information (ARI) Extension) to Proposed Standard


The IESG has received a request from the Automated Certificate Management
Environment WG (acme) to consider the following document: - 'Automated
Certificate Management Environment (ACME) Renewal
  Information (ARI) Extension'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2024-12-06. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


  This document specifies how an ACME server may provide suggestions to
  ACME clients as to when they should attempt to renew their
  certificates.  This allows servers to mitigate load spikes, and
  ensures clients do not make false assumptions about appropriate
  certificate renewal periods.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-acme-ari/



No IPR declarations have been submitted directly on this I-D.




2024-11-22
06 Cindy Morgan IESG state changed to In Last Call from Last Call Requested
2024-11-22
06 Deb Cooley Last call was requested
2024-11-22
06 Deb Cooley Last call announcement was generated
2024-11-22
06 Deb Cooley Ballot approval text was generated
2024-11-22
06 Deb Cooley IESG state changed to Last Call Requested from AD Evaluation
2024-11-22
06 Deb Cooley AD Evaluation comment:  https://mailarchive.ietf.org/arch/msg/acme/A1AoYFZXt0Ie8dWNi5yd7C7VGpI/
2024-11-22
06 Deb Cooley IESG state changed to AD Evaluation from Publication Requested
2024-11-22
06 Deb Cooley Ballot writeup was changed
2024-11-04
06 Yoav Nir
This is the shepherd write-up for draft-ietf-acme-ari

Current version is 06
Document author is Aaron Gable (aaron@letsencrypt.org)
Document shepherd is Yoav Nir ( …
This is the shepherd write-up for draft-ietf-acme-ari

Current version is 06
Document author is Aaron Gable (aaron@letsencrypt.org)
Document shepherd is Yoav Nir (ynir.ietf@gmail.com)
Responsible AD is Deb Cooley (debcooley1@gmail.com)

## Document History

1. Does the working group (WG) consensus represent the strong concurrence of a
  few individuals, with others being silent, or did it reach broad agreement?

The WG discussed this heavily in F2F meetings, with somewhat less discussion on
    the mailing list. For the WGLC more people did speak up in favor, with none
    objecting. For ACME, this is what consensus looks like.

2. Was there controversy about particular points, or were there decisions where
  the consensus was particularly rough?

No

3. Has anyone threatened an appeal or otherwise indicated extreme discontent? If
  so, please summarize the areas of conflict in separate email messages to the
  responsible Area Director. (It should be in a separate email because this
  questionnaire is publicly available.)

No

4. For protocol documents, are there existing implementations of the contents of
  the document? Have a significant number of potential implementers indicated
  plans to implement? Are any existing implementations reported somewhere,
  either in the document itself (as [RFC 7942][3] recommends) or elsewhere
  (where)?

Both Google and Let's Encrypt have server implementations in production.
The draft lists 4 client implementations.

## Additional Reviews

5. Do the contents of this document closely interact with technologies in other
  IETF working groups or external organizations, and would it therefore benefit
  from their review? Have those reviews occurred? If yes, describe which
  reviews took place.

No

6. Describe how the document meets any required formal expert review criteria,
  such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.

N/A. The only formatted specification in the draft is a bit of json.

7. If the document contains a YANG module, has the final version of the module
  been checked with any of the [recommended validation tools][4] for syntax and
  formatting validation? If there are any resulting errors or warnings, what is
  the justification for not fixing them at this time? Does the YANG module
  comply with the Network Management Datastore Architecture (NMDA) as specified
  in [RFC 8342][5]?

No YANG module

8. Describe reviews and automated checks performed to validate sections of the
  final version of the document written in a formal language, such as XML code,
  BNF rules, MIB definitions, CBOR's CDDL, etc.

N/A

## Document Shepherd Checks

9. Based on the shepherd's review of the document, is it their opinion that this
  document is needed, clearly written, complete, correctly designed, and ready
  to be handed off to the responsible Area Director?

Yes, this draft is understandable, well-written. It's needed as evidenced by the
multiple existing implementations. I believe it's ready to be handed over.

10. Several IETF Areas have assembled [lists of common issues that their
    reviewers encounter][6]. For which areas have such issues been identified
    and addressed? For which does this still need to happen in subsequent
    reviews?

For the Security Area, common issues have been addressed.

11. What type of RFC publication is being requested on the IETF stream ([Best
    Current Practice][12], [Proposed Standard, Internet Standard][13],
    [Informational, Experimental or Historic][14])? Why is this the proper type
    of RFC? Do all Datatracker state attributes correctly reflect this intent?

Proposed Standard.
All the datatracker state attributes are correct.

12. Have reasonable efforts been made to remind all authors of the intellectual
    property rights (IPR) disclosure obligations described in [BCP 79][7]? To
    the best of your knowledge, have all required disclosures been filed? If
    not, explain why. If yes, summarize any relevant discussion, including links
    to publicly-available messages when applicable.

Yes

13. Has each author, editor, and contributor shown their willingness to be
    listed as such? If the total number of authors and editors on the front page
    is greater than five, please provide a justification.

Yes

14. Document any remaining I-D nits in this document. Simply running the [idnits
    tool][8] is not enough; please review the ["Content Guidelines" on
    authors.ietf.org][15]. (Also note that the current idnits tool generates
    some incorrect warnings; a rewrite is underway.)

No nits.

15. Should any informative references be normative or vice-versa? See the [IESG
    Statement on Normative and Informative References][16].

No

16. List any normative references that are not freely available to anyone. Did
    the community have sufficient access to review any such normative
    references?

N/A

17. Are there any normative downward references (see [RFC 3967][9] and [BCP
    97
][10]) that are not already listed in the [DOWNREF registry][17]? If so,
    list them.

No

18. Are there normative references to documents that are not ready to be
    submitted to the IESG for publication or are otherwise in an unclear state?
    If so, what is the plan for their completion?

No

19. Will publication of this document change the status of any existing RFCs? If
    so, does the Datatracker metadata correctly reflect this and are those RFCs
    listed on the title page, in the abstract, and discussed in the
    introduction? If not, explain why and point to the part of the document
    where the relationship of this document to these other RFCs is discussed.

No

20. Describe the document shepherd's review of the IANA considerations section,
    especially with regard to its consistency with the body of the document.
    Confirm that all aspects of the document requiring IANA assignments are
    associated with the appropriate reservations in IANA registries. Confirm
    that any referenced IANA registries have been clearly identified. Confirm
    that each newly created IANA registry specifies its initial contents,
    allocations procedures, and a reasonable name (see [RFC 8126][11]).

The draft requests changes to four registries: "ACME Resource Types",
    "ACME Renewal Info Object Fields", "ACME Order Object Fields",
    and "ACME Error Types" - all four are ACME registries, and all
    assignments look OK.

21. List any new IANA registries that require Designated Expert Review for
    future allocations. Are the instructions to the Designated Expert clear?
    Please include suggestions of designated experts, if appropriate.

All four registries listed above require designated expert review.
The request is straight forward.

[1]: https://www.ietf.org/about/groups/iesg/
[2]: https://www.rfc-editor.org/rfc/rfc4858.html
[3]: https://www.rfc-editor.org/rfc/rfc7942.html
[4]: https://wiki.ietf.org/group/ops/yang-review-tools
[5]: https://www.rfc-editor.org/rfc/rfc8342.html
[6]: https://wiki.ietf.org/group/iesg/ExpertTopics
[7]: https://www.rfc-editor.org/info/bcp79
[8]: https://www.ietf.org/tools/idnits/
[9]: https://www.rfc-editor.org/rfc/rfc3967.html
[10]: https://www.rfc-editor.org/info/bcp97
[11]: https://www.rfc-editor.org/rfc/rfc8126.html
[12]: https://www.rfc-editor.org/rfc/rfc2026.html#section-5
[13]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.1
[14]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.2
[15]: https://authors.ietf.org/en/content-guidelines-overview
[16]: https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/
[17]: https://datatracker.ietf.org/doc/downref/

2024-11-04
06 Yoav Nir IETF WG state changed to Submitted to IESG for Publication from WG Consensus: Waiting for Write-Up
2024-11-04
06 Yoav Nir IESG state changed to Publication Requested from I-D Exists
2024-11-04
06 (System) Changed action holders to Deb Cooley (IESG state changed)
2024-11-04
06 Yoav Nir Responsible AD changed to Deb Cooley
2024-11-04
06 Yoav Nir Document is now in IESG state Publication Requested
2024-11-04
06 Yoav Nir Tag Doc Shepherd Follow-up Underway cleared.
2024-11-04
06 Yoav Nir
This is the shepherd write-up for draft-ietf-acme-ari

Current version is 06
Document author is Aaron Gable (aaron@letsencrypt.org)
Document shepherd is Yoav Nir ( …
This is the shepherd write-up for draft-ietf-acme-ari

Current version is 06
Document author is Aaron Gable (aaron@letsencrypt.org)
Document shepherd is Yoav Nir (ynir.ietf@gmail.com)
Responsible AD is Deb Cooley (debcooley1@gmail.com)

## Document History

1. Does the working group (WG) consensus represent the strong concurrence of a
  few individuals, with others being silent, or did it reach broad agreement?

The WG discussed this heavily in F2F meetings, with somewhat less discussion on
    the mailing list. For the WGLC more people did speak up in favor, with none
    objecting. For ACME, this is what consensus looks like.

2. Was there controversy about particular points, or were there decisions where
  the consensus was particularly rough?

No

3. Has anyone threatened an appeal or otherwise indicated extreme discontent? If
  so, please summarize the areas of conflict in separate email messages to the
  responsible Area Director. (It should be in a separate email because this
  questionnaire is publicly available.)

No

4. For protocol documents, are there existing implementations of the contents of
  the document? Have a significant number of potential implementers indicated
  plans to implement? Are any existing implementations reported somewhere,
  either in the document itself (as [RFC 7942][3] recommends) or elsewhere
  (where)?

Both Google and Let's Encrypt have server implementations in production.
The draft lists 4 client implementations.

## Additional Reviews

5. Do the contents of this document closely interact with technologies in other
  IETF working groups or external organizations, and would it therefore benefit
  from their review? Have those reviews occurred? If yes, describe which
  reviews took place.

No

6. Describe how the document meets any required formal expert review criteria,
  such as the MIB Doctor, YANG Doctor, media type, and URI type reviews.

N/A. The only formatted specification in the draft is a bit of json.

7. If the document contains a YANG module, has the final version of the module
  been checked with any of the [recommended validation tools][4] for syntax and
  formatting validation? If there are any resulting errors or warnings, what is
  the justification for not fixing them at this time? Does the YANG module
  comply with the Network Management Datastore Architecture (NMDA) as specified
  in [RFC 8342][5]?

No YANG module

8. Describe reviews and automated checks performed to validate sections of the
  final version of the document written in a formal language, such as XML code,
  BNF rules, MIB definitions, CBOR's CDDL, etc.

N/A

## Document Shepherd Checks

9. Based on the shepherd's review of the document, is it their opinion that this
  document is needed, clearly written, complete, correctly designed, and ready
  to be handed off to the responsible Area Director?

Yes, this draft is understandable, well-written. It's needed as evidenced by the
multiple existing implementations. I believe it's ready to be handed over.

10. Several IETF Areas have assembled [lists of common issues that their
    reviewers encounter][6]. For which areas have such issues been identified
    and addressed? For which does this still need to happen in subsequent
    reviews?

For the Security Area, common issues have been addressed.

11. What type of RFC publication is being requested on the IETF stream ([Best
    Current Practice][12], [Proposed Standard, Internet Standard][13],
    [Informational, Experimental or Historic][14])? Why is this the proper type
    of RFC? Do all Datatracker state attributes correctly reflect this intent?

Proposed Standard.
All the datatracker state attributes are correct.

12. Have reasonable efforts been made to remind all authors of the intellectual
    property rights (IPR) disclosure obligations described in [BCP 79][7]? To
    the best of your knowledge, have all required disclosures been filed? If
    not, explain why. If yes, summarize any relevant discussion, including links
    to publicly-available messages when applicable.

Yes

13. Has each author, editor, and contributor shown their willingness to be
    listed as such? If the total number of authors and editors on the front page
    is greater than five, please provide a justification.

Yes

14. Document any remaining I-D nits in this document. Simply running the [idnits
    tool][8] is not enough; please review the ["Content Guidelines" on
    authors.ietf.org][15]. (Also note that the current idnits tool generates
    some incorrect warnings; a rewrite is underway.)

No nits.

15. Should any informative references be normative or vice-versa? See the [IESG
    Statement on Normative and Informative References][16].

No

16. List any normative references that are not freely available to anyone. Did
    the community have sufficient access to review any such normative
    references?

N/A

17. Are there any normative downward references (see [RFC 3967][9] and [BCP
    97
][10]) that are not already listed in the [DOWNREF registry][17]? If so,
    list them.

No

18. Are there normative references to documents that are not ready to be
    submitted to the IESG for publication or are otherwise in an unclear state?
    If so, what is the plan for their completion?

No

19. Will publication of this document change the status of any existing RFCs? If
    so, does the Datatracker metadata correctly reflect this and are those RFCs
    listed on the title page, in the abstract, and discussed in the
    introduction? If not, explain why and point to the part of the document
    where the relationship of this document to these other RFCs is discussed.

No

20. Describe the document shepherd's review of the IANA considerations section,
    especially with regard to its consistency with the body of the document.
    Confirm that all aspects of the document requiring IANA assignments are
    associated with the appropriate reservations in IANA registries. Confirm
    that any referenced IANA registries have been clearly identified. Confirm
    that each newly created IANA registry specifies its initial contents,
    allocations procedures, and a reasonable name (see [RFC 8126][11]).

The draft requests changes to four registries: "ACME Resource Types",
    "ACME Renewal Info Object Fields", "ACME Order Object Fields",
    and "ACME Error Types" - all four are ACME registries, and all
    assignments look OK.

21. List any new IANA registries that require Designated Expert Review for
    future allocations. Are the instructions to the Designated Expert clear?
    Please include suggestions of designated experts, if appropriate.

All four registries listed above require designated expert review.
The request is straight forward.

[1]: https://www.ietf.org/about/groups/iesg/
[2]: https://www.rfc-editor.org/rfc/rfc4858.html
[3]: https://www.rfc-editor.org/rfc/rfc7942.html
[4]: https://wiki.ietf.org/group/ops/yang-review-tools
[5]: https://www.rfc-editor.org/rfc/rfc8342.html
[6]: https://wiki.ietf.org/group/iesg/ExpertTopics
[7]: https://www.rfc-editor.org/info/bcp79
[8]: https://www.ietf.org/tools/idnits/
[9]: https://www.rfc-editor.org/rfc/rfc3967.html
[10]: https://www.rfc-editor.org/info/bcp97
[11]: https://www.rfc-editor.org/rfc/rfc8126.html
[12]: https://www.rfc-editor.org/rfc/rfc2026.html#section-5
[13]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.1
[14]: https://www.rfc-editor.org/rfc/rfc2026.html#section-4.2
[15]: https://authors.ietf.org/en/content-guidelines-overview
[16]: https://www.ietf.org/about/groups/iesg/statements/normative-informative-references/
[17]: https://datatracker.ietf.org/doc/downref/

2024-10-28
06 Yoav Nir Tag Doc Shepherd Follow-up Underway set.
2024-10-28
06 Yoav Nir IETF WG state changed to WG Consensus: Waiting for Write-Up from In WG Last Call
2024-10-17
06 Aaron Gable New version available: draft-ietf-acme-ari-06.txt
2024-10-17
06 (System) New version approved
2024-10-17
06 (System) Request for posting confirmation emailed to previous authors: Aaron Gable
2024-10-17
06 Aaron Gable Uploaded new revision
2024-10-07
05 Yoav Nir Notification list changed to ynir.ietf@gmail.com because the document shepherd was set
2024-10-07
05 Yoav Nir Document shepherd changed to Yoav Nir
2024-10-07
05 Yoav Nir IETF WG state changed to In WG Last Call from WG Document
2024-10-07
05 Yoav Nir Changed consensus to Yes from Unknown
2024-10-07
05 Yoav Nir Intended Status changed to Proposed Standard from None
2024-08-23
05 Aaron Gable New version available: draft-ietf-acme-ari-05.txt
2024-08-23
05 (System) New version approved
2024-08-23
05 (System) Request for posting confirmation emailed to previous authors: Aaron Gable
2024-08-23
05 Aaron Gable Uploaded new revision
2024-07-25
04 Yoav Nir Added to session: IETF-120: acme  Fri-1630
2024-05-31
04 Aaron Gable New version available: draft-ietf-acme-ari-04.txt
2024-05-31
04 (System) New version approved
2024-05-31
04 (System) Request for posting confirmation emailed to previous authors: Aaron Gable
2024-05-31
04 Aaron Gable Uploaded new revision
2024-02-08
03 Aaron Gable New version available: draft-ietf-acme-ari-03.txt
2024-02-08
03 (System) New version approved
2024-02-08
03 (System) Request for posting confirmation emailed to previous authors: Aaron Gable
2024-02-08
03 Aaron Gable Uploaded new revision
2023-08-10
02 Aaron Gable New version available: draft-ietf-acme-ari-02.txt
2023-08-10
02 (System) New version approved
2023-08-10
02 (System) Request for posting confirmation emailed to previous authors: Aaron Gable
2023-08-10
02 Aaron Gable Uploaded new revision
2023-02-08
01 Aaron Gable New version available: draft-ietf-acme-ari-01.txt
2023-02-08
01 (System) New version approved
2023-02-08
01 (System) Request for posting confirmation emailed to previous authors: Aaron Gable
2023-02-08
01 Aaron Gable Uploaded new revision
2022-08-25
00 Yoav Nir This document now replaces draft-aaron-acme-ari instead of None
2022-08-25
00 Aaron Gable New version available: draft-ietf-acme-ari-00.txt
2022-08-25
00 Yoav Nir WG -00 approved
2022-08-24
00 Aaron Gable Set submitter to "Aaron Gable ", replaces to (none) and sent approval email to group chairs: acme-chairs@ietf.org
2022-08-24
00 Aaron Gable Uploaded new revision