Re: [quicwg/base-drafts] Dual-NAT / Dual-load-balancer scenarios (#745)

[Mike Bishop <[e-mail]>]

Let's say we configure a connection to use ID A when sending from client-to-server, but ID B when sending from server-to-client.  Now the server receives a packet with connection ID A, but has lost all its state.

In the current model, the server generates a Stateless Reset packet that looks like any other packet it would send to the client, re-creates the token by deriving it from A, and pads out the packet with random nonsense.

With dual connection IDs, the server has no idea what connection ID it's supposed to use in reply packets, so it necessarily looks different from a "real" response packet.  It could reuse 'A' in the wrong direction, or could omit the Connection ID entirely, but both of those will be different from "real" responses.  (And if the Connection ID is actually needed to route back to the client, then neither of those will actually reach the other end anyway.)

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/745#issuecomment-328226218