The CONNECT-IP method for proxying IP traffic
draft-kuehlewind-masque-connect-ip-00
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
---|---|---|---|
Authors | Mirja Kühlewind , Magnus Westerlund , Marcus Ihlar , Zaheduzzaman Sarker | ||
Last updated | 2021-05-06 (Latest revision 2020-11-02) | ||
Replaced by | draft-age-masque-connect-ip | ||
RFC stream | (None) | ||
Formats | |||
Additional resources | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This draft specifies a new HTTP/3 method CONNECT-IP to proxy IP traffic. CONNECT-IP can be used to convert a QUIC stream into a tunnel or initialise an HTTP datagram flow to a forwarding proxy. Each stream or HTTP datagram flow can be used separately to establish forwarding of an IP flow to potentially different remote hosts. To request forwarding, a client connects to a proxy server by initiating a HTTP/3 connection and sends a CONNECT-IP indicating the address of the target server. The proxy server then forwards payload received on that stream or in an HTTP datagram with a certain flow ID to the target server after adding an IP header to each of the frames received.
Authors
Mirja Kühlewind
Magnus Westerlund
Marcus Ihlar
Zaheduzzaman Sarker
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)