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

[martinduke <[e-mail]>]

@martinduke commented on this pull request.



> @@ -1069,6 +1069,18 @@ 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 MAY elect to only send or retransmit RETIRE_CONNECTION_ID frames
+with sequence numbers greater than or equal to the highest Retire Prior To field
+received minus its advertised active_connection_id_limit. This bounds the

I guess we're going to have this discussion in two places, but I'm not sure the non-RPT case is a valid threat model.

I am a little concerned with your formulation that the endpoint could make bad choices about which RCIDs it decides to stick with. For example, we might never increase RPT and for some reason have a low sequence number that sticks around and is still being used. The server really better actually send the RCID.

I'm happy to haggle about the exact threshold, but my formulation frees the endpoint of all the state only when the client is doing something legal but silly.

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