The way you explain is quite awesome. Need more please. 1.More about packet flow of Quic 2. Re-transmit handling in Quic 3. Congestion control in Quic 4. Connection reliability in QUIC
Because QUIC is disassembled at the app layer, it's impossible for a company gateway to sense or block undesirable content be that ads, inappropriate content, or known sources of malware. QUIC now forces end-point solutions to be able to catch content elements at the app layer. This really makes IDS/IPS much more difficult.
You're right. Someone could initiate the session to a blocked website through a vpn and upon closing the vpn the website would still work because the firewall didn't see the handshake.
This is very true, but many of these things are only possible to begin with because of the weaknesses in the previous protocols. Along with other layers like DNSBL too, to an extent
Nice video! Thank you for the explanation! On the http/2 vs quic diagram you have “udp connections”. But it’s irrelevant to the udp, cause on the lower lever udp doesn’t establish connections.
Hi there. Thanks so much for the feedback. Yep. That is correct. I think I used a diagram I found for this and forgot to modify it. I appreciate the correction!
Please make a deep dive Video for QUIC . I have a query: What if first packet is lost. UDP won't re-transmit so Server will never get it and Client will keep waiting time-out and then send again ?
I will. I need to do a deep dive myself to more full understand everything. The answer to you question is a bit long these comments to instead I will point you to where I found it. If you visit RFC 9002 (quicwg.org/base-drafts/rfc9002.html) and read section 3 (Design of the QUIC Transmission Machinery). It should answer some of your questions regarding retransmission. If the first packet is lost however, my guess is there would be a time out and then another transmission or retransmission in this case. Although I am not 100% sure how it is handled.
Hi there! Thanks so much for you question. So the QUIC protocol can be used between microservices and could potentially improve network speed, the actual implementation and support by service meshes might vary. I have never specifically worked in this area so I cannot really help you much more than this. Hope this helped a bit though!
So QUIC is a bit odd in how it fits in with conventional OSI, but it looks to me like HTTP/3 is handles most things at the application layer, UDP handles some of the transport layer. Then QUIC sits in between and handles some of both layers. For a deeper dive, I'd really need to make another video. If you would like that I will take a look more deeply at the QUIC protocol and make a video on it. Just let me know.
This is true. If I said that then I misspoke. Thanks for pointing that out. If you happen to know the timestamp(s), when I said that please drop them here so I can make a comment to correct it.
Hi @wuzhai2009 I appreciate the feedback. If you could give me the timestamp in the video where that was mentioned or tell me what was not well explained I would be happy to go back and give you some more details. Please let me know what questions I can answer, and I will do my best to help!
The thumbnail states how passionate and organized your efforts and knowledge. Kudos.
The way you explain is quite awesome.
Need more please.
1.More about packet flow of Quic
2. Re-transmit handling in Quic
3. Congestion control in Quic
4. Connection reliability in QUIC
I will do my best to get to these topics at some point soon!
Nice, concise, and clear. Good job.
So glad it was helpful to you! Thanks so much for the positive feedback!
Nice, much effort done.
most consise and organised explaination I've seen on this topic
Hi there. So happy that you found the video useful!
you did a good job explaining this, thank u :)
So glad you found it helpful! Thank you for the feedback!
Because QUIC is disassembled at the app layer, it's impossible for a company gateway to sense or block undesirable content be that ads, inappropriate content, or known sources of malware.
QUIC now forces end-point solutions to be able to catch content elements at the app layer.
This really makes IDS/IPS much more difficult.
I did not even think of this implication, but you are right. I can imagine that would add significant challenges for enterprise IDS/IPS
@lohphat Thanks for highlighting, please let me know any more such understanding about the QUIC/HTTP.
You're right. Someone could initiate the session to a blocked website through a vpn and upon closing the vpn the website would still work because the firewall didn't see the handshake.
This is very true, but many of these things are only possible to begin with because of the weaknesses in the previous protocols. Along with other layers like DNSBL too, to an extent
Great Video, thanks for putting i so much efforts and making it simpler
Glad it was helpful!
Thank you for the clear explanation!
Of course! So glad you found it useful.
thanks a lot!!! so nice reverb
Worked , thanks a lot!
good stuff.
Nice video! Thank you for the explanation!
On the http/2 vs quic diagram you have “udp connections”. But it’s irrelevant to the udp, cause on the lower lever udp doesn’t establish connections.
Hi there. Thanks so much for the feedback.
Yep. That is correct. I think I used a diagram I found for this and forgot to modify it. I appreciate the correction!
Good explanation!
Hi there! I am so glad this was helpful to you!
Please make a deep dive Video for QUIC .
I have a query: What if first packet is lost. UDP won't re-transmit so Server will never get it and Client will keep waiting time-out and then send again ?
I will. I need to do a deep dive myself to more full understand everything.
The answer to you question is a bit long these comments to instead I will point you to where I found it. If you visit RFC 9002 (quicwg.org/base-drafts/rfc9002.html) and read section 3 (Design of the QUIC Transmission Machinery). It should answer some of your questions regarding retransmission.
If the first packet is lost however, my guess is there would be a time out and then another transmission or retransmission in this case. Although I am not 100% sure how it is handled.
Nice man ty
Can quic protocol be used between Microservices ?
Any Service Mesh supports QUICK protocol? If so that would make the network faster right?
Hi there! Thanks so much for you question.
So the QUIC protocol can be used between microservices and could potentially improve network speed, the actual implementation and support by service meshes might vary.
I have never specifically worked in this area so I cannot really help you much more than this. Hope this helped a bit though!
@TheDataDaddi - your slide is wrong. Client-initiated streams are even, NOT odd. This is according to the RFC 9000
Thanks for the clarification. I will update the video when I get a chance.
What in OSI layer is QUIC?
So QUIC is a bit odd in how it fits in with conventional OSI, but it looks to me like HTTP/3 is handles most things at the application layer, UDP handles some of the transport layer. Then QUIC sits in between and handles some of both layers. For a deeper dive, I'd really need to make another video. If you would like that I will take a look more deeply at the QUIC protocol and make a video on it. Just let me know.
@@TheDataDaddi Thank you for sewwt fast response. I'm just here passing by. And hey... this is a really good video.
tysm ^^
Hands up who had to look up the word inchoate!
As far as I know. AdGuard is the only that has this.
There's no such thing as UDP Connection...
This is true. If I said that then I misspoke. Thanks for pointing that out. If you happen to know the timestamp(s), when I said that please drop them here so I can make a comment to correct it.
'Server load spike' - not well explained.
Hi @wuzhai2009 I appreciate the feedback. If you could give me the timestamp in the video where that was mentioned or tell me what was not well explained I would be happy to go back and give you some more details. Please let me know what questions I can answer, and I will do my best to help!
nice #amflearningbydoing #amflearning