RFC 9000: QUIC: A UDP-Based Multiplexed and Secure Transport

This document defines the core of the QUIC transport protocol. QUIC provides applications with flow-controlled streams for structured communication,…

Read RFC 9000 on the RFC Editor

Outgoing relationships (4 related RFCs)

Normative reference — RFC 9001: Using TLS to Secure QUIC
Normative reference — RFC 9002: QUIC Loss Detection and Congestion Control
Normative reference — RFC 8999: Version-Independent Properties of QUIC
Informative reference — RFC 8981: Temporary Address Extensions for Stateless Address Autoconfiguration in IPv6

Incoming relationships (74 related RFCs)

Showing 50 of 74 related RFCs.

Normatively referenced by — RFC 9114: HTTP/3
Normatively referenced by — RFC 9001: Using TLS to Secure QUIC
Normatively referenced by — RFC 9002: QUIC Loss Detection and Congestion Control
Normatively referenced by — RFC 9640: YANG Data Types and Groupings for Cryptography
Normatively referenced by — RFC 9645: YANG Groupings for TLS Clients and TLS Servers
Normatively referenced by — RFC 9641: A YANG Data Model for a Truststore
Normatively referenced by — RFC 9642: A YANG Data Model for a Keystore
Normatively referenced by — RFC 9298: Proxying UDP in HTTP
Normatively referenced by — RFC 9643: YANG Groupings for TCP Clients and TCP Servers
Normatively referenced by — RFC 9221: An Unreliable Datagram Extension to QUIC
Normatively referenced by — RFC 9644: YANG Groupings for SSH Clients and SSH Servers
Normatively referenced by — RFC 9204: QPACK: Field Compression for HTTP/3
Normatively referenced by — RFC 9297: HTTP Datagrams and the Capsule Protocol
Normatively referenced by — RFC 9292: Binary Representation of HTTP Messages
Normatively referenced by — RFC 9458: Oblivious HTTP
Normatively referenced by — RFC 9484: Proxying IP in HTTP
Normatively referenced by — RFC 9287: Greasing the QUIC Bit
Normatively referenced by — RFC 9312: Manageability of the QUIC Transport Protocol
Normatively referenced by — RFC 9368: Compatible Version Negotiation for QUIC
Normatively referenced by — RFC 9648: YANG Data Model for TCP
Normatively referenced by — RFC 9826: A YANG Data Model for the Path Computation Element Communication Protocol (PCEP)
Normatively referenced by — RFC 9369: QUIC Version 2
Normatively referenced by — RFC 9506: Explicit Host-to-Network Flow Measurements Techniques
Normatively referenced by — RFC 9647: A YANG Data Model for Babel
Normatively referenced by — RFC 9693: Benchmarking Methodology for Stateful NATxy Gateways
Normatively referenced by — RFC 9729: The Concealed HTTP Authentication Scheme
Normatively referenced by — RFC 9761: Manufacturer Usage Description (MUD) for TLS and DTLS Profiles for Internet of Things (IoT) Devices
Informatively referenced by — RFC 9293: Transmission Control Protocol (TCP)
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 9200: Authentication and Authorization for Constrained Environments Using the OAuth 2.0 Framework (ACE-OAuth)
Informatively referenced by — RFC 9438: CUBIC for Fast and Long-Distance Networks
Informatively referenced by — RFC 9330: Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture
Informatively referenced by — RFC 9331: The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)
Informatively referenced by — RFC 9065: Considerations around Transport Header Confidentiality, Network Operations, and the Evolution of Internet Transport Protocols
Informatively referenced by — RFC 9258: Importing External Pre-Shared Keys (PSKs) for TLS 1.3
Informatively referenced by — RFC 9522: Overview and Principles of Internet Traffic Engineering
Informatively referenced by — RFC 9528: Ephemeral Diffie-Hellman Over COSE (EDHOC)
Informatively referenced by — RFC 9834: YANG Data Models for Bearers and Attachment Circuits as a Service (ACaaS)
Informatively referenced by — RFC 9835: A Network YANG Data Model for Attachment Circuits
Informatively referenced by — RFC 9049: Path Aware Networking: Obstacles to Deployment (A Bestiary of Roads Not Taken)
Informatively referenced by — RFC 9833: A Common YANG Data Model for Attachment Circuits
Informatively referenced by — RFC 9836: A YANG Data Model for Augmenting VPN Service and Network Models with Attachment Circuits
Informatively referenced by — RFC 9907: Guidelines for Authors and Reviewers of Documents Containing YANG Data Models
Informatively referenced by — RFC 9621: Architecture and Requirements for Transport Services
Informatively referenced by — RFC 9623: Implementing Interfaces to Transport Services
Informatively referenced by — RFC 9064: Considerations in the Development of a QoS Architecture for CCNx-Like Information-Centric Networking Protocols
Informatively referenced by — RFC 9170: Long-Term Viability of Protocol Extension Mechanisms
Informatively referenced by — RFC 9317: Operational Considerations for Streaming Media
Informatively referenced by — RFC 9411: Benchmarking Methodology for Network Security Device Performance