News for hackers. Stuff that matters.
Re:QUIC as a solution to protocol ossification by nfoz on Friday February 09, 2018 @05:12AM (#16339155)
I wonder what is the real difference between QUIC vs SCTP-over-UDP?
Re:QUIC as a solution to protocol ossification by JulienSchmidt on Friday February 09, 2018 @07:03AM (#16339559)
Lower connection establishment latency: SCTP over UDP using DTLS requires 4 roundtrips (that's worse than standard TCP) while QUIC (which includes DTLS like encryption) only requires 1 roundtrip for the first connection and 0 RT for subsequent connections, when it cached some information.
Re:QUIC as a solution to protocol ossification by nfoz on Friday February 09, 2018 @02:23PM (#16343086)
Thanks, I found this: https://docs.google.com/document/d/1RNHkx_VvKWyWg6Lr8SZ-saqs...

"One of the major and believably achievable goals of QUIC, is to predominantly have zero RTT connection (re)establishment, as was mentioned in goal 3a above. It is highly doubtful that SCTP over DTLS can come close to achieving that goal."

----

I actually think the "zero round-trip-time" claim is a bit too strong. It's only 0RTT if you've communicated before, so in a way it's not a new connection. There's a privacy implication here -- you should wipe that state between communications to be more anonymous -- and also you only get "predominantely 0RTT" with an increasingly centralized web.

Re:QUIC as a solution to protocol ossification by baby on Friday February 09, 2018 @05:18AM (#16339182)
I'm guessing QUIC integrates better with HTTP/2?
Re:QUIC as a solution to protocol ossification by IshKebab on Friday February 09, 2018 @10:09AM (#16340684)
Or enet (ignoring encryption).