Re: [quicwg/base-drafts] Looping with multiple Retry packets (#1451)

[Kazuho Oku <[e-mail]>]

@marten-seemann 
> In an end-to-end protocol, we generally don't want "helpful" middleboxes to interfere with handshakes by performing a Retry (and thereby introducing latency). Obviously, this statement depends on the definition of "middlebox", which I here use as any node on the path that neither belongs to the server's nor the client's architecture.
We should design QUIC's retry mechanism such that a retry can **only** be performed by devices that are under the control of the server operator.

+1

I agree to what Marten says.

Allowing middleboxes that send retries without sharing secrets with the servers has two issues:
* the feature can be abused by somebody other than server operator
* that in turn may lead to ossification, considering the fact that Retry is not a invariant

Considering that, I'd prefer having a retry mechanism that enforces sharing a secret between the middlebox (that sends a retry) and the server. Which in turns would mean that multiple retries are unnecessary.

-- 
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/1451#issuecomment-398317321