AUTH48 status page for C475
Cluster Details
- draft-ietf-httpapi-rfc7807bis-07.txt RFC9457 PUB
- draft-ietf-ohai-ohttp-10.txt (RFC-to-be 9458) AUTH48
AUTH48 status of draft-ietf-ohai-ohttp-10 (RFC-to-be 9458)
This document is in AUTH48 state as of 2023-10-06. 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 |
|---|---|---|
| M. Thomson | N | |
| C. Wood | Y | 2023-10-16 |
| AD - M. Kucherawy | N |
** This document is part of Cluster C475, so may have additional holds before publication.
Notes:
2023-10-06: questions sent to authors.
2023-10-09: received response from authors.
2023-10-13: question sent to authors about links.
2023-10-16: posted files; still open discussion about links; one question for AD.
2023-10-16: received response from authors.
2023-10-18: posted files; still open discussion about links and one question for AD.
2023-17-17: posted update that avoids formatting issues in the XML file. Waiting on the following:
- a response from RSAB regarding the links and index. a
- a new release of xml2rfc that includes “deduplicate index entries”
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.