Closed mirjak closed 5 months ago
Also from discussion in PR #292:
@huitema huitema on Nov 20, 2023
Retire Prior cannot be path specific. In practice, retire prior applies to all connection ID allocated before some event, such as rotation of the encryption key of connection ID used by the load balancer. In that scenario, repeating MP_RETIRE_CONNECTION_ID for every path would be very error prone.
@huitema huitema 2 weeks ago
OK, strike that. We are going for collection of CID per path (or per path ID), and identification of CID by the tuple {path_id, sequence}. So we pretty much need MP_RETIRE_CONNECTION_ID .
Also from discussion in PR #292:
@huitema huitema on Nov 20, 2023
Retire Prior cannot be path specific. In practice, retire prior applies to all connection ID allocated before some event, such as rotation of the encryption key of connection ID used by the load balancer. In that scenario, repeating MP_RETIRE_CONNECTION_ID for every path would be very error prone.
@huitema huitema 2 weeks ago
OK, strike that. We are going for collection of CID per path (or per path ID), and identification of CID by the tuple {path_id, sequence}. So we pretty much need MP_RETIRE_CONNECTION_ID .
@huitema sounds like we can close this issue. Can you confirm and go ahead and close?
Yes.
Yes. MP_RETIRE_CONNECTION_ID is needed. It's consensus
From discussion in PR #292:
huitema on Nov 20, 2023
@michael-eriksson michael-eriksson on Nov 23, 2023