| CARVIEW |
Select Language
HTTP/2 200
date: Mon, 14 Jul 2025 19:12:52 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 95f355807b3ec17e-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 9001 » RFC Editor
Search RFCs
RFC 9001
Using TLS to Secure QUIC, May 2021
- File formats:
- Also available: XML file for editing
- Status:
- PROPOSED STANDARD
- Authors:
- M. Thomson, Ed.
S. Turner, Ed. - Stream:
- IETF
- Source:
- quic (wit)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC9001
Discuss this RFC: Send questions or comments to the mailing list quic@ietf.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 9001
Abstract
This document describes how Transport Layer Security (TLS) is used to secure QUIC.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us