Hello and welcome to the Thursday, March 7, 2024 edition of the Sansonet Storms, Stormcast.

My name is Johannes Ulrich, and today I'm recording from Jacksonville, Florida.

Today we have an exceptional good diary by Boyan.

I want to spend a little bit time on this today, and this diary is about Quick.

Quick being the new protocol or relatively new protocol that was developed by Google and initially used with HTTP in order to create HTTP.

But Quick tries to do a lot more than just sort of update HTTP.

Quick really is more replacement for TCP.

Now, Quick is running over UDP, but UDP being essentially data over IP,

all of the intelligence in the protocol.

Basically, what's commonly in your TCP sort of transport layer is now in your

quick header.

This is where it gets a little bit iffy because, yes, technically it's your application header,

but it really sort of more behaves like a transport protocol with the added complication

that it also provides encryption, which of course usually is part of the application layer.

So really an odd protocol in that sense.

The reason Quick was invented and that sort of, well, the name kind of gives it away, is to

avoid some of the performance issues that you run into with TCP, because A, TCP is a pretty

old protocol, and B, a lot of the parameters that determine TCP performance, like, for

example, how long it takes to resend the packet and the like.

Well, that's determined by the operating system,

not by the application.

With Quick, the application has more control,

...