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

[ianswett <[e-mail]>]

@ianswett commented on this pull request.

I don't think this describes quite what I had in mind, but maybe we can simplify this by not requiring sending RETIRE_CONNECTION_ID in this case?

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

```suggestion
An endpoint MAY elect to only send RETIRE_CONNECTION_ID frames
```

> @@ -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
+necessary state at the endpoint. For example, if an endpoint receives a Retire
+Prior To field of 7 and has an advertised active_connection_id_limit of 4, it
+may cease sending any RETIRE_CONNECTION_ID frame with sequence number less than

Is this the functionality we want?  If we're going to go this direction, we might as well just say you don't need to send RETIRE_CONNECTION_ID for anything below Retire Prior To, and you can assume it'll be retired 'soon'.  Maybe that's a good solution anyway?

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