RFC 9114: HTTP/3

The QUIC transport protocol has several features that are desirable in a transport for HTTP, such as stream multiplexing, per-stream flow control, and…

Read RFC 9114 on the RFC Editor

Outgoing relationships (5 related RFCs)

Normative reference — RFC 9000: QUIC: A UDP-Based Multiplexed and Secure Transport
Normative reference — RFC 9110: HTTP Semantics
Normative reference — RFC 9204: QPACK: Field Compression for HTTP/3
Informative reference — RFC 9113: HTTP/2
Informative reference — RFC 9112: HTTP/1.1

Incoming relationships (20 related RFCs)

Normatively referenced by — RFC 9298: Proxying UDP in HTTP
Normatively referenced by — RFC 9204: QPACK: Field Compression for HTTP/3
Normatively referenced by — RFC 9218: Extensible Prioritization Scheme for HTTP
Normatively referenced by — RFC 9220: Bootstrapping WebSockets with HTTP/3
Normatively referenced by — RFC 9297: HTTP Datagrams and the Capsule Protocol
Normatively referenced by — RFC 9484: Proxying IP in HTTP
Informatively referenced by — RFC 9460: Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
Informatively referenced by — RFC 9205: Building Protocols with HTTP
Informatively referenced by — RFC 9440: Client-Cert HTTP Header Field
Informatively referenced by — RFC 9292: Binary Representation of HTTP Messages
Informatively referenced by — RFC 9458: Oblivious HTTP
Informatively referenced by — RFC 9312: Manageability of the QUIC Transport Protocol
Informatively referenced by — RFC 9317: Operational Considerations for Streaming Media
Informatively referenced by — RFC 9411: Benchmarking Methodology for Network Security Device Performance
Informatively referenced by — RFC 10003: Certificate Management over CMS (CMC): Transport Protocols
Informatively referenced by — RFC 9275: An Extension for Application-Layer Traffic Optimization (ALTO): Path Vector
Informatively referenced by — RFC 9369: QUIC Version 2
Informatively referenced by — RFC 9729: The Concealed HTTP Authentication Scheme
Informatively referenced by — RFC 9931: Security Considerations for Optimistic Protocol Transitions in HTTP/1.1
Informatively referenced by — RFC 10006: Automatic SIP Trunking and Peering