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

[ianswett <[e-mail]>]

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

You can only retire as many as you store, so the only way you could have more than max_connection_id_limit RETIRE_CONNECTION_ID frames outstanding is if you need to retransmit all of them due to loss and subsequently you've both received a new connection ID AND need to retire it.  Retiring it because you decided to use it typically takes at least a round trip, so it's most likely the subsequent retiring is due to the peer's Retire Prior To increasing again.

Given the above situation starts looking increasingly like an attack(or a bug) and sending RETIRE_CONNECTION_ID quickly for the Retire Prior To case isn't critical, I'd suggest max_connecion_id_limit is a better recommendation.

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