Re:QUIC as a solution to protocol ossification
by ibotty on Friday February 09, 2018 @05:53AM
(#16339301)
I don't want to mess with the content in any way, I do want to send connections over more than one WAN, depending on utilization. That works great with https?-connections on tcp. It would be great to be able to do the same with quic connections.
[ Parent
| on HN ]
Re:QUIC as a solution to protocol ossification
by cesarb on Friday February 09, 2018 @06:40AM
(#16339464)
> I do want to send connections over more than one WAN
QUIC has something which can help with that (from https://tools.ietf.org/html/draft-ietf-quic-transport-09):
"QUIC connections are identified by a Connection ID, a 64-bit unsigned number randomly generated by the server. QUIC's consistent connection ID allows connections to survive changes to the client's IP and port, such as those caused by NAT rebindings or by the client changing network connectivity to a new address."
If that's not enough for your use cases, now is a good opportunity to mention them and suggest enhancements, since the IETF standard is still under development.