[quicwg/base-drafts] Forced connection ID retirement (#3420)

[Martin Thomson <[e-mail]>]

Requiring RETIRE_CONNECTION_ID has lead to all sorts of corner cases.  For instance, a server can force a client to retire the connection ID that is still in use for the handshake.  (We're uncertain yet as to whether the newly provided connection ID usable here, so this only *might* cause genuine problems.)

More to the point, this design assumes things about the nature of connection IDs and routing infrastructure that imply a coupling between path and endpoint state.  The reason you might want to retire a connection ID forcibly in this fashion is that it is no longer usable for routing purposes (or that it results in suboptimal routing, perhaps where packets need to be bounced between nodes in a cluster).

All of this implies that the address tuple is part of the routing assessment.  That makes this feature fragile and it also creates some uncertainty about whether it is possible to build such a system without having a stateless reset oracle.

-- 
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/3420