ietf-wg-masque / draft-ietf-masque-quic-proxy

Other
12 stars 7 forks source link

Example unclear about long headers #37

Open gloinul opened 3 years ago

gloinul commented 3 years ago

The example states:

When the proxy receives a response from target.example.com:443 that has 0x31323334 as the Destination Connection ID, the proxy will forward that packet to the client on DATAGRAM flow ID 2.

And the later:

Upon receiving the response, the client starts sending Short Header packets with a Destination Connection ID of 0x61626364 directly to the proxy (not tunnelled), and these are forwarded directly to the target by the proxy. Similarly, Short Header packets from the target with a Destination Connection ID of 0x31323334 are forwarded directly to the client.

So the first paragraph I think it is correct as far as long header packets are received. However, will not short header packets from the target arriving at the proxy be forwarded to the client, even if the second request never happened. Thus, the implied connection to the response in the last sentence of the second paragraph is misleading.

tfpauly commented 3 years ago

Forwarding mode does rely on the second request being accepted, to allow the server to choose whether or not to forward. This doesn't support only forwarding in one direction, which we deemed to not be a useful feature.