9 Comments

You wrote that QUIC is, “just a layer or wrapper on top of UDP.” To make sure people understand your meaning correctly, you should explain this is exactly equivalent to how “TCP is just a layer or wrapper on top of IP.” IP and UDP are both datagrams, and TCP and QUIC are both transport layers that run over datagrams. (If history had played out just a little differently, we might have designed the TCP transport layer to run over UDP datagrams — just like how QUIC works.)

Expand full comment

The meme you posted is racist.

Expand full comment

Trivial typo:

"packets in it’s buffer" ->

"packets in its buffer"

The sentence starting with "Although, it’s simple to enhance TCP" seems to have some missing words. Plus, you need to be consistent in your use of "space" vs. "layer".

Other than these minor details, this was a very clear explanation.

Expand full comment

hey the labels on the steps of tcp handshake above are off...

Expand full comment

sorry took me a long time to read article, didn't reload, hadnt seen comment below

Expand full comment

Not to be pedantic, but your TCP 3 way handshake picture shows the SYN-ACK before the ACK. But then describes it correctly in the paragraph below it.

Expand full comment
author

Thanks for the correction Jeff. Will update it.

Expand full comment

"It [TCP] guarantees delivery of all the packets from one device to another"

This is untrue. There is no concept of packets here. In my experience programming servers and clients the only thing that is true is any bytes received on one side is guaranteed to be in the same order as it was sent. It might still not be all the bytes, or even at the same time.

Expand full comment
author

I believe guaranteed delivery of all the data is fundamental feature of TCP. What do you mean by "no concept of packets" ?

Expand full comment