Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
Does ASP.NET Core support QUIC Client migration when using HTTP/3, and there are multiple servers behind a load balancer? Assuming the load balancer using source-destination addresses for balancing?
The issue described here: https://www.rfc-editor.org/rfc/rfc9000.html#name-considerations-for-simple-l
Describe the solution you'd like
I am curious if this is feasible at all.
Additional context
No response
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
Does ASP.NET Core support QUIC Client migration when using HTTP/3, and there are multiple servers behind a load balancer? Assuming the load balancer using source-destination addresses for balancing?
The issue described here: https://www.rfc-editor.org/rfc/rfc9000.html#name-considerations-for-simple-l
Describe the solution you'd like
I am curious if this is feasible at all.
Additional context
No response