What would you like to be added
A keyring that accepts the current and previous mesh key at once, so rotation does not need a coordinated restart.
Why is this needed
The design doc describes overlap as current behavior: rotation accepts current and previous keys without interrupting membership. The code holds one key. swim/src/crypto.rs: "safe rotation requires a coordinated restart or simultaneous replacement across sites because there is no multi-key keyring."
A partition during that restart window strands the rotation with sites on different keys.
Filing to verify intent and start tracking. If per-peer identity lands first this changes shape, since certificates renew one site at a time and no coordinated window exists.
From the Grid review, Gaps.
What would you like to be added
A keyring that accepts the current and previous mesh key at once, so rotation does not need a coordinated restart.
Why is this needed
The design doc describes overlap as current behavior: rotation accepts current and previous keys without interrupting membership. The code holds one key.
swim/src/crypto.rs: "safe rotation requires a coordinated restart or simultaneous replacement across sites because there is no multi-key keyring."A partition during that restart window strands the rotation with sites on different keys.
Filing to verify intent and start tracking. If per-peer identity lands first this changes shape, since certificates renew one site at a time and no coordinated window exists.
From the Grid review, Gaps.