AUTH48 status page for C394

Cluster Details


AUTH48-DONE status of draft-ietf-lamps-rfc6844bis-07 (RFC-to-be 8644)

This document is in AUTH48 state as of 2019-08-12. 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
P. Hallam-Baker Y 2019-09-20
R. Stradling Y 2019-09-20
J. Hoffman-Andrews Y 2019-09-20

** This document is part of Cluster C394, so may have additional holds before publication.

Notes:

2019-08-12: questions sent to authors (no cluster questions exist).


AUTH48-DONE status of draft-ietf-acme-caa-10 (RFC-to-be 8657)

This document is in AUTH48 state as of 2019-08-12. 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
H. Landau (content approved 9/28) Y 2019-10-01

** This document is part of Cluster C394, so may have additional holds before publication.

Notes:

2019-08-12: questions sent to author (no cluster questions exist). 2019-09-30: Received author approval for RFC 8647. However, we have notified him that this document has been converted to XML version 3 and will be assigned a new RFC number. 2019-09-30: v3 auth48 initiated. 2019-10-01: Received author approval for v3 RFC 8657. Informed the author that because (1) this document lists RFC-to-be 8644 as a Normative Reference and (2) the authors of RFC-to-be 8644 let us know on 2019-09-30 that they would like us to convert their document to v3 and give it a new RFC number, this document (8657) will be published when RFC-to-be 8644 (with the new "v3" number) is published.


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.