RFC 8999: Version-Independent Properties of QUIC
In plain English — editorial summary, not part of the RFC
This document defines the properties of the QUIC transport protocol that are common to all versions of the protocol.
Document record
- Document ID
- RFC8999
- Published
- May 2021
- Authors
- M. Thomson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 9
- Also known as
- —
- Updated by:
- RFC 9368
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9000QUIC: A UDP-Based Multiplexed and Secure TransportCurrent
May 2021
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
- RFC 8899Packetization Layer Path MTU Discovery for Datagram TransportsCurrent
September 2020
- RFC 9134RTP Payload Format for ISO/IEC 21122 (JPEG XS)Current
October 2021
- RFC 4366Transport Layer Security (TLS) ExtensionsObsoleted
April 2006
- RFC 3759RObust Header Compression (ROHC): Terminology and Channel Mapping ExamplesCurrent
April 2004
- RFC 3257Stream Control Transmission Protocol Applicability StatementCurrent
April 2002
- RFC 3243RObust Header Compression (ROHC): Requirements and Assumptions for 0-byte IP/UDP/RTP CompressionCurrent
April 2002
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?