Wtf I love QUIC now.
Wtf I love QUIC now
Dominic Morgan
Other urls found in this thread:
daniel.haxx.se
twitter.com
Grayson Gray
Mason Jenkins
>server pushes content instead of browser asking for it
JUST fill me up with ads, daddy!
Thomas Cruz
Can you read? The server responds to a request from the client, it's just TLS ClientHello and the request are all sent in the first packet, instead of waiting for a TCP connection to establish itself.
Alexander Adams
I didn't open any pics, and no I didn't not read either (cause apparently I read that as SPDY).
Kevin Turner
> QUIC has built-in mitigation against amplification attacks by requiring that the initial packet must be at least 1200 bytes and by restriction in the protocol that says that a server MUST NOT send more than three times the size of the request in response without receiving a packet from the client in response.
Joseph Perez
Isn't this open for network amplification? Send a small packet with the target IP and let the server respond with the "Application Data: response" which presumably would be way larger than the single packet request. I dont see how the handshake is validated.
Eli Hernandez
->
Levi Sanchez
>the initial packet must be at least 1200 bytes
>a server MUST NOT send more than three times the size of the request in response
so, Quick works by padding your packet. Basacally a waste compared to http if you're not using the 1200 bytes.
an amplification factor of 2 is still usefull. though there are probaly not alot of quick servers out there.
Sending small packets isn't that much of a problem. Handshakes happen fast enough to be hidden from the user.
Bentley Turner
> Basacally a waste compared to http if you're not using the 1200 bytes.
True, but only for the first packet in the session, not much. It's more interesting how they first try to eliminate latency at the session establishment but then introduce latency requiring the server to wait for an ACK packet before sending the rest of the data.