Re: [quicwg/base-drafts] Limit RCID state (#3547)

[martinduke <[e-mail]>]

@martinduke commented on this pull request.



> @@ -1069,6 +1069,15 @@ to cease using the connection IDs when requested can result in connection
 failures, as the issuing endpoint might be unable to continue using the
 connection IDs with the active connection.
 
+An endpoint SHOULD limit the number of outstanding RETIRE_CONNECTION_ID frames
+to bound the necessary state. In order to allow a peer to retire all previously
+issued connection IDs, the limit on the number of outstanding
+RETIRE_CONNECTION_IDs SHOULD be at least the active_connection_id_limit. An

So we're limiting in-flight to 2*(the limit), which for us is currently 4. I set a very large threshold to tear down the connection -- currently, if highest_rpt is 100 more than least_unacked. That makes it exceedingly unlikely weird ack loss cases are going to bring me down, but I can tear down the connection if it gets ridiculous. There's really no difference in state between it being 50, 100, or 1000 -- it just means the client will get application data a little slower.

-- 
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/pull/3547#discussion_r401056926