What is QUIC?

preview_player
Показать описание
QUIC is the Quick UDP Internet Connections protocol, developed by Google and currently in IETF workgroups for further development. It is being considered for replacing TCP as a transport protocol for HTTP/3. Join Jason in this Lightboard Lesson as he gives an overview of the protocol in light of a transition from TCP.
Рекомендации по теме
Комментарии
Автор

Nice and QUIC presentation! Please bring this guy to give whole presentation on the topic!

prasadbhokare
Автор

Thank you for the presentation. It was a very good introduction to QUIC.

horikuta
Автор

Great video! Thank you Jason! Super smart and likable guy.

Blocktelligence
Автор

Excellent presentation, as always, by the F5

stukafluka
Автор

its a great presentation related to QUIC!. new generation of protocols is comming...

alishakerinouri
Автор

Thank you! Everything I wanted to know happened in just 8 minutes. Magic! Before watching this video I tried understand that proto reading docs and it didn't work out.

bit_happens_
Автор

The shirt has the logo printed backwards right? How could he possibly write everything flipped so naturally?

jackhpeterson
Автор

I love this guy! Informative video. Thank you so much mr

overdrivegain
Автор

it is awesome video to understand how QUIC works.

이장군-ki
Автор

I enjoyed the explanation of QUIC and it sounds great. After watching the video I think that QUIC might still have its drawbacks if you are really into security (if I'm understanding it correctly). If anyone could add more to the security part I would greatly appreciate it! It sounds like the future, but as of 2021 it still might not be as secure as TCP & TLS

alexpolivka
Автор

What does it mean exactly that TCP/UDP is in kernel space and TLS/HTTP and QUIC are in userspace? And why is it that it takes longer to make changes to kernel space than user space?

amirhajimirsadeghi
Автор

1. Developed by google
2. Why does QUIC matters?
a. solves head of line blocking issue for layer 4 with application layer. With TCP+TLS we were solving only for application layer
b. TCP has 2 trips and TLS has 4 trips which makes the total as 6 trips for connection but with Quic it takes 1-2 trips per connection max. This is big deal if you have create connections for all request
c. Improved loss control and congestion feedback
d. TLS 1.3 is used with QUIC
e. Only particular stream of package is resent unlike TCP+ TLS as udp doesnot care much on order unlike TCP
f. For tcp we use ip:port for client and server however quip use conn uid. Benefit is now you can switch from mobile to wifi to wired etc but you will not lose information
g. Quic is developed by google and google owns clients like chrome with which they can do real world testing. In chrome you can enable quic in browser setting as well
3. Other Learnings
a. TCP UDP lives in kernel space so it is very hard to make any change at protocol level but since quic is in user space it is easier to make changes

shubhamgarg
Автор

with using Quic is there any risk of packet loss ?

younessmourid
Автор

So, does Big-IP fully support termination of QUIC sessions? If so, can you utilize it on the client-side, with a typical TCP/HTTP back-end connection? I'm thinking of the benefit gained by maintaining the connection UUID across changing networks more than any performance boost?

TobyGarcia
Автор

So, the two takeaways that I see are 1) QUIC is going to use a non ip:port id (Amazing!) and 2) QUIC won't suffer the head of line blocking problem occurring with TCP.

thealgorist
Автор

please allow me the very stupid question: How did you do this video? But then you have to do mirror writing? Is it done that way? Or did you mirror the video afterwards? (your shirt appeas laterally reversed, so this would be my guess.)

bosaudf
Автор

Tcp and tls use port 443. Quic us faster, because it stacks on top of udp.

truesonic
Автор

How does it sends acknowledgement especially for lost packets?

pratiknalage
Автор

What would happen if I cloned a connection UUID? Does the mean I could resume the session of another person regardless of the local device used?

Anthony-cnll
Автор

FYI: QUIC as used by the IETF is no longer an acronym.

robinmattheussen