News for hackers. Stuff that matters.
Re:QUIC as a solution to protocol ossification by londons_explore on Friday February 09, 2018 @04:45AM (#16339050)
Simply classifying on UDP port 443 would cover most usecases I'd guess?
Re:QUIC as a solution to protocol ossification by _wmd on Friday February 09, 2018 @05:19AM (#16339188)
Where did you get 443 from? AFAIK even Google aren't using that. I didn't think there was any standardized port number at all
Re:QUIC as a solution to protocol ossification by londons_explore on Friday February 09, 2018 @06:33AM (#16339435)
Google uses UDP 443 for all it's quic services. Chrome will autoconnect to UDP 443 for any https request in parallel with TCP, and prefer QUIC if it works.

Sure you could use another port, but it looks like UDP 443 is becoming the unofficial standard, even if not IETF endorsed...

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