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

It occurred to me that we might be talking about two entirely different ideas.

1) The "Maximum number of outstanding RCIDs" is a momentary restriction. I might send only 10 at a time, or whatever, but eventually I will send all of the RCIDs that the protocol required before any of these PRs.

2) I need only send N RCIDs at a time, and can assume all other (earlier) sequence numbers have been de facto retired.

If my limit is 10 and I get 100 NCIDs that increment RPT by 1 in rapid succession, option (1) would have us send all 100 RCIDs over 10 RTTs, assuming no loss. option (2) would have us send 10 and be done with it. Which are we describing here?

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