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

[Praveen Balasubramanian <[e-mail]>]

Connection migration is an optional feature of the QUIC transport protocol. An implementation should be allowed to omit it.

Server considerations:
Scalable  server deployment requires load balancing. Connection migration will require QUIC aware support from the load balancer. Most load balancers available today do not have this support. If a server does not support connection migration or is behind a load balancer that is known to not support QUIC, then all migrated traffic looks like attack traffic and will likely trip up DoS mitigation and cause a lot of traffic to failover to TCP unnecessarily.

Client considerations:
Many client devices will only have one network card or only one network available at a time. Most desktops, laptops and many tablets will qualify. Even of mobile devices, OS policy may dictate that metered connections must not be used aggressively or automatically. Applications may have policy or requirement that their traffic must not flow over specific interfaces - for example update traffic today must not flow over metered networks. 

For these reasons, clients which do implement migration, should make a negotiate attempt for connection migration support based on application and OS policy. Servers that know that they can support migration should negotiate and accept the request. 





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