RFC 9001: Using TLS to Secure QUIC

This document describes how Transport Layer Security (TLS) is used to secure QUIC.

Read RFC 9001 on the RFC Editor

Outgoing relationships (3 related RFCs)

Normative reference — RFC 9000: QUIC: A UDP-Based Multiplexed and Secure Transport
Normative reference — RFC 9002: QUIC Loss Detection and Congestion Control
Informative reference — RFC 8879: TLS Certificate Compression

Incoming relationships (14 related RFCs)

Normatively referenced by — RFC 9000: QUIC: A UDP-Based Multiplexed and Secure Transport
Normatively referenced by — RFC 9002: QUIC Loss Detection and Congestion Control
Normatively referenced by — RFC 9221: An Unreliable Datagram Extension to QUIC
Normatively referenced by — RFC 9312: Manageability of the QUIC Transport Protocol
Normatively referenced by — RFC 9369: QUIC Version 2
Informatively referenced by — RFC 9325: Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
Informatively referenced by — RFC 9525: Service Identity in TLS
Informatively referenced by — RFC 9331: The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)
Informatively referenced by — RFC 9848: Bootstrapping TLS Encrypted ClientHello with DNS Service Bindings
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 9261: Exported Authenticators in TLS
Informatively referenced by — RFC 9506: Explicit Host-to-Network Flow Measurements Techniques
Informatively referenced by — RFC 9729: The Concealed HTTP Authentication Scheme