Re:QUIC as a solution to protocol ossification
by _wmd on Friday February 09, 2018 @06:55AM
(#16339524)
Yoiks, good to know! When scanning the Quic docs, especially around the HTTP header that advertises an alternative protocol, the examples showed some random >1024 high port. I assumed that was part of the middlebox aversion stuff
But it makes perfect sense to have a defined port, so that connection racing can work without first having to receive a HTTP header
Sure you could use another port, but it looks like UDP 443 is becoming the unofficial standard, even if not IETF endorsed...