Re: [quicwg/base-drafts] simultaneous key update can lead to deadlock (#2214)

[Martin Thomson <[e-mail]>]

@kazuho, that's not a fix the problem that @marten-seemann is talking about, but if that's not written down, then that's also a problem.

The problem here is that one endpoint is updating too aggressively, even if it is entirely permissible.  If that coincides with an update on the other end, there is the possibility that one side thinks that no update has occurred, when two updates have happened.

The fix here is - I think - waiting for acknowledgment of a packet with the key phase.  Which means that you don't get to just use the key phase bit to drive this.  The interesting thing here is that when you couple this to acknowledgments you can validate updates.  If someone acknowledges an update with old keys, then you know they are misbehaving.

-- 
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/issues/2214#issuecomment-449195528