[quicwg/base-drafts] Bundle new client connection ID and path challenge in migration probes (#1730)

[Christian Huitema <[e-mail]>]

During migration, the server will respond to the client's probe. If the client does not use a null length connection ID, the server needs to chose one of the destination connection ID specified by the client in "new connection ID" frames. There is however a synchronization issue. The client may have sent a new connection ID frame on another path, but that frame may not have yet been received when the probe arrives. The server is in a bind. It does not know whether the client sent a new connection ID or not. It does not know whether it should reuse an old ID and compromise privacy, or delay processing of the probe.

The synchronization issue is solved if the probe bundles NEW_CONNECTION_ID and PATH_CHALLENGE frames.
You can view, comment on, or merge this pull request online at:

  https://github.com/quicwg/base-drafts/pull/1730

-- Commit Summary --

  * Merge pull request #5 from quicwg/master
  * Specifying use of new connection ID to avoid correlation

-- File Changes --

    M draft-ietf-quic-transport.md (13)

-- Patch Links --

https://github.com/quicwg/base-drafts/pull/1730.patch
https://github.com/quicwg/base-drafts/pull/1730.diff

-- 
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/1730