RFC 9484: Proxying IP in HTTP

This document describes how to proxy IP packets in HTTP. This protocol is similar to UDP proxying in HTTP but allows transmitting arbitrary IP packets. More…

Read RFC 9484 on the RFC Editor

Outgoing relationships (22 related RFCs)

Updates, Informative reference — RFC 9298: Proxying UDP in HTTP
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 3168: The Addition of Explicit Congestion Notification (ECN) to IP
Normative reference — RFC 2474: Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers
Normative reference — RFC 9000: QUIC: A UDP-Based Multiplexed and Secure Transport
Normative reference — RFC 9113: HTTP/2
Normative reference — RFC 9114: HTTP/3
Normative reference — RFC 6570: URI Template
Normative reference — RFC 6874: Representing IPv6 Zone Identifiers in Address Literals and Uniform Resource Identifiers
Normative reference — RFC 8441: Bootstrapping WebSockets with HTTP/2
Normative reference — RFC 9221: An Unreliable Datagram Extension to QUIC
Normative reference — RFC 9209: The Proxy-Status HTTP Response Header Field
Normative reference — RFC 9220: Bootstrapping WebSockets with HTTP/3
Normative reference — RFC 9297: HTTP Datagrams and the Capsule Protocol
Informative reference — RFC 4301: Security Architecture for the Internet Protocol
Informative reference — RFC 4291: IP Version 6 Addressing Architecture
Informative reference — RFC 6040: Tunnelling of Explicit Congestion Notification
Informative reference — RFC 8899: Packetization Layer Path MTU Discovery for Datagram Transports
Informative reference — RFC 5095: Deprecation of Type 0 Routing Headers in IPv6
Informative reference — RFC 6169: Security Concerns with IP Tunneling
Informative reference — RFC 8305: Happy Eyeballs Version 2: Better Connectivity Using Concurrency

Incoming relationships (2 related RFCs)

Informatively referenced by — RFC 9614: Partitioning as an Architecture for Privacy
Informatively referenced by — RFC 9931: Security Considerations for Optimistic Protocol Transitions in HTTP/1.1