Cluster Details

• 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-19.txt  RFC9111  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

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.