Re: [quicwg/base-drafts] MUST retire Connection IDs becoming stale (#3096)

[Martin Thomson <[e-mail]>]

martinthomson commented on this pull request.

I think that the most interesting behaviour to specify is at the endpoint that requests retirement.  "Endpoints that request that peers retire connection IDs SHOULD be prepared to receive packets that contain connection IDs that they have requested be retired for a period of approximately three times the PTO."

> @@ -1032,10 +1032,11 @@ longer plans to use that address.
 
 An endpoint can request that its peer retire connection IDs by sending a
 NEW_CONNECTION_ID frame with an increased Retire Prior To field.  Upon receipt,
-the peer SHOULD retire the corresponding connection IDs and send the
-corresponding RETIRE_CONNECTION_ID frames in a timely manner.  Failing to do so
-can cause packets to be delayed, lost, or cause the original endpoint to send a
-stateless reset in response to a connection ID it can no longer route correctly.
+the peer MUST retire the corresponding connection IDs and send corresponding
+RETIRE_CONNECTION_ID frames.  Failing to retire the connection IDs within one
+PTO can cause packets to be delayed, lost, or cause the original endpoint to

Maybe we could even say "approximately", and add "Endpoints that request that peers retire connection IDs SHOULD be prepared to receive packets that contain connection IDs that they have requested be retired for a period of approximately three times the PTO."

-- 
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/3096#pullrequestreview-302670225