AUTH48 status page for C430
Cluster Details
- draft-ietf-tls-8773bis-13.txt EDIT*R
- draft-ietf-tls-dtls-rrc-20.txt EDIT*R
- draft-ietf-tls-rfc8446bis-14.txt RFC-EDITOR
- draft-ietf-uta-require-tls13-12.txt EDIT*R
- draft-ietf-tls-tls12-frozen-08.txt EDIT*R
- draft-ietf-tls-svcb-ech-08.txt RFC-EDITOR*R
- draft-ietf-tls-keylogfile-05.txt RFC-EDITOR*R
- draft-ietf-quic-invariants-13.txt RFC8999 PUB
- draft-ietf-quic-transport-34.txt RFC9000 PUB
- draft-ietf-quic-tls-34.txt RFC9001 PUB
- draft-ietf-quic-recovery-34.txt RFC9002 PUB
- draft-ietf-httpbis-semantics-19.txt RFC9110 PUB
- draft-ietf-httpbis-cache-header-10.txt RFC9211 PUB
- draft-ietf-httpbis-messaging-19.txt RFC9112 PUB
- draft-ietf-httpbis-http2bis-07.txt RFC9113 PUB
- draft-ietf-quic-http-34.txt RFC9114 PUB
- draft-ietf-httpbis-expect-ct-08.txt RFC9163 PUB
- draft-irtf-cfrg-hpke-12.txt RFC9180 PUB
- draft-ietf-core-senml-data-ct-07.txt RFC9193 PUB
- draft-ietf-quic-qpack-21.txt RFC9204 PUB
- draft-ietf-httpbis-bcp56bis-15.txt RFC9205 PUB
- draft-ietf-httpbis-proxy-status-08.txt RFC9209 PUB
- draft-ietf-httpbis-cache-header-10.txt RFC9211 PUB
- draft-ietf-httpbis-targeted-cache-control-04.txt RFC9213 PUB
- draft-ietf-httpbis-priority-12.txt RFC9218 PUB
- draft-ietf-httpbis-h3-websockets-04.txt RFC9220 PUB
- draft-pauly-dprive-oblivious-doh-11.txt RFC9230 PUB
- draft-ietf-httpapi-linkset-10.txt RFC9264 PUB
- draft-ietf-httpbis-binary-message-06.txt RFC9292 PUB
- draft-ietf-tls-rfc8447bis-15.txt (RFC-to-be 9847) AUTH48
- draft-ietf-tls-esni-25.txt (RFC-to-be 9849) AUTH48*R
AUTH48 status of draft-ietf-tls-rfc8447bis-15 (RFC-to-be 9847)
This document is in AUTH48 state as of 2025-10-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 |
|---|---|---|
| J. Salowey (content) | N | |
| S. Turner (content) | N | |
| J. Salowey (format) | N | |
| S. Turner (format) | N | |
| IANA | N |
** This document is part of Cluster C430, so may have additional holds before publication.
Notes:
2025-10-30: Questions sent to authors. IANA action requested. 2025-10-31: Initial IANA actions are complete. Other registry updates will be needed prior to PUB. 2025-11-06: reminder sent. 2025-11-13: reminder sent. 2025-11-17: posted files. no outstanding questions. awaiting content approvals. 2025-11-25: reminder sent. posted files. updated iana cons section. RFC-EDITOR Note: IANA updates are needed prior to PUB. - updated note (Section 7) should be updated in the IANA registry
AUTH48 status of draft-ietf-tls-esni-25 (RFC-to-be 9849)
This document is in AUTH48 state as of 2025-11-14. 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 |
|---|---|---|
| E. Rescorla (content) | N | |
| K. Oku (content) | N | |
| N. Sullivan (content) | N | |
| C. A. Wood (content) | N | |
| E. Rescorla (format) | N | |
| K. Oku (format) | N | |
| N. Sullivan (format) | N | |
| C. A. Wood (format) | N | |
| IANA | N |
** This document is part of Cluster C430, so may have additional holds before publication.
Notes:
2025-11-14: questions sent to authors. 2025-11-25: updated files posted. 2 questions outstanding. Formatting: RFCYYY1 (draft-ietf-tls-svcb-ech) IANA: https://www.iana.org/assignments/tls-ech-configuration-extensions/tls-ech-configuration-extensions.xhtml - update "Grease entries" to "GREASE 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.
