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

[Kazuho Oku <[e-mail]>]

@kazuho 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

@martinduke Thank you for sharing your experience.

Could you please clarify why you have two limits? Are you limiting the number of inflight RCID frames to 4, even though you retain state of up to 100 CIDs to be retired?

I'm curious, because that's not something I would expect as an outcome of this PR. My read of the text proposed in the PR has been that we assume that a RCID frame becomes "outstanding" when an endpoint decides to (or being instructed to) retire a CID.

IIUC, what we need to do is limit the amount of state that the endpoint retains. Number of RCID frames sent at one time does not really matter, as it is bound by the CWND size.

-- 
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_r401277994