Re: [quicwg/base-drafts] Connection migration must be negotiated (#1271)

[Tommy Pauly <[e-mail]>]

A few points:
- Generally, restrictions are around using metered interfaces when unmetered interfaces are available; when only a metered interface is available, things are more open. Migration in this case should be generally allowed.
- Preventing use of interfaces based on metering is separate from allowing migration. I can either let user policy or API specify that a connection should never use metered interfaces, but still migrate a connection between two Wi-Fi networks as my association changes. This also works for going between Wired Ethernet and Wi-Fi.

My main concern is that implementations, especially server implementations, MUST implement migration support, even if they allow it to be configured "off".

One of the points of migration is the path validation, which applies even in the case of NAT re-binding. For clients behind NATs, they may look to the server that they are "migrating" between ports, which is quite likely with UDP to happen quickly. By default, we should make sure connections are resilient here. The connection ID does give us the necessary support to allow the server to detect the case, and validate the path back to the client.

-- 
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/1271#issuecomment-379328731