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

[Kazuho Oku <[e-mail]>]

@kazuho commented on this pull request.

Thank you for working on the PR. I think this PR almost done.

The only complaint I have is the limit, which as I have previously stated. If people are going to use the minimum recommended value, it becomes risky to retire all CIDs at once. I'd prefer recommending something safer. Please see my suggestion below.

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

How about something like: _In order to allow a peer to retire all previously issued connection IDs while an endpoint waits for some RETIRE_CONNECTION_ID frames to be acknowledged, the limit on the number of outstanding RETIRE_CONNECTION_IDs SHOULD be at least the active_connection_id_limit plus the number of retirements that the endpoint might initiate at one time._

-- 
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#pullrequestreview-384353335