AUTH48 status page for C509
Cluster Details
- draft-ietf-httpbis-compression-dictionary-19.txt MISSREF*R(1G)
- draft-ietf-httpbis-sfbis-06.txt (RFC-to-be 9651) AUTH48
- draft-ietf-httpapi-link-template-04.txt (RFC-to-be 9652) AUTH48-DONE*R
AUTH48 status of draft-ietf-httpbis-sfbis-06 (RFC-to-be 9651)
This document is in AUTH48 state as of 2024-08-28. 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. Nottingham | N | |
| P-H. Kamp | N |
** This document is part of Cluster C509, so may have additional holds before publication.
Notes:
2024-08-28 Questions sent to authors. 2024-09-05 Response received from M. Nottingham. 2024-09-09 Feedback incorporated. 2024-09-18 Reminder sent. 2044-09-26 Reminder sent. Response received from P-H. Kamp. Feedback incorporated. Note that the RFC Editor will ask IANA to make a minor typographical update to the Note for the "Hypertext Transfer Protocol (HTTP) Field Name Registry" when all author approvals are received.
AUTH48-DONE status of draft-ietf-httpapi-link-template-04 (RFC-to-be 9652)
This document is in AUTH48 state as of 2024-08-30. 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. Nottingham | Y | 2024-09-04 |
** This document is part of Cluster C509, so may have additional holds before publication.
Notes:
2024-08-30: Questions sent to author. 2024-08-31: Response received from M. Nottingham. 2024-09-03: Feedback incorporated. 2024-09-04: Approval received. Waiting for RFC-to-be RFC 9651 (draft-ietf-httpbis-sfbis-06) to complete AUTH48.
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.