RFC 9001: Using TLS to Secure QUIC
In plain English — editorial summary, not part of the RFC
This document describes how Transport Layer Security (TLS) is used to secure QUIC.
Document record
- Document ID
- RFC9001
- Published
- May 2021
- Authors
- M. Thomson; S. Turner
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 52
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8999Version-Independent Properties of QUICUpdated
May 2021
- RFC 9577The Privacy Pass HTTP Authentication SchemeCurrent
June 2024
- RFC 7619The NULL Authentication Method in the Internet Key Exchange Protocol Version 2 (IKEv2)Current
August 2015
- RFC 6605Elliptic Curve Digital Signature Algorithm (DSA) for DNSSECCurrent
April 2012
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
- RFC 9002QUIC Loss Detection and Congestion ControlCurrent
May 2021
- RFC 9000QUIC: A UDP-Based Multiplexed and Secure TransportCurrent
May 2021
- RFC 8985The RACK-TLP Loss Detection Algorithm for TCPCurrent
February 2021
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?