AUTH48 status page for C450
Cluster Details
- draft-irtf-cfrg-ristretto255-decaf448-08.txt RFC-EDITOR
- draft-irtf-cfrg-voprf-21.txt RFC-EDITOR*R
- draft-irtf-cfrg-hash-to-curve-16.txt RFC9380 PUB
- draft-irtf-cfrg-vrf-15.txt RFC9381 PUB
- draft-irtf-cfrg-spake2-26.txt (RFC-to-be 9382) AUTH48
- draft-bar-cfrg-spake2plus-08.txt (RFC-to-be 9383) AUTH48-DONE*R
AUTH48 status of draft-irtf-cfrg-spake2-26 (RFC-to-be 9382)
This document is in AUTH48 state as of 2023-04-03. It has not yet been published as an RFC. The RFC Editor is awaiting approvals from the author(s) as shown below (and anyone else listed) before continuing the publication process.
| Name | Approved? | Date of Approval |
|---|---|---|
| W. Ladd | Y | 2023-05-02 |
| B. Kaduk, Ed. | N | |
| Document Shepherd - Stanislav Smyshlyaev | Y | 2023-05-02 |
** This document is part of Cluster C450, so may have additional holds before publication.
Notes:
2023-04-03: questions sent to authors. 2023-04-04: additional updates received. queries not yet addressed. 2023-04-04: note from Watson: "...we may be in for an extended AUTH48 due to time off". 2023-04-06: updated files sent. 2023-04-14: reminder sent. 2023-04-21: reminder sent. 2023-04-28: reminder sent. 2023-05-01: response received. updated files sent. follow-up queries sent. 2023-05-01: response received. updated files sent. Document Shepherd approval requested. 2023-05-02: additional nit received. updated files sent. 2023-05-10: reminder sent. 2023-05-17: reminder sent. 2023-05-25: reminder sent. 2023-06-12: reminder sent. 2023-06-12: Ben noted that he will take a closer look at the document this week. 2023-06-19: reminder sent. 2023-06-28: reminder sent. 2023-07-05: reminder sent. 2023-07-12: reminder sent. 2023-08-04: reminder sent to Ben. Ben replied, will respond with additional updates next week. 2023-08-14: reminder sent. 2023-08-21: reminder sent. 2023-08-28: reminder sent.
AUTH48-DONE status of draft-bar-cfrg-spake2plus-08 (RFC-to-be 9383)
This document is in AUTH48 state as of 2023-04-03. It has not yet been published as an RFC. The RFC Editor is awaiting approvals from the author(s) as shown below (and anyone else listed) before continuing the publication process.
| Name | Approved? | Date of Approval |
|---|---|---|
| T. Taubert | Y | 2023-08-18 |
| C. A. Wood | Y | 2023-08-16 |
| Independent Submissions Editor - E. Lear | Y | 2023-08-18 |
** This document is part of Cluster C450, so may have additional holds before publication.
Notes:
2023-04-03: questions sent to authors. 2023-04-06: reply received. 2023-04-11: This document normatively depends on draft-irtf-cfrg-spake2 (RFC-to-be 9382), which in turn depends on draft-irtf-cfrg-hash-to-curve (RFC-to-be 9380). 2023-04-11: Initial approvals from Chris Wood, Tim Taubert, and ISE. 2023-04-11: All approvals received. This document will be published when RFC-to-be 9382 and RFC-to-be 9380 are published. 2023-08-14: RFC 9380 has been published. Now waiting on RFC-to-be 9382. 2023-08-16: Chris Wood confirmed approval following today's updates to capitalization of two terms (now initial-capitalized). 2023-08-18: Tim Taubert confirmed approval. 2023-08-18: ISE confirmed approval.
Instructions to author(s):
Please see the AUTH48 notification email from the RFC Editor that contains links to the edited files and other information. To send your approval of or changes for a specific document, please Reply All to the message for the given RFC-to-be in question.
If cluster-wide questions were received, please Reply All to that email so each of the relevant parties may partake in the decision process.
See information below for the status of documents within the cluster that are in AUTH48.
When all approvals for a given document have been received, publication will continue once its normative references have completed the AUTH48 process as well. Upon publication of the cluster, this AUTH48 status page will no longer be available.