| CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 17:27:58 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
set-cookie: __cf_bm=hC.Y0ny.pS27j6cVWRX8A0FktAGK6DSO_aEgUfxAtv8-1760030878-1.0.1.1-XGewcy8qMlVS6XlaVYolmBaVZiRC2hPWfhM8IBnkIei2f4wmK8o2S1Q0s2H00jExkmHX2wq94fBbkp_JQKUjkazmbiGUqPhPPjgdDzKky6Y; path=/; expires=Thu, 09-Oct-25 17:57:58 GMT; domain=.rfc-editor.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98bf9776afdec1f7-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 8999 » RFC Editor
Search RFCs
RFC 8999
Version-Independent Properties of QUIC, May 2021
- File formats:
- Also available: XML file for editing
- Status:
- PROPOSED STANDARD
- Updated by:
- RFC 9368
- Author:
- M. Thomson
- Stream:
- IETF
- Source:
- quic (wit)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC8999
Discuss this RFC: Send questions or comments to the mailing list quic@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8999
Abstract
This document defines the properties of the QUIC transport protocol that are common to all versions of the protocol.
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