@gaikwadbharat42
Good Explanation ❤
@dread1089
Nice, much effort done.
@pranavsingh8503
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
@shubhamchandra9258
good stuff.
@lohphat
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.
@stephenday4834
Nice, concise, and clear. Good job.
@Md.AbuBakr
thanks a lot!!! so nice reverb
@abdallahelhdad819
you did a good job explaining this, thank u :)
@Ranjeet_88
Great Video, thanks for putting i so much efforts and making it simpler
@guillaumejumel5578
Nice man ty
@hemant_pande
most consise and organised explaination I've seen on this topic
@stevenhe3462
Good explanation!
@aminaelbekkali6187
Worked , thanks a lot!
@cthutu
Hands up who had to look up the word inchoate!
@delpsiphi9
Thank you for the clear explanation!
@cthutu
@TheDataDaddi - your slide is wrong. Client-initiated streams are even, NOT odd. This is according to the RFC 9000
@user34user73
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.
@epsisayidina2989
What in OSI layer is QUIC?
@pranavsingh8503
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 ?
@ShivaShaktiOnMoon