RFC 9298: Proxying UDP in HTTP
In plain English — editorial summary, not part of the RFC
This document describes how to proxy UDP in HTTP, similar to how the HTTP CONNECT method allows proxying TCP in HTTP. More specifically, this document defines a protocol that allows an HTTP client to create a tunnel for UDP communications through an HTTP server that acts as a proxy.
Document record
- Document ID
- RFC9298
- Published
- August 2022
- Authors
- D. Schinazi
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 16
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9297HTTP Datagrams and the Capsule ProtocolCurrent
August 2022
- RFC 9729The Concealed HTTP Authentication SchemeCurrent
February 2025
- RFC 9869Datagram Packetization Layer Path MTU Discovery (DPLPMTUD) for UDP OptionsCurrent
October 2025
- RFC 3519Mobile IP Traversal of Network Address Translation (NAT) DevicesCurrent
May 2003
- RFC 2354Options for Repair of Streaming MediaCurrent
June 1998
- RFC 9264Linkset: Media Types and a Link Relation Type for Link SetsCurrent
July 2022
- RFC 9368Compatible Version Negotiation for QUICCurrent
May 2023
- RFC 9211The Cache-Status HTTP Response Header FieldCurrent
June 2022
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?