RE: Interest in a UDP equivalent to the CONNECT method

Hi Göran,

The intent is to emulate the behavior of CONNECT as far as possible, just with UDP as the transport for the remote side.

To this end, the scenario would allow a chain. From RFC 7231 section 4.2.6:

   The recipient proxy can establish a tunnel either by directly
   connecting to the request-target or, if configured to use another
   proxy, by forwarding the CONNECT request to the next inbound proxy.

Regards
Lucas

From: Göran Eriksson AP [mailto:goran.ap.eriksson@ericsson.com]
Sent: 03 February 2018 15:42
To: Lucas Pardue <Lucas.Pardue@bbc.co.uk>; HTTP Working Group <ietf-http-wg@w3.org>
Cc: bemasc@google.com
Subject: Re: Interest in a UDP equivalent to the CONNECT method


On 2018-02-03, 15:31, "Lucas Pardue" <Lucas.Pardue@bbc.co.uk<mailto:Lucas.Pardue@bbc.co.uk>> wrote:

The sad part here is that an HTTP/QUIC client that uses an HTTP/QUIC proxy in this mode needs to support TCP for secure connection to the remote host. This presents some resistance to moving away from TCP in the future.

Just to make sure I get it right; the intent is to support the case of a  L4 proxy (L4 after connection being established) with UDP (QUIC) on the remote side, as seen from the client.

If so, +1.

Does your scenario assume only one proxy between the client and the remote host or is the case of a set of proxies in a chain included?

Best Regards
Göran