search

marten-seemann / draft-seemann-quic-nat-traversal

Other
15 stars 4 forks source link

Compatibility with multipath #30

Open huitema opened 2 months ago

huitema commented 2 months ago

The proposed mechanism is to have server and clients start "path validation" simultaneously, using the "PUNCH_ME_NOW" frame for synchronization. I assume that the goal is to create a single path.

There is no problem doing that with RFC 9000, but there is an issue if the multipath extension is negotiated, because then path creation implies picking a path ID -- i.e., both server and client pick a CID associated with the same path-ID. If they don't, we get two paths.

The simplest way to do that would be to add a "path_id" element in the PUNCH_ME_NOW frame.

huitema commented 2 months ago

Or, we will have to define MP_PUNCH_ME_NOW, but that does not feel right.