Hi Mikkel, I think this current protocol does not prevent you from doing that as it is designed as a minimally-scoped extension of QUIC-v1. The goal is to make it easier for people to try different things with multi-path. As pointed out by Christian, announcing address/port/QoE does have some complexity. One way is to let the client server cooperate, but you may also want to use a STUN server to help you achieve that which is similar to the case of RTC. We would appreciate it if you could try and let us know your experience.
Cheers, Yunfei On Mon, Dec 14, 2020 at 2:56 PM Mikkel Fahnøe Jørgensen <[email protected]> wrote: > These are good problems to address, but I would rather address them in a > targeted effort than as part of the multipath design. > > Good point and interesting description on VPN case. > > I think it would be helpful for multipath to still consider this at an > abstract level such that it can be plugged in at a later point without > deciding on the exact details up front, if for no other reason than to > avoid hardcoding things that don’t have to be. > > >
